Agree how measured quantity, unit price and product identity reach the sale for each product type. Test the proposed scale or manual entry arrangement with actual packaging and rounding requirements. The acceptance scenario should let staff explain the customer charge and stock movement without assuming that a device connection automatically establishes measurement or labelling compliance.
Understand the decision
A shopper buys a weighed item, two packaged jars and a prepared gift assortment. Different quantity conventions meet at one checkout. The review should expose how labels, product selection and price entry are controlled, especially when a cashier corrects a weight or changes a container during the sale.
Work through the requirements
- Define quantity and pricing evidence by product type
- Rehearse corrections before payment
- Compare receipt quantities with stock treatment
| Record or decision | Why it matters |
|---|---|
| Measurement reference | Explains the entered sale quantity |
| Product pricing rule | Defines the approved unit basis |
| Checkout record | Connects the mixed sale and payment |
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 infer that a connected scale or printed label satisfies every applicable requirement. The business must review the measurement and customer-information process, and the implementation test should document exactly what the proposed hardware and configuration do.
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 Specialty food 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 ↗