Suppliers and ASN

Collaboration with suppliers and timely transmission of an Advance Shipping Notice (ASN) are critical levers for smooth goods receipt. Those who view suppliers merely as procurement sources and only plan goods receipt when the truck arrives lose valuable preparation time, block warehouse capacity, and increase error rates in booking and put-away. Professional supplier management with ASN integration makes goods receipt predictable, measurable, and scalable – whether in your own warehouse or with a 3PL partner.

This guide explains how to build supplier relationships for fulfillment, what data an ASN must contain, which transmission methods are suitable, and how to systematically handle discrepancies between advance notice and actual delivery.

What does ASN mean in goods receipt?

An ASN (Advance Shipping Notice) is an electronic or structured advance notification that the supplier sends to the warehouse before or at the latest when goods are shipped. It contains the essential information about the upcoming delivery: which items in what quantity, on which transport units, with which shipment number, and expected arrival time.

In the fulfillment context, the ASN serves as a bridge between procurement and warehouse processes. The WMS can pre-create deliveries, generate inspection plans, and reserve staff and storage locations. Without an ASN, the warehouse operates blind – every delivery is a surprise.

Important: An ASN does not replace physical goods receipt inspection. It speeds up and refines the process but does not eliminate quantity and quality control at the warehouse.

The role of suppliers in the fulfillment ecosystem

Suppliers are more than purchasing partners. In e-commerce fulfillment, they directly influence:

  • Availability: Delivery times and reliability determine whether stock is ready for shipping in time
  • Data quality: Correct SKUs, EANs, and package information prevent booking errors
  • Process costs: Poorly labeled pallets or missing delivery notes extend goods receipt by hours
  • Customer experience: Delayed or incorrect supplier goods lead to stockouts and delayed customer orders

A mature supplier process therefore includes not only price negotiation but also binding delivery windows, defined labeling standards, ASN requirements, and clear escalation paths for discrepancies.

Supplier classification for goods receipt

Not every supplier requires the same level of attention. A sensible classification by volume, error rate, and strategic importance helps allocate resources effectively.

Supplier class
Characteristics
ASN requirement
Inspection depth
A – Strategic
High volume, critical SKUs, tight delivery times
EDI or API, 24 h before arrival
100% quantity and sample quality inspection
B – Standard
Regular deliveries, moderate error rate
Portal upload or structured email
Quantity check, quality sample
C – Occasional
Rare orders, low risk
Delivery note with barcode list
Quantity check on arrival
D – Problematic
Frequent discrepancies, new partners
ASN mandatory until reclassification
Full inspection of every line item

Mandatory fields of an ASN

A complete ASN must contain at least the following information so that warehouse and WMS can process it automatically:

  1. Supplier number – unique identification in ERP/WMS
  2. Purchase order number (PO) – reference to open procurement
  3. ASN number – unique identifier of the advance notice
  4. Ship date and expected arrival date
  5. Transport mode and shipment number (carrier, tracking)
  6. Line items with SKU, EAN, quantity per line
  7. Pack structure – cartons per line, units per carton, pallet SSCC
  8. Weight and dimensions (for volumetric items)
  9. Batch or serial numbers (if required)
  10. Special instructions – hazardous goods, cold chain, fragile

ASN transmission formats compared

Transmission format
Automation level
Error susceptibility
Implementation effort
Suitability
EDI
Very high
Very low
High
A suppliers
API
Very high
Low
Medium to high
A suppliers
CSV portal
Medium
Medium
Low
B and C suppliers
Manual PDF delivery note
Low
High
Very low
C suppliers

Common ASN errors and their consequences

Suppliers often transmit ASN data incorrectly or incompletely. The most common problems and their impacts:

  • Incorrect SKU mapping: WMS creates delivery with unknown items → manual rework
  • Quantity deviation from PO: booking blocked, quarantine required
  • Missing SSCC numbers: pallets cannot be assigned via scan
  • Delayed ASN: warehouse cannot plan staff, waiting times at the dock
  • Duplicate ASN number: system conflict, delivery rejected
Booking ASN data into available stock without reconciliation with the physical delivery is prohibited. Always inspect first, then book – the ASN is a planning basis, not a booking document.

ASN process from order to put-away

The ideal flow connects procurement, supplier, and warehouse in a seamless chain:

Process flow: ASN-based goods receipt

1
Purchase order (PO)
2
Supplier confirms
3
Shipment and ASN
4
WMS creates GR notice
5
Arrival at dock
6
Goods receipt inspection
7
ASN vs. actual reconciliation
8
Put-away and booking

Step 1: Purchase order and supplier confirmation

After the purchase order is issued, the supplier confirms dates and quantities. Discrepancies become visible here – not only on arrival. The ERP or WMS should maintain open orders as reference for incoming ASNs.

Step 2: ASN receipt and GR notice

As soon as the ASN arrives, the WMS creates a goods receipt notice. Staff, forklifts, and storage locations can be prepared. In cross-docking scenarios, goods are reserved directly for outbound shipment.

Step 3: Physical arrival and reconciliation

During unloading, warehouse staff scan SSCC labels or cartons and reconcile them with the ASN. Discrepancies are documented immediately – over-delivery, short delivery, or wrong item. Only after successful inspection does put-away and booking follow.

