What Is an Advanced Shipping Notice (ASN)? Benefits, Process, and Key Components

• An advanced shipping notice is an electronic pre-delivery message from a supplier or carrier to a receiver, sent once the shipment leaves and before it lands.
• It typically covers purchase order references, product identifiers, quantities, packaging hierarchy, carrier details and expected arrival.
• Receivers use it to plan labour and dock capacity, then verify goods by scanning against the notice rather than counting blind.
• Senders use it to confirm dispatch, reduce disputes over what was shipped, and meet the trading requirements of large retailers and 3PLs.
• Most advanced shipping notifications are transmitted by electronic data interchange (EDI), commonly the ANSI X12 856 or UN/EDIFACT DESADV message, or by API where both parties support it.

An advanced shipping notice is a standardised electronic document that tells a receiver exactly what is on its way. It is sent by the party dispatching the goods, usually a supplier, manufacturer or carrier, and it is received by the party taking them in, usually a retailer, distributor, warehouse or third-party logistics provider. The notice describes the shipment at the level the receiving warehouse actually works at: not just which products and how many, but how they are packed into cartons and pallets, and which purchase order each line belongs to.

The distinction that matters is timing. An invoice records what to pay for after the fact. A packing slip travels with the goods and is read on arrival. An advanced shipping notice arrives ahead of the goods, which is what makes it operationally useful. It converts an unknown delivery into a planned one.

An ASN is built to be read by a system rather than a person, so its contents are structured and predictable. Most notices cover:

• Sender and receiver identifiers, including trading partner codes and ship-to location
• Purchase order or sales order references so lines can be matched back to what was agreed
• Product identifiers such as SKU, GTIN or barcode number, plus description
• Quantity per line and unit of measure
• Packaging hierarchy: how many units per carton, how many cartons per pallet, and the licence plate or SSCC label on each
• Batch, lot or serial numbers, and expiry dates where the product requires them
• Carrier name, consignment or tracking reference, and number of parcels or pallets
• Dispatch date and expected delivery date or window

Not every trading relationship needs every field. A grocery retailer receiving temperature-controlled stock will insist on batch and expiry data. A homewares distributor may only need order references, quantities and carton counts.

The notice is sent after the shipment is packed and dispatched, and before it arrives. In practice that means it is triggered by the dispatch event: goods are picked, packed, labelled and loaded, and the sending system releases the ASN as the vehicle leaves. For domestic road freight that might give the receiver a day of notice. For sea freight it might be weeks.

Some trading agreements set a minimum lead time, for example requiring the notice at least 24 hours before the booked delivery slot. Sending it too late defeats the purpose, because the receiver cannot act on information that lands at the same time as the truck.

The exchange follows the same four steps in almost every trading relationship, whether the volumes involved are a few pallets a week or thousands of cartons a day.

Step 1: Shipment is prepared

The sender picks and packs the order against the purchase order. Cartons and pallets are labelled, commonly with a Serial Shipping Container Code (SSCC) barcode that acts as a unique licence plate for each unit of packaging. This labelling step matters, because the labels are what the receiver will later scan to match physical goods to the data in the notice.

Step 2: ASN is created and transmitted electronically

Once dispatch is confirmed, the sender's system generates the notice from the pack data rather than from the original order. That distinction is important: the ASN should describe what actually shipped, including short shipments and substitutions, not what was requested. It is then transmitted to the receiver, usually over EDI or an API connection, and lands directly in the receiving system.

Step 3: Receiver prepares for delivery

The receiving warehouse now has a booked, itemised inbound. Teams use it to schedule dock and labour, reserve putaway locations for the volume arriving, flag lines that need quality inspection or quarantine, and update stock control records so demand planning and the order management system reflect what is inbound rather than only what is on hand.

Step 4: Goods are received and checked

On arrival, receivers use mobile barcode scanning to read carton and pallet labels against the notice. Matching lines are confirmed in a few seconds each. Discrepancies, whether short, over or damaged, are raised against a known expectation rather than discovered through a manual count. Once receipt is confirmed, stock is available to sell and the record is ready for three-way matching against the purchase order and invoice.

The fields in an ASN group into three layers. Every layer needs to be present for the notice to be usable at the dock.

Shipment and order details

Product and quantity information

Carrier and delivery information

Advanced shipping notifications pay off on both sides of the transaction, though for different reasons.

Benefits for receivers

Benefits for senders

Better shipment visibility

• Inbound stock becomes visible while it is still in transit, not on arrival
• Planners can promise stock against confirmed inbound quantities
• Delays are identified early enough to act on, because the expected date is recorded and monitored

Improved receiving efficiency

• Dock schedules and rosters are built around known volumes
• Putaway locations are reserved before the goods arrive
• Scanning replaces counting, which cuts both the time and the error rate in the warehouse receiving process

Fewer communication and delivery issues

• One structured message replaces chains of emails and phone calls confirming what shipped
• Short shipments and substitutions are declared upfront rather than found at the dock
• Both parties work from identical data, which removes most of the argument from a claim

An advanced shipping notice only delivers value if it moves between systems without human handling. Emailing a spreadsheet ahead of a delivery is better than nothing, but it still needs someone at the receiving end to open it, interpret it and key it in. That reintroduces the delay and the error rate the notice was meant to remove.

Electronic Data Interchange (EDI) and ASN transmission

EDI is the long-established method for sending advanced shipping notifications. It defines a fixed message format both trading partners agree to, so the sender's system and the receiver's system can exchange data without a person in the middle. Two standards dominate:

• ANSI X12 856 (Ship Notice/Manifest), used widely in North America and by global retailers operating there
• UN/EDIFACT DESADV (Despatch Advice), used widely in Europe, Australia and New Zealand, and supported through GS1 standards

Both carry the same operational content. The choice is usually dictated by the larger trading partner. Alongside EDI, API-based transmission is increasingly common, particularly where a supplier and a 3PL both run cloud platforms and want near-real-time updates rather than scheduled batches.

Automated ASN management

Automation on the receiving side is what turns the notice into throughput. A warehouse management system that consumes ASNs directly can create the expected receipt automatically, generate putaway tasks against reserved locations, and validate scanned labels against the notice line by line. Exceptions are surfaced as they happen rather than discovered at the end of a count. Inbound handling of this kind sits alongside the other key features of a warehouse management system, including picking, putaway and stock control.

On the sending side, automation means the notice is generated from pack data at the moment of dispatch, using the same barcodes applied to the cartons. Because the data comes straight from the pack record, it describes the shipment accurately without anyone assembling it by hand.