Rehearse a dispatch request for material with an unresolved release, including an attempted substitution and a later authorized decision. Confirm that users can identify the hold, locate available alternatives and preserve the customer obligation. The accepted process should show the exact batch and approval supporting shipment, with an auditable path through any changed decision.
Understand the decision
For a hypothetical rehearsal, a driver arrives for an order while the allocated batch awaits laboratory review. Another released batch is available in a different package size. Dispatch needs an authorized commercial and technical decision, rather than bypassing the hold or assuming that the alternate packaging is acceptable to the customer.
Work through the requirements
- Attempt the planned dispatch while release remains pending.
- Review alternative batch and packaging suitability with owners.
- Record the approved shipment and remaining customer balance.
| Record or decision | Why it matters |
|---|---|
| Dispatch request | Identify planned batch and quantity. |
| Alternative approval | Document accepted batch and package changes. |
| Shipment evidence | Connect actual output with its release decision. |
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
Urgent collection can expose weaknesses that ordinary order-entry tests miss. Rehearse with dispatch and technical owners together, and verify that the recorded shipment reflects the authorized physical material instead of a convenient substitute identifier chosen to finish the transaction.
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 ↗