Record the rejected quantity, lot, reason and physical location before deciding whether goods may re-enter any saleable stock. Keep the customer credit and disposition approvals separate. Test a partial rejection so accepted goods, returned goods and quantities awaiting investigation remain distinguishable through the warehouse records and the customer’s financial adjustment.
Understand the decision
A receiver accepts most cases but rejects several after inspecting their condition. The truck returns with a mixture of rejected goods and unrelated undelivered stock. The process needs enough evidence to avoid treating every returning case as the same type of inventory or issuing an unsupported full credit.
Work through the requirements
- Capture receiver evidence by lot and quantity
- Separate held returns from other truck stock
- Approve disposition and customer adjustment
| Record or decision | Why it matters |
|---|---|
| Delivery rejection | Records accepted and rejected quantities |
| Held-stock record | Identifies location lot and condition |
| Credit approval | Explains the commercial resolution |
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 driver’s return quantity does not explain its condition or commercial outcome. Require reason and identity evidence before changing availability, and leave safety or suitability decisions with the designated responsible people rather than an automatic credit workflow.
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 Food 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.
Lot numbers ↗Expiration dates ↗Packaging ↗