Deutsch Deutsch English English

ASN and Advance Shipping Notice

An Advance Shipping Notice, usually abbreviated as ASN, is the structured advance information about an upcoming delivery. In fulfillment, it is a central building block between procurement, supplier, warehouse, and IT systems. Before the goods physically arrive at goods receipt, the warehouse already knows relevant data such as notice number, estimated arrival time, packages, item lines, quantities, batches, or serial numbers. This pre-availability of information is exactly what makes ASN a lever for speed, transparency, and quality.

In day-to-day operations, the quality of the ASN determines whether a team can book goods within a few minutes or falls into manual clarifications. A good ASN reduces search effort, lowers error rates, and improves the management of docks, staff, and putaway. At the same time, it is an integration point between ERP, WMS, carrier systems, and marketplace or shop processes.

What exactly is an ASN?

An ASN is not just an email update, but a standardized data record for the delivery event. Depending on technical maturity, it is transmitted via EDI, API, or structured file formats. The goal is always the same: the recipient should be able to prepare, validate, and accelerate goods receipt.

Typical ASN contents

  • Unique references such as ASN number, purchase order number, delivery note number
  • Supplier and recipient data including location reference
  • Estimated arrival time and, if applicable, time window
  • Packing hierarchy, for example pallet, carton, and line-item level
  • Item master data such as SKU, EAN, batches, best-before date, or serial numbers
  • Quantity details per line item and per loading unit
  • Shipping-related information such as carrier, tracking references, or labels

Distinction from related terms

Many teams confuse ASN with a delivery note or tracking event. The difference is operationally relevant:

  • The delivery note is often only available with the shipment and is frequently paper-based.
  • Tracking shows the movement status of a shipment, but not necessarily the complete line-item content structure.
  • The ASN arrives before delivery and represents the expected target state for goods receipt.

Why ASN is so important in fulfillment

The biggest effects occur where many line items, short throughput times, and high SKU variance come together. A warehouse without reliable advance data works reactively. A warehouse with ASN works in a planned manner.

Operational advantages

  1. Faster goods receipt: Teams can pre-plan gates, staff, and scanning processes.
  2. Higher data quality: Target-vs-actual comparisons become possible at system level.
  3. Fewer booking errors: Structured line items reduce manual input.
  4. Better putaway control: Storage zones and priorities can be assigned in advance.
  5. More transparency: Procurement, service, and planning can see earlier what is actually coming.

Economic effects

  • Lower process costs per goods-receipt line item
  • Reduced clarification cases with suppliers
  • Faster goods availability for sales
  • Fewer out-of-stocks due to more precise inventory visibility

Process in detail: from shipping confirmation to booking

1
Purchase order approved
2
Supplier packs goods
3
ASN is created
4
Transmission via EDI/API
5
Pre-check in WMS
6
Physical goods receipt and scan
7
Target-actual comparison and posting

Practical step sequence in the warehouse

  1. ASN arrives in the system in advance and is technically validated.
  2. WMS assigns the ASN to an open purchase order or expected receipt.
  3. Upon arrival, the delivery is scanned at package or line-item level.
  4. System checks differences in quantity, batch, serial number, or damage.
  5. Deviations are handed over to defined clarification workflows.
  6. Correct line items are posted and, if required, immediately released for picking.

Mandatory data and quality criteria for reliable ASNs

An ASN is only valuable if it arrives consistently, on time, and completely. In many projects, exactly these three criteria are the bottleneck.

Minimum data-set requirements

Data field
Mandatory level
Benefit in goods receipt
Risk if missing
ASN number
Mandatory
Clear identification and traceability
Duplicate capture and assignment errors
Order reference
Mandatory
Automatic assignment to procurement
Manual research and delay
SKU + quantity
Mandatory
Target-actual comparison per line item
Misbookings and inventory deviations
Package structure
Recommended
Faster scan at carton or pallet level
Higher manual effort
Batch / best-before / serial
Depends on goods
Compliance and traceability
Regulatory and operational risks

