What an ASN rejection actually means
Of the four documents that move between a supplier and a retailer, the advance ship notice is the one that gets checked against something physical. A purchase order is a request. An invoice is a claim. The ASN says "this is what is on the truck, packed like this, arriving then", and the retailer's distribution centre scans the cartons to find out whether that was true.
That is why ASN problems cost more than any other EDI fault. A rejected invoice delays payment. A rejected ASN means a receiving team unpacking a pallet by hand, a late-ASN chargeback, or stock that cannot be put away because the system does not know it has arrived.
What the document carries
In X12 the ASN is the 856; in EDIFACT it is the DESADV. Whatever the syntax, a retailer's guide asks for the same structure:
- Shipment level: the ship-from and ship-to locations as GLNs, the carrier, the expected delivery date, and a shipment identifier that will appear on the paperwork.
- Order level: the retailer's purchase order number, exactly as they sent it.
- Pack level: each pallet and each carton, identified by an SSCC, the serial shipping container code that is printed as the barcode on the label.
- Item level: the GTIN and the quantity inside each carton, matching the lines on the order.
The retailer's receiving system reads this as a tree: shipment, then pallets, then cartons, then items. When the tree does not match what the scanner sees, the ASN fails.
The five reasons it bounces
1. The GLN is not known. A ship-to or ship-from location that the retailer has not set up for you, or that you have mistyped, fails before anything else is read. The message often arrives as a generic "partner not found". In my experience this is the first thing to check, because a wrong GLN makes every other field irrelevant.
2. The purchase order reference does not match. Leading zeros dropped, a release number missing, or an order that was changed after you accepted it and your ERP still holds the original.
3. The hierarchy is wrong for the order model. A distribution centre replenishment order wants pallets with cartons inside. A direct-to-store or cross-dock order wants cartons allocated by store. Sending a flat list of items when the retailer expects a pallet and carton structure is a rejection, even when every quantity is right.
4. The SSCC does not match the label. The number in the message and the number on the carton barcode have to be the same eighteen digits. A label printed from the warehouse system while the ASN was built from the ERP is the classic way they drift apart.
5. It arrived after the truck. Most compliance guides require the ASN before the goods are received. A technically perfect ASN sent an hour late is still a chargeback.
Where to look first
Start with the retailer's rejection text and the document that was actually sent, side by side. Do not start with the mapping. Most rejections are data problems that the mapping faithfully transmitted: a GLN missing from your customer master, a pack configuration with the wrong inner quantity, a carton label printed from a different system than the one that built the message.
Then ask which of the five reasons above it is. Each points at a different owner. GLNs and pack configurations live in the ERP master data. Hierarchy problems live in the mapping specification or the order-model configuration. SSCC mismatches live between the warehouse and the ERP. Timing lives in the dispatch process.
Fixing it once
The fix that stops the chargebacks is never "resend it". It is finding the master record or the configuration that produced the fault and correcting that, so the next hundred shipments go through first time. Re-sending the corrected document inside the retailer's window is the second step, not the first.
If you are reading rejection notices every week, the pattern is usually one or two causes repeating. A day with the compliance guide, the last ninety days of rejections and your product and customer master data will show which ones.