An Advance Shipping Notice, usually shortened to ASN, is a pre-arrival message that tells a receiver what a supplier or origin says has actually been shipped before the goods reach the receiving site.
It can describe items, quantities, packaging, handling units, expected receipt date, purchase-order references, lot or serial information and other details needed to prepare the inbound process.
The purchase order says what was requested. The ASN says what the sender says is now on the way. The receiving event later says what physically arrived.
This is Article 113 in the extended How Logistics Works series. Warehouse Receiving remains the owner for converting arrival into trusted stock. Shipment Documentation remains the wider document owner. This page owns the pre-arrival information bridge between dispatch and receiving.
The ASN Chain
Order / replenishment requirement → actual shipment built → ASN created → receiver imports or processes ASN → inbound records and receiving work prepared → vehicle arrives → physical receipt verified against ASN → discrepancies recorded → inventory and supplier records updated.
The ASN is therefore a forecast of a specific physical inbound shipment, but it is stronger than a generic ETA because it describes the shipment’s contents and structure.
Modern Warehouse Systems Use ASNs as Receiving Structure
Microsoft’s current 2026 Dynamics 365 Supply Chain Management documentation defines ASNs as messages that notify receivers about vendor deliveries and describe shipment contents such as items, quantities and packaging so warehouse workers can prepare to receive them.
Its 2026 warehouse-only receiving update goes further: ASN packing structures can support receiving by a single license-plate scan when the packing hierarchy is already represented in the ASN.
Oracle’s current 26B Receiving tools similarly expose ASN number, item, quantity, expected receipt date, lot and serial information as structured receiving data.
The ASN Should Be Built From the Shipment That Exists
A weak process copies the purchase order into an ASN before packing and assumes the shipped contents will match the order.
A stronger process creates the ASN from the physical shipment state after the relevant quantities, packaging and identifiers are known.
That matters when:
- the order ships partially;
- one order becomes several shipments;
- several orders consolidate into one load;
- packaging changes;
- serial or lot numbers are assigned during packing;
- a line is short or substituted under an authorised process.
The ASN should describe the shipment, not merely repeat the demand.
Order Quantity, Shipped Quantity and Received Quantity Are Three Different States
| State | Question |
|---|---|
| Ordered | What did the buyer or replenishment process request? |
| Shipped / advised | What does the sender claim has left or is ready to leave? |
| Received | What did the receiving process physically verify? |
These numbers can all differ legitimately. A useful receiving process compares them without silently replacing one with another.
An ASN Can Create the Inbound Delivery Before the Truck Arrives
Current SAP Business Network documentation for 2026 shows ASN creation flowing into a buyer system where an inbound delivery can be created before the physical goods reach the site.
This changes the receiving sequence. Instead of discovering the shipment at the gate, the warehouse can prepare the inbound record in advance.
Preparation can include:
- dock appointment;
- receiving labour;
- storage location planning;
- quality or specialist checks;
- cross-dock destination;
- putaway resources;
- expected inventory visibility.
ASN Data and Delivery Appointment Data Reinforce Each Other
Article 110, Delivery Appointment Management, reserves receiver capacity.
The ASN tells the receiver what that capacity must handle.
A 09:00 booking for one pallet is a different receiving job from a 09:00 booking for twenty mixed pallets requiring lot verification.
Appointment and ASN should therefore share enough identity that changes in one can be reconciled with the other.
Packing Structure Can Turn One Scan Into Many Receiving Relationships
If the ASN says:
Pallet P1 contains Cases C1–C20; Cases C1–C10 contain Product A; Cases C11–C20 contain Product B.
the receiver can scan the pallet identity and recover the expected contents rather than scanning every case merely to discover what the shipper intended.
The physical pallet still needs verification according to the receiving process. The ASN reduces repeated data entry and makes discrepancy checking more structured.
License Plates and SSCCs Make ASN Packing Structures More Useful
An ASN becomes much stronger when the electronic packing hierarchy references stable physical handling-unit identifiers.
For GS1 logistics units, the SSCC provides a globally unique logistics-unit identifier.
The electronic ASN can say which SSCCs are expected. The physical label can carry the SSCC. Receiving can scan the real unit and match it to the expected electronic structure.
ASN Is Not Proof of Physical Receipt
The sender can advise ten cases and accidentally load nine.
The pallet can be damaged after the ASN is transmitted.
The truck can be lost, delayed or diverted.
The receiver must therefore verify physical receipt before inventory becomes trusted usable stock.
ASN = expected inbound state. Goods receipt = observed inbound state.
ASN Is Not Proof of Carrier Custody Either
A supplier can generate an ASN before the carrier picks up.
That can be operationally useful if the process defines the ASN as shipment-ready advice. It should not be interpreted automatically as carrier acceptance or departure.
Keep distinct:
- ASN created;
- carrier collected;
- shipment departed;
- shipment arrived;
- goods received.
ASN Timing Matters
An ASN sent two minutes before the truck reaches the gate provides less preparation value than one sent when the shipment leaves origin.
Useful ASN timeliness metrics can include:
- time from physical dispatch readiness to ASN creation;
- time from ASN creation to receiver processing;
- time from ASN processing to vehicle arrival;
- percentage of arrivals with usable ASN available before check-in.
The optimal lead time depends on route duration and receiving complexity. The principle is to provide enough advance notice for a real decision to change.
An ASN Can Arrive Too Early
If an ASN is created before the shipment is physically final, later changes can make it stale.
The network then needs a correction or cancellation process.
A pre-advice system should distinguish:
- original ASN;
- updated ASN;
- cancelled ASN;
- shipment actually received.
Do not leave two active ASNs describing different versions of the same shipment.
ASN Corrections Need Shipment Identity and Version Control
Microsoft’s 2026 despatch-advice documentation includes processes to update or correct an inbound ASN message.
The practical requirement is that the receiver can determine which advice is current while preserving enough history to explain changes.
For example:
ASN v1: 10 pallets → ASN v2: 9 pallets after one pallet held at origin → physical receipt: 9 pallets.
The final receipt matches the updated advice. The original variance remains visible as a shipment change rather than disappearing.
ASN Completeness Should Be Process-Specific
A simple pallet receipt may need:
- shipment ID;
- supplier;
- PO reference;
- items;
- quantities;
- handling-unit IDs;
- expected arrival.
A controlled or serialised product may need additional lot, serial, expiry or handling information.
Do not demand every possible field from every supplier. Require the data the receiving and compliance processes genuinely need.
ASN Accuracy Should Be Measured Against Receipt
Useful accuracy checks include:
- advised quantity versus received quantity;
- advised handling units versus received handling units;
- advised lot / serial versus received lot / serial where applicable;
- advised ETA / receipt date versus actual arrival;
- advised packaging hierarchy versus physical hierarchy.
The purpose is not to punish every legitimate shipment change. It is to distinguish well-maintained pre-advice from habitual inaccurate advice that forces the warehouse to rediscover inbound truth at the dock.
ASN Quality Can Change Receiving Labour
With trustworthy pre-advice, receiving can focus on verification.
Without it, receiving must also perform data discovery:
- identify supplier and order;
- manually key lines;
- reconstruct handling-unit relationships;
- resolve unknown quantities;
- create inbound records after arrival.
ASN quality therefore changes the amount of information work done at the receiving dock.
Cross-Docking Depends Heavily on Good Pre-Advice
Cross-docking tries to move inbound goods quickly toward outbound demand with little storage.
That requires the warehouse to know before arrival:
- what is coming;
- which orders need it;
- which outbound route will take it;
- which handling units can bypass storage.
A late or inaccurate ASN can turn cross-docking back into receiving, staging and manual investigation.
ASN Supports Putaway Planning Too
When the expected product, quantity and packaging are known, the WMS can prepare storage decisions before arrival.
This can reduce dock dwell when the physical receipt matches advice.
If the ASN is wrong, premature putaway planning can reserve the wrong capacity. The plan should remain conditional until receipt confirms the physical state.
ASN Can Trigger Transport Requirements Too
Current SAP Business Network documentation shows an ASN flowing not only to the buyer’s inbound delivery but also into Business Network for Logistics, where a transportation requirement can be created for the relevant logistics service provider.
This demonstrates how one shipment advice can bridge procurement and logistics coordination when the data model and ownership are explicit.
Do Not Let ASN Become a Supplier Performance Shortcut
A supplier can have excellent ASN accuracy and poor product quality.
Another can have an occasional ASN quantity error and perfect physical delivery.
ASN accuracy is one operational measure. It should not be silently converted into a universal supplier score.
Worked Example: One Pallet Missing Before Arrival
The following is hypothetical.
A purchase order requests 1,000 units packed on ten pallets.
At shipment build, one pallet is held at origin after a packaging check. The supplier ships nine pallets, 900 units.
A weak process sends an ASN copied from the purchase order: ten pallets, 1,000 units.
The warehouse books dock capacity and putaway for ten pallets, then discovers the shortage only at receiving.
A stronger process creates the ASN after physical shipment confirmation: nine pallets, 900 units, with nine handling-unit IDs and the original PO reference.
Receiving now expects the short shipment, allocates nine pallet positions and preserves the open 100-unit PO balance for later replenishment.
When the truck arrives, nine pallets are received. The physical receipt matches the ASN even though the ASN does not match the original order.
The ASN has done its job: it described what was actually sent.
ASN at Three Zoom Levels
One inbound shipment
Does the ASN describe the physical shipment currently on the way closely enough for receiving to prepare and verify it?
One warehouse
Do timely, accurate ASNs reduce data entry, receiving dwell and discrepancy investigation without replacing physical receipt control?
One network
Can suppliers, carriers and warehouses share shipment advice early enough that physical inbound flow is planned before the vehicle arrives?
Hostile Test: “The ASN Says Ten Pallets”
Was the ASN created from actual packing? Did the load change later? Which version is current? Are there ten physical handling units? What does the carrier have? What does receiving observe?
The ASN is evidence of advised shipment state, not an instruction to make the warehouse see what the supplier expected to send.
ASN Audit
- When is the ASN created relative to physical shipment build?
- Does it describe ordered quantity or actual shipped quantity?
- Which shipment identity connects ASN to the physical load?
- Are handling-unit IDs included where useful?
- Is the packing structure represented?
- Are item, quantity and unit-of-measure fields clear?
- Are lot or serial data included where required?
- Is expected arrival information current?
- Can the ASN create or prepare an inbound delivery before arrival?
- Does the dock appointment reference the same shipment?
- How are ASN changes, corrections and cancellations handled?
- Can late ASNs be detected?
- Can stale ASNs be superseded?
- Is physical receipt verified independently?
- Are ASN-versus-receipt discrepancies classified?
- Do recurring discrepancies feed supplier and process improvement?
- Does the ASN reduce receiving work without reducing receiving truth?
Evidence and Further Reading
Microsoft’s current Import inbound ASNs as despatch advice messages documentation explains that ASNs describe vendor-delivery contents such as items, quantities and packaging so warehouses can prepare to receive them. Its 2026 warehouse-only receiving updates use ASN packing structures for more efficient receipt. Oracle’s 26B ASN notification and current receiving APIs expose ASN number, item, quantity and expected receipt date as receiving state. SAP’s 2026 Business Network integration shows supplier ASN creation feeding buyer inbound deliveries and logistics requirements.
Return to the Logistics Hub
Advance Shipping Notice begins Batch 29 by creating an expected inbound state before physical receipt. Return to How Logistics Works for the whole mechanism. Continue next to Logistics Unit Labels | When the Physical Package Must Carry Machine-Readable Truth.
Final compression: an ASN is a pre-arrival promise about the shipment that actually exists, not a copy of what was originally ordered and not proof that the receiver already has the goods. It earns its value by arriving early enough, carrying reliable shipment structure and identifiers, surviving controlled correction and letting the warehouse prepare before the physical load reaches the gate.