Capture the requested part, the information used to select it and the person or source responsible for the fitment decision. Keep approved alternatives distinguishable from the original request. The handoff test should show that picking follows the accepted item while customer service can explain why that reference was supplied if the workshop later challenges it.
Understand the decision
A workshop describes a vehicle and requests a component using an old number. A catalogue suggests a replacement, but the application details are incomplete. The review should make that uncertainty visible before the order is released rather than allowing a part-number match to imply confirmed compatibility.
Work through the requirements
- Capture the relevant fitment evidence
- Obtain approval for any alternative reference
- Preserve the decision through delivery
| Record or decision | Why it matters |
|---|---|
| Fitment decision reference | Identifies the evidence used |
| Requested part record | Preserves the customer’s original requirement |
| Accepted alternative | Records the approved supplied reference |
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
A part-number cross-reference does not prove fitment for every application. Keep compatibility decisions with the designated source or responsible staff, and do not advertise catalogue integration as automatic verification of vehicle suitability or repair safety.
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 ↗