Advanced Shipping Notice (ASN 856) for Apparel Wholesale: Compliance, Format, and Common Errors

It is 4:45pm on a Thursday in a New Jersey 3PL. A trailer is loaded for Nordstrom’s Elizabethtown DC, pickup booked for 5:00pm. The EDI coordinator at the brand is still hand-keying carton counts into the middleware portal because the pick deviated from the original allocation. The ASN goes out at 5:42pm, 42 minutes after the trailer rolls. Three weeks later, a $1,250 late-ASN chargeback hits the remittance. The same brand will absorb that same fee, on the same lane, four more times that quarter.

This is the texture of ASN compliance in apparel wholesale. Major US retailers require an ASN (sent as EDI 856) from every vendor before every shipment. The ASN tells the retailer’s receiving system what to expect, in which cartons, with which SSCC labels, against which PO. When the ASN matches the physical shipment, receiving is fast and automated. When it does not, chargebacks accumulate at $250 to $5,000 per error and the brand becomes the vendor that retailers complain about in their quarterly compliance review.

This guide explains what an ASN is, how the EDI 856 structure works, the five most common errors, why they produce chargebacks, and how apparel brands fix the workflow rather than working around it.

What is an Advanced Shipping Notice?

An Advanced Shipping Notice (ASN) is a structured electronic message a brand sends to a retailer before a wholesale shipment arrives. It declares three things in advance: what is coming (PO, SKUs, quantities), how it is packed (cartons, SSCC labels, carton-to-item mapping), and when it will arrive (carrier, tracking, expected delivery date). In apparel wholesale, the ASN is transmitted as an EDI 856 X12 transaction and must land in the retailer’s EDI inbox before the trailer arrives at the DC.

Retailers built their receiving operations around ASNs because the alternative is manual. Without an ASN, a receiving clerk has to open every carton, read the contents, look up the PO, count units, and key everything into the warehouse system. With an ASN, the clerk scans the SSCC label on the carton, the system already knows what is inside, and the entire receipt processes in seconds.

Multiply this across every shipment from every vendor across hundreds of stores and distribution centers, and the operational difference is enormous. Retailers do not negotiate ASN compliance. It is required, it is enforced through automatic chargebacks, and the chargeback structure is published in the retailer’s vendor compliance manual. From the go-lives I have run this year, the pattern is consistent: brands that treat ASN as a paperwork problem stay stuck in chargeback cycles; brands that treat it as a warehouse-data problem exit the cycle in one quarter.

What is the difference between an ASN and EDI 856?

The two terms are often used interchangeably, but they refer to slightly different things.

ASN is the business document. The advanced shipping notice as a concept exists regardless of how it is transmitted. A small brand could theoretically send an ASN by email or fax, though no major retailer accepts this.

EDI 856 is the specific X12 transaction set that carries the ASN over the EDI network. Major US retailers require EDI 856. The format is standardized but each retailer publishes its own implementation guide specifying which segments, fields, and qualifier codes are required.

In practice, when an apparel brand says “we send ASNs to Nordstrom,” they mean “we send EDI 856 messages to Nordstrom’s EDI inbox.” The X12 format is fixed; the retailer-specific implementation guide is where the configuration variance lives, and where most brands get caught.

What goes into an apparel ASN?

An apparel ASN is structured into four levels that nest hierarchically inside the EDI 856 hierarchical loop (HL segment).

Header level (HL01 in EDI 856)

The shipment-level information: who is shipping, who is receiving, when, on which carrier.

• Ship-from and ship-to addresses with retailer-specific facility codes
• Carrier identification and tracking number
• Ship date and expected delivery date
• Total cartons and total units in the shipment
• Reference numbers (BOL, pickup number, delivery appointment)

Order level (HL with PO reference)

For each PO included in the shipment, the order-level reference.

• Original PO number from the retailer
• PO date and PO type (regular, replenishment, drop-ship)
• Department and division codes if the retailer requires them
• Total units and total weight against this PO

Pack level (HL with carton reference)

For each carton in the shipment, the carton-level structure.

• SSCC (Serial Shipping Container Code) barcode, the unique 18-digit identifier printed on the GS1-128 label
• Carton type (master, inner, prepack)
• Carton dimensions and weight
• Carton sequence within the shipment

Item level (HL with SKU detail)

For each SKU within each carton, the item-level data.

