What is an ASN? Advance ship notices explained for apparel vendors.

What an ASN actually is

An advance ship notice (ASN) - the X12 856 document in EDI terms - is the message a vendor sends a retailer before a shipment arrives, detailing exactly what’s on the way: which purchase orders are being fulfilled, which items in which quantities, packed into which physical cartons, each carton identified by a unique serialised label, travelling on which shipment with which carrier.

It’s the shipping manifest, made machine-readable and sent ahead of the freight. Of the core apparel EDI set covered in our EDI guide - the 850 purchase order, the 856 ASN, the 810 invoice - the ASN is the one that touches physical operations, which is why it’s both the most operationally valuable document and the most error-prone.

Why retailers require it

A retail distribution centre receives hundreds or thousands of vendor shipments weekly. Without advance carton-level data, every receipt means opening cartons, counting contents, and manually matching against POs - slow, expensive and error-prone at scale.

With a valid ASN, receiving becomes scanning: the DC scans each carton’s label, the system looks up that carton’s declared contents from the ASN, and the receipt is booked in seconds. Cross-docking - sending cartons straight from inbound to outbound store lanes without putaway - is only possible when the carton’s contents are known before it arrives. The productivity difference between ASN-receiving and blind-receiving is the reason ASN compliance is a hard requirement at effectively every major retailer, enforced through chargebacks.

The same data serves the retailer upstream of arrival: inbound visibility feeds their inventory planning, store allocation and, increasingly, their customer-facing delivery promises for drop-ship programs.

The 856 structure

The 856 is hierarchical - a nested structure rather than a flat list:

Two standard configurations matter in apparel: standard carton (uniform cartons, one SKU or one fixed prepack per carton, contents identical across cartons) and pick-and-pack (mixed cartons whose contents vary carton by carton, each detailed individually). Retailer routing guides specify which structure they require per program - getting the structure wrong fails validation even when the totals are right.

UCC-128 labels and SSCCs

The ASN’s partner in the physical world is the UCC-128 label (GS1-128 in current standards language) on each carton. Its critical element is the SSCC - serial shipping container code - an 18-digit globally unique serial number for that specific carton.

The contract between label and ASN is exact: every SSCC on a physical carton must appear in the ASN with that carton’s declared contents, and every SSCC in the ASN must be on a carton in the shipment. The DC scans the barcode, the system resolves the SSCC against the ASN, and receiving proceeds automatically. Any mismatch - a label the ASN doesn’t know, an ASN carton that never arrives, contents that don’t match the declaration - breaks the automation and triggers manual handling, which is what the chargeback is pricing.

Label placement, size and format are specified per retailer in their routing guide, down to which corner of the carton and how far from the edges. Pedantic, but scannability at conveyor speed is the entire point, and unscannable labels are charged like missing ones.

The ship-confirm workflow

Clean ASNs are produced by a clean physical workflow, because the ASN is a description of physical packing that has to be true:

1. Pick against the PO - the warehouse picks the ordered items, respecting the retailer’s prepack or unit requirements.
2. Pack and assign cartons - items are packed; each carton gets an SSCC assigned and its actual contents recorded at pack time. This is the step that determines ASN accuracy: contents recorded as-packed are true; contents assumed from the pick list are hopeful.
3. Print and apply UCC-128 labels - generated from the recorded carton data, applied per the routing guide.
4. Ship confirm - the shipment is confirmed with carrier and tracking details, which finalises the shipment-level data.
5. ASN generated and transmitted - built from the recorded shipment-order-carton-item hierarchy and sent via EDI, inside the retailer’s timing window.

The structural point: when carton contents are captured during packing and the ASN is generated from that capture, ASN accuracy is a by-product of the workflow. When the ASN is assembled afterwards from what was supposed to have been packed, accuracy depends on nothing having gone differently on the floor - and something always eventually does.

Timing rules

Retailer requirements vary, but the pattern is consistent: the ASN must be transmitted at or around ship confirmation and must arrive before the freight does. Common formulations in routing guides: “within one hour of shipment,” “prior to arrival at the facility,” or a fixed window after carrier pickup.

Late ASNs - arriving after the physical goods - defeat the document’s purpose entirely: the DC has already had to blind-receive the shipment, and the chargeback reflects that cost. For short-haul lanes the window can be tight: a same-state truck delivery might arrive in hours, which is why ASN transmission belongs in the ship-confirm event itself, not in a nightly batch. Batch-timed EDI transmission is a common and avoidable cause of technically-accurate-but-late ASNs.

ASN chargebacks

The ASN generates more chargebacks than any other EDI document because it has the most ways to be wrong - data, physical, and timing failures all count against it:

• Late or missing ASN - the classic. Flat fees per shipment plus, at some retailers, a percentage of the merchandise value.
• Carton contents vs ASN mismatch - the DC’s audit finds different contents than declared; charged per carton plus rework.
• Label failures - unscannable, misplaced, or wrong-format UCC-128 labels; charged per carton.
• SSCC mismatches - labels not in the ASN or ASN cartons not in the shipment.
• Quantity variances against the PO - over-shipment and under-shipment both trigger handling deductions.
• Structural or validation failures - the ASN rejects at the retailer’s EDI gateway and is effectively missing until corrected.

As covered in the EDI guide, chargebacks land in the payment remittance rather than as invoices, so they erode margin quietly. Vendors who categorise chargebacks monthly consistently find ASN-related triggers at the top of the list - which is actually good news, because ASN failures are the most fixable kind.

Keeping ASNs clean

• Capture contents at pack time. The single highest-impact change: carton contents recorded as physically packed, with the ASN generated from that record. Scan-to-carton workflows make this the default rather than a discipline.
• Transmit on ship-confirm, not in batches. Event-driven ASN transmission eliminates the late-ASN class of chargeback entirely.
• Validate before transmission. PO-level quantity checks, SSCC completeness, and retailer-specific structure rules checked at generation time, when fixing is cheap.
• Keep routing guides current. Retailers revise requirements - label formats, structure rules, timing windows - and notify vendors through portals that someone has to actually read. Assign an owner.
• Reconcile chargebacks monthly by trigger. The categorised list tells you which fix pays most. A vendor whose chargebacks are 70% late-ASN has a one-line fix; a vendor at 70% content-mismatch has a packing-floor fix.
• Test new retailer relationships properly. Certification testing exists to catch structural problems before live orders; rushing it moves the discovery to production, where it’s priced as chargebacks.

None of this is exotic - it’s the workflow-and-discipline layer on top of whichever EDI model (middleware or native ERP) the vendor runs. The vendors whose wholesale margin survives contact with major retail are, almost without exception, the ones whose ASN process is boring, automatic and monitored.

Frequently asked questions