Reconcile open orders by channel, fulfilment state, physical location and financial position before migration. Distinguish prepared collection goods from ordinary saleable stock and record which customer message has already been sent. Stable references should let staff complete or cancel the remaining obligation after cutover without repeating a charge, shipment or readiness notification.
Understand the decision
The store has bags awaiting pickup, the website has paid orders not yet picked and another warehouse has shipped part of one order. A single open-order export does not describe those states. The review needs a shared cutover register that connects physical goods with customer and financial obligations.
Work through the requirements
- Inventory every unfinished channel obligation
- Match prepared goods to customer references
- Rehearse completion and cancellation after import
| Record or decision | Why it matters |
|---|---|
| Open-channel register | Shows unfinished work by origin |
| Prepared-stock map | Identifies goods already set aside |
| Customer-message history | Prevents contradictory repeat notifications |
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 treat all unclosed orders as unstarted orders. The physical store may already hold customer-specific goods, and ignoring that state can generate duplicate picking, repeated notifications or an incorrect claim that previously reserved stock is available.
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 Omnichannel retail 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.
Point of Sale daily workflow and refunds ↗Ecommerce order handling ↗Packaging ↗