Record the operational exception and supporting evidence before deciding its effect on customer or carrier charges. Separate waiting time, failed attendance, changed instructions and other additional services according to the actual agreements. Preserve the original commitment and the reviewed adjustment so finance can explain the variance without treating every carrier invoice line as automatically recoverable.
Understand the decision
A vehicle may arrive within the agreed window but cannot access the site, or delivery may be split after the customer changes instructions. The customer and subcontractor can have different commercial terms. The workflow needs to retain those differences while the responsible coordinator resolves the remaining service obligation.
Work through the requirements
- Classify the exception and remaining service.
- Preserve supporting operational evidence.
- Review customer and carrier adjustments separately.
| Record or decision | Why it matters |
|---|---|
| Exception evidence | Explains the event and its documented cause. |
| Charge review | Separates proposed and accepted commercial adjustments. |
| Remaining service | Keeps unfinished delivery work assigned. |
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
Passing every subcontract charge directly to the customer can conflict with the accepted service terms. Preserve the operational evidence and both agreements, then record the responsible commercial decision before treating the difference as approved revenue.
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 Logistics service businesses 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: sales quotations and invoicing methods ↗Odoo 19: project management ↗Odoo 19: timesheet configuration and recording ↗