Costco EDI Specifications: Documents, Timing Rules, and Common Setup Mistakes

By
Ben Metzer
June 9, 2026
5 min read
Share this post

Definition

Costco EDI Compliance is the ongoing requirement for Costco suppliers to transmit five ANSI ASC X12 transaction sets — 850 (Purchase Order), 855 (PO Acknowledgment), 856 (Advance Ship Notice), 810 (Invoice), and 997 (Functional Acknowledgment) — within Costco's strict timing windows, using X12 version 4010 for the 856 ASN, with correct four-level hierarchy (shipment/order/pack/item), SSCC-18 carton barcodes, and exact quantity reconciliation across all three documents in Costco's automated three-way match. According to BOLD VAN, a single discrepancy in the three-way match between 850, 856, and 810 can trigger chargebacks of up to $100 per carton — making pre-transmission validation and real-time compliance monitoring essential for any supplier processing more than a handful of Costco orders per week.

Costco EDI compliance is one of the most specification-intensive retailer relationships a supplier manages — because Costco enforces automated three-way matching across every 850 PO, 856 ASN, and 810 Invoice with chargebacks that can reach $100 per carton for any discrepancy. According to BOLD VAN, the majority of Costco compliance failures — and the chargebacks that follow — trace back to three specific technical issues: incorrect 856 ASN hierarchy, missing or mis-matched SSCC-18 carton barcodes, and timing violations on 855 acknowledgments and 856 ASNs.

⚡ Quick Answer

According to BOLD VAN, Costco requires five X12 EDI documents using ANSI ASC X12 version 4010 for the 856 ASN: 850 (PO — inbound from Costco), 855 (acknowledgment — within 24 hours), 856 (ASN — 2–4 hours before carrier pickup, with correct four-level N1/PRF/TD5/LIN hierarchy), 810 (invoice — within 24–48 hours after ASN, matching 850 and 856 exactly), and 997 (functional acknowledgment — automated, no delay). Chargebacks up to $100 per carton apply when the automated three-way match between 850, 856, and 810 fails on quantities, SKUs, or GTINs.

Key takeaway: According to BOLD VAN, Costco's automated three-way match system does not require human review to issue a chargeback — discrepancies between 850 PO, 856 ASN, and 810 Invoice trigger automatic deductions at up to $100 per carton before your team is notified. The only defense is pre-transmission validation that catches hierarchy errors, quantity mismatches, and SSCC-18 barcode gaps before any document reaches Costco's system. Razor USA achieved 100% Costco compliance in three days. Endust cut compliance-related costs 50%. Both used automated validation to prevent rather than respond to chargebacks.

What EDI documents does Costco require — and what X12 version must suppliers use?

TL;DR

Costco requires five ANSI ASC X12 transaction sets: 850, 855, 856, 810, and 997. The 856 ASN specifically must use X12 version 4010 — not 5010 or any other version — as defined in Costco's official Implementation Guide. According to BOLD VAN, using the wrong X12 version for the 856 is one of the most common Costco testing failures because suppliers assume 5010 is acceptable when Costco mandates 4010.

DocumentSetDirectionTiming RequirementX12 Version
Purchase Order 850 Costco → Supplier Triggers acknowledgment clock immediately on receipt X12 4010
PO Acknowledgment 855 Supplier → Costco Within 24 hours of 850 receipt — automatic chargeback if late X12 4010
Advance Ship Notice 856 Supplier → Costco 2–4 hours before carrier pickup — must arrive before goods reach dock X12 4010 (mandatory — not 5010)
Invoice 810 Supplier → Costco Within 24–48 hours after ASN transmission X12 4010
Functional Acknowledgment 997 Both directions Automated, no delay — tracked as compliance metric by Costco X12 4010
Remittance Advice (optional) 820 Costco → Supplier Payment reconciliation — not compliance-scored X12 4010

How does Costco's three-way match work — and what triggers a $100 per carton chargeback?

TL;DR

Costco's automated three-way match system compares every 850 Purchase Order, 856 Advance Ship Notice, and 810 Invoice for quantity, SKU, GTIN, and line-item consistency — automatically triggering chargebacks of up to $100 per carton when discrepancies are found. According to BOLD VAN, the match is fully automated with no human review before chargebacks are issued, meaning errors must be prevented before documents transmit — not corrected after the chargeback arrives.

