Build a controlled mapping between the internal item, supplier reference and customer purchasing reference. Preserve meaningful differences in specification, unit and revision rather than merging records by description. A trial migration should let staff find the intended item from each known reference and flag an ambiguous match before any live order is accepted.
Understand the decision
The old catalogue contains abbreviated descriptions and separate spreadsheets for key accounts. Two suppliers use the same short code for different products, while one customer changes its own identifier. This is a master-data decision requiring purchasing knowledge, not merely a spreadsheet cleanup based on matching text.
Work through the requirements
- Catalogue references with their owning organization
- Resolve ambiguous matches with purchasing staff
- Test lookup from real customer requests
| Record or decision | Why it matters |
|---|---|
| Internal item identity | Anchors the approved product record |
| Reference crosswalk | Keeps customer and vendor codes distinct |
| Merge decision register | Explains preserved and retired duplicates |
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
Automatic deduplication by description can remove the very distinction a buyer depends on. Keep a reviewed exception queue for uncertain references and do not turn unresolved catalogue ambiguity into a supposedly clean master file.
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 Industrial supplies 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 ↗Units of measure ↗Lot numbers ↗