Preserve the relationship between product family, shade, size and physical identifier, adding lot or date information where the reviewed operation requires it. Separate testers and held returns from opening saleable quantities. Validate a representative shelf sample so similar packaging or renamed ranges do not merge distinct stock or erase useful historical references.
Understand the decision
A supplier renames a range while the retailer still holds earlier packaging. The old export contains abbreviated shade names and a separate tester spreadsheet. Migration should make the correspondence explicit and keep uncertain matches under review instead of using the newest marketing description as the sole identity.
Work through the requirements
- Map old and current product references
- Verify variants against physical samples
- Reconcile testers held goods and saleable stock
| Record or decision | Why it matters |
|---|---|
| Variant crosswalk | Connects shade size and physical codes |
| Restricted-stock register | Separates testers and held returns |
| Opening quantity review | Explains the approved stock position |
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 current marketing catalogue does not describe every unit still held by the store. Preserve meaningful older references and reviewed stock states so migration does not turn testers into available goods or make a historical customer return impossible to identify.
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 Beauty 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 ↗Lot numbers ↗Expiration dates ↗