The decision to keep clear

Approve a specific version of the plan with its order list and readiness evidence. Do not approve a changing total on a screen.

The decision is whether this version can proceed

A planner combines several purchase orders into a shipment. The total seems to fit the planning limit, so transport is provisionally arranged. Later, a packing list is missing, carton quantities change or another order is added. The vehicle arrangement and the shipment details now describe different versions of the work.

Keep a single plan reference with the selected order references, packing basis, carton totals, volume totals, document status, reviewer and version. The operational decision is not merely whether there is spare space. It is whether this exact selection is sufficiently defined for the next authorised step.

The workflow below is a coordination proposal, not a universal customs checklist or loading specification. Your forwarder, carrier and responsible operations team need to confirm the requirements for the particular goods, route and service.

Check the basis behind the volume

Cubic metres describe volume. For identical rectangular packages measured in metres, multiply length by width by height and then by quantity. If measurements are in centimetres, convert the resulting cubic centimetres to cubic metres by dividing by 1,000,000. Mixed packages should be calculated as separate groups before adding their volumes.

Record whether figures describe packed cartons or loose goods, and whether pallet or other packaging dimensions are included. Do not multiply a total batch volume by quantity a second time. Gross weight, stackability, load distribution, access and physical arrangement are separate considerations: a volume total is not proof that a vehicle can safely or physically carry the selection.

DHL's freight FAQ distinguishes shipment volume from chargeable weight, which can depend on gross or volumetric weight and the transport mode. Do not turn the CBM total in an internal demo into a freight price or a promise of capacity.

Source: DHL Global Forwarding: Freight shipping FAQs

From carton dimensions to CBM: a separate calculation

StepCalculationResult
Group A carton60 × 40 × 50 cm ÷ 1,000,0000.12 m³ per carton
Group A total0.12 × 120 cartons14.4 m³
Group B carton50 × 40 × 30 cm ÷ 1,000,0000.06 m³ per carton
Group B total0.06 × 80 cartons4.8 m³
Combined carton volume14.4 + 4.819.2 m³
Group A repacked at 65 × 40 × 50 cm0.13 × 120 + 4.820.4 m³ after revision

These dimensions form a separate fictional exercise; they are not the dimensions behind the PO totals in the next table. They describe packed cartons only, excluding additional pallets, clearances and a physical loading arrangement.

Repacking adds 1.2 m³ without changing carton count. Give the revised packing list a version, recalculate the affected group, and ask the plan reviewer to check the changed facts. Approval based on 19.2 m³ must not silently become approval of 20.4 m³.

A worked example with two independent blockers

Fictional orderCartons / volumeReadiness
PO-01120 cartons / 12.4 m³Example document set complete
PO-0280 cartons / 9.6 m³Packing list not confirmed
PO-0360 cartons / 8.0 m³Invoice not confirmed
PO-01 + PO-02200 cartons / 22.0 m³Within the example limit; document gap remains
All three260 cartons / 30.0 m³Over the example limit; document gaps remain

The demo uses an illustrative 28 m³ planning limit. Selecting the first two orders gives 22 m³, but the plan should not pass the demonstration's review while PO-02's packing-list status is unresolved. Selecting all three gives 30 m³; confirming the documents would not remove that separate volume blocker.

The correct response is to resolve each issue explicitly. Confirm or correct the document status with the owner. Change the order selection or obtain a separately assessed transport arrangement where necessary. Never hide a blocker by raising a capacity number just to make a status turn green.

Give every document gap a next action

A label saying missing is useful only when someone owns the follow-up. Record the expected document type, related order, responsible person, current revision and required review time. Distinguish a file received from a file checked: the attachment may exist but describe an earlier carton quantity.

Use an explicit not-required state only where the responsible reviewer has established that it does not apply. Do not automatically require every document for every movement, and do not let users mark a missing file as complete merely to continue. The sample's two document labels are illustrative, not a statement of all shipping obligations.

Lock the approved version, not future decisions

Approval should record who reviewed which version, when, and against which selected orders and totals. Once approved, prevent silent changes to quantities or the order list. If new information arrives, reopen under a visible revision or create a successor plan and review the changed facts again.

A plan lock protects the meaning of an approval. It is not a ban on correcting mistakes. Keep the earlier approved version available to explain what transport and warehouse teams were originally told. In the public demonstration, reset starts a new fictional exercise; it is not an implementation of production audit history.

Acceptance tests before connecting transport

Start by stabilising the handoff between order selection and review. This article covers that planning decision, not delivery proof, failed-delivery recovery or customer tracking. Each of those downstream workflows needs its own ownership and acceptance criteria.

  1. Add and remove one order and verify that cartons, CBM and document gaps all update together.
  2. Try approving with no orders, an unresolved document and an over-limit selection; each must fail distinctly.
  3. Approve a complete plan, then try changing the selection without reopening it.
  4. Revise a packing quantity and verify that the previous approval does not silently cover the new version.
  5. Keep transport availability separate: an approved planning record is not proof that a vehicle or loading slot is booked.

Try the decision with fictional records

The demonstration runs independently. It does not connect to customer data, real dispatches, payments or the original project backends.

Open the matching demoExplore the full workflow