Skip to content

Ship the same goods on fewer, fuller trucks.

Duvo flags purchase orders bound for the same destination, batches them into fewer, fuller loads before they reach the warehouse, and writes the plan back to SAP.

Every order

Screened for overlap

Open purchase orders are checked against the rest of the stream, not just the ones a planner has time to compare.

Before release

Batching window

Groups are proposed while the orders can still merge, before the warehouse picks and the trucks are booked.

One plan

Written to SAP

The batched loads, the orders inside them, and the reasoning land back in SAP for planning and the dock to work from.

Duvo establishes the baseline and validates the opportunity on your records before a live scope is agreed. No customer result is claimed for this solution yet.

Every overlap grouped, with the fuller load already drafted.

Each group of orders becomes a case: the destination, the overlapping orders, the load they combine into, and the trucks the batch removes.

Load Consolidation · Illustrative

Compatible purchase orders are grouped before warehouse release, with cut-offs and handling rules applied.

Adds cases
Purchase Orders
Processes cases
Load Planning
Total

24

Pending

5

Postponed

2

In progress

4

Needs input

3

Failed

0

Completed

10

Add filter
Case
Case Status
Consolidation fit
Scope
Decision
Exceptions
Next action
Group 021
Needs Input
Same destination
Berlin DC
Combine three POs
1
Review
Group 022
In Progress
Window aligned
Prague DC
Combine two POs
0
Review
Group 023
Completed
Handling conflict
Vienna DC
Keep separate
0
Closed
Group 024
Pending
Capacity open
Madrid DC
Add one PO
1
Review
Group 025
Postponed
Cut-off close
Paris DC
Review release
0
Review

Showing 5 of 24 cases

  1. 1

    Approval

    Exceptions pause for the named owner

    Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.

  2. 2

    Consolidation fit

    Consolidation fit is visible before the action

    Each group shows the common destination, shipping window, and constraint that decides whether the orders can move together.

Orders raised one by one ship one truck at a time.

Nobody plans a part-empty truck. It happens one purchase order at a time, when orders raised separately each move separately.

  • Fragmented orders ship fragmented.

    Buyers and planning systems raise purchase orders by need date and quantity, not by truck. The same lane gets several part-full shipments in the same week.

  • The consolidation window closes quietly.

    By the time anyone could see the overlap, the first order is already picked, packed, and booked. Combining loads after warehouse release is too late.

  • The dock pays for it too.

    More trucks for the same goods means more appointments, more waiting, and more congestion at the dock for the warehouse to absorb.

Orders get grouped before the warehouse picks them.

Clear overlaps are batched with the limits applied. Borderline groups reach a person with the trade-off laid out.

  1. 01Intake

    Watch the order stream.

    Open purchase orders are read from SAP and order files as they are raised, with destination, dates, quantities, and volumes attached.

  2. 02Group

    Find the overlaps.

    Orders heading to the same destination in the same delivery window are grouped, within weight, volume, and date limits.

  3. 03Build

    Build the fuller load.

    Each group becomes a proposed load: which orders combine, how full the truck runs, and which separate shipments it replaces.

  4. 04Approve

    Pause where judgement matters.

    A tight delivery date, a customer-critical order, or a batch that would push goods late routes to the planning owner before anything changes.

  5. 05Update

    Write it back to SAP.

    Approved batches update the orders and deliveries in SAP before the warehouse picks them, with the grouping and its reasoning recorded.

Planning keeps authority over every batch.

  • Approval thresholds

    Batches that touch a tight delivery date, a priority customer, or an unusual order pause for the planning owner before anything moves.

  • Grouping rationale

    Each case shows the orders combined, the window and capacity limits applied, and the separate shipments the batch replaces.

  • Adoption path

    Start with proposals only, then let Duvo batch routine overlaps once the team trusts the rules.

Review security and assurance

No planning transformation project required to start.

Duvo reads the order, transport, and warehouse systems your team already uses.

Works across

SAP purchase orders and deliveries, order and demand files, transport management system (TMS), warehouse schedules and dock calendars, truck and container capacity rules, carrier bookings, supplier and site master data, email and shared inboxes

Contracted guarantee

5x ROI, guaranteed.

If measured results fall below 5x the total proposal price, the whole contract is free.

What teams ask about Load Consolidation

  • When does Load Consolidation run?

    Purchase orders are raised for the same destination in the same window.

  • Who owns Load Consolidation?

    Transportation, logistics, supply chain, warehouse operations

  • Which systems can Duvo work across?

    Duvo reads the order, transport, and warehouse systems your team already uses. Typical sources include SAP purchase orders and deliveries, order and demand files, transport management system (TMS), warehouse schedules and dock calendars.

  • Where does a person stay in control?

    Approval thresholds: Batches that touch a tight delivery date, a priority customer, or an unusual order pause for the planning owner before anything moves.