Assign responsibility for supplier references, pack information, cost changes and customer-facing descriptions before importing a catalogue feed. Protect internal barcodes and accepted special orders from uncontrolled overwrites. The test should include a discontinued item and a changed pack quantity so staff can see which updates require a commercial or operational decision.
Understand the decision
A supplier file arrives with thousands of lines, but only a few changes affect current special orders or open shelf labels. Bulk import success does not identify those consequences. The review should prioritize actionable changes and show how the store confirms that labels and counter records remain consistent.
Work through the requirements
- Classify fields by update permission
- Review changes affecting commitments or quantities
- Confirm counter and shelf information agree
| Record or decision | Why it matters |
|---|---|
| Catalogue change set | Identifies the incoming differences |
| Protected reference list | Prevents identity overwrites |
| Counter review task | Tracks label or order consequences |
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 supplier catalogue is not automatically the authority for your shelf labels or customer commitments. Keep a reviewed boundary around internal identity and selling rules so a bulk refresh does not create mistakes faster than staff can recognize them.
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 Hardware 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 ↗Packaging ↗Units of measure ↗