Freeze the quoted board revision and identify which component alternatives are already approved, conditional or unreviewed. Record customer-supplied material and testing obligations separately. The production handoff should make availability assumptions visible so purchasing cannot silently replace an engineering decision with a cheaper or faster component that merely resembles the requested item.
Understand the decision
A hypothetical customer requests a repeat controller board but sends an updated parts list after the price is agreed. One component now has a different tolerance and another has two proposed alternatives. The assembler needs an explicit decision about the manufacturing revision and the commercial effect of those changes.
Work through the requirements
- Identify the approved board and parts-list revision.
- Classify alternatives by approval state.
- Resolve changed material and test obligations before release.
| Record or decision | Why it matters |
|---|---|
| Quoted configuration | Preserve the revision used for pricing. |
| Alternative approval | Identify acceptable replacement components. |
| Release package | State the approved build and test requirements. |
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 supplier cross-reference is not automatically an engineering approval. Preserve who accepted an alternative and for which build, especially when similar part numbers differ in tolerance, package, firmware compatibility or customer-specific acceptance requirements stated in the project.
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 Electronics assembly 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.
Odoo 19: manufacturing product configuration ↗Odoo 19: multilevel bills of materials ↗Odoo 19: lot numbers ↗Odoo 19: quality control points ↗