Advanced Shipping Notices Explained for Resellers

At 6:30 a.m., a reseller’s receiving dock can go in two very different directions. At one bay, a truck arrives with no reliable shipment notice. A receiver checks cartons against a clipboard, searches for the right purchase order, and sends uncertain items to overflow while someone else recounts the load. At the next bay, the team already knows which pallets are arriving, what each carton contains, and where the inventory should go.

That difference comes from an advanced shipping notice, or ASN. An ASN is a structured electronic message a supplier sends before delivery, describing the shipment, its packaging, its contents, and its expected arrival. Used well, it turns receiving from detective work into a planned workflow. Used as a static form that nobody updates, it creates a different kind of uncertainty.

Table of Contents

• What an Advanced Shipping Notice Really Does
• Inside an ASN Message Structure
  • Why hierarchy matters
• Why ASNs Matter for Multichannel Resellers
• EDI Versus API for ASN Exchange
• Rolling Out ASNs Without a Heavy Mandate
  • A practical rollout sequence
• The Live ASN and Downstream Change Management
• How an OMS Like Ruit Consumes and Generates ASNs
  • Turning data into receiving work
• ASN Pitfalls and a Receiver Readiness Checklist
  • Data errors
  • Label errors
  • Timing errors
• Frequently Asked Questions

What an Advanced Shipping Notice Really Does

An ASN is best understood as a pre-arrival brief for the receiving team. It connects the supplier’s packing activity with the buyer’s warehouse process, so the receiver can compare the expected shipment with the physical shipment before putting goods away.

Without an ASN, the receiver often starts with incomplete information. They may know a purchase order exists, but not which cartons are on the truck, how the goods are grouped, or whether a partial shipment is expected. The result is manual counting, repeated data entry, and delayed decisions about storage.

With an ASN, the warehouse can prepare around known details. The notice can identify the purchase order, supplier, carrier, tracking reference, package identifiers, item quantities, and expected delivery information. The ASN guide from Programmers.io explains that the message can carry shipment-level, order-level, item-level, pack-level, and tare-level data.

Practical rule: An ASN should answer three questions before the truck arrives: what is coming, how is it packed, and what should the warehouse do when it arrives?

The document doesn’t replace the physical receipt. The receiver still scans labels, checks quantities, and records exceptions. The difference is that the system has an expected structure against which those actions can be tested.

That structure also changes labor planning. A warehouse can assign a dock, prepare receiving space, and create putaway work before the trailer is fully unloaded. If a carton is missing or a quantity differs from the purchase order, the receiver can route the problem as an exception instead of discovering it after inventory has already been mixed into storage.

For a multichannel reseller, this matters because inbound accuracy affects every downstream channel. An incorrect receipt can leave inventory unavailable, create an oversell on a marketplace, or force a team member to investigate a discrepancy long after the supplier has closed the shipment.

Inside an ASN Message Structure

The easiest way to understand an ASN is to follow one shipment from its smallest physical unit to the complete delivery.

Start with a carton or case. At this level, the notice can identify the SKU, quantity, lot number, and expiry date. For a supplement shipment, one case of vitamin bottles might contain a specific SKU, a defined number of units, lot LOT-A1, and an expiry month. That information lets the receiver decide whether the goods can go directly to available stock, require a short-dated review, or need a specific rotation rule.

Next comes the pallet or tare level. A pallet has a unique container identifier, commonly an SSCC or GS1-128 label, and the ASN can show how many cartons it carries. The pallet identifier becomes the bridge between the electronic record and the physical object at the dock. Scan the label, and the warehouse can retrieve the expected carton and item hierarchy.

At the top sits the shipment level. This can include the supplier identifier, purchase order reference, shipment reference, expected delivery information, carrier, and tracking details. The system uses this layer to connect the physical delivery with the commercial order and the transport movement.

Why hierarchy matters

A flat list might say that a supplier shipped vitamin bottles. A hierarchy says which cartons contain which items, which cartons sit on which pallet, and which pallet belongs to which purchase order. That relationship is what makes automated matching and selective receiving possible.

In North America, suppliers typically transmit ASNs as ANSI X12 EDI 856. In Europe, the common equivalent is EDIFACT DESADV, as outlined in the 856 mapping examples guide. The transport format matters for compatibility, but the operational value comes from accurate relationships between shipment, order, package, and item.

