A deduction nobody saw coming
Your client forwards a remittance from a national retailer. It has a deduction on it with a code and a one-line reason: non-compliant pallet label. Another line says the delivery was outside its booked slot. The client wants to know what happened, and so do you, because the pallet was built and labelled by your team on a Thursday afternoon when three retailer orders went out at once.
Each retailer wants something slightly different. One needs a specific label layout with a serial shipping container code, another limits pallet height, another insists the electronic delivery note is sent before the lorry leaves your yard. Your B2B team knows most of it. The new starter on the pallet line does not.
Why the rules keep getting broken
Retailer requirements are written for the brand, not for the warehouse. The brand passes them to you as a forwarded PDF when the account opens, and then the retailer updates the manual and nobody forwards the new one. The rules are specific to each combination of retailer, depot and sometimes product type, which is too much to hold in anyone's head.
| Common requirement | How it usually fails in a 3PL |
|---|---|
| Pallet label format and content | Generic label printed, missing retailer's order number or container code |
| Maximum pallet height or weight | Built to your normal standard, which is taller |
| Electronic advance notice | Sent late, or quantities differ from what was loaded |
| Booked delivery slot | Haulier booked without the slot reference, or arrives outside it |
| Outer case barcodes and quantities | Cases split to make up an order, barcode no longer true |
Nothing in the WMS stops a non-compliant order being released, so the check happens at the last minute, by eye.
What it costs you and your clients
The deductions land on your client, and your client asks you to cover them. Even when you do not, the relationship takes the hit. Rejected deliveries are worse: the pallet comes back, the stock has to be rebooked in, and the retailer's shelf is empty for another week, which the brand will remember when their contract is up.
Your B2B team also spends a lot of its time double-checking, which caps how many retail accounts you can handle.
How we build the checks in
- A rulebook per retailer and delivery point, held as data: label template, pallet limits, case rules, booking and notice requirements. Your team maintains it through a simple screen, not code.
- An order check at release: when a B2B order arrives from the client, it is matched to its retailer and tested against the rules, such as order quantities that break case multiples or missing purchase order references.
- Label generation: the correct retailer label layout filled from the order and pallet data, printed from the packing bench.
- A pallet check at dispatch: height and weight entered or captured at the pallet line, compared with the retailer's limits before the pallet is wrapped.
- Notice sending: the advance delivery message built from what was actually loaded, sent through the retailer's required route, whether that is EDI via your client's provider or a supplier portal upload.
- An evidence record per delivery: labels printed, photos of the built pallet, the notice sent and when, so a deduction can be disputed with facts.
What your B2B team gets
The rules stop depending on who is working that day. Orders that would break a retailer's rules are caught when they arrive, while there is still time to query the client. And when a deduction does come through, you can open the delivery record and see exactly what left your warehouse.
Taking on a brand that supplies a new retailer becomes a matter of adding a rulebook, rather than hoping the team remembers.
Signs your retail deliveries need this
- Clients forward retailer deductions and ask what went wrong.
- Retailer supplier manuals live in an inbox or a shared drive.
- Pallet labels for retailers are made in a word processor or by hand.
- The advance notice is typed after the lorry has gone.
- Only one or two people really know each retailer's rules.