Test picking and dispatch against the required project stage, including a shortage and a site-requested delivery change. Confirm actual product, quantity and destination references on the shipment. Remaining commitments should stay visible, and proof of delivery or a reported discrepancy should reconcile to what was physically dispatched rather than merely what the order originally requested.
Understand the decision
For a sample rehearsal, a contractor advances one delivery area and postpones another after site access changes. One pack is short during loading. The dispatch team must produce a revised shipment, identify the undelivered balance and later record that the receiving crew reported a damaged item on arrival.
Work through the requirements
- Replan delivery stages against the approved site request.
- Confirm actual loaded quantities and project references.
- Reconcile receipt discrepancies and remaining obligations.
| Record or decision | Why it matters |
|---|---|
| Stage plan | Identify delivery area and required quantities. |
| Dispatch record | Show what was actually loaded. |
| Delivery exception | Record damage or short receipt and ownership. |
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
Closing the order when a truck departs can hide undelivered or disputed quantities. Acceptance should follow the physical shipment through customer receipt and show who resolves the gap between the requested, dispatched and accepted project material.
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 Building products 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 ↗