Intro

When a retailer issues a chargeback for a late or inaccurate ASN, the brand pays it. But the cause usually sits in the warehouse. The 856 your EDI provider sends is built from data your 3PL's warehouse management system captured: what was received, what was picked, which cartons were packed, which label went on which carton, and when the truck left.

That means your EDI maps can be perfect and you can still fail compliance. If the WMS can't capture the final carton structure, can't send a 945 within minutes of ship confirmation, or doesn't explain its inventory adjustments, the bad data flows straight through a clean integration to the retailer.

Most brands evaluate a 3PL on rates, locations and capacity. This guide covers the questions that decide whether your retail EDI will actually work once you go live, asked from the warehouse side by someone who has spent more than 20 years implementing WMS for retail and wholesale distribution.

Why the WMS decides most compliance outcomes

Follow one retail order and you can see where the risk lives:

1. The retailer sends an 850 purchase order to the brand.

2. The brand's ERP or EDI provider translates it into a 940 and sends it to the 3PL.

3. The 3PL's WMS allocates, picks, packs and labels the order.

4. The WMS sends a 945 back when the shipment is confirmed at the dock.

5. The EDI provider builds the 856 from the 945's carton and tracking detail and sends it to the retailer, followed by the 810 invoice.

Steps 1, 2 and 5 are translation and transport, which a good EDI provider handles reliably. Step 3 is physical work, and step 4 is the WMS reporting on that work. Every field the retailer audits on the 856, from SSCC numbers to carton counts to ship date, was created or captured in steps 3 and 4.

If the order touches ERP-side integration as well, Surpass explains how EDI connects to an ERP and what each integration method costs . On the warehouse side, the questions below are the ones worth asking before you sign.

The questions to ask your 3PL

Inbound: does receiving start from data or from paper?

Does a 943 or inbound 856 create an expected receipt automatically? If the dock team is keying in POs from an emailed spreadsheet, every typo becomes an inventory error you'll see later on an 846.

Can the WMS receive against SSCC labels? When a supplier sends an 856 with pallet and carton SSCCs, a WMS that understands them can receive a full pallet in one scan instead of counting every carton.

When does the 944 go out? It should go out when the receipt is closed, with overages, shortages, damages and lot or expiration data. A 944 sent at the first scan books inventory in your ERP that is still being counted.

Where do item records come from? Ask how case packs, dimensions and lot or date control are maintained, and what happens when you change a case pack. Clean item data is the foundation of everything else, which is why Foysonis treats the warehouse's digital model of areas, locations and items as the starting point of any implementation.

Outbound: does the WMS know what actually shipped?

How does the WMS handle a changed or cancelled 940 after picking has started? There should be one clear rule, applied the same way every time, and an exception the 3PL's team sees immediately.

Can allocation enforce your rules? Minimum remaining shelf life, FEFO, lot restrictions and customer-specific requirements all have to be enforced at inventory allocation, before anything is picked.

Is the final carton structure captured? Repacks, consolidations and split pallets all change which items are in which carton. If the WMS records the original pack and not the final one, your 856 will disagree with the freight at the retailer's dock.

How fast does the 945 go out after ship confirm? This is the single most important question for retail. Your EDI provider usually can't send the ASN until the 945 arrives, and many retailers expect the ASN before the truck does. A 945 that waits for a nightly batch is a chargeback waiting to happen. Surpass has a field-level breakdown of the 945 and the data retailers depend on .

Can the WMS hold a packed order for routing? Retailers that control inbound freight answer a 753 routing request with a 754. The WMS should keep the order staged until the 754 arrives, then apply the carrier and load ID so freight doesn't leave on the wrong truck.

Inventory: will your numbers match theirs at month end?

What does "available" mean in their 846? On-hand minus allocated, minus holds, minus damaged is common, but agree on it in writing before you build a retailer inventory feed on top of it.

