IDXE by EDI Partners Talk to an Expert

← Insights

Routing Guides Change. Your Maps Don't. Then Chargebacks Appear.

"We were compliant last quarter." Every supplier compliance team has said it, usually while looking at a deduction for an ASN, label, appointment, or carrier rule that nobody on the team remembers changing. Usually nothing changed on your side. The retailer's routing guide changed, and your EDI maps, label templates, and dock procedures kept running against the version you onboarded with.

During peak season that gap gets expensive fast. Volume goes up, scorecards get stricter, and an outdated rule that used to cost one deduction a month now shows up on every PO. The fix isn't a better dispute process. It's treating the routing guide the way an engineering team treats a product spec: versioned, owned, monitored, and tested against before anything ships.

Routing guides are living documents, and retailers say so

You don't have to guess that guides change. Retailers put it in writing:

None of this is hidden. It's just spread across portals and PDFs that change on the retailer's schedule, not yours.

How guide drift becomes a deduction

Most suppliers build their retailer setup once, at onboarding. Someone reads the routing guide and the EDI implementation guide, builds the maps, configures labels, writes a dock checklist, and passes certification. Then the project closes.

From there, the guide and the setup start to drift apart. The most common gaps:

What changed in the guide Where it lives on your side How it shows up
ASN timing rule (e.g., before in-yard vs. at ship) ASN trigger in ERP/WMS/EDI Late or "no ASN" violations on loads that shipped on time
ASN content (BOL format, required segments, item data) 856 map and master data ASN accuracy defects or application advice rejects
Label layout or required data Label templates, print station Barcode/label defects at receiving
Appointment requirements Transportation and dock process Missed or invalid appointment charges
Approved carriers, pallet limits, mode rules TMS routing rules, carrier contracts Routing non-compliance, refused freight
Case pack and item attributes Item master, packaging specs New-metric defects (casepack, dimensions)
Ship-to or network program changes Ship-to tables, partner IDs Wrong-DC or receiving exceptions

Every one of these can pass a 997. The functional acknowledgment confirms the file was received and parsed. It says nothing about whether you followed this quarter's routing rules. That's why drift tends to surface first on a scorecard or a deduction, weeks later, when the evidence is harder to reconstruct.

Treat the routing guide like a versioned spec

Software teams don't build against "the spec we read last year." They build against a version number. Retail compliance should work the same way.

Keep a guide register per retailer. For each trading partner, record the current version or effective date of every governing document: routing guide, EDI implementation guides (856, 810, 855), labeling guide, and compliance or chargeback policy. Store the PDFs and note where each one lives in the portal.

Diff every new version. When a retailer flags changes, as Von Maur does with italics, the diff is easy. When it doesn't, compare the new and old documents directly. Write each change down as a rule, not as a page reference: "ASN must be received before trailer in-yard," "BOL must use format X in segment Y," "appointments required for all LTL."

Map each rule to a control. For every rule, name the system or step that enforces it: the 856 map, the ASN trigger, the label template, the TMS carrier list, the dock checklist. A rule with no control is a future deduction.

Record effective dates. Because some programs grade on receipt date rather than ship date, the change has to be live before freight that will arrive after the effective date leaves your dock.

A disciplined spreadsheet with an owner beats a folder of PDFs nobody opens.

One owner, not a distribution list

Routing guide changes cut across EDI, warehouse, transportation, item data, and finance, which is why they fall through the cracks: everyone is consulted and nobody is accountable.

Name one owner per retailer, or one owner for the whole compliance spec program with named delegates. Their job:

The owner doesn't have to make every fix. They have to make sure no change is left unassigned. (If a 3PL ships your orders, the same owner coordinates with the warehouse. We covered the brand–3PL split separately.)

Change monitoring: catch drift before the deduction

Waiting for the next PDF is too slow. Combine several signals:

EDI preflight tied to the current guide

Monitoring tells you a rule changed. Preflight makes sure every outbound document follows the current rule before it leaves. Useful preflight checks include:

Each check should hold the document or alert a person, not log a warning nobody reads. Version the preflight rules alongside the guide register, so you can always say which guide version a load was checked against.

Where managed EDI fits

Most of this is operational discipline that no single platform owns. A managed model helps on the EDI side of the loop: maps get updated when guides change, validation follows the current spec, and someone watches rejects and acknowledgments every day, not just at certification.

IDXE, EDI Partners' proprietary Azure-native managed EDI platform, is built for that ongoing role. It provides partner-specific mapping, pre-send validation against each trading partner's rules, and managed operations past go-live that keep up with guide changes, so your team can focus on the warehouse and transportation controls only you can own.

Takeaways

If your maps still match the onboarding PDF, now is a good time to compare them with the current guide, before peak volume does it for you. Talk to EDI Partners about keeping retail maps current with IDXE →