Preserve the supplier order while recording each planned and actual shipment as a distinct operational event. Confirm the quantity, document references and ownership of any remainder before treating the purchase as complete. The test should show how a split arrival affects receiving, customer promises and finance without recreating the full supplier order for every shipment.
Understand the decision
A supplier dispatches one purchase in two containers, and one arrives with fewer cartons than expected. The purchasing team sees the original order while the warehouse sees only the current arrival. The review should make the outstanding quantity and supporting shipment evidence available to both teams.
Work through the requirements
- Map shipment references to purchase lines
- Record each arrival’s actual quantity
- Review the remaining supplier obligation
| Record or decision | Why it matters |
|---|---|
| Purchase commitment | Defines the ordered goods |
| Shipment allocation | Connects quantities to transport references |
| Receipt discrepancy | Records shortages and unresolved evidence |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
A transport milestone is not a warehouse receipt or supplier settlement. Keep the events distinguishable so arrival messages cannot make missing goods appear on hand or cause an unfinished purchase commitment to disappear from the operating view.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Import and export businesses in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Landed costs ↗Import vendor pricelists ↗Packaging ↗