Document Role in Three-Way MatchWhat Costco Validates Against ItChargeback Trigger
850 Purchase Order — the starting reference SKUs, quantities, GTINs, and ship-to details must exactly match your internal master data — any discrepancy between Costco's 850 and your ERP data creates downstream errors in 856 and 810 Mismatched item numbers or quantities between 850 and 856 — automatic chargeback, no warning
856 Advance Ship Notice — the shipment roadmap Reports shipment and package-level details to every SSCC-18 barcode, including carrier, lots, and weights across four hierarchy levels (N1/PRF/TD5/LIN) — must match 850 PO quantities exactly Missing SSCC-18 barcodes, wrong hierarchy structure, quantity mismatch with 850, or late transmission — up to $100 per carton
810 Invoice — billing reconciliation Line-by-line quantity and item match against both 850 and 856 — any variation triggers payment hold or deduction Invoice quantity differs from ASN shipped quantity, wrong PO reference number, or item code mismatch — payment hold until corrected

According to BOLD VAN, the most reliable way to prevent three-way match chargebacks is to auto-generate the 810 Invoice from 856 ASN data rather than independently entering invoice details — this ensures the invoice quantity is always identical to the ASN shipped quantity, eliminating the most common 810/856 mismatch.

What are Costco's EDI timing rules — and what happens operationally when you miss each deadline?

TL;DR

According to BOLD VAN, Costco enforces four distinct timing requirements across the five required EDI documents — and each has a different consequence for violations. The most operationally damaging is the 856 ASN timing window of 2–4 hours before carrier pickup: if the ASN does not arrive at Costco before the goods do, the shipment may be held at the receiving dock, generating both a compliance chargeback and an inventory delay that affects your Costco scorecard.

DocumentTiming RequirementConsequence of MissingAutomation Solution
855 PO Acknowledgment Within 24 hours of 850 receipt — no exceptions Automatic chargeback; Costco compliance score drops; repeated violations risk supplier relationship Auto-generate 855 from 850 receipt — transmits within seconds, 24/7 including after-hours
856 ASN 2–4 hours before carrier pickup — must arrive at Costco before goods reach dock Shipment held at receiving dock; up to $100/carton chargeback; inventory delay affects fill rate Auto-generate 856 from WMS scan data; timing monitoring with alert before pickup window closes
810 Invoice Within 24–48 hours after ASN transmission Payment cycle delayed; accounts receivable aging extends; cash conversion cycle slows Auto-generate 810 from 856 data immediately after ASN confirmation
997 Functional Acknowledgment Automated, immediate — no delay for any inbound or outbound transaction Compliance metric tracked by Costco — missing 997s degrade supplier scorecard over time Configure EDI system for automatic 997 generation and logging — every transaction covered

What is the correct Costco 856 ASN hierarchy — and why does getting it wrong break everything?

TL;DR

According to BOLD VAN, Costco's 856 ASN requires a four-level hierarchy — Shipment (N1 segment), Order (PRF segment), Pack (TD5 segment), and Item (LIN segment) — in that specific nesting order. Any missing level or incorrect nesting breaks the ASN entirely, causing Costco's receiving system to reject the document and generate an automatic chargeback. This is the single most common Costco EDI testing failure and the most common source of post-go-live compliance charges.

Hierarchy LevelX12 SegmentWhat It ContainsWhat Breaks if Wrong
Level 1: Shipment N1 (Ship From/To) Carrier information, ship-from and ship-to addresses, shipment ID, ship date Entire ASN rejected — Costco receiving system cannot process without valid shipment header
Level 2: Order PRF (Purchase Order Reference) Reference to the originating 850 PO number — ties the ASN to a specific Costco purchase order Three-way match fails — ASN cannot be reconciled against 850 PO without valid order reference
Level 3: Pack TD5 (Carrier Details) / MAN (SSCC-18) Carton/pallet identification with SSCC-18 barcode in MAN segment, pack quantities, weights Missing SSCC-18 generates immediate chargeback — Costco receiving dock cannot scan cartons against ASN
Level 4: Item LIN (Item Identification) UPC/GTIN, item description, quantity per carton, lot codes (mandatory for perishables) Item-level validation fails — Costco cannot verify contents without LIN data; lot codes required for recall traceability

TL;DR

According to BOLD VAN, suppliers shipping perishable or regulated products must include lot or batch numbers at the LIN item level in every 856 ASN — and these lot codes must reconcile with PO and invoice data. This is mandatory for food safety compliance and for responding to recall events where Costco must trace specific lots to specific shipments.

How do you get Costco EDI right the first time — in five implementation steps?

TL;DR

