Reconcile each customer balance with the approved selection, delivered components and genuine outstanding supplier commitment before migration. Preserve the source references for deposits, credits and changes. Finance should approve the accounting representation while the order team verifies exactly what the customer is still expecting, including any unresolved delivery or specification decision.
Understand the decision
A customer has paid in several instalments and received one piece from a larger order. The supplier changed its reference and the showroom recorded a later finish amendment. Migration must bring those threads together without making the remaining order look newly unpaid or duplicating goods already delivered.
Work through the requirements
- Build a customer-by-order opening bridge
- Reconcile delivery and supplier remainders
- Approve financial and operational opening states
| Record or decision | Why it matters |
|---|---|
| Customer payment bridge | Explains deposits and adjustments |
| Undelivered selection register | Records the remaining approved items |
| Supplier backlog map | Connects outstanding procurement |
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
Matching total deposits does not prove that each customer’s order is correct. Review the individual relationship between money, specification and remaining goods, because a balanced aggregate can still leave a household expecting furniture the new system does not show.
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 Furniture 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.
Import vendor pricelists ↗Ecommerce order handling ↗Packaging ↗