Define the beverage quantity, selling pack and returnable-container obligation separately before confirming the order. The customer document should make the commercial arrangement understandable, while dispatch can identify the physical load. Test a mixed order so a returned container cannot be mistaken for returned beverage or automatically reverse the original product sale.
Understand the decision
A hospitality customer orders packaged drinks and kegs while arranging collection of empty containers from an earlier delivery. The truck carries both directions of movement. The review should show how staff distinguish today’s product sale from container accountability and any separately approved financial treatment.
Work through the requirements
- Confirm product packs and container expectations
- Prepare separate outward and collection instructions
- Reconcile the customer’s resulting obligations
| Record or decision | Why it matters |
|---|---|
| Beverage order | Defines the product and selling quantity |
| Container ledger | Tracks the agreed return obligation |
| Load instruction | Distinguishes deliveries from collections |
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 container and its contents may share a delivery but not the same commercial lifecycle. Avoid collapsing them into one quantity or credit decision, especially when the empty asset returns much later than the beverage is consumed.
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 Beverage distribution 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.
Packaging ↗Lot numbers ↗Units of measure ↗