Keep the affected batch unavailable under the agreed control while the authorized specialist decides its disposition. Preserve measured results, the approved decision and any resulting rework or transfer records. The planning view should show the customer and capacity consequences, without treating a proposed corrective action as proof that the batch has become acceptable for shipment.
Understand the decision
In a sample operation, laboratory results leave a bulk batch outside its approved specification. Production wants to free the vessel for another order, while customer service asks for a delivery update. The team needs a controlled decision path that separates physical movement, technical disposition and the final release of any resulting output.
Work through the requirements
- Record results against the affected batch identity.
- Assign disposition to the authorized technical owner.
- Replan capacity and commitments using the approved status.
| Record or decision | Why it matters |
|---|---|
| Laboratory result | Preserve measurement and specification reference. |
| Disposition authorization | State the approved handling decision. |
| Batch movement | Track any resulting transfer or rework relationship. |
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
Moving material to free equipment does not resolve its technical status. Keep location, disposition and release as distinct information, and ensure operators act on approved instructions rather than interpreting a planning priority as permission to use held output.
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 Chemical blending 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 ↗