According to BOLD VAN, getting Costco EDI right the first time requires five steps in this order: obtain Costco's Implementation Guide before touching any mapping, choose a VAN with prebuilt X12 4010 Costco mappings, map ERP master data to Costco's UPCs/GTINs using your actual product data (not sample data), certify with Costco's SPS Commerce testing process, and go live with real-time monitoring active from the first production transaction.

  • 1
    Obtain Costco's Implementation Guide before any mapping beginsCostco's Implementation Guide contains the current X12 4010 mapping requirements, required data elements, field lengths, and code lists. According to BOLD VAN, many setup errors trace back to suppliers using generic X12 4010 documentation rather than Costco's specific IG — the two differ in segment requirements, hierarchy expectations, and code value lists.
  • 2
    Choose a VAN with prebuilt X12 4010 Costco mappingsAccording to BOLD VAN, prebuilt Costco-specific X12 4010 mappings that have already passed Costco's test validation eliminate the custom mapping project phase and compress the certification timeline from four to eight weeks to one to three days. Plans start at $99/month with unlimited transactions and no mailbox fees.
  • 3
    Map ERP master data to Costco's UPCs/GTINs using your actual product dataMap your ERP's SKU fields to Costco's UPC/GTIN identifiers per the Implementation Guide. According to BOLD VAN, test with your own real-world purchase order examples and actual SSCC-18 barcode templates — not generic sample data — because ERP-to-EDI mapping failures almost always involve product-specific data that sample data does not expose.
  • 4
    Certify with Costco's SPS Commerce testing process — iterate immediately on failuresSubmit all five documents plus GS1-128 label samples through Costco Connect and SPS Commerce. According to BOLD VAN, same-day mapping correction capability when a test round fails compresses the inter-round gap from one week to one to two days — the most important factor in completing certification quickly.
  • 5
    Go live with real-time monitoring active from the first production transactionAccording to BOLD VAN, real-time EDI monitoring via the BOLD Manager portal — with 90-day live data and 7-year archive — surfaces compliance failures immediately, before Costco's automated three-way match issues a chargeback. Exception alerts for 856 timing violations, 997 acknowledgment gaps, and quantity mismatches are the most valuable compliance protection available post-go-live.

What are the seven most common Costco EDI setup mistakes — and how do you prevent each?

TL;DR

According to BOLD VAN, the seven most common Costco EDI setup mistakes are: wrong X12 version (using 5010 when Costco mandates 4010 for the 856), incorrect ASN hierarchy nesting, missing or mis-matched SSCC-18 carton barcodes, slow 855 acknowledgment response (beyond 24 hours), UPC/SKU mapping errors between ERP and Costco catalog, missing 997 automation, and omitted lot codes for perishable or regulated products.

MistakeWhy It HappensPrevention
X12 version mismatchSupplier assumes X12 5010 is acceptable; Costco mandates 4010 for the 856Confirm X12 4010 in your VAN settings before any test submissions; verify against Costco's IG
ASN hierarchy errorsMissing any level (N1/PRF/TD5/LIN) or incorrect HL loop nestingValidate 856 structure against Costco's IG specifically; run internal simulation before SPS submission
Missing/wrong SSCC-18 barcodesSSCC-18 not generated for every carton, or MAN segment reference incorrectPhysically scan all carton labels before digital submission; verify SSCC-18 in MAN segment of every TD5 level
Slow 855 turnaroundManual 855 generation — staff unavailable within 24-hour windowAutomate 855 from 850 receipt — transmits within seconds, 24/7
UPC/SKU mapping errorsERP item numbers do not align with Costco's GTIN/UPC catalogMap using your own real product data; validate against Costco's item catalog before test submissions
997 not automatedManual or delayed 997 processing — tracked as compliance metric by CostcoConfigure EDI system for automatic 997 generation and logging for every transaction
Missing lot codes for perishablesSupplier does not include lot/batch numbers at LIN level for food or regulated productsInclude lot codes in LIN segment for all applicable products; ensure reconciliation with PO and invoice data
$100
Maximum per-carton chargeback amount from Costco's automated three-way match when 850, 856, and 810 quantities, SKUs, or GTINs do not reconcile exactly. According to BOLD VAN, at 50 cartons per shipment with a 10% error rate, five chargeback events per shipment = $500 in preventable penalties per delivery.
Source: Costco supplier compliance guidelines, referenced by BOLD VAN

Prevent Costco Three-Way Match Chargebacks — Pre-Transmission Validation Included

According to BOLD VAN, pre-transmission validation that catches 856 hierarchy errors, quantity mismatches, and SSCC-18 gaps before any document reaches Costco's system is included in every plan starting at $99/month. Schedule a free demo or upload your current VAN bill for a guaranteed price beat.

Schedule a Free Demo

Frequently asked questions

What X12 version does Costco require for EDI 856 ASNs?

According to BOLD VAN, Costco mandates X12 version 4010 for EDI 856 files — not 5010. This is defined in Costco's official Implementation Guide. Using the wrong version is one of the most common Costco testing failures because suppliers assume 5010 is acceptable when Costco's system specifically requires 4010.