A reseller platform can use those relationships to prepare an inbound receipt, identify expected cartons, and create SKU-level putaway suggestions. If the shipment contains a dozen cases on one pallet, the receiver shouldn’t need to open every case to discover what was supposed to be inside. The scan should expose the expected contents, while the physical check confirms whether reality matches the notice.

Why ASNs Matter for Multichannel Resellers

For a reseller, the main benefit isn’t the message itself. It’s the control it creates between arrival, receipt, and available inventory.

Suppose a supplier sends mixed cartons for several marketplace listings. Without structured advance data, the receiving team may count units manually, identify products by sight, and enter totals after the fact. With an ASN, the team can match the delivery to the purchase order, scan package identifiers, and route discrepancies before putaway. The receiving process becomes a comparison rather than a reconstruction.

The hierarchy creates different operational benefits at different levels:

• Carton detail: Supports SKU, lot, and expiry checks, which helps route goods according to inventory rules.
• Pallet identifiers: Let the warehouse recognize a complete handling unit and prepare dock or staging space.
• Shipment detail: Connects the delivery to the supplier, purchase order, carrier, and expected arrival.

Industry guidance recommends validating duplicate carton identifiers, missing mandatory fields such as lot numbers, and differences between shipped quantities and purchase orders. The Produce Traceability Initiative ASN guidance also describes ASN reporting as a way to measure shipment timeliness and accuracy, making the notice useful for supplier performance management.

Metric	Without ASN	With ASN
Receiving preparation	Team discovers contents at the dock	Team prepares around expected contents
Quantity control	Manual count and later reconciliation	Electronic comparison with the purchase order
Package identification	Cartons may need manual sorting	SSCC or GS1-128 labels can identify handling units
Lot and expiry handling	Information may arrive after receipt	Data can guide routing before putaway
Supplier review	Problems are reconstructed later	Timeliness and accuracy can be tracked from shipment records

The same logic applies to packaging. Carton dimensions, pallet composition, and labeling decisions affect scanning, staging, and storage, so resellers can use practical procurement packaging insights when defining supplier requirements.

ASNs won’t solve poor packing or inaccurate master data by themselves. They give the receiving team a dependable expectation, then make deviations visible while there’s still time to act.

EDI Versus API for ASN Exchange

An ASN is the business document. EDI and API are delivery methods for moving that document between systems.

EDI 856 is the established route for large trading relationships. It uses agreed structures, partner mappings, acknowledgments, and controlled transmission processes. Think of it as a standardized postal network. It can be dependable and governed, but every trading partner may bring its own implementation rules.

An API is more like a direct courier. A supplier platform sends structured data, often as JSON, to an endpoint, and the buyer’s system can respond immediately. Webhooks can also notify the receiving platform when a shipment status changes.

Attribute	EDI 856	API or JSON
Setup	Formal partner mapping and testing	Direct integration with defined endpoints
Speed	Depends on transmission and processing cycles	Can support near-real-time exchange
Governance	Strong fit for mandated retailer workflows	Requires clear authentication and validation rules
Error handling	Uses acknowledgments and partner processes	Can return immediate validation responses
Small supplier fit	Often heavier for low-volume partners	More accessible when a supplier already has a modern platform
Best use	Buyers with strict trading-partner requirements	Flexible reseller and supplier ecosystems

A reseller shouldn’t choose a format based on fashion. If a retail customer requires EDI 856, that requirement controls the decision. For suppliers without EDI capability, a portal, CSV upload, or API can provide structured data without forcing a full EDI project.

The OMS should normalize both inputs into one internal ASN model. That prevents warehouse users from learning separate receiving workflows for each supplier. Resellers connecting multiple sales channels can also review Shopify, Wallapop, Vinted, and eBay integration considerations when deciding where inbound and outbound order data should converge.

Rolling Out ASNs Without a Heavy Mandate

A blanket ASN mandate sounds tidy, but it often creates the wrong first project. A low-volume supplier may not have an ERP, may rely on spreadsheets, or may face integration fees that make the relationship less profitable. Forcing every partner into EDI before the warehouse has proved the workflow can waste effort and create resistance.

