A customer hands the driver two cases back. One is unopened, one is damaged, and the office will not see either until the van returns. If the only record is “two cases returned”, the difficult questions have simply been postponed: why did they come back, what condition are they in, should the customer receive a credit, and can either case return to sellable stock?
Customer returns are easiest to control when the record is created at the visit, while the driver, customer and goods are still together. The method is not complicated. Capture the item and quantity, the reason, the condition, the commercial decision and the stock destination as separate facts.
At the door: capture four facts before the van leaves
The value of separating these facts appears later. Finance can see why a credit exists. Warehouse staff can see whether the stock is good, damaged or expired. Operations can count reasons without guessing from free text. And the customer does not have to explain the same return to three different people.
Identify
Item and quantity
Reason
Why it came back
Condition
What state it is in
Stock path
Where it should go
Commercial action
Credit where required
In the van: reason is not condition
“Damaged” is often used as both a reason and a condition, but the two questions are different. The reason explains why the customer is returning the product. The condition explains what the business can do with the physical stock.
| Return fact | Example | Why keep it separate? |
|---|---|---|
| Item and quantity | 2 cases of Product A | Sets the physical and commercial quantity. |
| Reason | Ordered in error / short-dated / damaged in transit / wrong item | Explains the cause and supports exception analysis . |
| Condition | Good / damaged / expired | Determines the stock path under your own rules. |
| Credit decision | Credit required, partial credit, no credit | Separates customer settlement from physical receipt. |
| Destination | Return to warehouse, quarantine/hold, disposal process | Stops returned stock becoming anonymous stock. |
The examples are deliberately generic. Your own reason codes, quality rules and credit policy should be more precise. The important design principle is that the driver should not have to invent a narrative that somebody later interprets differently.
Back at depot: condition decides the stock path
The physical side of the process should be just as clear. Returned goods should not become a loose crate on the van and then an unexplained adjustment at day end. Tag the return to the customer and the visit, keep its condition visible, and move it through the warehouse process that matches that condition.
This is especially important where shelf life, batch identity or damage status affects whether stock can be resold. The returns process should preserve those controls rather than reset the product to “available” simply because it is back inside the building.
A clean doorstep record still needs a depot close-out. Someone should be able to match the returned quantity unloaded from the vehicle with the return captured at the customer, then confirm the stock condition and the next physical destination. Any difference should be explained before the item becomes another stock adjustment.
That close-out is also where the commercial side can be checked. If a return requires a credit note, the office should be able to see that the physical return and the customer settlement refer to the same event. If no credit is due under the business's policy, that decision should be visible rather than inferred from the absence of a credit later.
In finance: return and credit are related, not identical
A return can create a credit note where the commercial policy requires it, but the existence of returned stock and the existence of a customer credit are not the same event. That distinction matters when goods are returned because they were supplied incorrectly, when only part of the quantity qualifies for credit, or when the customer is returning an item under a separate agreement.
Make the policy explicit enough that the driver knows what they may confirm at the door and what requires office review. If a driver is not authorised to decide the credit, capture the return cleanly and let finance or customer service make the commercial decision from the record. Do not force the driver to promise an amount that the system or policy has not yet approved.
Keep partial acceptance and reusable packaging separate
Returns become harder when the customer accepts part of a delivery and rejects the rest. The record should preserve both sides of the event: what was successfully delivered and what came back. Treating the whole stop as either delivered or returned makes stock, proof and credit harder to reconcile later.
Use the line and quantity as the anchor. If ten cases arrive and two are rejected, record eight as accepted and two as returned under the applicable process. Capture the reason and condition for the returned quantity, then keep any credit decision linked to that quantity rather than rewriting the history of the eight cases the customer kept.
The same principle applies when more than one return reason appears at a stop. One item may be damaged, another may have been ordered in error, and empty returnable trays may be coming back on the same visit. They can share a van journey without sharing one accounting or stock treatment. The visit record should be able to explain each movement independently.
Crates, trays, cylinders and other returnable packaging can look like customer returns because they travel back on the van. Commercially they are often a different problem: the business needs a deposit or asset balance, not a product credit. Keep that flow separate so product-return reporting is not distorted by packaging movements.
The same principle applies to service equipment placed at customer sites. An asset coming back because the placement ended is not the same event as a customer returning saleable goods. Give each process its own record and reconciliation.
RouteMagic records the return at the visit
RouteMagic’s Driver App supports returns as part of the site visit. Returns are captured against the customer visit, routed to the appropriate stock condition, and can be linked to a credit note where required. The product also supports stock condition changes such as good, damaged and expired.
Because the return sits inside the same order and delivery operation, the office does not have to start from a handwritten note when the van gets back. The physical receipt still needs to be checked, and the commercial policy still decides whether a credit is due, but the visit record preserves who returned what and where the process started.
Deposit Items are a separate capability for returnable packaging on a deposit ledger. That distinction is worth keeping in the implementation: product returns should answer the sale/credit/condition questions, while reusable packaging should answer the customer-balance question.
Conclusion
A good returns process captures the facts while they are easiest to know. At the customer, record the item and quantity, why it is coming back, its condition and the commercial action that is permitted. At the depot, reconcile the physical receipt against that visit record before the stock is made available or adjusted. Keep credit policy separate from stock condition, and keep returnable packaging separate from saleable-product returns. Once those distinctions are clear, returns stop arriving at the office as a pile of goods plus a story. They become a traceable operational event that finance, warehouse and customer service can all work from. Start by taking a week of recent returns and checking whether each one can answer the same five questions without calling the driver or customer again.
