Some product will always come back on the truck. A case gets crushed, the wrong item gets picked, the lettuce does not pass the chef's inspection, or the kitchen ordered too much. The refusal itself is not the problem. The problem is what happens next: a vague note on the manifest, product dropped in a corner of the return dock, and a credit worked out days later from memory.
A return handled at the door goes differently. The driver records what came back and why, the warehouse knows what to expect, and the office reviews a credit that already has its facts attached.
What the driver records at the stop
- Mark the line, not the stop. Record the delivered count on each affected line. Two refused cases out of ten is a partial delivery, not a failed stop.
- Pick a reason from a fixed list. Free text is hard to report on. Keep the list short and clear (see below).
- Take a photo. The damaged case, the wrong label, the product the customer is rejecting. One clear photo can save a long phone call.
- Get the receiver's signature and name. The signature covers what was delivered, and the record shows what was refused.
- Load the returned product separately. Keep it apart from product for later stops so nothing refused gets delivered to the next customer by mistake.
That record is part of the stop's proof of delivery. It should take the driver a short time at the door, not a phone call to the office.
A reason list that someone owns
Reason codes are only useful if each one points to who fixes it.
| Reason | Usually points to |
|---|---|
| Wrong item or wrong quantity picked | Warehouse picking |
| Damaged in transit | Loading or handling on the route |
| Quality (ripeness, appearance, short dating) | Purchasing, receiving or stock rotation |
| Temperature concern | The truck, the load or the stop sequence |
| Ordered by mistake or no longer needed | Sales and order entry |
| Not on the order | Order entry or picking |
Keep the list to a handful of reasons. When the list is long, drivers pick whatever is at the top.
Back at the warehouse
Returned product needs its own check-in, not a corner of the dock.
- Count it against the driver's record. Differences are found today, not at the next inventory count.
- Inspect before restocking. Product that was out of temperature control, damaged or past its date should not go back into sellable stock without a decision from someone responsible for quality. Hold it in quarantine until that decision is made.
- Decide what happens to it. Restock, return to the supplier, donate where that is allowed and safe, or dispose of it. Record the decision so inventory and cost stay right.
- Keep the lot. If the product carries a lot code, the return should keep it, so lot tracking still holds if the case goes back on the shelf.
The credit
With a driver record in hand, the credit memo can be drafted from it: customer, invoice, lines, quantities, reasons and photos. A reviewer then approves it, adjusts it or asks a question. Set clear rules for who can approve what. For example, a credit for a picking error that a photo clearly shows might need only a supervisor, while a large credit, or one where no product came back, needs a manager.
Do not let drivers negotiate credits at the door. The driver records the facts; the office decides the credit. That keeps drivers out of arguments and keeps credits consistent from one customer to the next.
Speed matters to the customer too. A credit that arrives soon after the delivery, referencing what they refused and why, shows that someone was paying attention. A credit that arrives weeks later as an unexplained lump sum invites a second dispute.
Compare that with handling returns from memory
Without a record at the door, the usual path looks like this:
- The truck comes back in the afternoon with refused product.
- Receiving writes a rough note.
- The next day, someone tries to work out what happened.
- They call the customer, and the sales rep gets involved.
- Eventually a credit goes out with a vague reason.
By then, details are lost, the customer is annoyed, and the returns data is too vague to learn from.
What the returns data tells you
Once every return carries a reason, a few simple reports answer useful questions:
- By item: which products come back most, and why. That is a conversation with the supplier, about the spec, or about rotation.
- By customer: which accounts refuse most. Sometimes it is a quality issue; sometimes a customer is using refusals to manage their own stock.
- By route or driver: where damage and temperature issues cluster.
- By picker: where picking errors come from, so training goes to the right place.
For more on keeping credits honest, see credit-memo discipline and driver-assisted returns.
Where APFoodz fits
The APFoodz driver app records partial deliveries and returns at the door alongside signatures and photos. Each return carries a reason through returns and credit memos, and inventory can hold returned product in quarantine until someone decides what happens to it.