Separate the external catalogue’s application data from the distributor’s internal stock identity, pricing and accepted customer commitments. Define how revised mappings are reviewed and how open orders are affected. The connection should expose uncertain matches and preserve source versions so a later question can be investigated against the information available when the selection was made.
Understand the decision
A catalogue refresh changes an application note while a workshop order is already being picked. The warehouse also uses an internal barcode that the catalogue does not know. The review must connect the records without allowing an external update to silently rename physical stock or erase the earlier decision.
Work through the requirements
- Assign field authority across catalogue and ERP
- Review material mapping changes before use
- Retain the source version behind accepted selections
| Record or decision | Why it matters |
|---|---|
| Catalogue version | Identifies the external evidence set |
| Internal item mapping | Connects catalogue entries to physical stock |
| Affected-order review | Tracks consequences of changed application data |
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
Do not let an external catalogue become the unreviewed owner of your physical stock records. Application data, item identity and commercial commitments serve different purposes and require clear boundaries even when one interface displays them together.
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 ↗