Carry the accepted variant identity from the customer selection into picking, customer communication and the final sale record. Keep a style-level description separate from the physical variant barcode. The acceptance test should include an unavailable size and an approved alternative so staff cannot substitute a similar garment merely because the parent style is in stock.
Understand the decision
A customer chooses one colour online while a store colleague sees several sizes under the same style name. The stock count is positive at style level but not for the requested variant. The review should make the precise selection and any customer-approved change unambiguous at every handoff.
Work through the requirements
- Confirm the selected variant and barcode
- Resolve unavailable sizes with customer approval
- Verify the picked item against the accepted selection
| Record or decision | Why it matters |
|---|---|
| Variant selection | Records the exact size and colour |
| Physical barcode map | Identifies the garment handled by staff |
| Substitution approval | Explains any accepted alternative |
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 style-level quantity is not a promise of every size and colour. Avoid availability or substitution rules that hide variant shortages, and do not let a familiar product image substitute for checking the actual physical identifier.
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 Fashion 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 ↗Import vendor pricelists ↗