The corner of the depot nobody wants to look at
Every evening a few pallets come back. The business was closed. The consignee refused it because the order was cancelled. The address was a housing estate with no room for a 7.5 tonne vehicle. The customer insisted they had a forklift and did not.
They go in the returns corner with the driver's note taped on. Somebody is meant to phone the consignee, tell the sending depot and rebook. On a busy week the corner fills, pallets get moved to make room, and the one the sending depot asks about on Thursday cannot be found.
Why failed pallets stall
A failed delivery needs three conversations: with the consignee to agree a new date, with the sending depot so their customer knows, and with your planner to put it on a run. Each one waits on the others.
- The failure reason is on a piece of paper, not in a system.
- Nobody owns the list of failed pallets as a job.
- Consignee phone numbers are missing or wrong on the booking.
- Storage and redelivery charges depend on network rules that someone has to look up.
The cost of a crowded returns corner
Floor space in a pallet depot is valuable, and failed pallets take it for days. Each one generates calls from the sending depot and complaints from their customer. Some sit long enough to trigger storage or return questions, and a few get lost among the rest, which becomes a claim.
Redeliveries that are chargeable under your network's rules often go uncharged because nobody recorded the reason properly on the day.
There is a planning cost as well. A pallet that should have gone out again yesterday sits until someone remembers it, and then it is squeezed onto a run that was already full. The failed deliveries of one week become the late deliveries of the next, and the pattern is hard to break while the list lives in a tray.
How we keep every failed pallet moving
- The driver app asks for a reason and a photo when a delivery fails, from a list that matches your network's failure codes.
- The failure creates a record, tied to the consignment, with a bay location when the pallet is put away.
- The consignee gets an automatic text or email asking them to pick a new delivery day, with the reason stated.
- The sending depot is notified through the network system where possible, or by email with the photo.
- Pallets with a new date drop onto that day's planning list. Pallets with no response after a set time go to the office to chase.
- Any storage or redelivery charge your network allows is flagged against the consignment for your statement or invoicing.
| Reason | Next step | Who acts |
|---|---|---|
| Closed | Consignee picks a new day | Consignee via link |
| Refused | Sending depot instructs | Sending depot |
| No access for vehicle | Replan on smaller vehicle | Planner |
| No forklift or tail lift | Tail lift vehicle | Planner |
The network's rules on failed deliveries still apply. The system just makes sure each pallet has someone responsible for it.
A returns corner that empties
The office opens a list, not a corner. Every failed pallet shows its reason, location, who has been contacted and when it is due out again. The sending depot gets the reason and photo the same evening, which ends most of their calls before they start.
Recognise your returns bay?
- Failed pallets stay in the depot for days.
- Failure reasons are written on paper.
- Sending depots ring to ask what happened.
- Pallets have been lost among the returns.
- Redelivery charges are rarely raised.