Create a responsibility map for design, material supply, substitutions, inspection and additional purchasing before releasing the order. Connect it to the approved specification and commercial scope. The handoff should show which obligations belong to the customer and which belong to the manufacturer, so an urgent gap does not become an unapproved purchase or undocumented scope expansion.
Understand the decision
A hypothetical customer supplies a critical component and expects the manufacturer to source the remaining materials. The supplied quantity arrives short, while the quote is unclear about replacement purchasing and repeat testing. The planner needs an authorized decision path before spending money or changing the agreed build sequence to protect the delivery date.
Work through the requirements
- Assign supply and approval responsibility by requirement.
- Confirm the accepted build and inspection scope.
- Define authorization for shortages and additional work.
| Record or decision | Why it matters |
|---|---|
| Responsibility map | Identify customer and manufacturer obligations. |
| Scope baseline | Preserve approved work and exclusions. |
| Change authorization | Record accepted additions and their basis. |
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
Informal agreement to keep production moving can create a later dispute about cost or responsibility. Make the decision easy to record at the point of change, with enough detail to explain what was authorized and by whom.
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 Contract manufacturing 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: lot numbers ↗Odoo 19: quality control points ↗Odoo 19: vendor pricelists ↗