Define which product, measurement, lot and customer-information records the business needs in the new process, then validate a representative label-to-stock relationship. Preserve reviewed product information and distinguish missing data from confirmed values. Opening quantities should reconcile in the chosen units, with held or removed-from-sale goods separated before the first live checkout.
Understand the decision
The shop’s labels use abbreviated names while purchasing records use supplier descriptions. Some goods have lot information on packaging that was never entered into the old system. The migration should expose that gap and assign a responsible review rather than inventing dates or identities from the import file.
Work through the requirements
- Map label identity to approved product records
- Review missing lot or measurement information
- Count and classify opening stock before loading
| Record or decision | Why it matters |
|---|---|
| Label product crosswalk | Connects selling labels to stock identity |
| Data-review register | Records missing or uncertain information |
| Opening quantity sheet | Separates usable held and removed stock |
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
Copying old label text does not establish that product information is current or complete. Have responsible reviewers approve the content they rely on and preserve uncertainty where historical records cannot support a reliable identity or date.
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 ↗