You Open the Dock Without Knowing What's Coming
Ask why receiving runs late and the answer is usually "the trucks arrive late." Time the dock, though, and a different picture emerges. If 90 minutes pass between a trailer docking and the load being cleared, it is common for 60 of those minutes to go not to unloading but to verification and labeling.
The mechanics are easy to see. Someone walks the pallet with a packing slip, counting cases by hand, then reprints center-standard labels because every supplier uses a different barcode scheme. At eight seconds per case, a facility handling 6,000 cases a day burns roughly 13 hours — about 1.7 full-time people — standing at a label printer.
When GS1-standard labels are applied at the point of production instead, the same carton flows through any distribution center without relabeling. And note that conveyors and sorters do not fix this: without inbound data, automation stalls at the door, because a sorting rule has nothing to decide on when nobody knows what is arriving or in what quantity.
How an ASN Changes the Inbound Flow
An Advance Shipping Notice (ASN) delivers item, quantity, lot, expiry date, and packaging hierarchy before the vehicle arrives. DESADV in EDIFACT and the 856 transaction in X12 are the standard formats.
Once an ASN is in hand, the nature of verification changes: receiving stops being an exercise in counting and becomes an exercise in confirming against something already known. Operationally, that unlocks:
The caveat is that an inaccurate ASN destroys trust, and the floor quietly reverts to 100% manual counts. So ASN accuracy — quantity and lot match rate — should be held to 98% or better, tracked as a supplier scorecard metric and shared monthly.
One SSCC Scan Instead of a Full Count
The SSCC (Serial Shipping Container Code) is an 18-digit unique identifier assigned to a logistics unit such as a pallet, case, or tote, carried under GS1 application identifier `(00)`. Scanning it pulls up the ASN detail and expands the GTINs and lot numbers of every case beneath it in a single step.
A GS1-128 case label typically carries:
The pallet-level logistic label carries `(00)` SSCC, plus `(02)` (GTIN of the contained trade item) and `(37)` (count of contained units) when the load is homogeneous. Note that `(37)` pairs only with `(02)` and is not permitted alongside `(01)`.
The payoff shows up in the clock. Inspecting a 24-case pallet at ten seconds per case takes about four minutes; one SSCC scan takes three seconds. Manual keying introduces three to five typos per 1,000 entries, an error class that effectively disappears on the scan path.
Not everything should move to pallet-level receipt, of course. A workable rule is to keep high-value, pharmaceutical, and expiry-sensitive items on full case-level inspection while routing fast-moving, high-volume goods from standards-compliant suppliers through SSCC receipt — and to store that rule as an attribute on the item master rather than in someone's head.
When Some Suppliers Ignore the Standards
In practice, compliant and non-compliant suppliers share the same dock. That is why a WMS should be designed for two paths from day one: a standard path built on SSCC scanning, and a fallback path built on manual entry plus center-issued labels. Downstream of receipt confirmation, both converge into a single inventory-posting flow.
When persuading a supplier to convert, numbers work better than appeals. Convert the 13 relabeling hours above into labor cost and you arrive at tens of millions of won a year; allocating that cost by supplier turns it into a negotiating document.
ASN intake channels are just as mixed — EDI, spreadsheet attachments, email, portal uploads. Rather than writing logic per channel, normalize everything to one internal format in a receiving adapter, then run validation and loading through a single pipeline. That choice is what keeps maintenance cost flat as channels multiply.
Where Data Integrity Breaks Down
Most "we received the ASN but nothing matched" incidents start in the product master. If the supplier transmits GTINs while the center maintains only its own internal item codes, any new SKU without a mapping entry drops straight into exception handling.
Three items belong in the design requirements, not in a later cleanup project:
Lot and expiry data follow the same logic. Miss them at receipt and every downstream rule — FEFO allocation, recall traceability, near-expiry management — loses its basis. What you fail to capture inbound cannot be invented outbound.
Sequencing the Rollout and What to Expect
Converting every supplier at once almost always fails. The safer approach is to integrate ASNs from your top three to five suppliers by volume, then build the case by comparing three metrics before and after: verification time, quantity error rate, and dock turnover. Because inbound volume concentrates in a handful of accounts, converting only those accounts already moves a substantial share of total receipts onto the standard path.
Drawing on our WMS implementation experience, POLYGLOTSOFT designs the ASN intake interface (EDI, spreadsheet, API), GS1-128 label issuance, and the scan-verification screens as one continuous flow rather than separate projects. If you would like to start by scoping the integration surface with your existing ERP and supplier systems, please get in touch.