ASN Receiving Guide for E-commerce 2026

Your warehouse team is standing at the dock with a lorry full of stock. No paperwork. No system notification. Just boxes. That's not a receiving process — that's organised chaos, and it costs you in labor, in errors, and eventually in oversells on channels you can't afford to disappoint.

An ASN receiving workflow flips this entirely. When your supplier sends an Advance Shipping Notice before the lorry even leaves their dock, your team knows exactly what's coming, when it's arriving, and how it's packed — down to the carton level. That visibility is what separates a warehouse that scales from one that perpetually firefights.

This guide covers the full picture: building the workflow from scratch, handling the exceptions that other guides ignore, integrating ASNs with your inventory management system, and measuring whether any of it is actually working.

What is an ASN and Why is it Crucial for 2026 Fulfillment?

An Advance Shipping Notice (ASN) is an electronic notification sent by a supplier to a buyer before a shipment departs — or sometimes while it's in transit. It includes detailed information on the contents of the shipment: which SKUs, how many units, how they're packaged (pallet, carton, or unit level), carrier details, tracking numbers, and expected delivery date. Think of it as a manifest that arrives before the goods do.

The format varies. Traditional retail and wholesale supply chains use EDI 856 — a standardised electronic document exchanged between ERP systems. Smaller suppliers increasingly send ASNs via API integrations or even supplier-facing web portals, where they log in and submit shipment data manually. Each method has trade-offs, which we'll come to.

Here's why this matters in 2026 specifically: fulfillment speed expectations haven't plateaued. Same-day and next-day delivery windows have become table stakes for competitive channels, meaning your dock-to-stock time — the hours between a pallet hitting your receiving bay and those units being available to pick — is directly tied to your ability to meet those SLAs. Manual receiving, where a warehouse operative ticks off a paper delivery note line by line, simply can't keep pace.

And the accuracy argument is even more compelling. Manual receiving typically runs at around 1 error per 100 lines processed. Barcode-scanning against an ASN can drop that to fewer than 1 error per several million scans (a figure frequently cited across warehouse operations literature, including by GS1, the body that governs barcode standards). That's not a marginal improvement — it's a different category of operation.

When we were running our own e-commerce brands, the turning point wasn't some grand technology investment. It was the first time a supplier sent us a clean ASN with GS1-128 carton labels and we processed a 400-unit delivery in under 20 minutes. Before that, the same delivery would take an hour and a half, and we'd still find a unit discrepancy two weeks later during a stocktake.

For brands selling across Shopify and Amazon simultaneously, accurate receiving isn't optional — it's the foundation. If your IMS doesn't know a delivery landed, you're either underselling (leaving money on the table) or overselling (creating cancellations and account health issues).

RFID is still largely out of reach for most SME operations on cost grounds. Barcode scanning against an ASN is the practical sweet spot for brands doing anywhere from 500 to 50,000 inbound units per month.

Step-by-Step: Building Your Barcode-Powered ASN Receiving Workflow

A good ASN workflow has six distinct stages. Miss any one of them and the whole system gets leaky.

1. ASN Creation and Transmission

The ASN originates with your supplier. Your job is to define what data you need and how you want to receive it. At minimum, a usable ASN contains: PO number, SKU codes (ideally GTINs), quantities by SKU, carton count, carton contents, and expected delivery date.

For suppliers equipped with EDI, the EDI 856 Ship Notice/Manifest handles this automatically between systems. For smaller suppliers — and frankly, most SME brands work with a mix — a supplier portal (where they submit a form) or even a structured CSV template sent by email can work. It's less elegant, but if the data fields are standardised, it's processable.

Don't accept a flat "X units of product Y" ASN. Insist on carton-level detail, especially if you're receiving mixed-SKU cartons.

2. Pre-Receiving Validation

When the ASN arrives in your system, it should automatically validate against the open purchase order. Your IMS should flag: are the SKUs on the ASN actually on the PO? Are the quantities within expected tolerance? Is the delivery date within the agreed window?

