Rehearse a purchase with split arrivals, a receipt discrepancy and a later transport charge. Require purchasing, receiving and finance to explain the same shipment using their normal roles. Acceptance should cover outstanding quantities, document links and approved cost treatment, with explicit ownership of unresolved customs, supplier or accounting questions outside the demonstrated scope.
Understand the decision
A clean receipt on the same day as every invoice hides the timing differences that make importing difficult. The test should deliberately separate the events and include an amended charge. This exposes whether staff can maintain a useful operating view while waiting for complete financial evidence.
Work through the requirements
- Stage purchase receipt and charge events separately
- Reconcile quantities before reviewing final costs
- Approve handover and unresolved dependencies
| Record or decision | Why it matters |
|---|---|
| Shipment rehearsal file | Contains the ordered event sequence |
| Quantity reconciliation | Explains receipts and supplier remainder |
| Cost review worksheet | Records finance-approved allocation decisions |
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
Do not accept a single same-day transaction as proof that import operations are ready. The important evidence is how the process handles incomplete and revised documents over time, with clear ownership rather than forced finality.
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 ↗