Agree each product’s inventory basis, purchasing pack and selling quantity before loading opening stock. Preserve product-specific conversions and verify them with a real package and a counter transaction. The migration should flag ambiguous bulk records rather than infer a universal pack size from the supplier name or an abbreviated description.
Understand the decision
The legacy system records a box in purchasing, individual units in sales and a handwritten bin count in the aisle. Some boxes contain different quantities despite similar labels. The review should establish a conversion staff can explain and then reconcile both stock quantity and the associated opening value.
Work through the requirements
- Collect actual pack and selling-unit evidence
- Approve conversions at product level
- Reconcile trial stock with a physical count
| Record or decision | Why it matters |
|---|---|
| Pack conversion record | Defines the approved quantity relationship |
| Bin count sheet | Supplies the physical opening baseline |
| Import exception log | Tracks unclear bulk records |
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
Rounding a bin count to whole boxes can hide material quantity differences. Keep the inventory basis useful for the smallest quantity the business actually handles, and validate the proposed configuration instead of forcing the operation into a convenient spreadsheet unit.
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 ↗