Technical integration of suppliers

The choice of transmission channel depends on supplier size, IT maturity, and order volume.

Transmission method
Advantages
Disadvantages
Typical use
EDI (EDIFACT, X12)
Standardized, fully automated, scalable
High setup effort, costs
Large A suppliers, retail chains
REST API / Webhook
Flexible, real-time, modern integration
Individual development per partner
Tech-savvy suppliers, marketplaces
Supplier portal (CSV/XML)
Low entry barrier, centralized maintenance
Manual upload, copy-paste errors
B and C suppliers
Structured email
No IT required at supplier
Parsing error-prone, no real-time
Small suppliers, transition phase

For 3PL scenarios, the technical integration of the fulfillment partner is critical: can they receive ASN data from your suppliers directly, or must you remain in the middle as the merchant?

Tip: Start with a supplier portal for B and C partners before mandating EDI for everyone. A working process with 80% of suppliers beats a perfect EDI setup that only two major suppliers use.

SLAs and supplier agreements

Binding Service Level Agreements (SLAs) with suppliers reduce uncertainty in goods receipt. Important SLA parameters:

  1. ASN deadline: e.g. at least 24 hours before planned arrival
  2. Delivery window: fixed time slots for delivery (e.g. Tue–Thu, 8 a.m.–2 p.m.)
  3. Labeling standard: SSCC, EAN on every carton, pallet label
  4. Deviation tolerance: e.g. max. 2% quantity deviation without inquiry
  5. Response time for errors: e.g. clarification within 48 hours
  6. Consequences: chargeback, priority shift, right to terminate

The SLA definition should be documented in writing in the supplier contract or framework agreement – not only verbally in purchasing.

ASN punctuality by supplier class: A suppliers typically achieve 92% on-time ASN, B suppliers 71%, and C suppliers 34%. After introducing a portal requirement, the rate measurably increases over 12 months – especially for B and C partners.

Checklist: Preparing suppliers for ASN

Use this checklist when onboarding new suppliers or optimizing processes:

  • Supplier number created in ERP/WMS
  • SKU mapping between supplier and internal item numbers verified
  • ASN format and transmission method agreed (EDI, API, portal)
  • Mandatory ASN fields documented and communicated
  • SSCC and carton label standard defined
  • Delivery window and dock capacity aligned
  • Contact person for goods receipt discrepancies named
  • Test ASN run and successfully processed in WMS
  • Escalation process for incorrect ASN or delay defined
  • KPI reporting (ASN punctuality, deviation rate) set up

KPIs for suppliers and ASN quality

Measurable metrics make supplier performance transparent and provide a basis for negotiation:

  1. ASN punctuality: share of deliveries with timely advance notice
  2. ASN accuracy: match between ASN data and physical delivery in percent
  3. GR throughput time: time from dock to booking in available stock
  4. Deviation rate: short deliveries, over-deliveries, wrong items per 1,000 line items
  5. OTIF in goods receipt: On Time In Full – delivered on time and in full

Discrepancy handling ASN vs. actual

1
Discrepancy detected
2
Photo and documentation
3
System hold
4
Supplier notification
5
Resolution (follow-up delivery, credit note, return)

Practical example: ASN in a growing e-commerce warehouse

A mid-sized online retailer with 400 active SKUs and 12 suppliers introduced ASN step by step. First, the three A suppliers (65% of goods receipt volume) received access to a supplier portal. Within three months, average goods receipt time per pallet dropped from 47 to 28 minutes.

The most important success factors:

  • Unified SKU list as download for all suppliers
  • Test environment in WMS for trial ASNs before go-live
  • Weekly ASN reporting to purchasing with discrepancy list
  • Scanner and barcode equipment at every dock for SSCC reconciliation

After six months, B suppliers were required to upload at least structured CSV files. Inventory accuracy rose from 96.8% to 99.1% – a direct contribution to reliable inventory management.

Collaboration with 3PL and supplier ASN

If you use a fulfillment service provider, clarify early who operates the ASN interface. Options:

  • Direct integration supplier → 3PL: supplier sends ASN directly to partner's WMS
  • Merchant as hub: you receive ASN and forward to 3PL
  • Manual via onboarding: small suppliers report deliveries by email to the partner

Onboarding with the fulfillment partner should explicitly cover ASN processes, labeling standards, and escalation paths – not only after the first incorrect delivery.

FAQ: Common questions about suppliers and ASN

Is ASN worthwhile for small warehouses too?

Yes, from around 20 deliveries per week, at least a portal pays off.

Can I start without EDI?

Yes, portal or CSV is sufficient to get started.

What happens with ASN but no physical delivery?

Notice expires after deadline, PO remains open.

Who bears EDI costs?

Subject to negotiation, often shared setup costs.

Must every carton have a barcode?

Recommended from B suppliers, mandatory for A suppliers.

Conclusion

Suppliers and ASN are not purely purchasing topics but central fulfillment building blocks. A timely, complete Advance Shipping Notice transforms goods receipt from reactive unloading into a plannable process with measurable quality. Combined with clear SLAs, appropriate technology, and consistent discrepancy handling, throughput times, inventory errors, and complaint effort decrease – and your warehouse is better prepared for growth and peak seasons.

Related topics

Last updated: July 6, 2026