Maturity checklist for ASN capability

  • Suppliers send ASN before goods receipt, not only upon arrival.
  • Mandatory fields are jointly defined and versioned.
  • Validation rules in the WMS are active and documented.
  • Deviation process with roles and response times is established.
  • KPI monitoring for ASN quality runs monthly.
The best ASN strategy combines clear mandatory fields, fixed transmission times, and strict validation rules. Only this combination scales during peak periods.

EDI, API, and integration standards

In practice, there are three dominant integration paths: classic EDI, API-based near-real-time integration, and file-based exchange. Which variant fits depends on supplier maturity, volume, and IT landscape.

Integration path
Strengths
Typical limits
Suitable for
EDI (e.g. DESADV)
High standardization, stable at large volumes
Setup is often more complex, partner coordination required
Mature suppliers and multi-site operations
API
Fast feedback, flexible extension
Depends on API quality and monitoring
Dynamic, digitally strong partner networks
File-based (CSV/XML)
Quick start with low setup effort
Error-prone when schema changes
Onboarding phase and smaller partners

Technical best practices

  • Use a clear versioning strategy for message formats.
  • Separate technical validation errors from business deviations.
  • Implement idempotent processing so duplicates do not trigger double postings.
  • Measure latency between ASN receipt and physical goods receipt.
  • Establish alerting for missing or heavily delayed ASNs.

Common errors and how teams avoid them

The most common error is not missing technology, but unclear responsibility: who maintains mandatory fields, who checks quality, who escalates when deviations occur?

Top error patterns

  • ASN arrives after the goods have arrived.
  • Quantities are correct at header level, but line-item data is missing.
  • SKU mapping is not synchronized between supplier and WMS.
  • Batch or serial number is in the wrong format.
  • Multiple ASNs reference the same order without clean partial-quantity logic.

High-impact countermeasures

  1. Partner onboarding with test cases: Mandatory test matrix per supplier before go-live.
  2. Schema governance: Centrally document and version field definitions.
  3. Automated plausibility checks: Strict rules for mandatory data and quantity logic.
  4. Deviation dashboard: Triage by criticality and supplier frequency.
  5. Regular retro sessions: Review top causes and corrective measures monthly.

KPI set for ASN performance

So that ASN does not remain only an IT topic, it requires clear metrics with target values and escalation thresholds.

KPI
Definition
Target range
Control benefit
ASN timeliness
Share of ASNs received before arrival
> 95 %
Planning reliability for dock and staff
ASN completeness
Share of ASNs without missing mandatory fields
> 98 %
Reduction of manual rework
Line-item accuracy
Match between ASN line item and goods receipt
> 99 %
Inventory quality and availability
Clarification rate
Share of deliveries with a deviation case
< 3 %
Supplier management and process maturity
Show a 12-month monthly trend for timeliness, completeness, and clarification rate. Three lines in the chart, with a red marker when defined thresholds are undershot.

Implementation in 90 days: realistic roadmap

Day 1-30
Data model, mandatory fields, test cases, and pilot supplier
Day 31-60
WMS validation, monitoring, deviation workflow
Day 61-90
Rollout to additional suppliers, KPI target values, governance cadence

Concrete 90-day plan

  1. Define scope: which suppliers and which product groups first.
  2. Jointly approve mandatory fields and format rules.
  3. Define technical channel per partner (EDI, API, file).
  4. Run pilot operation with real special cases.
  5. Set up KPI dashboard and assign owners.
  6. After pilot, roll out to additional suppliers.
Start with the suppliers that account for the largest share of goods receipt volume. This is where the benefit of ASN implementation becomes visible fastest.

Conclusion

ASN and Advance Shipping Notice are a strategic lever in fulfillment because they directly connect operational speed and data quality. The greatest added value is achieved when process, data model, and governance are designed together. Teams that establish ASN as a mandatory standard accelerate their goods receipt, reduce error costs, and create a reliable foundation for scaling, multi-channel operations, and better delivery performance.

Related topics

Last updated: July 6, 2026