Preserve manufacturer identity, internal references and contractor-specific codes as distinct information. Review superseded items and accepted alternatives before importing project commitments. Sample the migrated catalogue using real contractor requests, then reconcile open releases so a familiar code cannot direct a picker toward the wrong revision, pack quantity or manufacturer.
Understand the decision
A legacy item description omits the finish or rating that distinguishes two products. Historical project quotes use the abbreviated code, while the supplier now sells a replacement reference. Migration needs decisions about old commitments and future purchasing rather than a global replacement of every occurrence.
Work through the requirements
- Map references with manufacturer context
- Review supersessions against open project lines
- Verify lookup and picking after import
| Record or decision | Why it matters |
|---|---|
| Manufacturer crosswalk | Retains the original product identity |
| Supersession register | Records approved future replacements |
| Open release file | Preserves outstanding contractor commitments |
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
Replacing obsolete codes everywhere can alter the evidence for an already accepted project. Preserve historical meaning while recording future purchasing choices, and ask the project owner to approve any substitution affecting a live commitment.
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 Electrical 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.
Units of measure ↗Import vendor pricelists ↗Packaging ↗