Costco EDI Requirements: Supplier Certification and ASN Guide

What are Costco's EDI requirements?

Costco requires full EDI compliance from all active suppliers. The mandate deadline for existing suppliers was June 3, 2024; new suppliers onboard to EDI immediately after approval. The required X12 document set is the 850 purchase order, 855 acknowledgment, 856 advance ship notice, 810 invoice, 820 remittance, and 997 functional acknowledgment.

Testing and certification run through the SPS Commerce network— you do not need SPS software, but your EDI traffic must certify through their network before you can go live. The ASN uses Costco's Enterprise 856 v4010mapping with a strict shipment > order > item > pack hierarchy, every carton and pallet carries a GS1-128 label with a unique SSCC-18 that matches that hierarchy, and the ASN must arrive before the truck reaches the depot. Two details that surprise first-time suppliers: your shipping label and packing slip must be approved before final EDI certification, and food/produce shipments must include lot codes in the ASN for traceability.

For SMB suppliers, the practical question is not "what documents?" but "how do we run this every day without an EDI team?" — which is why self-serve EDI onboarding with Costco's mapping pre-built matters. The rest of this guide covers the operational discipline behind the requirements.

Why the Costco ASN breaks first

Retail programs publicly discuss transaction sets—850, 855, 856, 810—because documents are easy to checklist. The painful failures are almost always semantic: the 856 exists, but it asserts a shipment state your warehouse has not committed to yet, or it references carton IDs that never existed on a label. Costco tunes enforcement around receiving economics: a wrong ASN hurts slotting, labor planning, and vendor scorecards simultaneously.

Treat the ASN as a binding narrative of physical movement, not an invoice preamble. If your process generates the 856 when finance “closes” the order, you will eventually collide with a carrier event that diverges—split shipments, short picks, or LTL consolidations. Certification labs catch syntax; production catches timing.

Shipment windows vs. document windows

Costco's hard rule is that the 856 must arrive before the truck reaches the depot. Most SMB suppliers optimize ERP batches to nightly Close; retail networks optimize dock appointments to the hour. Bridging those clocks is an integration design problem: you need an event stream—pick complete, stage scan, trailer departure—with idempotent retries so EDI does not double-send ASN waves when a TMS webhook replays.

Signals that matter

Prioritize the earliest durable operational signal you trust. For many teams that is WMS pick confirm + pack confirm; for 3PL-led flows it is the partner's closed trailer scan. Map each milestone to which HL segments must exist before you claim carton-level truth.

SSCC discipline and hierarchy hygiene

Scan failures cluster around duplicate SSCC reuse, skipped inner packs, and mixing residual pallets after rework. Your EDI hierarchy should reflect what departs, not what was ordered. If your catalog allows substitutions at ship time, your ASN builder must consume the substituted SKU set, not the original PO line mirror.

Label generation should consume the same identifiers as EDI—same SSCC pool, same pack structure. When label templates drift from ASN segments, DCs see exceptions even though “the file validated.”

Costco EDI certification vs. production behavior

Costco's certification runs through the SPS Commerce network with deterministic fixtures—known SKUs, predictable quantities—plus the physical-artifact gate: your shipping label and packing slip must be approved before final certification. Production then introduces partials, backorders, and multi-stop routes. Build regression packs from real weeks of shipping, not only lab vectors. Snapshot messy shipments with splits and prove your mapper emits stable HL nesting across those branches. If you ship food or produce, prove lot codes flow into the ASN from day one — traceability data is a requirement, not an enhancement.

X12 segments Costco programs stress-test

Beyond BSN timing, Costco-scale programs validate CLD carton detail, LIN item IDs, and REF carrier references against physical labels. Developers ingesting ASNs should start with 856-in-Python and the ASN API guide rather than parsing HL loops ad hoc in warehouse scripts.

Debug ASN rejects with segment references, not guesswork

When Costco-scale enforcement hits, operators need segment-level context — not hex dumps. Trace HL hierarchy breaks to the HL reference, carton mismatches to CLD load detail, and ship-to errors to N1 party IDs. Developers can validate fixes in sandbox using 856 in Python before resubmitting production ASNs.

Where to go next

If you are modernizing alongside compliance, read EDI vs API for hybrid architectures, and EDI explained for non-technical stakeholders. For SMB-friendly onboarding paths, start at Quickstart.

Frequently Asked Questions