Agree the operational and accounting state of every open shipment at the cutover point, using the business’s reviewed terms and evidence. Distinguish ordered, shipped, received and billed quantities rather than forcing all goods into one opening stock number. Preserve links between supplier obligations, transport references and any amounts already recorded in accounting.
Understand the decision
A container has departed, a supplier invoice has been recorded and the goods have not reached the warehouse. Another shipment is partly received. The migration must represent those different states consistently; ownership and accounting treatment cannot be inferred merely from a tracking page that says the shipment is moving.
Work through the requirements
- List open shipments with dated evidence
- Approve their operational and financial states
- Reconcile later receipts against the opening position
| Record or decision | Why it matters |
|---|---|
| In-transit register | Shows each shipment’s reviewed state |
| Accounting cutover bridge | Explains recorded amounts and remaining treatment |
| Receipt mapping | Connects future arrivals to opening commitments |
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 shipping status does not decide legal ownership or accounting recognition. Have responsible reviewers determine the treatment under the actual arrangement, and avoid importing every moving shipment as either ordinary stock or an entirely new purchase.
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 ↗