A customer refuses a case at the door. The driver puts it back on the truck, it ends up on the dock floor, and a few days later someone in the office tries to work out what happened. By then nobody remembers the details, the product may no longer be sellable, and the customer is still waiting for a credit they were told was coming.

A driver-assisted return fixes the first step. The driver records the return at the stop, with the facts, while the customer is standing there. The office still decides the credit, but it decides from a complete record instead of a guess.

What the driver records at the stop

  1. The line being returned and the quantity, taken from the delivery on screen or on paper, not from memory.
  2. A reason from a short, fixed list: wrong item, damaged, short-dated or expired, temperature, quality, not ordered, or customer changed their mind. Keep the list short enough that drivers pick the right reason instead of the first one.
  3. A photo of the product and its label, showing the damage or the date when that is the reason.
  4. A short note in the customer's words, when the reason needs explaining.
  5. The customer's signature on the delivery record, showing what was delivered and what came back.

This is the same record as the proof of delivery, with the returned lines marked. Keeping both in one record means nobody has to match two pieces of paper later.

What the driver should not decide

Drivers should record, not approve. A driver who can promise a full credit at the door is under pressure to say yes to everything, and different drivers will say yes to different things. A clear rule helps everyone: the driver records the return and tells the customer the office will confirm the credit. The office then applies one credit policy the same way for every customer.

The exception is a clear-cut case your policy already covers, such as an item that was never on the order. Decide those cases in advance, write them down, and train drivers on them.

Back at the warehouse

  • Returned product goes to a marked returns area, never straight back on the shelf.
  • Someone checks each return against the driver's record and decides: back to stock, back to the supplier, or dispose.
  • Chilled and frozen returns are checked for temperature and time out of the cold chain before anything goes back into sellable stock. When in doubt, do not restock it.
  • The decision and the quantity go into the stock record the same day, so inventory stays right.

The article on returns at the dock covers the receiving side in more detail.

Turning it into a credit

With the driver's record in hand, the office can issue the credit memo quickly, often the same day. The credit should name the lines and the reason, so the customer can see their complaint was heard and accounts receivable can match the credit to the right invoice. A customer who disputes an invoice weeks later can be shown the photo and the signature.

For guidance on when to credit in full, when to credit part, and when to push back, see credit-memo discipline.

What the return data tells you

Once every return carries a reason, you can report on it. Each month, look at returns:

  • By item. Repeated damage or quality returns on one item may point to a supplier or packaging problem worth raising with the supplier.
  • By reason. Many "wrong item" returns point to order entry or picking, not the driver.
  • By customer. A customer with many returns may have a real problem worth a visit, or a habit of ordering more than they need.
  • By route and driver. Damage concentrated on one route may be a loading or handling issue.

To compare one month with the next, turn returns into a rate: returned lines divided by delivered lines for the period. A hypothetical example with round numbers: 50 returned lines out of 10,000 delivered is 0.5%. Track your own rate month to month and by reason, rather than against someone else's.

How to start

  1. Write the reason list and the rules for what drivers may and may not promise.
  2. Train drivers on the five steps, using real examples from recent returns.
  3. Set up the returns area and a daily check of what came back.
  4. Review the first month of returns with the drivers. Their notes on why customers refused product are useful for sales and the warehouse too.

How APFoodz handles it

The APFoodz driver app records deliveries and returns at the door, and each return carries a reason and can require approval (returns and credit memos).