ASN (Advance Shipping Notice) Explained

Almost every conversation about faster receiving eventually arrives at the same realisation: the slowest part of checking in a delivery is not the physical work, it is the not-knowing. A truck arrives, a pallet comes off, and the receiving team has to figure out what it is, whose order it belongs to, how many cartons there should be, and what is inside each one. That discovery work is where receiving time goes. The advance shipping notice, almost always shortened to ASN, removes the discovery by having the supplier tell you the exact contents of the shipment before it physically arrives. This article is part of the wider warehouse automation guide, and receiving is the doorway to everything else in the building, so getting the ASN right is one of the highest-leverage moves a distribution operation can make.

The message up front: an ASN is not a document you file, it is an inbound data feed. When it arrives before the truck, your warehouse system can pre-stage the receipt, reserve the putaway locations, print the labels, and turn arrival into a scan-and-confirm exercise measured in minutes. When it is missing, late, or wrong, receiving falls back to manual discovery and every downstream process inherits the delay.

1. What an ASN is

An advance shipping notice is an electronic message a supplier sends to a customer to declare, in structured detail, the contents of a shipment that is on its way. It is sent at the moment the goods leave the supplier's dock, not when they arrive at yours, which is the whole point: it gives the receiving warehouse a window of hours or days to prepare. In the world of electronic data interchange it is formally known as the EDI 856 transaction, and in modern integrations it is increasingly delivered as an API payload, but the concept is identical regardless of the pipe it travels down.

The distinction worth holding onto is that an ASN is not a purchase order and it is not an invoice. A purchase order is what you asked the supplier to send. An invoice is what the supplier is billing you for. The ASN sits between them and describes what is physically in the truck: this specific shipment, referencing that purchase order, packed into these cartons, containing these items in these quantities, with these serial or lot numbers, arranged in this physical hierarchy. It is the bridge between the commercial order and the physical goods, and it is the single most valuable piece of data a receiving operation can have.

Because it is structured data rather than a printed packing slip, the ASN can be consumed by software the instant it arrives. The warehouse management system can validate it against the open purchase order, flag discrepancies before the goods even ship, generate the expected-receipt record, and pre-allocate putaway locations. None of that is possible with a paper document that a driver hands over at the gate. The value of the ASN is not the information itself, which a packing slip also carries, it is that the information arrives early and in a form a machine can act on.

2. How the ASN flow works

The sequence is straightforward once you see it laid out. The customer raises a purchase order and transmits it to the supplier. The supplier picks and packs the order, and at the point of dispatch generates an ASN describing exactly what has been loaded onto the truck. That ASN travels ahead of the physical shipment, over EDI or an API, and lands in the customer's warehouse management system while the truck is still in transit. The warehouse uses that lead time to pre-stage the receipt: it creates the expected receipt, reserves dock and putaway capacity, and prints or queues the labels it will need. When the truck arrives, the team scans against a receipt that is already in the system, confirms rather than discovers, and checks the load in fast.

The critical property of the diagram is the gap between the two arrows. The ASN, the fast data path along the top, reaches the warehouse before the truck, the slow physical path along the bottom. Everything the warehouse can do in that gap is preparation that would otherwise happen under time pressure on the dock with the driver waiting. Pre-staging is the entire economic case for the ASN. If the notice arrived at the same moment as the truck it would be little better than a packing slip. It is the head start that makes it valuable.

3. What an ASN contains

A well-formed ASN is a nested, hierarchical document. It does not just list items in a flat table; it describes how the shipment is physically built, from the shipment as a whole down through pallets and cartons to the individual items and their serial or lot identifiers. That hierarchy is what lets a receiver scan a single carton label and know everything inside it. The table below sets out the layers of a typical ASN and what each one carries.

The hierarchy row is the one people underestimate. A flat item list is useful, but a properly nested ASN means a receiver can scan a single pallet or carton license plate and the system already knows every item, quantity, serial and lot inside it. That is the difference between counting a shipment and confirming one. The richer the hierarchy the supplier provides, the fewer scans and the fewer opened cartons the receiving team needs. For how that scan actually drives the receipt, see the barcode receiving pillar.

4. Receiving with versus without an ASN

The clearest way to feel the value of an ASN is to walk the same delivery through receiving twice, once with the notice and once without. The physical goods are identical; only the information changes, and yet the two experiences barely resemble each other.

Without an ASN, receiving is a research project performed on the dock while a driver waits and a door stays occupied. With one, it is a verification step. The goods have not changed, but the information that arrived ahead of them converted an open-ended discovery into a bounded confirmation. That is why high-throughput operations treat ASN compliance as a supplier requirement rather than a nice-to-have, and why the ASN is the enabling layer beneath any serious automated goods receiving process.

5. EDI and API delivery of the ASN

The ASN concept is older than most of the systems that consume it, and for decades its native format has been the EDI 856 transaction: a rigidly structured message exchanged over established EDI networks, understood by trading partners across retail, manufacturing and distribution worldwide. EDI 856 is battle-tested, deeply standardised, and still the backbone of large-partner supply chains. If you trade with a major retailer or a large industrial customer, the ASN will almost certainly be an EDI 856, and compliance with its exact structure is often contractual.

