Rehearse a changeover from the previous product through setup, first accepted output and normal production. Confirm that material identity, tool configuration and inspection decisions follow the new run. Include failed startup parts and a delayed approval so production completion cannot obscure whether the resulting stock is actually ready for dispatch.
Understand the decision
For a hypothetical test, the prior run used a dark colour and startup parts for the new product show contamination. Operators discard the affected pieces, adjust the setup and submit another sample. The team must distinguish setup loss from accepted production and preserve the evidence supporting the release decision.
Work through the requirements
- Record the new material and tooling setup.
- Capture startup rejects and sample review.
- Release only the output covered by the approval.
| Record or decision | Why it matters |
|---|---|
| Changeover record | Identify the new run configuration. |
| Startup inspection | Document samples and rejection reasons. |
| Output reconciliation | Separate setup loss from accepted parts. |
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 successful machine restart is not the same as an accepted production run. The rehearsal should involve the people authorized to approve product quality and show dispatch a usable status without requiring informal interpretation of operator notes.
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 Plastics 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: quality control points ↗Odoo 19: lot numbers ↗