The 824 Tells You Your ASN Was Rejected. Almost Nobody Reads It

You sent the ASN on time. The retailer accepted the file. The shipment failed anyway.

That combination looks impossible until you know that Walmart's ASN validation is three messages, and the only one that says "rejected" is the last one.

The first message is yours: the 856 Ship Notice/Manifest, transmitted before the trailer leaves the dock. What it carries, and the four ways a clean-looking 856 still fails, is in what the 856 actually is.

The second is the 997 functional acknowledgment, the retailer's confirmation that it received and accepted the functional group. The 997 is about the envelope, not the data. It says the group was taken, not that the shipment was right, and it is the one inbound document nobody archives, the acknowledgement nobody keeps.

The third is the 824 Application Advice, and it is the only one of the three that answers the question you are actually asking. The chain, 856, then 997, then 824 where there is a problem, is Bekah Tatem's description in "What is an ASN? Understanding Walmart's ASN Validation Process", SPS Commerce, 20 June 2024.

What each message can tell you

Most teams read the first two and never open the third. The 824 arrives as a transaction set you may not have a screen for.

WARN, ERROR, and the message with no text

SPS Commerce's account of the 824 gives three outcomes. The third is the one that gets missed.

Read that last row again. An 824 carrying no error or warning text is a rejection, not an acknowledgement. A team that opens the file, finds nothing in it and files it under "fine" has read a rejection as a pass.

The split decides your alert volume: a WARN is a trend to watch, an ERROR is a file to fix before the truck moves.

On time is two conditions, not one

This is the rule that turns a fast ASN into a late one. An ASN is on time only if it arrives before the gate-in time of the shipment or trailer at the Walmart facility and passes all validation rules.

A fast-but-rejected ASN is still a late ASN for receiving purposes. The DC cannot stage labour against a file it did not accept.

Walmart's accuracy test is separate, with three parts: the PO lines on the ASN match the purchase order, the items align with the physical shipment, and the quantity matches what arrives. None of that is checkable before the trailer is broken out. An 824 is a judgement about the file; a deduction is a judgement about the load. The distance between them is the whole cost of the channel.

One rejected file is not one rejected carton

An 856 is a single document for the whole load. Walmart's validation runs against that document. The count it reconciles against is per carton.

The physical consequence is documented. SPS Commerce, 5 August 2026, records that the SSCC-18 on the carton has to be the exact 18-digit string in the EDI 856, or the shipment is effectively invisible to the retailer's automated receiving: scan failure, manual intervention, receiving delays, compliance chargebacks. A rejected ASN leaves no accepted advance record to scan against, so the fallback is manual across the load.

How much that costs depends on how the retailer prices it, and the two major US retailers price it in opposite currencies. Our portal reference records Walmart's ASN and labelling penalties at $50 to $500 per incident, one event, one amount, however many cartons rode the trailer. Target prices the same class of failure per carton, at $0.75 a carton with a $100 minimum, so a 600-carton load carries $450 for one file to fix.

The larger layer never appears on a remittance advice. "How To Calculate the True Blast Radius of Supplier ASN Failure", SPS Commerce, 5 June 2026, models the true cost of an ASN failure at three to ten times the deduction, manual receiving, exception handling, dispute labour, expedited freight, scorecard erosion, lost volume. It is one vendor's published model, not a measured study, and the roughly two hours of dispute handling and 40% higher receiving labour it cites come from the same article. Directionally useful, not a planning input.

That is the whole argument for reading the 824. Fixed inside the receiving window, it is one edit. Discovered when the deduction posts, it is the full blast radius, and the fix window closed hours after the trailer did. That is where the dispute loop picks it up.

Make it an error feed, not a report

Four things, and none of them is a project.

Capture the 824 on arrival, next to the 997, keyed by ASN number and purchase order number. Without that key the message is worth nothing.

Alert on ERROR, and route the alert to whoever can edit the file, not to an inbox. WARN belongs on a weekly trend, not a pager.

Read the aggregate before the individual files. Walmart's Advanced Shipment Notice Dashboard has an IDOCS tab carrying a Coverage chart, the share of purchase orders shipped with and without an ASN, and an Exception Distribution chart, the share of ASNs that raised an error or warning broken out by error type. Both are in SPS Commerce's 20 June 2024 walkthrough. That chart is the root-cause map: the first week 80% of your exceptions land in one error type, you have found a mapping defect rather than 200 separate mistakes.

Count the ERRORs you fixed before gate-in, not the 824s you received. The second number will not improve on its own.

What is not published

Walmart has not published the ASN validation rule set: no public list of the conditions that raise a WARN against the conditions that raise an ERROR, no rate, no public inventory of the 824 as Walmart sends it. The EDI mapping guide the rules align to sits behind a Retail Link login. Two SPS Commerce articles, 20 June 2024 and 5 June 2026, carry the chain and the WARN/ERROR semantics, and they are the best record that exists, practitioner accounts, not Walmart documentation. We would not defend the rule set from them, which is why this post names the messages and not the segments.

So your own 824 archive is the only complete record of the rules you are failing. Nobody publishes a benchmark for a healthy exception rate on either chart; the percentages you can act on are the ones you measured last quarter.

What did change is volume. Walmart tightened its ASN business rules in May 2024 to align them with its EDI mapping guides, with the stated aim of letting more of the ASN data be used, and said the resulting increase in 824 error and warn transmissions would not itself create new SQEP charges. It described its own sequence: implement a standard, track compliance, eventually levy charges. Whether the count in your account is the 2024 tightening or your own mapping, the Exception Distribution chart is where the answer is.

An ERROR has to be fixed before the shipment arrives, and an ASN is only on time if it lands before the trailer gates in and passes validation. Those share one deadline. The moment the wheels turn, the 824 stops being something you read and becomes something you pay for.