Supplier orders

Plan shipments around the goods that are actually ready.

Connect orders, supplier confirmations and packing lists to prepare the next departure. Your teams can review available quantities, dates and the references to retain in the shipment.

In practice

An order date is not enough to plan a departure

Your order book tells you what should be delivered. Planning the shipment needs a different view: which products are available, in what quantities and on which date? A supplier confirmation or a new packing list may change the plan. Without links to the order, teams reconcile different file versions before they know what to ship.

OneChain connects orders, readiness information and preparation documents. Procurement and transport teams can find the references needed to plan the next departure, using the data confirmed through their supplier workflow.

A practical case · Illustrative example

Wait or prepare the departure?

Two orders share a destination, but their readiness dates differ.

Order A
Available today
Order B
Available later
Review
Urgency, quantities and constraints
The decision to prepare

Choose what can leave now and keep a clear view of what remains to ship.

Plan a departure while keeping track of what remains

An order does not necessarily correspond to one shipment. Some goods may be ready before the rest, while several orders may contribute to the same departure. Keeping order lines and quantities connected to the shipment helps teams understand what has left and what still needs preparation.

Packing lists describe the goods to be shipped. Reviewing them alongside orders and confirmed dates helps the team prepare a departure with identifiable references. Partial shipments and consolidation are organized around the rules agreed for your operations.

Try it yourself · Interactive demo

Which goods are ready to leave?

Open a demonstration order and review ordered, available and allocated quantities. Find the references connecting the lines to the shipment.

Interactive OneChain demo · fictional data

Consolidate for an operational reason

The same destination does not always mean the same departure. Readiness dates, transport mode, cargo requirements and commercial urgency influence the choice. Planning a consolidation starts with those details: what can wait, what needs to leave now and which orders must stay together?

The decision needs to remain clear to both the supplier and the transport team. Identifying the selected orders, their documents and their requirements allows people to prepare the shipment without losing the purchasing context.

Find the order in the shipment follow-up

Once transport is arranged, procurement needs to understand which goods are affected by a delayed arrival. Connecting the order to the shipment avoids starting from a container number alone.

Updates and information returned to the ERP are defined through the project interfaces. Teams establish what needs to be exchanged to follow goods that are expected, in transit or still being prepared.

Prepare your implementation

Details to work through using your flows and organization.

Where do orders come from?

Orders can be brought in from your ERP or a structured file. The project defines references, required fields and how updates are handled.

Who confirms readiness?

The workflow defines the information expected from the supplier and the procurement team’s role. Confirmed dates, packing lists and available quantities inform the next step.

How do we handle a partial shipment?

Splitting and consolidation rules are defined from your actual cases. This includes the relationship between order lines, selected quantities and the resulting shipments.

Supplier orders

Review your order-to-shipment process

Start with an order, a supplier confirmation and a packing list to examine how your team prepares transport.

Discuss my needs