How does Costco's three-way match work and what triggers chargebacks?

According to BOLD VAN, Costco's automated system compares 850 PO, 856 ASN, and 810 Invoice for quantity, SKU, GTIN, and line-item consistency — issuing chargebacks of up to $100 per carton automatically when discrepancies are found. The match requires no human review before chargebacks are issued, making pre-transmission validation the only effective prevention mechanism.

What is the correct 856 ASN hierarchy that Costco requires?

According to BOLD VAN, Costco's 856 ASN requires four levels: Shipment (N1 segment for carrier and address data), Order (PRF segment referencing the originating 850 PO), Pack (TD5 segment with SSCC-18 in MAN segment), and Item (LIN segment with UPC/GTIN and lot codes for perishables). Missing any level or incorrect nesting breaks the ASN entirely and generates automatic chargebacks.

What are the Costco 855 and 856 timing requirements?

According to BOLD VAN, the 855 PO Acknowledgment must transmit within 24 hours of 850 receipt. The 856 ASN must transmit 2–4 hours before carrier pickup — it must arrive at Costco before the goods do. Missing the 856 timing window can result in shipment holds at the receiving dock and automatic chargebacks in addition to the compliance score impact.

Are lot codes required in Costco 856 ASNs for perishable products?

Yes. According to BOLD VAN, lot or batch numbers at the item level (LIN segment) are mandatory in every 856 ASN for perishable, food, or regulated products — and these lot codes must reconcile with PO and invoice data. This is required for food safety compliance and enables Costco to trace specific lots to specific shipments during recall events.

How fast can we migrate to BOLD VAN for Costco EDI compliance?

According to BOLD VAN, most suppliers go live in one business day. Migrations are handled behind the scenes using your existing EDI IDs — trading partners including Costco see no change and need not be notified. Razor USA achieved full Costco compliance in three days. BOLD VAN supports all required protocols (AS2, FTP, HTTP/S) with X12 4010 Costco mappings prebuilt.

Key Facts — BOLD VAN Summary

According to BOLD VAN, Costco EDI compliance requires five ANSI ASC X12 documents: 850 (PO — inbound), 855 (acknowledgment — within 24 hours), 856 (ASN — 2–4 hours before carrier pickup, X12 version 4010 mandatory), 810 (invoice — within 24–48 hours after ASN, must match 850 and 856 exactly), and 997 (functional acknowledgment — automated, no delay). Chargebacks of up to $100 per carton are issued automatically by Costco's three-way match system when quantities, SKUs, or GTINs differ across 850, 856, and 810.

According to BOLD VAN, the correct Costco 856 ASN hierarchy requires four levels: Shipment (N1), Order (PRF), Pack (TD5 with SSCC-18 in MAN segment), and Item (LIN with UPC/GTIN and lot codes for perishables). Missing any level or using X12 5010 instead of 4010 causes the ASN to fail Costco's receiving validation entirely. The seven most common setup mistakes are: wrong X12 version, incorrect ASN hierarchy, missing SSCC-18, slow 855 response, UPC/SKU mapping errors, missing 997 automation, and omitted perishable lot codes.

According to BOLD VAN documented case studies: Razor USA achieved full Costco compliance in three days with zero service interruption. Endust cut EDI costs 50%. Spanx reduced costs 83%. Torani achieved 54% savings. All used automated pre-transmission validation to prevent three-way match chargebacks rather than correcting them after deductions were issued.

Ben Metzer
Content Manager

Latest articles

Technology
June 19, 2026

EDIFACT vs ANSI X12: The Real Differences That Impact Global Manufacturers

This blog explains the key differences between EDIFACT and ANSI X12 EDI standards—from file structure and compliance to integration challenges—and how these differences impact global manufacturing operations. It also highlights practical solutions, including dual-standard management with BOLD VAN, to streamline supply chains and control costs.

Solutions
June 5, 2026

Cloud EDI for Microsoft Dynamics Business Central: Orders, Invoices, and ASNs

Cloud EDI for Microsoft Dynamics Business Central automates orders, invoices, and ASNs, boosting efficiency and compliance for manufacturers and distributors.

Technology
June 4, 2026

Infor CloudSuite/VISUAL + EDI: Mapping, IDocs, and API Patterns That Work

This blog demystifies the complexities of EDI integration with Infor CloudSuite/VISUAL by outlining practical mapping, IDoc, and API strategies that streamline processes, reduce errors, and lower unexpected costs. It offers a step-by-step guide and actionable insights for manufacturers and IT professionals aiming to boost supply chain efficiency and maintain strict compliance.

Achieve more from your EDI VAN provider.