The Receipt Nobody Reads: Why “ASN Not Received” Is Retail’s Most Avoidable Fine

Every week, somewhere in America, an operations manager opens a chargeback notice that reads “ASN not received,” walks to the EDI provider's portal, finds the advance ship notice sitting right there with a timestamp, and experiences a feeling usually reserved for people who were definitely, absolutely on the guest list.

They did send it. In most cases that isn't the question. The question is whether the retailer accepted it, and the answer is written in a document most suppliers never look at.

A fine with a long memory

Big-box retail runs on the advance ship notice, the EDI 856. It tells a distribution center what is on the truck before the doors open: which purchase order, which cartons, which barcodes. When the ASN is missing or wrong, the receiving dock has to count by hand, and retailers have long passed that cost back to suppliers.

Walmart set the tone in 2017, when it told suppliers it would charge 3% of the value of shipments that arrived late, early, or short under its On-Time In-Full program, according to Supply Chain Dive. The bar has risen since. Supplier guides now cite targets of 98% on-time for collect shipments and 90% for prepaid, with 95% in-full for both, and fines below $1,000 a month waived, per 8th & Walton.

ASN problems are billed separately. Industry compliance guides put Walmart's missing-or-late ASN charge at roughly $100 to $500 per purchase order, with a dispute window of 15 to 30 days, according to ShipCalm. Retailers rarely publish their fee schedules in full, so treat those figures as a range, not a rate card. Either way, a supplier shipping a few POs a week can fund a nice company offsite with these fines, and get nothing for it.

“Sent” and “accepted” are different verbs

Here is the sequence that produces most of these fines:

1. The supplier's EDI provider transmits the 856. The portal shows “sent.” Everyone relaxes.
2. Minutes later, the retailer's system checks the file and returns a 997 functional acknowledgment, an automated receipt.
3. The 997 says AK5*R: rejected. Perhaps the order loop is missing its purchase-order reference (the PRF segment). Perhaps the trailer says the document has 20 segments when it has 21.
4. Nobody opens the 997. The truck arrives. As far as the distribution center is concerned, no ASN exists.

That last step is the expensive one. A rejected ASN is, operationally, a missing ASN. The fine is valid, and because the underlying map is still broken, it will recur on every purchase order until someone fixes it.

The EDI equivalent of mailing a check, watching it bounce, and filing the bounce notice under “newsletters.”

When the receipt is your best evidence

The same document can also clear you. Suppose the 997 says AK5*A (accepted) and is timestamped 21 hours before the truck pulled in, and the retailer still charges “ASN not received prior to arrival.” That is a retailer-side matching or timing failure, and the supplier is holding a machine-generated, retailer-issued receipt that says so.

Most suppliers never dispute fines like this. Some can't read the acknowledgment; others don't know it counts as evidence. Deductions add up quickly: in a January 2026 analysis, Jon Allen, chief executive of Bentonville-based Woodridge Group, sketched a hypothetical $150 million snack brand absorbing about $7 million in fourth-quarter deductions, $1 million of them compliance and OTIF charges, per Talk Business & Politics. “The fourth quarter is fantastic for revenue and also dangerous for margin,” Allen said.

The five-point check

Most ASN rejections come from a short list of mistakes. Forward this to whoever owns your EDI map:

1. Segment count. The SE trailer must count every segment from ST to SE. One extra line and the whole document fails.
2. PO reference. Every order-level loop (HL*…*O) needs a PRF segment carrying the purchase order number. Without it, the ASN can't be matched to anything.
3. Carton IDs. Each SSCC-18 needs a valid GS1 check digit and must be unique. Typed-in or spreadsheet-generated serials are the usual culprit.
4. The test flag. ISA15 = T marks the file as a test, and production systems ignore it. It is surprisingly common after onboarding.
5. Timing. The ASN should go out after the shipment leaves and before it arrives, and must match what is physically on the truck.

The bottom line

Treat every 997 as a delivery confirmation for money. Route any AK5*R or AK9*R to a human the same day, keep the 856, the 997 and the arrival time together for every shipment, and fix the map, not the individual file. The fine is rarely about whether you hit “send.” It's about whether anyone read the reply.