Assign responsibility for product identity, price, measurement settings and label content before connecting retail devices. Define how approved changes reach each device and how stale data is detected. The interface test should include a product update that fails on one device, ensuring staff can identify the mismatch before relying on the printed or displayed result.
Understand the decision
A price changes in the central catalogue but one counter scale retains yesterday’s setting. A label printer also uses its own product template. The review should map those dependencies and the approval process, rather than treating all device output as a faithful reflection of the latest ERP record.
Work through the requirements
- Identify the owner of each shared field
- Control approved device updates and versions
- Test stale and missing product data
| Record or decision | Why it matters |
|---|---|
| Device data map | Defines fields shared with each device |
| Approved label version | Identifies the reviewed output content |
| Update exception log | Shows devices that missed a change |
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 device being online does not prove it holds current product information. Require evidence of update completion and version consistency, and keep responsibility for measurement and food-information requirements distinct from the technical success of a data transfer.
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 ↗