Define which external events are informational and which require an internal confirmation before changing an operational record. Use stable shipment references and preserve event timestamps. The integration should handle delayed or corrected messages without turning an estimated arrival, customs event or carrier delivery scan into an unreviewed inventory receipt.
Understand the decision
A forwarder sends several milestone updates, including a revised arrival estimate and a delivered status that refers to a terminal rather than the company warehouse. The review should map the meaning of each event and identify who confirms actual receipt and resolves inconsistent shipment references.
Work through the requirements
- Classify the meaning of each forwarder event
- Keep estimates separate from confirmed receipt
- Review late and contradictory messages
| Record or decision | Why it matters |
|---|---|
| Event mapping | Explains each external status |
| Shipment reference crosswalk | Joins forwarder and internal identities |
| Receipt confirmation | Records the company’s actual receiving 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
Words such as delivered or released may mean different things in different systems. Document the event semantics before integration, and do not allow a convenient status mapping to create inventory that receiving staff have never verified.
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 ↗