We had a client, a home-goods exporter, who sent its first shipment — with a faulty EDI 856 ASN — to a big-box US retailer in the fall of 2024 and learned an expensive lesson before the goods had even cleared the retailer's regional distribution center. Twelve pallets, 480 cartons, clean paperwork, a signed proof of delivery. Two weeks later the chargeback statement arrived, and the deductions were bigger than the margin on the whole order. The client called me and asked, Susan, the goods were all received — how can they charge me for this? I had him read the deduction reasons out loud, one by one. By the second line I knew: the problem was never the freight. It was the EDI 856 ASN we had sent ahead of it.
An EDI 856 ASN is the advance ship notice — the electronic heads-up a supplier sends a retailer's receiving system before the truck arrives. It lists what is in the shipment, how many cartons, which SSCC code sits on each pallet, and which purchase order line each carton belongs to. When the truck docks, the retailer does not open every carton and count. A worker scans the pallet label, and the system checks it against the ASN line by line. Match, and the goods flow straight into inventory. Mismatch, and the system logs an exception — and the chargeback machine starts turning.
What the ASN Actually Tells the Retailer
The single most important field on that notice is the SSCC, the Serial Shipping Container Code: an 18-digit number that identifies one logistics unit, usually printed as a GS1-128 barcode on the pallet or outer carton. One pallet, one number, never reused. Scan it and the retailer's system knows what is inside, how many units, and which purchase-order line it answers to. Get the SSCC wrong and the whole pallet is, as far as the system is concerned, freight from nowhere.
A lot of warehouses treat the ASN as an electronic packing list for the carrier. That is the wrong mental model. A packing list is written for a human. The ASN is written for the retailer's receiving system. A human who spots an error can ask a question. A system that spots an error just posts a charge. The buyer's system will not call you to double-check.
How One Bad EDI 856 ASN Eats Your Margin
Our home-goods client tripped on the most common failure: quantity mismatch. The warehouse plan said 40 cartons on pallet A; on the floor, eight cartons got moved to pallet B during loading, and nobody updated the ASN. The receiving scan found eight cartons too many on B and eight too few on A, and the whole shipment was flagged as a quantity discrepancy. Not a single carton was missing. The deductions posted anyway — a shortage charge plus an exception-handling fee. The client was furious: the goods were all there. The retailer's answer, in effect, was that the ASN and the physical freight disagreed, and the system only trusts the ASN.
The second failure mode is a late ASN. Another client, a small-appliance supplier, shipped to the same retailer in the spring of 2025. The truck reached the distribution center gate while the ASN was still sitting in the EDI provider's queue. With no advance notice to match against, receiving had to process the load manually: unloading ran four hours late, a no-ASN receiving fee posted, and the truck missed its appointment window and waited another day at the gate. A late ASN sounds like a small thing. The invoice says otherwise.
The third one is sneakier: wrong carton labels. The UCC-128 label printed on the outer cartons carried the SSCC from a previous shipment, so the label and the contents told two different stories. The scanner read the code, the system decided the carton belonged to a different purchase order, and the pallet was rejected on the spot. The crew spent half a day re-labeling and re-scanning one pallet.
Here is the table I walk clients through when we reconcile a chargeback statement. The dollar figures are hypothetical examples to show the scale of each failure; real deductions follow each retailer's current compliance manual:
| Failure | Typical chargeback line | Evidence the warehouse should keep |
|---|---|---|
| Quantity differs from physical freight | Quantity discrepancy, exception-handling fee | Weighing records at pack-out, carton photos, scan logs |
| SSCC does not match the pallet | Label-error deduction | Label verification records, pallet-to-SSCC map |
| ASN sent late or never sent | No-ASN receiving fee | EDI transmission timestamps, carrier pickup records |
| Carton label belongs to another shipment | Rejection, rework fee | Outbound verification sign-off, photos of the problem cartons |
Here is the counterintuitive part: earlier is not better. Plenty of warehouses send the ASN the moment the shipment is planned, terrified of being late — before the cartons are sealed, before the labels are checked. The moment anything changes on the floor, that early ASN is wrong. I tell clients the opposite: wait twenty minutes. Let the freight be sealed, labeled, and verified, then send it. An accurate ASN sent slightly late costs far less than an early one that is wrong. The retailer wants precision, not speed.
Your EDI 856 ASN Is Wrong — Now What?
Start with the 997. After you transmit the ASN, the retailer's system sends back a 997 functional acknowledgement. A lot of suppliers see the 997 come back and relax, assuming the job is done. It is not. The 997 proves exactly one thing: the trading partner received your transmission and could read its syntax. It says nothing about whether the contents are right. Wrong quantities, wrong SSCCs — the 997 comes back looking just as clean. Anyone treating a 997 as a clean bill of health is the first to lose a dispute.
Then mind the 810 invoice. The 810 is the invoice you send after shipping, and its quantities and amounts have to match the ASN. The ASN says 480 cartons, the invoice says 480 cartons, receiving counts 480 cartons — three-way match, the books close. If the ASN is wrong and the invoice is right, the reconciliation flags another discrepancy. So at the ship-confirm step, check all three — ASN, physical freight, invoice — together, not one at a time.
Disputes are won on records made at the time, in the place. Pack-out photos, weighing records, scan logs, EDI transmission timestamps: a burden on a normal day, money on a chargeback day. Without them, you cannot rebut a single line of the deduction. With them, you can at least negotiate the unreasonable parts down. One of our clients used a complete scan log to talk a five-figure deduction down to a fraction of the original amount — but only because the timestamps on the records lined up with the ASN timeline.
Next time you're negotiating a contract, ask these three questions. First, which section of the compliance manual governs ASN deductions, and what are the rates? Second, how long is the dispute window, and what evidence is accepted? Third, is there a first-offense waiver or a warning before the first deduction? Get those three answers in writing and the cost of an ASN mistake drops by at least half. Skip them, and when the statement arrives, all you can do is pay it.
By Susan, 3PL Sales Director







