A rejected 856 (Advance Ship Notice) can hold up a shipment, trigger chargebacks, and strain a trading-partner relationship — and the rejection reason is often terse. This guide walks the usual causes in the order worth checking, so you can resolve it before it costs you.
1. Validate the ASN hierarchy (the most common failure)
The 856 is built on a nested hierarchy — typically Shipment, Order, Pack, Item. If the hierarchy levels don't balance (an item without its pack, a pack count that doesn't match the contents, a level out of sequence), most partners reject the whole ASN. Confirm the HL structure is complete and internally consistent.
2. Check quantities and weights reconcile
Rejections frequently come from totals that don't add up: carton counts that don't match the sum of packs, shipped quantities that differ from the order, or weights that fall outside tolerance. Verify the roll-up totals match the detail.
3. Confirm timing — the ASN must arrive before the goods
An ASN is an advance notice. If it transmits after the shipment physically arrives, or too close to arrival, some partners reject it on timing rules alone. Check when the 856 was sent relative to dispatch and delivery.
4. Verify identifiers and partner-specific data
Trading partners are strict about the data that lets them match the ASN to their systems:
- Purchase order number: must exactly match an open PO on their side — a trailing space or wrong format fails.
- SSCC / carton labels: the barcode identifiers in the ASN must match the physical labels; a mismatch is a common chargeback trigger.
- Item identifiers: UPC, GTIN, or partner item numbers must be the ones that partner expects, not your internal codes.
5. Check compliance with the partner's specific 856 spec
Two partners rarely implement the 856 identically. A segment or qualifier that's optional for one is mandatory for another. If the rejection is partner-specific, compare your outbound ASN against that partner's published EDI specification — the gap is usually a required element you're not populating.
6. Trace it back to the source system
Once you know which data is wrong, trace where it originates — WMS pack confirmation, the shipping system, or the mapping in your integration layer. Fixing it at the source prevents the next ASN from failing the same way.
The faster way
ASN rejections are exactly the kind of multi-cause, partner-specific problem SupplyChain Assist helps untangle — describe the rejection and the partner, and it walks the likely causes with the specific checks, so you clear the shipment and avoid the chargeback.