This is where most operations managers skip a step. They assume the ASN is correct and just wait for the delivery. But a mismatched ASN — a supplier accidentally shipping 500 units of SKU-A when the PO specifies 500 units of SKU-A and 200 of SKU-B — caught at this stage costs you nothing. Caught at the dock? It costs you an hour.

3. Dock Preparation

With a validated ASN in hand, your team can prepare before the lorry arrives. Print or download the expected manifest to a scanning device. Pre-stage your receiving area — if 12 pallets are coming and four are going straight to a dedicated bulk location, assign those locations now. If you're running batch picking operations, you'll also know whether any inbound stock is needed urgently to fill a backorder wave.

4. Physical Receipt and Barcode Scanning

This is the core of the ASN receiving workflow. As cartons come off the lorry, your operative scans each GS1-128 carton label. The scan reads the GTIN (product code), quantity in carton, batch/lot number if applicable, and serial number if required. Your system matches that against the ASN line item and confirms receipt — or throws an exception (more on those shortly).

A decent handheld scanner (Zebra TC-series devices are the industry standard for this, typically £600–£1,200 per unit depending on spec) processes a scan in under a second. For a 400-unit delivery across 20 cartons, the physical scanning stage should take under 10 minutes. That's not an estimate — that's what we see consistently in warehouses running this process properly.

If your supplier labels at the unit level (individual barcodes on each item), you get an extra layer of accuracy. This is worth requiring for high-value SKUs. For bulk commodity items, carton-level scanning is sufficient.

5. Putaway and Location Assignment

Once a carton is scanned in, your system should immediately assign it to a storage location — either a fixed location (same bin every time for that SKU) or a dynamic location based on current bin availability. The operative sees the location on their scanner screen and moves the carton directly there.

This is where dock-to-stock time collapses. No paper. No re-counting. No "leave it in the staging area until someone processes it." It's in the system the moment it's scanned, and it's in a named location within minutes.

6. ASN Closure and Three-Way Match

Once all lines are received, your system closes the ASN and initiates the three-way match: ASN quantity vs. PO quantity vs. supplier invoice quantity. Any variance gets flagged for your finance or ops team. This is where you either approve payment or raise a dispute — cleanly, with a full audit trail.

If you're managing wholesale purchasing across multiple channels, that audit trail becomes especially important when you're reconciling supplier invoices against multiple simultaneous POs.

Handling Exceptions: Managing Discrepancies and Damages

Here's the thing: no guide covers this part well, and it's where most ASN workflows fall apart in practice. Exceptions are not edge cases — they're a regular feature of any receiving operation.

Quantity Discrepancies

Your scanner says 48 units in a carton. The ASN says 50. What happens?

Your system should automatically flag this as a short receipt and hold the ASN line open. Don't close the line and don't just accept 48. The operative notes the discrepancy on the scanning device, photographs the carton if possible, and continues with the rest of the delivery. At the end, your system generates a discrepancy report that lists every short or over-received line. That goes to your supplier within 24 hours — and your contract with them should specify what tolerance you accept (typically ±2% on quantity) before you raise a formal claim.

Over-receipt is less common but also needs handling. If you receive 110 units against a PO for 100, don't just stock them silently. They need to be either returned, held in a designated over-receipt location, or confirmed against an amended PO. Silently absorbing over-receipts is how inventory counts drift.

Item Mismatches

You scan a carton and the GTIN doesn't match any line on the ASN. This happens. Common causes: supplier mislabelled a carton, wrong product shipped, or the carton contains an older version of a SKU with a superseded barcode.

The operative should quarantine the carton immediately — move it to a dedicated exception area, never to a live pick location. Your ops team then identifies the item, either by opening the carton and checking contents, or by contacting the supplier. Don't attempt to manually receive it against a "close enough" SKU. That's how phantom inventory appears.

Damaged Goods

