Think of it this way: you order takeout, and the restaurant texts you "rider arrives in 5 minutes, two mains and a side, packed in three bags." You clear the table, get the change ready, send someone downstairs. An ASN — advance ship notice — is that text message, sent by the supplier to your warehouse: the goods have not arrived yet, but their resume already has.
You can think of it as the difference between opening a blind box and checking goods against a packing list. Same truck, wildly different cost. This piece is not about commercial terms or supplier chargebacks — that belongs in a supplier compliance manual. This is about execution: once the ASN lands in your inbox, what exactly can the receiving team do with 24 hours of lead time?
The ASN is the freight's resume: the only fields receiving actually uses
An ASN carries dozens of fields, but a receiving team needs at most eight. Here they are, ranked by usefulness:
| ASN field | What receiving does with it | Data quality bar |
|---|---|---|
| ETA | Shift scheduling, dock appointments, staggering arrivals | Accurate to the half-day; "arriving this week" is the same as nothing |
| SKU + quantity | Labor planning, pallet staging, pre-assigning putaway slots | Line-item accuracy ≥95% (more on this number later) |
| Pallet / carton count | Forklift booking, unload-time math | Off by more than 2 pallets and the schedule breaks |
| Lot / expiry date | Food, cosmetics, pharma: FIFO needs this | One date format, no mixing day-month-year |
| SSCC (pallet license plate) | Scan-and-receive, full-pallet no-count | Must match the physical label one-to-one |
| Case pack spec | The denominator for inspection sampling | If the case pack changed and nobody said so, all sampling is wrong |
| PO number / supplier | Order matching, exception tracing | Unique, no one-order-many-numbers |
| Special handling (temp-controlled/fragile) | Reserve cooler slots, prep bumpers | State it if it exists; do not invent it if it does not |
See the pattern? The value of an ASN is not "knowing freight is coming." It is "knowing what the freight looks like." Putaway slots are prepared for the shape of the goods, not for the arrival time of the truck. Plenty of warehouses get this backwards: big money on system integration, the ASN lands in the system and sits there, and the receiving team still calls the driver asking "where are you?" That is a fake requirement, and I have no patience for those projects — the system is not the problem; nobody using it is.
During the 2024 Singles' Day peak, a 3PL warehouse in eastern China serving three brands had 38 trucks arrive on November 10. Their internal review produced one telling comparison: trucks with a complete ASN averaged 25 minutes from dock-in to release; trucks without one averaged 1.5 hours. ASN trucks had putaway slots assigned two hours ahead and pallet labels pre-printed — unload and go. No-ASN trucks went: unload, count, ask "what is this," hunt for a slot. Over one shift, ASN windows processed 20 pallets per labor-hour; no-ASN windows managed 8.
The 24-hour receiving prep list: labor, slots, and pallets
Once the ASN is in hand, the receiving team has three jobs to do 24 hours ahead. Each one is a cost equation.
Job one: staff the shift. The formula is simple:
Labor hours needed = expected inbound pallets ÷ receiving productivity per labor-hour
Use your own measured productivity, not someone else's. The 3PL above measured 20 pallets per labor-hour for full-pallet receiving (system check-in plus labeling). Expecting 120 pallets means 6 labor-hours — three people for two hours, or two people for three. Loose cartons that need breakdown and piece-counting run at roughly a third to a half of full-pallet speed; measure your own.
Job two: stage the slots. Pre-assign putaway by the ASN's SKUs and quantities: big and heavy goods to low levels near the dock; short-expiry SKUs to the front of the pick zone; slow movers nowhere near prime slots. The principle is "loose first, tight later" — zone by category first, pin the exact slot when the goods land. If ASN accuracy clears the 95% bar (below), pre-assign precisely; if not, zone only and hold 20% of slots as flex.
Job three: stage pallets and consumables. Empty pallets, stretch film, and label stock, sized to the ASN's pallet count. Sounds trivial — I have watched a peak-season line stop three times for lack of pallets. Pallets take up space when you do not need them and stop the whole warehouse when you do.
Done right, receiving turns from firefighting into plan execution. In April 2025, a maternal-and-baby brand's east-China warehouse showed me their morning huddle sheet: every day at 8 a.m., the receiving lead reads off the ASN list — "six trucks today, 214 pallets, three expiry-date SKUs, two fragile pallets" — and labor, slots, and consumables are all settled. Overtime in receiving fell 40% over the year (their internal HR data).
The selection threshold: what inbound volume justifies pre-arrival ASN management
Straight to the threshold, no circling.
Under 5 trucks a day: skip the system. A spreadsheet plus a group chat is enough — suppliers send a one-day-ahead arrival sheet (date, SKU, quantity, pallet count) to the chat, and the receiving lead schedules from it. Near-zero investment, 70% of the benefit.
Five to 20 trucks a day: lightweight ASN is worth it. Get your core suppliers — the few that make up 80% of inbound volume — to send a fixed-template spreadsheet or email, and write a small script to parse it into the WMS. Start with the top suppliers; do not demand EDI from everyone on day one.
Over 20 trucks a day, or more than 5,000 SKUs: go formal with EDI 856. ANSI X12's 856 message exists precisely for this, and an SSCC (serial shipping container code, the GS1 standard) scans straight into receiving — full pallets, no piece-counting. At this volume, the cost of handling ASNs by hand exceeds the cost of integration. The threshold is crossed.
Fake-requirement warning: a warehouse doing 3 trucks a day insisting on EDI integration, demanding suppliers rebuild their systems — suppliers will not comply, you will nag; if they comply, the data quality is worse than the spreadsheet in the group chat. Money burned for nothing.
The maintenance pitfalls: the no-ASN fallback flow and ASN accuracy scoring
Two pitfalls, one at a time.
Pitfall one: no-ASN arrivals. Here is the counter-intuitive call: a no-ASN arrival is not an exception. It is the norm. Small suppliers have no EDI capability; emergency replenishments, transfers, and return flows never come with ASNs. Treat no-ASN as an exception and every one becomes a fire drill. The right move is to make the fallback flow a standard flow:
- Truck hits the dock: scan the plate, register, create a "no-ASN receiving order" in the system.
- Unload to the inspection staging area by supplier and category — not straight to putaway.
- Complete SKU and quantity entry within 2 hours (photos plus counting), then convert to the normal flow.
- Track the no-ASN share monthly; past 30%, go talk to your top suppliers about ASN onboarding.
With a standardized fallback, no-ASN truck turnaround drops from 1.5 hours to about 45 minutes (same 3PL's numbers). Remember: a process is not judged by how smooth the ideal case is, but by how orderly the worst case stays.
Pitfall two: ASN accuracy. This is the single most important number in the whole piece, and the close lands on it.
ASN line-item accuracy = (ASN lines matching actual receipts) ÷ total lines × 100%
In April 2025, that maternal-and-baby warehouse took a hit: the supplier's ASN said 1,200 units, 980 arrived — 220 short. The team had pre-assigned slots and staffed to the ASN; slots sat empty, labor sat idle, and the day's plan had to be rebuilt. That is the backlash of pre-assigning on bad data: the better you prepare, the more expensive the miss.
Here is the threshold: line-item accuracy ≥95% — pre-assign slots with confidence. 90–95% — zone only, do not lock slots. Below 90% — no pre-assignment, count on arrival, and start a supplier corrective program. Grade suppliers on it: three straight months under 90% means demotion to "count on arrival," no pre-assignment privileges; three straight months at 98% or better earns "green-lane" status (sampling drops to 5%).
Is pre-arrival management worth it? Watch this one number: ASN line-item accuracy. Above 95%, do it with your eyes closed — the payoff is certain. Below 90%, fix the supplier's data first and leave the system alone. No system fixes a broken data source — the plainest sentence in an engineer's worldview.
By Da Liu, Automation Engineer
