The Costco EDI Requirements Guide for CPG Brands 2026: Every Transaction, Every Timing Rule and How to Go Live Without Chargebacks
- alexsteinbergmojo
- 10 hours ago
- 13 min read

EDI is not optional at Costco. It is the operational language of the channel — and the supplier that does not speak it fluently pays the price in chargebacks, receiving failures, and delayed payments that compound into a financial drain that undermines the commercial opportunity the Costco program was supposed to create.
Non-compliance results in chargebacks — financial penalties deducted from your payments.
Common triggers include inaccurate or late ASNs at $50 to $200 per incident, data mismatches between PO, ASN, and invoice at 1 to 3 percent of PO value, and incorrect GS1-128 labeling at $50 to $150 per carton.
On a $150,000 purchase order, a 2 percent data mismatch chargeback is $3,000. A single late ASN is $50 to $250. A pallet of 20 cartons with incorrect GS1-128 labels is $1,000 to $3,000 in carton-level chargebacks. These are not hypothetical risks — they are the documented commercial consequences of inadequate EDI infrastructure that the Costco vendor community has accumulated data on across thousands of transaction cycles.
The inverse is also true: the supplier whose EDI infrastructure is built correctly — whose ASNs arrive before the truck does, whose invoices match the PO exactly, whose SSCC-18 labels scan perfectly at the depot dock — never pays these chargebacks. The investment in correct EDI setup is a one-time cost. The chargebacks it prevents are a perpetual cost that compounds with every PO.
This guide provides the complete Costco EDI compliance picture for CPG brands in 2026 — every required transaction set, every timing rule, the SSCC-18 label specification, the five most common failure causes, the five-step setup process, and the two performance metrics that communicate whether the EDI program is running correctly.
What EDI Is and Why Costco Requires It
Electronic Data Interchange (EDI) is the structured exchange of business documents — purchase orders, advance ship notices, invoices — between trading partners in a standardized electronic format. Rather than exchanging paper documents or unstructured email attachments, EDI-enabled trading partners exchange structured data files that their respective systems can read, validate, and process automatically without manual re-entry.
Costco's EDI programs commonly require suppliers to exchange structured business data using ANSI X12 EDI. These EDI transactions connect Costco's ordering, fulfillment, receiving, and financial processes to the supplier's ERP, warehouse, fulfillment, and invoicing systems.
The reason Costco requires EDI at volume is structural and operational: the cross-docking model that Costco's depot network uses cannot function without advance electronic notice of what is arriving, when, in what quantities, in what packaging configuration, and with what product identifiers. The EDI 856 Advance Ship Notice is not an administrative formality — it is the operational document that allows the depot to schedule receiving labor, stage outbound trailers for the specific warehouse locations on the manifest, and process inbound product without manual inspection of every carton.
A depot receiving team that does not have an ASN before the truck arrives cannot efficiently process the inbound shipment in the tight timeframe that cross-dock scheduling requires. The operational disruption ripples downstream to the warehouse floor: the product that should have been delivered to 60 warehouse locations on Tuesday is now delayed because the depot's receiving timeline was disrupted by a missing ASN.
Costco does not absorb this disruption cost. It charges it back to the vendor.
The Required EDI Transaction Sets: Every Document in the Costco Cycle
Costco requires suppliers to exchange a specific set of EDI transaction documents. Each document serves a distinct role in the order-to-cash cycle and must conform to Costco's exact formatting specifications as outlined in their EDI Implementation Guide.
EDI 850 — Purchase Order (Costco to Supplier)
The EDI 850 is the purchase order that Costco sends to the vendor when a buying decision has been made to replenish or initiate inventory for a specific product at a specific set of locations. It contains the PO number, the Costco item number for each ordered product, the quantity per item, the required delivery date, the ship-to depot, and the agreed cost price per unit.
The 850 is the triggering document for the entire operational cycle: production scheduling, co-manufacturer engagement, freight booking, SSCC-18 label generation, and the downstream documents (855, 856, 810) that respond to it. The vendor whose ERP or order management system receives the 850 and automatically creates a sales order — without manual re-entry — is operating with the efficiency that Costco's high-volume model requires.
EDI 855 — Purchase Order Acknowledgment (Supplier to Costco)
The EDI 855 is the vendor's formal acknowledgment of the PO — confirming acceptance of each PO line and signaling the anticipated ship date feasibility. The 855 must be sent within 24 hours of receiving the EDI 850 from Costco.
The 855 is the transaction that most first-time Costco vendors overlook — because it is not required at every retailer, and because the urgency of beginning production after a PO arrives can push the acknowledgment response into the background. Failing to transmit the 855 within the 24-hour window is tracked by Costco as a compliance metric, and patterns of missing or late 855 acknowledgments communicate unreliable PO management to the buying team.
EDI 856 — Advance Ship Notice (Supplier to Costco) — The Most Critical Transaction
The EDI 856 is the Advance Ship Notice — the document that the vendor transmits when the shipment leaves their facility (or is picked up from their co-manufacturer), describing the complete packing structure: pallet SSCC-18 identifiers, carton counts per pallet, UPCs or GTINs at the item level, total shipped quantity, carrier name, trailer number, and estimated delivery date at the Costco depot.
The 856 is the most operationally critical EDI transaction in the Costco compliance framework because Costco relies on the ASN to schedule depot receiving. An ASN that arrives late, carries incorrect data, or is missing entirely will disrupt Costco's receiving timeline.
The timing rule that most frequently triggers ASN chargebacks: the ASN must be sent 2 to 4 hours before carrier pickup — meaning the ASN must arrive at Costco's EDI system before the truck leaves the shipping facility with the product. ASNs must arrive before the truck does. If the ASN is late, your product may get stuck on the dock, creating operational headaches.
The ASN hierarchy is the most common technical failure point in Costco EDI implementation. The 856 must follow a specific four-level hierarchy: shipment level (the overall shipment), order level (the PO being fulfilled), pack level (each pallet), and item level (each carton's contents). Missing any level — submitting a three-level ASN that omits the pack level, for example — breaks the ASN for Costco's receiving system. Stick closely to their X12 4010 856 Implementation Guide.
EDI 810 — Invoice (Supplier to Costco)
The EDI 810 is the electronic invoice — the vendor's billing document submitted to Costco after the shipment has been dispatched. The 810 must reference the PO number and the ASN identifiers, and must exactly match the purchase order and shipment details for payment to be processed.
The 810 should be submitted within 24 to 48 hours after ASN transmission. Delays disrupt payments. Invoice matching at Costco is automated: the 810 is compared against the 850 (PO) and the 856 (ASN) in a three-way match. Any discrepancy between these three documents — a quantity on the invoice that differs from the received quantity, a cost price that differs from the PO, a missing item number reference — triggers a dispute process that delays payment.
The most common 810 failure: an invoice submitted at a cost price that reflects the vendor's standard pricing rather than the Costco-specific cost price established in the vendor agreement. This discrepancy — which is entirely avoidable — requires manual resolution that delays payment and creates unnecessary administrative burden on both the vendor and Costco's accounts payable team.
EDI 997 — Functional Acknowledgment (Both Directions)
The EDI 997 is the confirmation message that verifies a trading partner has received an EDI transmission. It is mandatory for every document exchange — Costco sends a 997 to confirm receipt of every 856 and 810 the vendor transmits, and the vendor must send a 997 to confirm receipt of every 850 and other incoming transaction from Costco.
The 997 must be processed automatically and without delay for every transaction received.
Failing to handle 997s is a common compliance metric that will be tracked by Costco. The vendor whose EDI system does not automatically generate and transmit 997 acknowledgments — or whose system allows 997s to queue without transmission — is accumulating a compliance failure record that the Costco EDI team monitors.
The SSCC-18 Label: The Physical-Digital Bridge
The SSCC-18 (Serial Shipping Container Code 18-digit) label is the physical barcode label applied to every shipping carton and pallet in a Costco shipment. It creates a direct link between the physical packaging and the electronic ASN data — allowing the depot's barcode scanning system to match physical cartons against the ASN contents as they move through the receiving process.
Costco requires all shipping cartons to carry GS1-128 barcoded labels (formerly UCC-128) that contain the SSCC-18 identifier.
The SSCC-18 is an 18-digit number built from the vendor's GS1 company prefix, a unique serial number, and a check digit. Each pallet and each carton in the shipment must have a unique SSCC-18 — the pallet-level SSCC-18 is the identifier referenced in the pack level of the 856 ASN, and the carton-level SSCC-18 is the identifier referenced in the item level.
The most common SSCC-18 failure modes:
Incorrect GS1 company prefix. A vendor using a borrowed or incorrect GS1 prefix generates SSCC-18 numbers that cannot be validated against the GS1 registry — creating a barcode that scans but cannot be verified. Vendors must use their own GS1 company prefix, obtained directly from GS1 US.
SSCC mismatch between physical label and ASN. The SSCC-18 number on the physical label must exactly match the SSCC-18 number in the corresponding level of the EDI 856 ASN. A transposition error in the serial number — a single digit out of place — creates a mismatch that the depot's receiving system flags as an exception. Every carton flagged as an exception requires manual resolution at the depot — and the vendor pays for that resolution in a label compliance chargeback.
Labels applied to the wrong cartons. In a high-volume production run where pallet configurations change between the pre-shipment label generation and the actual pallet build, labels from one pallet may be applied to cartons that end up on a different pallet. This mismatch produces an ASN-to-physical discrepancy that generates both a label compliance chargeback and an ASN accuracy concern.
Communication Protocols: How EDI Data Moves Between Vendor and Costco
Costco supports multiple communication protocols for EDI data exchange: Value Added Network (VAN), AS2, and SFTP.
VAN (Value Added Network)
A VAN is a third-party network that facilitates EDI transmission between trading partners — the vendor connects to the VAN, and the VAN routes documents to Costco's trading partner mailbox. VANs provide mailbox services, translation services, and communication reliability features that make them the most common EDI connectivity choice for vendors who are not technically sophisticated enough to manage direct AS2 connectivity.
The pricing model consideration for VAN selection: per-transaction and per-mailbox pricing compounds as Costco volume grows; trading partner-based pricing — a flat rate per active partner regardless of document volume — keeps costs predictable as you scale.
AS2 (Applicability Statement 2)
AS2 is a direct internet-based protocol for EDI transmission — the vendor's EDI system connects directly to Costco's AS2 endpoint without intermediary routing. AS2 provides real-time transmission confirmation (an MDN — Message Disposition Notification) that confirms the document arrived at Costco's system, which is commercially valuable for ASN timing compliance management.
SFTP (Secure File Transfer Protocol)
SFTP is the most technically straightforward protocol for EDI file exchange — structured EDI files are deposited in a designated SFTP folder and retrieved by the receiving system. SFTP is less common as the primary Costco EDI connectivity method but may be appropriate for specific document types or as a backup connectivity option.
The Five Most Common EDI Setup Mistakes
Address the five most common failure causes before the first test cycle, not after.
Mistake 1: Late or missing ASNs
If the ASN doesn't arrive before the truck, the delivery is dead on arrival. This is Costco's most enforced requirement.
The setup mistake that creates late ASNs: building the ASN generation workflow as a manual step rather than an automated trigger. If generating and transmitting the ASN requires a human decision and manual action after the shipment is dispatched, the risk of a late or missing ASN is never eliminated. The correct architecture: ASN generation is triggered automatically when the shipment is confirmed in the warehouse management or ERP system, with transmission occurring within the required 2 to 4-hour pre-pickup window without human intervention.
Mistake 2: Barcode and ASN mismatches
The SSCC-18 numbers in the ASN must exactly match the SSCC-18 numbers on the physical labels. The most common source of mismatch: generating ASN data from a pre-shipment pick list rather than from the actual pallet-level scan data captured at the time of palletization. If the pallet build differs from the pre-shipment plan — which it commonly does in high-volume production environments — the pre-pick-list ASN generates mismatches on every changed pallet.
The correct architecture: SSCC-18 data is captured by scanning the physical labels at palletization, and the ASN is generated from this scan data rather than from the pre-shipment plan.
Mistake 3: Incorrect ASN hierarchy
The four-level ASN hierarchy (shipment/order/pack/item) must be correctly implemented at the data structure level of the 856 transaction. A vendor whose EDI implementation generates a three-level 856 — missing the pack level — will fail Costco's certification testing and cannot go live. The pack level is the level that contains the pallet SSCC-18 — and without it, Costco's system cannot associate cartons to pallets, which is essential for depot cross-dock operations.
Mistake 4: Invoice price or quantity mismatches
The 810 invoice must match the 850 PO on cost price and the 856 ASN on shipped quantity. The most common mismatch: the vendor invoices for the ordered quantity rather than the actually shipped quantity when the two differ. If the vendor shipped 2,950 cases against a PO for 3,000 cases — because 50 cases failed QC inspection before shipping — the invoice must reflect 2,950 cases, not 3,000.
Mistake 5: Missing 997 Functional Acknowledgments
997s are processed automatically by every EDI system — but only if the system is configured to do so. An EDI provider that does not automatically generate and return 997 acknowledgments to every incoming transaction is a provider whose configuration is incomplete. Many vendors discover this gap when Costco's EDI team flags missing 997s as a compliance issue weeks after go-live — weeks during which every transaction Costco sent was received without the required acknowledgment.
The Five-Step EDI Setup Process for New Costco Vendors
Follow these five steps to go live with Costco EDI without chargebacks:
Step 1: Obtain Costco's EDI Implementation Guide
Request the current EDI Implementation Guide from your Costco buyer or the supplier operations contact assigned during the vendor onboarding process. The Implementation Guide contains Costco's specific data field requirements, segment structures, and formatting rules for each transaction set — and it is the authoritative reference for every mapping decision in the setup process.
Do not use generic ANSI X12 standards as the sole reference for Costco EDI mapping. The data mapping must follow Costco's exact specifications, which differ from both Walmart and Target in specific fields and segment structures. Generic standards produce a technically valid EDI document that fails Costco's specific requirements.
Step 2: Select an EDI Solution
Cloud-based or managed service is recommended for most suppliers. The EDI provider selection criteria specific to Costco: experience with Costco's compliance testing specifically, not just general retail EDI. A provider who has completed Costco EDI certification with multiple vendor clients understands the specific testing failure points and can navigate the certification process more efficiently than a provider encountering Costco's requirements for the first time.
Step 3: Map Internal Data to Costco's X12 Format Requirements
Map the vendor's internal data — item numbers, SSCC-18 generators, shipment data, invoice data — to the specific fields in each X12 transaction set as defined in the Costco Implementation Guide. Build the Costco item number cross-reference that maps the vendor's internal SKU identifiers to Costco's item numbers, and validate it against the first test POs before go-live.
Step 4: Complete Certification Testing
Costco requires a round of validation with test transactions: 850, 855, 856, 810, and 997.
The Costco EDI team will flag missing data points — a common tripwire is incorrect ASN hierarchy or missing SSCC-18 codes. Budget for two to four rounds of testing and address feedback from each round before proceeding.
The certification testing timeline cannot be compressed below what Costco's EDI testing protocol requires. Most vendors complete certification in two to four weeks with a competent EDI provider and a well-prepared data mapping. Vendors who attempt to rush the process — submitting incomplete or untested transactions to meet a PO deadline — extend the testing timeline by generating multiple failure rounds rather than accelerating it.
Step 5: Go Live and Monitor Continuously
Once live, track two baseline metrics: ASN accuracy above 99 percent and an invoice dispute rate below 1 percent.
Real-time transaction visibility is the operational tool that sustains these metrics after go-live. The vendor whose EDI system provides a dashboard of transaction statuses — which ASNs have been transmitted, which 997s have been received, which invoices are in dispute — can identify and resolve compliance issues before they accumulate into systematic chargebacks. Instead of reacting to errors only after they affect receiving or payment, teams can detect and resolve issues earlier in the process.
The Manual Pathway: Starting Without Full EDI
For vendors whose EDI infrastructure is not yet configured for Costco, the manual pathway is the appropriate starting point — not a permanent solution.
Smaller vendors may start with manual purchase orders transmitted through Costco's vendor portal and manual ASNs communicated via email. The manual pathway allows the vendor to begin fulfilling Costco purchase orders before EDI certification is complete — but it carries higher operational risk because it is more labor-intensive, more error-prone, and less scalable than EDI.
The specific risks of the manual pathway that the EDI setup should eliminate as quickly as possible: manual ASN email transmissions that miss the timing window because of human error or communication delay, manual invoice submissions that contain data entry errors that trigger payment disputes, and the absence of the automated validation layer that EDI systems provide before documents are transmitted.
The vendor who uses the manual pathway as a permanent operating model — allowing volume to grow without transitioning to EDI — creates an operational fragility that becomes commercially damaging at the volume levels that a successful Costco program generates.
At Fractional Brand Managers, we guide CPG brands through the complete Costco EDI setup process — from Implementation Guide interpretation through provider selection, mapping, testing, and go-live — and we build the operational monitoring infrastructure that sustains EDI compliance after the first purchase order.
Contact us at 732-433-7873 or info@fractionalbrandmanagers.com before your first Costco EDI certification cycle begins.
Costco EDI Requirements 2026 — Complete Quick Reference:
Transaction | Direction | Timing Requirement | Failure Cost |
EDI 850 Purchase Order | Costco → Vendor | Receive and process immediately | N/A (incoming) |
EDI 855 PO Acknowledgment | Vendor → Costco | Within 24 hours of 850 receipt | Compliance metric tracked |
EDI 856 ASN | Vendor → Costco | 2-4 hours before carrier pickup | $50-$250+ per incident |
EDI 810 Invoice | Vendor → Costco | Within 24-48 hours of ASN | Payment delay; dispute |
EDI 997 Functional Ack | Both directions | Immediately/automatically | Compliance metric tracked |
SSCC-18 Label Chargebacks: $50-$150 per carton with incorrect/unscannable labels
Data mismatch chargebacks (PO/ASN/Invoice): 1-3% of PO value
Performance benchmarks post go-live: ASN accuracy: above 99% | Invoice dispute rate: below 1%
Five-step setup: Implementation Guide → EDI provider → data mapping → certification testing → go-live + monitoring
#CostcoEDIRequirementsGuideCPG2026 #CostcoEDI2026 #CostcoEDICompliance #CostcoEDI850 #CostcoEDI856 #CostcoEDI810 #CostcoASN2026 #CostcoSSCC18 #CostcoEDISetup #CostcoVendorEDI #FractionalBrandManagers #CostcoChannel2026 #CPGBrands2026 #CostcoVendor2026 #CostcoCompliance2026 #EDICompliance2026 #CPGOperations2026 #CostcoEDIChargebacks #GetIntoCostco2026 #CPGSupplyChain2026



Comments