Record why the product leaves normal saleable stock and apply the business’s reviewed handling and disposition rules. Treat tester allocation, customer return and damaged packaging as different events. The acceptance test should show that a refund or unused-looking package does not automatically restore availability, while the responsible staff can explain the quantity and financial adjustment.
Understand the decision
A counter opens a new tester on the same day a customer returns a similar product. Both units remain physically present but have different histories and possible outcomes. The review should make those distinctions visible without prescribing universal hygiene, resale or disposal rules for every product.
Work through the requirements
- Classify tester return and damage events
- Record identity and observed condition
- Approve disposition separately from the refund
| Record or decision | Why it matters |
|---|---|
| Tester allocation | Explains deliberate removal from selling stock |
| Return inspection | Records the customer-return evidence |
| Disposition decision | Documents the reviewed final treatment |
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 let visual appearance or refund approval determine resale suitability automatically. The business must define product-specific handling rules, and the implementation should preserve the responsible decision rather than invent a general rule for opened or returned beauty products.
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 ↗