Keep the requested part and proposed substitute distinguishable until the customer or designated technical owner approves the change. Record the relevant specification, quantity and commercial effect. The test should show that warehouse picking follows the accepted substitute while purchasing and the customer document retain an understandable trail back to the original request.
Understand the decision
A maintenance team requests a bearing that is unavailable, and a supplier offers another reference with a similar description. The order desk needs a decision quickly. The software evaluation should make the approval evidence accessible without implying that a product cross-reference can determine technical compatibility by itself.
Work through the requirements
- Capture the requested specification and reference
- Obtain a documented substitution decision
- Release only the approved picking instruction
| Record or decision | Why it matters |
|---|---|
| Customer part reference | Preserves the original request |
| Substitution decision | Records authorized acceptance |
| Supplier specification | Supports the technical review |
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
An alternative-product list is a convenience, not engineering approval. Do not let descriptive similarity, a vendor suggestion or a previous customer’s acceptance silently authorize a substitution for a different installation or operating condition.
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 ↗