Damage discovered on arrival needs immediate documentation. Photograph everything — the outer packaging, the damage itself, and the carton label showing the GTIN and lot number. Create a damage receipt in your system rather than a standard receipt. Damaged stock should never hit your available inventory pool. Route it to a quarantine or returns location, and flag it for supplier claim or disposal decision.

This matters even more if you're in a regulated category. If you sell products subject to EPR packaging compliance, damaged inbound goods that you end up disposing of can affect your reported packaging volumes — so you need that documentation clean.

ASN-Less Deliveries

Some suppliers — particularly smaller or newer ones — will arrive without an ASN. You have two options: blind receive against the PO (slower, more error-prone, back to manual process) or refuse to process until an ASN is submitted through your supplier portal. Frankly, if you've told a supplier three times that ASN submission is a condition of delivery acceptance and they still don't comply, that's a supplier relationship issue, not a warehouse issue. The warehouse team shouldn't bear the cost of someone else's non-compliance.

Integrating Your ASN Process with Your Inventory Management System (IMS)

An ASN workflow without proper system integration is just a slightly fancier paper process. The integration is where the compounding value lives — because every ASN received cleanly feeds better inventory data across every channel you sell on.

Ceendesis IMS handles ASN receiving natively, linking inbound purchase orders to your live channel inventory across Shopify, Amazon, eBay, Etsy, and Walmart. When a delivery is received against an ASN, those units become available across all channels simultaneously — no manual stock update, no channel-by-channel adjustment.

The integration points you need your IMS to handle:

• PO creation and ASN matching — your IMS should hold the open PO and match incoming ASN data against it automatically
• Scanning device connectivity — via WiFi or Bluetooth, your scanners should push data directly to the IMS in real time, not batch-upload at end of shift
• Location management — your IMS needs to know your bin structure to assign putaway locations at point of receipt
• Multi-channel stock update — the moment a receipt is confirmed, available inventory on all connected sales channels should update
• Supplier portal or EDI connection — for ASN ingestion from suppliers, either via direct EDI 856 feed or a portal interface

If you're evaluating platforms, look at the available integrations — specifically whether the platform can receive ASN data from multiple supplier formats, not just one. Suppliers aren't going to standardise on your preferred format. Your IMS needs to handle the variation.

One common mistake: treating ASN integration as a one-time IT project. It isn't. Supplier data quality drifts. GTINs get updated. New SKUs get onboarded. Your ASN workflow needs an ongoing owner in your ops team who reviews exception rates monthly and pushes back on suppliers whose ASN quality is degrading. Check out our guide to e-commerce workflow automation for how to build that kind of structured ops review into your calendar without it consuming your week.

For operations managers who are also managing stock across warehouses, ASN integration needs to account for inter-warehouse transfers — because an ASN can originate not just from a supplier but from another fulfilment node in your own network.

See our pricing if you want to understand what this costs at different volumes.

Beyond the Basics: Advanced ASN Tactics for 2026

Measuring What Actually Matters

Most brands implement ASNs and then never formally measure the impact. That's a missed opportunity — both for justifying the investment internally and for identifying where the workflow still has friction.

The KPIs worth tracking for an ASN receiving workflow:

• Dock-to-stock time — hours from lorry arrival to units available to pick. Measure per delivery, not just as an average.
• ASN compliance rate — what percentage of inbound deliveries arrive with a valid, pre-arrival ASN? Anything below 85% and you've got a supplier management problem.
• First-scan match rate — of all cartons scanned, what percentage matched the ASN without exception? This is your ASN accuracy metric. Target 98%+.
• Receiving labor cost per unit — total labor hours in receiving ÷ units received. Track this monthly. A well-run ASN workflow should see this fall quarter-on-quarter as the process matures.
• Discrepancy claim rate — how often are you raising claims against suppliers? A rising rate suggests either supplier quality is declining or your own ASN validation is catching things it previously missed (both are useful signals).

Supplier Scorecards

Once you're capturing the data above, building a simple monthly supplier scorecard becomes straightforward. Score each supplier on ASN lead time (did the ASN arrive before the goods?), ASN accuracy (first-scan match rate), and on-time delivery. Share the scorecard with suppliers quarterly. You'll be surprised how fast ASN quality improves when suppliers can see their own data.

