Separate open fulfilment obligations from historical customer records, payment evidence and archived orders. Reconcile each unfinished order’s paid, refunded, shipped and remaining quantities before cutover. Keep stable storefront references so later messages match the intended target record, and define how events occurring during the transition will be captured without duplicates.
Understand the decision
An order has one shipped line, another awaiting stock and a partial refund recorded outside the warehouse tool. Importing it as a fresh paid order would recreate work already completed. The migration plan should preserve the remaining obligation and enough history to handle customer service accurately.
Work through the requirements
- Classify open obligations and retained history
- Reconcile partial shipments and adjustments
- Plan the handling of events during cutover
| Record or decision | Why it matters |
|---|---|
| Open-order cutover register | Lists genuine remaining work |
| External reference map | Connects later storefront events |
| Financial-status bridge | Explains payments refunds and open amounts |
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 equate an order’s latest headline status with all of its line-level obligations. Partial shipments and refunds can coexist, and a migration that ignores those details may duplicate fulfilment even when its imported order count is correct.
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 Ecommerce brands 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.
Ecommerce order handling ↗Packaging ↗Import vendor pricelists ↗