• Vendor SKU and retailer SKU (or UPC)
• Color, size, style attributes per the retailer’s data dictionary
• Quantity in this carton
• PO line reference
• Lot or batch number if applicable

The four levels nest: a shipment contains orders, orders contain packs, packs contain items. The receiving clerk scans the SSCC on a carton, the retailer’s system reads the pack-level entry, and the item-level entries tell the system exactly what units to expect inside.

Which ASN errors actually generate chargebacks?

Five errors account for the majority of ASN chargebacks across major US apparel retailers. If you cannot name which of these five is biting you this quarter, you are not running ASN compliance, you are absorbing it.

Error 1: Late ASN

The ASN was not transmitted before the physical shipment arrived. Retailers require ASNs to land in their EDI inbox at least 24 hours before delivery (some require longer, some require the timestamp earlier than physical pickup). When the ASN is late, the receiving system cannot process the shipment automatically and the chargeback fires.

Typical chargeback: $500 to $2,500 per shipment.

Operational cause: ASN generation is manual or batched, not triggered by the warehouse pick-and-pack event. The shipment leaves the warehouse before the ASN is sent.

Fix: ASN generation is triggered automatically by pick-and-pack completion in the warehouse system. The ASN is sent before the carrier picks up.

Error 2: ASN/physical mismatch

The ASN declared one quantity for an SKU; the physical receipt was different. Either the ASN was generated from the original pick list (not the actual ship), or the warehouse picked and packed differently than the system recorded.

Typical chargeback: $250 to $5,000, depending on retailer and discrepancy size.

Operational cause: ASN is generated from the order, not from the actual pick. Last-minute substitutions, partial picks, or carton-content errors are not reflected in the ASN.

Fix: scan-based pick-and-pack. The ASN is generated from scan-confirmed carton contents, not from the order line.

Error 3: Missing or incorrect GS1-128 SSCC labels

The ASN declared a carton with a specific SSCC, but the physical carton has no SSCC label, an unreadable label, or a label with a different SSCC.

Typical chargeback: $100 to $500 per carton.

Operational cause: SSCC generation and label printing are decoupled from the ASN data source. The labels are printed from a different system than the ASN, or labels are printed before SSCCs are assigned.

Fix: SSCC generation, label printing, and ASN generation all read from the same warehouse data. The label that prints on the carton is the SSCC in the ASN.

Error 4: Incorrect carton structure

Prepacks or master cartons did not match the retailer’s spec. A retailer that requires assorted-size prepacks gets a single-size carton. A retailer that requires master cartons of 12 inner cartons gets a different structure.

Typical chargeback: varies; often a percentage deduction or fixed per-shipment fee.

Operational cause: the warehouse system does not enforce retailer-specific carton specs. Pickers pack to a generic standard rather than to the retailer’s requirement.

Fix: retailer-specific pack rules in the warehouse system. The system enforces the correct carton structure at pick time and the ASN reflects the correct structure.

Error 5: SKU/PO line mismatch

A SKU was shipped against a PO line that did not include it. The retailer’s system rejects the line and either chargebacks or refuses receipt.

Typical chargeback: $250 to $1,500 per occurrence.

Operational cause: allocation and substitution decisions made at pick time are not validated against the original PO before the ASN is sent.

Fix: allocation logic that respects the original PO. Substitutions require explicit approval and produce a corrected PO before the ASN goes out.

Why does native EDI beat middleware for ASN compliance?

The architectural difference between native EDI and middleware-EDI matters significantly for ASN compliance. This is where I take a clear position: for apparel brands $5M to $100M with meaningful wholesale volume, native EDI is the operationally cleaner architecture.

Native EDI means the ASN is generated inside the operating record. The same system that holds the wholesale order, the warehouse pick, the carton pack data, and the SSCC assignment generates the ASN from one consistent data source. Retailer-specific implementation guides are configured per retailer. The label that prints on the carton is the SSCC in the ASN. Chargebacks fall to background-noise levels.

Middleware EDI means a third-party vendor (SPS Commerce, TrueCommerce, DiCentral) sits between the brand’s ERP and the retailer’s EDI inbox. The middleware translates the brand’s order/shipment data into EDI 856 format and routes it to the retailer. The model works, but introduces additional failure points: the brand’s ERP and the middleware can disagree about carton contents, label printing happens in a different system than the ASN, and retailer-specific rules require maintenance in two places.