A better starting point is the 20% of suppliers responsible for 80% of inbound volume or risk, a tiered rollout recommendation described in the ASN glossary from SGS Global. Begin with suppliers whose shipments create the most receiving work, compliance exposure, or inventory uncertainty.

A practical rollout sequence

1. Discover the pressure points. Review inbound volume, frequent discrepancies, short-dated products, and suppliers that create repeated manual work. Define the fields receiving needs, rather than copying a large partner specification without review.

2. Pilot with strategic suppliers. Ask selected suppliers to generate ASNs from their pack-out process. Accept EDI or API where available, then offer a portal or structured CSV route for partners that need a lighter entry point.

3. Expand by operational value. Add suppliers when the warehouse can show that the pilot produces usable receipts, reliable scans, and actionable exceptions. Supplier onboarding should include label examples, required fields, timing rules, and a named contact for corrections.

4. Mandate selectively. Require structured ASNs on lanes where volume, risk, or customer compliance justifies the requirement. Keep a manual lane for the long tail, but make it visible, controlled, and progressively smaller.

The key exit test isn’t whether every supplier has signed an ASN policy. It’s whether the notice is accurate enough to support receiving decisions. Validation should check package IDs, required lot or expiry data, purchase order quantities, and shipment status before the warehouse depends on the message.

Commercial principle: Ask suppliers to solve the operational problem with you. Don’t begin by selling them an integration burden.

The Live ASN and Downstream Change Management

A shipment notice shouldn’t be treated as a fire-and-forget document. Once the carrier collects the goods, the shipment can change, and the warehouse needs those changes to reach the same operational record.

The lifecycle usually has three important moments:

• Initial shipment notice: The supplier reports what was packed and dispatched.
• In-transit update: A carton is cancelled, a shipment is split, or the carrier reports a delay.
• Delivery confirmation: The final shipment state is reconciled when the goods reach the dock.

An in-transit change can affect labor immediately. If a supplier removes one carton from the shipment, the warehouse may reduce expected receiving work and avoid creating a false shortage task. If the supplier splits the delivery, the system should preserve the relationship between the original purchase order and each resulting receipt.

Pallet and carton identifiers make these updates useful on the floor. A scanned SSCC label can direct the receiver to the current contents of that handling unit, while lot and expiry data can support rotation, FEFO, and recall preparation. The transport format is secondary if the data is incomplete or stale.

SAP Business Network’s release notes for supply-chain collaboration describe ship-notice updates using freight-collaboration inputs such as bill of lading, carrier, delivery date, service level, and transit direction. That points to a broader role for the ASN as a synchronized execution record rather than a one-time alert.

The receiving OMS must therefore show changes as tasks. “Quantity reduced” should route to an exception queue. “Delivery delayed” should update dock planning. “Carton cancelled” should alter expected receipt contents. Silent version changes are dangerous because they leave warehouse users working from an outdated picture.

For teams managing customer deliveries across several channels, order tracking documentation provides useful context for treating status events as operational work rather than passive history.

How an OMS Like Ruit Consumes and Generates ASNs

An OMS should turn an ASN into warehouse actions, not merely store the original message. The inbound flow starts when a supplier sends shipment data through EDI, an API, a portal upload, or a structured file.

The system first identifies the supplier and purchase order. It then validates the notice against open order lines, expected quantities, package identifiers, required dates, and any lot or expiry rules. A failed check should return a clear reason, such as an unknown SKU, a duplicate SSCC, or a quantity that cannot be reconciled with the order.

Turning data into receiving work

After validation, the OMS can create a planned inbound receipt and expose concrete instructions to warehouse users:

• Dock assignment: Associate the shipment with the expected receiving area or appointment.
• Carton expectation: Show the number of cartons or pallets the receiver should scan.
• Putaway guidance: Use SKU, lot, expiry, and storage rules to suggest the next location.
• Inventory posting: Update stock when the physical carton scan confirms receipt, not merely when the ASN arrives.

Consider a drop-ship order containing 12 units across 3 cartons. The outbound notice should identify the customer order, the three carton IDs, the SKU and quantity in each carton, the carrier and tracking reference, and the destination partner. If one carton contains four units, the ASN should preserve that carton-level relationship instead of reporting only a total of 12.