Alongside EDI, a growing share of ASNs now arrive as API payloads, typically JSON over HTTPS, pushed to a webhook or posted to an endpoint the moment goods dispatch. The information carried is the same shipment hierarchy; only the transport and encoding differ. APIs bring near-real-time delivery, easier onboarding for smaller partners who never invested in EDI infrastructure, and simpler error handling, at the cost of the deep, universal standardisation that EDI enjoys. In practice most mature operations run both: EDI for the large established partners who mandate it, APIs for newer and smaller suppliers. The choice is rarely all-or-nothing. For the wider trade-off between the two integration styles, see EDI versus API.

The point that matters: the value of an ASN comes from what the warehouse does with it, not from the pipe it arrives on. Whether the notice is an EDI 856 or a JSON webhook, the payoff is identical: structured shipment data landing early enough to pre-stage the receipt. Choose the transport that fits each partner, and put the engineering effort into consuming the data well rather than arguing over the format. This is the receiving edge of the broader warehouse-to-ERP integration picture.

6. SSCC labels and carton hierarchy

The mechanism that connects the electronic ASN to the physical cartons on the truck is the license-plate label, most commonly the Serial Shipping Container Code, or SSCC, defined under the GS1 standards. An SSCC is a globally unique identifier assigned to a logistics unit, a carton or a pallet, and encoded in a barcode on its label. The supplier assigns an SSCC to each packaging unit, references those same SSCCs inside the ASN, and applies the matching barcode labels to the physical units before they ship.

That shared identifier is what makes scan-and-confirm receiving possible. When a receiver scans the SSCC on a carton, the warehouse system looks up that exact code in the ASN it already holds and instantly knows the full contents: which items, what quantities, which serials and lots, and where in the shipment hierarchy the carton belongs. There is no keying, no counting into a form, no opening the box to read a packing list. The label is the link between the data and the metal, and the hierarchy in the ASN means scanning a pallet SSCC can cascade to confirm every carton and item nested beneath it.

This is also why supplier labelling discipline matters so much. An ASN with a perfect hierarchy is worthless if the physical cartons carry mislabelled, duplicated or missing SSCCs, because the scan will not resolve to the right record. The electronic notice and the physical label are two halves of one mechanism, and both halves have to be correct for receiving to stay in confirmation mode rather than dropping back to manual discovery. Getting suppliers to label to the GS1 standard consistently is as important as getting them to send the ASN at all.

7. The honest limits: supplier data quality

Everything above assumes the ASN is accurate, and that assumption is exactly where the concept meets reality. An ASN is only as good as the supplier who generated it, and a wrong ASN can be worse than no ASN at all. If the notice says a carton contains twenty units and it actually holds eighteen, and the receiver trusts the ASN and confirms without verifying, the two-unit shortage flows straight into inventory as fact. The system now believes stock exists that is not on the shelf, and the error surfaces later as a phantom stockout, a failed pick, or a cycle-count mystery that is expensive to trace back to its origin on the dock.

The honest limitation: an ASN moves trust upstream to the supplier. That is a huge efficiency gain when the supplier is reliable and a hidden liability when they are not. Blind ASN-based receiving, confirming without any verification, is only safe with partners whose data quality you have measured and proven. For everyone else you need a middle path: trust the ASN to pre-stage and structure the receipt, but keep a verification step, whether that is scanning every carton, weigh-checking, or sampling, until the supplier has earned the right to be trusted blind.

This is why mature operations grade their suppliers on ASN accuracy the same way they grade them on on-time delivery and quality. A supplier who sends timely, accurate, correctly labelled ASNs can be received on trust with light verification, which is fast and cheap. A supplier whose ASNs are late, incomplete or wrong gets full verification on every receipt, which is slow, and often a corrective-action conversation as well. The ASN does not remove the need to check goods in; it lets you concentrate your checking effort on the suppliers who actually need it and stop spending it on the ones who do not. The technology enables the efficiency, but supplier data discipline is what unlocks it, and no integration effort on your side can substitute for a supplier who cannot pack the truck the way their own ASN says they did.

8. References

The concepts in this article rest on two widely used industry standards, referenced here generically rather than by any specific document version or deep link:

• EDI 856 (Ship Notice / Manifest): the electronic data interchange transaction set that has served as the standard advance shipping notice format across retail, manufacturing and distribution supply chains for decades.
• GS1 standards: the global identification standards body whose Serial Shipping Container Code (SSCC) and barcode specifications define how logistics units are uniquely identified and labelled so that a physical carton can be matched to its record inside an ASN.

Both are living standards maintained by their respective bodies; consult the current published specifications directly when implementing, as the details evolve and the authoritative versions live with the standards organisations rather than in any single article.

Final thoughts

The advance shipping notice is one of those unglamorous pieces of supply-chain plumbing that quietly determines how fast a whole warehouse can run. It carries no exotic technology; an EDI 856 or a JSON webhook is not hard to consume. What it changes is the state of knowledge at the dock. When the warehouse knows exactly what is coming before it arrives, receiving stops being a bottleneck of discovery and becomes a rapid confirmation, and everything downstream, putaway, inventory accuracy, order availability, inherits that head start.

The two things that make it work are equally simple to state and easy to underestimate. First, consume the data well: land it early, validate it against the open order, pre-stage the receipt, and link it to physical scans through SSCC labels. Second, be honest about supplier data quality, and grade your trust accordingly rather than confirming blind. Get both right and the ASN delivers exactly what it promises. It is a small message that, handled properly, is the difference between a receiving dock that discovers its work and one that simply confirms it. For the full picture of how receiving fits the wider operation, return to the warehouse automation guide.

Related reading: Warehouse automation: the complete guide, Automated goods receiving, Barcode receiving, EDI versus API, Warehouse automation and ERP integration.