Does every adjustment carry a reason code, and does it reach you as a 947? Cycle count variances, damages, disposals and quality holds all change your inventory. Without a 947 trail, month-end reconciliation becomes a manual investigation. For multi-client operations, also ask how they keep each client's stock separate and accurate.

Exceptions: who finds out when something breaks?

What happens when a 940 references an unknown item? It should land in an exception queue with a clear message, not fail silently.

Who watches acknowledgments? Ask who is alerted when an outbound 945 or 944 isn't acknowledged by a 997 within the agreed window, and who sees an 824 business rejection. A missing acknowledgment is often the first sign of a dropped order.

Red flags in a 3PL demo

A polished demo can hide a weak integration. These are the answers that should make you dig further:

• "We send shipment files at end of day." Fine for some channels, but a problem for retailers with tight ASN windows, especially near order cutoff times during peak.

• "We can add lot tracking later." Adding lot and expiration capture after go-live means remapping the 944, 945 and 947. Food, beverage and supplement brands should settle it during scoping.

• "Our team fixes exceptions manually each morning." That tells you exceptions are common and that nobody is alerted when one happens during the day.

• "Adjustments are on a report we can send you." A report is not a 947. Ask whether reason codes come to your ERP automatically.

• No clear owner for each retailer's spec. Every retailer adds rules on top of X12. If neither the 3PL nor your EDI provider owns those changes, they won't get tested.

None of these is a deal-breaker on its own. Together, they predict how much of your team's time will go into fixing data the warehouse should have sent correctly.

Who should own what

Most compliance failures trace back to work nobody clearly owned. Agree on a split like this before testing starts:

The right column is where your 3PL's WMS earns its keep. A managed EDI provider can keep every partner spec current and every map tested, but it can only send what the warehouse captured. Surpass keeps a directory of retailer EDI requirements  that shows how much those specs vary from one partner to the next.

Frequently asked questions

Why am I getting ASN chargebacks when my EDI maps are correct?

Usually because the data feeding the 856 is wrong or late. Check whether the 945 is sent in real time at ship confirm, and whether the WMS records repacks and consolidations before the carton labels are final.

Does my 3PL need to send the 856 directly to the retailer?

Not necessarily. Many brands have their EDI provider build the 856 from the 3PL's 945. What matters is that the 945 carries complete carton, SSCC and tracking detail and arrives fast enough to meet the retailer's ASN window.

Which EDI transactions should a 3PL support for a retail brand?

At minimum the 940 and 945 for shipping, the 943 and 944 for receiving, the 846 for inventory, the 947 for adjustments and the 997 for acknowledgments. Brands selling to retailers that control freight will also need the 753 and 754 routing pair.

Can a 3PL use an API instead of EDI?

Yes, between the WMS and your EDI provider or ERP. Many modern WMS platforms exchange the same data as JSON over an API, and the EDI provider translates it to X12 for your trading partners.

When should we raise these questions?

Before you sign, and again in the mapping workshop. Changing 945 timing or adding lot capture after go-live costs far more than settling it during scoping.

Closing

A 3PL's rate card tells you what fulfillment will cost. Its WMS tells you what compliance will cost. Before you sign, walk through the questions above with the 3PL's operations and IT teams together, ask to see a 945 generated from a real ship confirmation, and agree in writing on timing, reason codes and who owns each retailer's spec.

The brands that do this up front tend to spend their time growing retail accounts. The ones that skip it tend to spend it disputing chargebacks.

——————————————————

About the author

Shashank Dhadphale is the Co-Founder of Foysonis, a cloud WMS built for small and mid-size warehouses and 3PLs. He has more than 20 years of experience implementing warehouse systems, including Blue Yonder (JDA) WMS for large retail and distribution operations, and holds an APICS CSCP certification. Foysonis connects to ERPs and EDI providers over API for expected receipts, receipt confirmations, inbound orders, shipment confirmations and inventory adjustments.