Connecting ASN Data to Demand Planning

An underused benefit of clean ASN data is its value for inventory planning. If you know that a specific supplier consistently ships 3–5 days after ASN transmission, and you track that historically, you can build that lead time into your reorder point calculations automatically. Your IMS can use confirmed ASN receipt dates as inputs to adjust safety stock levels dynamically — especially useful for blended JIT and safety stock strategies where timing precision matters.

ASN Data and Returns

If your brand processes significant return volumes, ASN principles apply inbound from your 3PL or returns processor too — effectively a reverse ASN. The 3PL sends you a manifest of what they're sending back before it arrives. Processing returns against a pre-notified manifest is dramatically faster than blind returns receiving. Our reverse logistics guide covers this in more detail.

2D Barcodes and Serialisation

GS1's move toward 2D barcodes (QR and DataMatrix formats, under the GS1 Sunrise 2027 initiative) is relevant here. By 2027, all GS1-compliant barcodes are expected to carry 2D symbology as well as, or instead of, traditional 1D barcodes. For ASN workflows, this means carton labels will increasingly carry richer data — lot number, expiry date, and serial number — in a single scan. Worth reading our 2D barcode fulfillment guide if you're planning a scanner hardware refresh in the next 12 months, because not all current handheld scanners read 2D natively.

Frequently Asked Questions

What is the receiving process with an Advance Shipping Notice (ASN)?

The ASN receiving process starts when a supplier transmits an electronic shipment notification before goods depart their facility, which your system validates against the open purchase order. When the delivery arrives, warehouse operatives scan carton barcodes against the pre-loaded ASN data, with the system confirming each line or flagging discrepancies in real time. The process closes with a three-way match between the ASN, the PO, and the supplier invoice — creating a clean audit trail for payment approval or dispute.

How do you improve warehouse receiving accuracy?

Warehouse receiving accuracy improves most dramatically by replacing manual line-by-line checking with barcode scanning against a pre-loaded ASN. Requiring suppliers to submit ASNs with GS1-compliant carton labels before delivery, and routing any non-matching scans to an exceptions workflow rather than forcing operatives to make judgment calls on the dock, eliminates the main sources of error. Tracking first-scan match rate monthly and sharing supplier scorecards creates ongoing accountability that sustains accuracy gains over time.

What are the 5 steps in the receiving process?

The five steps in a modern ASN receiving process are: (1) ASN creation and transmission by the supplier; (2) pre-receiving validation against the open PO in your IMS; (3) dock preparation using the pre-loaded manifest; (4) physical receipt via barcode scanning with real-time system matching; and (5) putaway to assigned storage locations followed by ASN closure and three-way match. Each step depends on clean data from the previous one — which is why pre-receiving validation is worth doing even when it feels like overhead.

What is the difference between PO receiving and ASN receiving?

PO receiving means operatives check physical goods against a purchase order at the time of delivery — it's reactive, relying on manual counting and comparison at the dock. ASN receiving means the expected shipment data is loaded into your system before the lorry arrives, so operatives are scanning to confirm rather than counting to discover, which is fundamentally faster and more accurate. The practical difference is that PO receiving typically takes 2–4 hours per delivery and runs at around 99% accuracy; ASN receiving with barcode scanning cuts that to under 45 minutes at accuracy rates that approach 99.9999%.

An ASN receiving workflow isn't a nice-to-have for growing e-commerce brands — it's the operational foundation that everything else depends on. Accurate receiving feeds accurate inventory, which feeds accurate channel listings, which feeds your ability to fulfil reliably and avoid the kind of stockout or oversell that costs you both revenue and platform standing. If you're still receiving blind against paper delivery notes, the gap between where you are and where you could be is large, and the fix is less complicated than it looks. See how operations managers use Ceendesis IMS to run this end-to-end — from supplier ASN ingestion through to live multi-channel stock updates.