EDI 856 ASN: The Document That Causes the Most Chargebacks

What Is the EDI 856 ASN?

The EDI 856 — formally called the Advance Ship Notice — is the document you send to a retailer when a shipment leaves your warehouse. It tells them exactly what's coming: which purchase order it fulfills, what items are packed in which cartons, how many units per carton, the carrier, the tracking number, and the expected delivery date.

Retailers use the ASN to prepare their receiving dock, pre-populate their inventory systems, and verify shipments against purchase orders — all before the truck arrives. When the ASN is accurate, receiving is fast and automated. When it's wrong, everything breaks down.

If you're getting chargebacks and you're not sure why, the 856 is the first place to look. In our experience working with brands selling to Walmart, Target, and Kohl's, the ASN is responsible for more chargebacks than any other EDI document.

Why the ASN Is So High-Stakes

Every other EDI document is a confirmation of intent. The 850 is a purchase order. The 855 is your acknowledgment. The 810 is an invoice. These documents matter, but errors in them are usually caught and corrected before they cause compliance failures.

The 856 is different. It's a real-time document tied to physical inventory in transit. By the time the retailer receives your shipment, their system has already consumed your ASN and made decisions based on it. If the ASN said 48 units and 50 arrived, that's a discrepancy. If the ASN carton count didn't match the packing list, that's a receiving delay. If the ASN arrived after the shipment, you've failed a timing requirement.

Retailers don't absorb these costs — they charge them back to you.

The Exact Fields That Cause Failures

Not all ASN errors are equal. These are the fields that generate the most chargebacks:

1. Timing — ASN sent after shipment arrives

Every retailer has a timing requirement: the ASN must arrive in their system before the physical shipment does. Walmart requires the ASN to be transmitted within 24 hours of shipment departure. Target requires it prior to carrier pickup in many cases. Send it late and you trigger an automatic chargeback, regardless of whether the shipment itself is perfect.

2. Carton count mismatch

The number of cartons declared in the ASN must match exactly what's on the packing list and what the carrier picks up. A single carton discrepancy — whether it's extra cartons added at the last minute or a carton left behind — generates a chargeback.

3. Item-level detail errors

The ASN must declare every item, at the correct unit count, mapped to the correct carton. If you ship 6 units of SKU A and your ASN says 5, that's a discrepancy. If your ASN lists the wrong UPC, the retailer's system can't reconcile it. These errors are common when ASNs are built manually or when product data isn't synchronized.

4. Missing or incorrect SSCC (Serial Shipping Container Code)

The SSCC is the barcode on each carton — it's how the retailer's system tracks individual boxes from your dock to their shelf. If the SSCC in your ASN doesn't match the label on the carton, the receiving scan fails and the shipment can't be processed automatically.

5. Ship-to address errors

Large retailers like Walmart route shipments to distribution centers, not stores. If the ASN references the wrong DC or an outdated facility code, the shipment may arrive at the wrong location — or the ASN may be rejected entirely.

6. PO reference errors

Your ASN must reference the exact purchase order number from the retailer's 850. If the PO number is wrong, truncated, or formatted differently than expected, the retailer's system can't match the ASN to an open order.

Chargeback Triggers by Retailer

Each retailer enforces their 856 requirements differently. Here's how the major ones compare:

Walmart has the most rigid enforcement. Their Retail Link system automatically flags ASN discrepancies and issues chargebacks without human review in most cases. Their ASN timing window is strict, and SSCC format requirements are specific to their GS1 implementation. Target enforces carton-level accuracy aggressively. Their system uses SSCC scans at receiving to match against the ASN line by line. Discrepancies trigger immediate holds on payment. Kohl's is particularly sensitive to timing. They require ASN transmission before carrier pickup for most vendor programs, which is earlier than most brands expect. Late ASNs at Kohl's are one of the most common chargeback sources we see.

Why Manual ASN Creation Always Fails Eventually

If your team is building ASNs manually — filling in spreadsheets, copy-pasting from packing lists, entering data into a web portal — it's not a question of whether you'll generate chargebacks. It's a question of when.

Manual ASN creation fails for three reasons:

Human error compounds. A single transposed digit in a carton count cascades into a receiving discrepancy. A missed SKU becomes an inventory shortage. A timing slip turns a compliant shipment into a chargeback. Speed requirements aren't compatible with manual processes. When a shipment is ready to go, the warehouse needs to move it. Waiting for someone to manually build and transmit the ASN creates pressure to cut corners or send it late. Retailer requirements change. Walmart, Target, and Kohl's update their EDI specifications regularly. Manually tracking those changes — and updating your templates accordingly — is a full-time job that nobody has.

How Automation Eliminates Every Error Type

A properly implemented EDI automation system eliminates ASN chargebacks by removing human involvement from the ASN generation process entirely.

Here's what automated ASN processing looks like:

Trigger: Your warehouse management system (WMS) or shipping software confirms a shipment and generates a packing list. Data pull: The EDI system automatically pulls the packing list data — carton count, SKUs, quantities, carrier, tracking number — and maps it to the open purchase order. SSCC generation: The system generates valid, GS1-compliant SSCC codes for each carton and links them to the shipment record. Validation: Before transmission, the system validates every required field against the retailer's specific requirements — PO reference, ship-to code, item counts, carton counts, SSCC format. Transmission: The validated 856 is transmitted to the retailer's EDI network immediately upon shipment confirmation — within minutes, not hours. Acknowledgment: The system receives and logs the retailer's functional acknowledgment (997), confirming the ASN was received and accepted.

The result: zero timing failures, zero carton count mismatches, zero SSCC errors, zero PO reference errors. Every field is correct because it's populated from your own shipment data, not entered manually.

The Business Case for Getting This Right

Chargeback rates vary by retailer, but the math adds up fast. A 1-2% chargeback rate on a $500,000 annual retail relationship is $5,000–$10,000 in direct deductions. Add the labor cost of disputing chargebacks, the cost of failed receiving appointments, and the long-term vendor score impact — and a single misconfigured ASN process can cost a brand six figures over the course of a year.

More importantly, vendor scorecards at Walmart and Target are cumulative. Poor ASN compliance scores affect your eligibility for promotional placements, new item reviews, and expanded shelf space. The brands that grow in retail are the ones with the cleanest operational metrics.

The 856 is where that starts.