On the outbound side, the OMS can generate the notice after pick completion and cartonization, then add carrier details when the shipment is handed over. The notice tells a marketplace, wholesale partner, or fulfillment location what to expect and how to reconcile the delivery.

The same platform should support different exchange methods while presenting one internal workflow. Guidance on complete 3PL setup for Shopify can help teams think through the wider connection between storefront orders, fulfillment partners, and shipment data. For broader operational control, a cloud-based order management system can provide the central layer where purchase orders, receipts, inventory, and outbound notices meet.

ASN Pitfalls and a Receiver Readiness Checklist

Most ASN failures fall into three groups: data errors, label errors, and timing errors. Each category needs a system check and a clear owner.

Data errors

A supplier may send a SKU that doesn’t match the buyer’s item master, a quantity that exceeds the purchase order, or a notice without a required lot number. The OMS should validate identifiers, quantities, mandatory fields, duplicate package IDs, and order status before creating a receivable.

Label errors

A correct ASN still fails on the dock if the receiver can’t connect it to the physical carton. Require scannable SSCC or GS1-128 labels where the workflow depends on package-level identification. The scan should retrieve the expected contents and stop the process when the label is missing, duplicated, or assigned to another shipment.

Timing errors

A notice that arrives after the truck is unloaded can’t support labor planning. One that’s created before packing is final can become inaccurate when the supplier changes quantities or cartons. Set a timing rule around the supplier’s actual dispatch event, then require updates when the shipment changes in transit.

Use this readiness checklist before onboarding a supplier:

• Match the purchase order: Confirm supplier, PO, SKU, quantity, and shipment reference.
• Validate mandatory data: Reject missing lot, expiry, carton, or carrier fields where those fields are operationally required.
• Enforce label scans: Make the physical package identifier the link between the dock and the electronic receipt.
• Create putaway work: Generate location or handling instructions from the accepted receipt.
• Route exceptions: Send mismatches to a named queue with a reason, owner, and resolution status.
• Track supplier quality: Review shipment timeliness and accuracy as part of supplier management, not just receiving administration.

Receiving desk summary: Accept only notices that match the open order, identify the physical packages, arrive in time to prepare the dock, and update when the shipment changes.

Frequently Asked Questions

What is an advanced shipping notice (ASN)?

An ASN is a structured electronic message a supplier sends before a shipment arrives, describing what was packed, how it’s packaged, and when it’s expected. It lets the receiving team prepare the dock, staging space, and putaway work around known details instead of discovering the contents when the truck arrives.

What information does an ASN usually include?

A well-formed ASN carries data at three levels: shipment (supplier, purchase order, carrier, tracking, expected delivery), pallet or tare (a unique container identifier such as an SSCC), and carton or case (SKU, quantity, lot number, and expiry date). That hierarchy is what lets a warehouse match the physical delivery to the electronic record instead of opening every case to find out what’s inside.

What’s the difference between EDI and API for sending ASNs?

EDI and API are both delivery methods for the same document. EDI 856 is the established route for large trading relationships, with agreed structures and acknowledgments, while an API sends structured data such as JSON directly to an endpoint and can support near-real-time exchange. A retail customer’s mandate usually decides which one applies; an OMS should normalize both into one internal ASN model either way.

Do I need EDI to start using ASNs with my suppliers?

No. EDI 856 fits buyers with strict trading-partner requirements, but a supplier without EDI capability can still send structured shipment data through a portal, a CSV upload, or an API. Forcing every partner into EDI before the workflow is proven tends to waste effort, which is why a tiered rollout starting with high-volume or high-risk suppliers works better than a blanket mandate.

What happens if the ASN doesn’t match what actually arrives?

The receiver still scans labels, checks quantities, and records exceptions against the physical shipment — the ASN sets the expectation, it doesn’t replace the count. A mismatch, such as a missing carton or a quantity that differs from the purchase order, should route to an exception queue with a reason and an owner instead of being discovered only after the inventory is mixed into storage.

---

Ruit helps professional resellers centralize inventory, orders, marketplace operations, accounting, and analytics in one platform, so shipment and stock information doesn’t remain scattered across disconnected tools. Visit Ruit to see how a unified operating system can support cleaner inbound workflows and more reliable multichannel fulfillment.