Confirm the model, finish, dimensions, options and approved customer document before placing the supplier commitment. Keep later revisions visible and review their impact on anything already ordered. The acceptance scenario should show how the supplier instruction, customer promise and warehouse identity remain linked when a configurable selection is not represented by a simple stock SKU.
Understand the decision
A customer chooses a sofa configuration and changes its fabric after paying a deposit. The supplier may already have accepted the original order. The review should distinguish the requested change from an approved change and make the commercial and operational consequences clear to the responsible staff.
Work through the requirements
- Approve the full selection specification
- Translate it into the supplier instruction
- Review changes against existing commitments
| Record or decision | Why it matters |
|---|---|
| Selection approval | Preserves the customer’s chosen specification |
| Supplier order reference | Connects procurement to that selection |
| Change decision | Records acceptance and consequences of revisions |
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
A deposit confirms a financial event, not necessarily a complete product specification. Do not release a special order from an incomplete description or treat a customer’s requested change as accepted before the supplier and responsible staff have reviewed it.
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 ↗