The annual cost of middleware (typically $15K to $40K plus per-retailer setup fees) plus the recurring chargeback cost from integration gaps usually exceeds the cost of an apparel ERP that ships native EDI. Uphance was built native EDI on purpose for this reason.

What does ASN-compliant operations actually require?

For apparel brands shipping wholesale to major retailers, three operational requirements separate compliant from chargeback-prone operations.

Requirement 1: a warehouse system that scans every unit at pick

The ASN is only as accurate as the pick. If the warehouse system does not scan every unit at pick time, the ASN cannot reflect actual physical contents. Scan-based picking is the foundation of every other ASN improvement.

Requirement 2: SSCC generation tied to carton-level pack data

When a carton is sealed, the warehouse system assigns an SSCC, prints the GS1-128 label with that SSCC, and attaches the SSCC to the carton’s pack data. The ASN is generated from this data. The label and the ASN cannot disagree because they come from the same source.

Requirement 3: retailer-specific configuration

Each retailer publishes its own EDI 856 implementation guide. The guide specifies which segments are required, which optional, which qualifier codes apply, which dates and references must be present. Native EDI systems support per-retailer configuration; middleware systems require the configuration in the middleware vendor.

Brands operating at scale across multiple major retailers maintain a configuration matrix: Nordstrom requires X, Macy’s requires Y, Saks requires Z. The operations team treats this as ongoing maintenance work, not as a one-time project.

How does ASN compliance connect to the rest of the EDI lifecycle?

ASN is part of a broader EDI workflow that touches the full retailer relationship.

The retailer sends an EDI 850 (PO) to the brand. The brand acknowledges with EDI 855 (PO acknowledgement). The brand picks, packs, and generates the ASN as EDI 856. The brand invoices with EDI 810 after shipment. The retailer remits with EDI 820.

A brand handling ASN cleanly typically handles the rest of the EDI suite cleanly too, because the underlying operational discipline (scan-based receiving and picking, accurate inventory, retailer-specific configuration, structured workflow) is the same across the suite. A brand with frequent ASN chargebacks typically has chargebacks across the EDI lifecycle.

This maps directly onto the 6 Breakpoints of Apparel Operations framework. ASN failures cluster in Breakpoint 3 (inventory truth gets weaker), Breakpoint 4 (order flow becomes harder to trust), and Breakpoint 5 (warehouse execution gets less predictable). The chargebacks are not a paperwork problem, they are a downstream symptom of those three breakpoints firing together. The fix is operational, not document-specific. Tighten the warehouse workflow, integrate the ASN with the operating record, configure retailer specifics correctly, and the entire wholesale-compliance picture improves together.

Key takeaways

• An ASN is a structured electronic message that tells a retailer what is coming in a wholesale shipment, in which cartons, with which SSCC labels.
• ASN is sent as EDI 856; the two terms are used interchangeably in apparel wholesale.
• The four levels of an ASN are header, order, pack, and item, nested hierarchically.
• Five errors account for most chargebacks: late ASN, ASN/physical mismatch, missing GS1-128 SSCC, incorrect carton structure, and SKU/PO line mismatch.
• Chargebacks run $250 to $5,000 per occurrence and compound across shipments.
• Native EDI in the operating record is operationally cleaner than middleware EDI for apparel brands $5M to $100M with meaningful wholesale volume.
• Three operational requirements separate compliant from chargeback-prone operations: scan-based picking, SSCC tied to pack data, and retailer-specific configuration.

What this means for an apparel operations team

If your wholesale ops team is logging into a chargeback portal every Monday morning to dispute deductions, the workaround tax has already exceeded the cost of fixing the workflow. The honest diagnostic is to pull six months of remittance data, categorize each chargeback against the five error types above, and identify which two are recurring. In most apparel brands I have looked at, two errors account for 70% of the dollar volume, and both trace back to the same root cause: the ASN is generated from order data, not from scan-confirmed carton data.

The fix is sequenced. First, get scan-based picking live in the warehouse, even if EDI stays on middleware temporarily. Second, tie SSCC generation to the carton-seal event so the label and the ASN cannot drift apart. Third, migrate retailer-specific configuration into the system that owns the operating record, so Nordstrom’s qualifier codes and Macy’s department codes live next to the orders they apply to. Fourth, run a 30-day parallel period where you compare ASN data against physical pick data, and close the gaps before turning off the manual checks. The chargeback line on the wholesale P&L is a leading indicator of operational maturity, not a cost of doing business.