Retail Routing Guides and Chargebacks: The Compliance Rules Behind Every B2B Order
Retail chargebacks are a warehouse problem long before they are a paperwork problem. The five violations that generate most deductions, how ASN and label requirements actually work, and how to build routing-guide compliance into the pick-and-pack workflow.
The routing guide is the contract nobody reads
When a brand wins a retail account, the celebration is about the purchase order. The document that determines whether the account is profitable is the routing guide: a PDF, often a hundred pages, that specifies exactly how the retailer wants goods labeled, palletized, documented, tendered, and delivered.
It is not advisory. Deviations are billed back as chargebacks — deductions taken off your invoice, usually a flat fee per violation plus a percentage of the shipment value. A brand can hit a 99% on-time rate and still lose several points of margin to labels applied in the wrong corner.
The awkward part is that routing guides get revised, quietly, sometimes twice a year. The version saved on someone's desktop when the account was opened is not the version you are being measured against.
Where the deductions actually come from
Across most large retailers, the same handful of violations account for the majority of deductions.
| Violation | Typical trigger | Where it is prevented |
|---|---|---|
| Late or early delivery | Arrival outside the delivery window on the PO | Carrier selection, ship-by date logic |
| ASN error | Advance ship notice missing, late, or not matching the physical shipment | Data validation before the truck is tendered |
| Carton or pallet label defect | Wrong label format, placement, or unreadable barcode | Label template control, print-and-apply |
| Packing violation | Mixed SKUs in a carton, wrong pallet height, overhang | Pack station rules, pallet build spec |
| Quantity discrepancy | Units received differ from ASN quantity | Scan verification at pack and load |
Note what all five have in common: every one of them is prevented at the warehouse, not at the desk of whoever manages the account.
The ASN has to describe the pallet that actually shipped
The advance ship notice is where retail compliance most often quietly fails. An EDI 856 has a nested structure — shipment, order, pack, item — and the retailer's receiving process scans a pallet or carton label, looks up that identifier in your ASN, and expects the contents to match exactly.
Three rules keep this clean. Transmit the ASN after the trailer is loaded but before it arrives, within the window the routing guide specifies. Build it from what was physically scanned, not from what the order said should be picked. And make sure the license plate on the label is the same identifier carried in the ASN, because a mismatch there turns a correct shipment into a receiving exception.
Brands doing this across borders have an additional documentation layer to reconcile; our guide to customs, duties, and compliance for B2B sellers covers where those two paper trails have to agree.
Labels and pallet build are a specification, not a habit
Most retailers require a GS1-128 shipping label with specific data elements, at a specified height from the pallet base, on specified faces. Some want it on two adjacent sides. Some specify the exact placement window on a carton. These details feel arbitrary until you see the receiving dock: the retailer is scanning at speed, often automatically, and a label three inches out of position is a manual exception that costs them money — which is precisely what the chargeback is recovering.
Pallet build is specified the same way. Maximum height including the pallet, no overhang, layer patterns, corner boards for certain commodities, stretch wrap tension and coverage, and whether the pallet must be a specific grade. "It arrived intact" is not the standard being applied.
Build the rules into the workflow, not into a memo
The reliable pattern is that compliance rules live in the system and appear at the moment of action, rather than living in a binder that a supervisor is expected to remember.
In practice that means the warehouse management system holds a customer profile per retailer — label template, carton rules, pallet spec, ASN format, ship window — and applies it automatically when an order for that account is released. The pack station shows the right label. The system refuses to close a carton that violates the mixing rule. The ship-by date is calculated backward from the delivery window and the transit time, not chosen by whoever is building the load. Peak volume is when memory-based compliance fails, which is why routing-guide rules belong in the same pre-season review as the rest of your outbound peak readiness checklist.
Measure it as a rate, and chase the deductions
Two numbers are worth reporting monthly: compliance rate by retailer, and deduction dollars per shipment. The second one is what makes the case for fixing anything.
Then dispute. A meaningful share of chargebacks are issued in error — duplicate deductions, violations against a superseded routing guide version, delivery delays caused by the retailer's own dock. Most retailers allow a dispute window, often 30 to 90 days, and unclaimed deductions are simply kept. Assign the recovery work to a person, not to "we should look at that."
If retail compliance is turning into a full-time job internally, it is a reasonable thing to hand off: our B2B fulfillment and retail fulfillment operations are set up to carry routing-guide requirements per account. The mechanism that makes that work is unglamorous — retailer rules configured once in AIDWMS and enforced at the pack bench on every order after that, so nobody has to remember which retailer wants the label on two sides.
