Migrate open service orders with their shipment identifiers, delivery state, carrier commitments and unresolved charge reviews. Reconcile customer invoices and supplier balances separately from operational completion, using an agreed cutover boundary. Preserve evidence references so late delivery documents and carrier charges can be matched without recreating the original service order.
Understand the decision
A shipment can be delivered before cutover while its proof of delivery or carrier invoice arrives afterward. Another may be only partly fulfilled. The opening snapshot should preserve those states and explain what remains to be collected, delivered, reviewed or paid rather than relying on a single completed flag.
Work through the requirements
- Map customer and carrier shipment references.
- Identify missing delivery and charge evidence.
- Reconcile financial and operational opening positions.
| Record or decision | Why it matters |
|---|---|
| Shipment opening register | Shows execution state and remaining obligations. |
| Evidence cross-reference | Connects delivery documents to service records. |
| Charge reconciliation | Explains invoices, commitments and pending adjustments. |
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
Migrating only unpaid invoices misses delivered but unsettled work and movements still in progress. Reconcile shipment state, evidence and commitments together, and assign a responsible owner to every unmatched opening reference before switching systems.
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 Logistics service 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.
Odoo 19: sales quotations and invoicing methods ↗Odoo 19: project management ↗Odoo 19: timesheet configuration and recording ↗