Preserve historical part references and map approved future purchasing choices without rewriting every old transaction. Review whether a supersession changes packaging, application or supplier terms. The migration test should show that staff can find past demand under the old number while the proposed new order follows the current reviewed selection rule.
Understand the decision
A fast-moving reference has been replaced more than once, and old exports contain several aliases. Some stock still carries the earlier label. Migration must distinguish a search alias, a purchasing replacement and a genuinely different item so quantities and history remain understandable after cutover.
Work through the requirements
- Classify aliases and genuine product changes
- Map supersessions with effective decision evidence
- Test historical lookup and new ordering separately
| Record or decision | Why it matters |
|---|---|
| Part reference chain | Preserves original and later identities |
| Supersession approval | Explains the future selection rule |
| Opening stock crosswalk | Connects physical labels to target 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
Blindly replacing retired numbers can distort history and hide incompatible stock. Treat supersession as a reviewed relationship, not a global text replacement, and preserve the evidence needed to explain which item was actually sold or held.
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 Automotive parts distribution 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.
Import vendor pricelists ↗Serial numbers ↗Units of measure ↗