Costco EDI requirements: specifications, ASN rules, and compliance guide

Costco EDI compliance depends on making sure the data behind each order stays synchronized across ERP, warehouse, labeling, fulfillment, EDI, and finance systems.

Many suppliers approach Costco EDI as a documentation problem, when it’s actually an integration architecture problem. Costco EDI programs commonly include requirements for:

• Purchase orders
• Advance ship notices
• Invoices
• Functional acknowledgments
• ASN timing
• SSCC or GS1-128 label synchronization

When order, shipment, label, receiving, and invoice data fall out of sync, suppliers can face rejected transactions, delayed receiving, payment issues, deductions, or chargebacks.

The root cause is often not the X12 format alone. It is disconnected systems that cannot keep purchase orders, shipments, labels, acknowledgments, and invoices aligned as the order moves from purchase order to payment.

Because Costco requirements can vary by supplier program, region, fulfillment model, and implementation guide, suppliers should validate document requirements, timing windows, label rules, certification steps, and chargeback policies against Costco’s current official supplier documentation.

This guide explains how Costco EDI integration works, where it can break down, and how suppliers can build a governed data pipeline that supports compliance at scale.

What Costco commonly requires suppliers to send via EDI

Costco 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.

Each transaction must follow Costco’s current implementation guide, which may define:

• Required segments
• Field-level formats
• Sequencing rules
• Label and shipment data requirements
• Compliance validation rules
• Testing or certification requirements

Failure to comply can result in rejected transactions, payment delays, deductions, or chargebacks depending on the supplier program and issue type.

In order to generate these documents, the data behind them must be consistent across systems.

Core EDI transactions: 850, 856, 810, 997, and 860

Costco EDI workflows commonly include the following transaction sets, depending on the supplier program and implementation guide.

EDI 850 purchase order Costco sends a purchase order to the supplier.

EDI 856 advance ship notice The supplier sends an advance ship notice describing the shipment before it arrives. This may include shipment, carrier, carton, pallet, item, quantity, and label details depending on Costco’s requirements.

EDI 810 invoice The supplier sends invoice data for goods shipped or delivered.

EDI 997 functional acknowledgment The receiver confirms whether an EDI transaction was received and accepted or rejected at the functional or syntax level. A 997 does not confirm business acceptance, shipment receipt, or invoice approval.

EDI 860 purchase order change Costco may send an order change to update a purchase order.

These transactions form a connected workflow that must stay synchronized across ERP, warehouse, labeling, fulfillment, finance, and EDI systems.

Matching purchase order, ASN, receiving, and invoice data

Costco and other large retailers typically reconcile purchase order, ASN, receiving, and invoice data. If quantities, item identifiers, shipment details, label values, or invoice data do not align, suppliers may face rejections, payment delays, deductions, or chargebacks.

Maintaining this alignment at scale requires continuous synchronization between ERP, warehouse, labeling, fulfillment, finance, and EDI systems. Without that coordination, discrepancies accumulate and surface as operational and financial exceptions.

This is not only a document issue. It is a data pipeline and governance problem.

Why the advance ship notice is often the highest-risk document

The EDI 856 advance ship notice is often the most operationally complex and financially sensitive transaction in a Costco EDI workflow.

It can affect:

• Shipment receiving
• Inventory updates
• Carton or pallet validation
• Invoice matching
• Payment processing

ASN errors are a common source of compliance risk because the ASN must accurately represent the physical shipment before it arrives.

ASN data requirements

A Costco ASN implementation may require data such as:

• Shipment date
• Carrier and tracking details
• Purchase order reference
• Ship-from and ship-to information
• Item-level data, including SKU, quantity, and unit of measure
• Carton or pallet hierarchy
• SSCC identifiers, when required
• Packaging or handling-unit details

The ASN should reflect the physical shipment as accurately as possible. If the ASN says a carton contains one item and the physical carton contains another, receiving and invoice matching can break.

SSCC and GS1-128 label synchronization

When Costco requires carton-level or pallet-level ASN detail, suppliers may need GS1-128 labels with SSCC identifiers that match the values transmitted in the EDI 856\.

The SSCC should:

• Match the value in the ASN
• Match the barcode on the carton or pallet
• Stay synchronized across warehouse, labeling, fulfillment, and EDI systems

Suppliers often generate SSCC values, shipment data, and ASN content across different systems. Without orchestration, these values can drift, creating costly compliance failures.

This is why SSCC accuracy is an integration problem, not just a labeling problem.

Timing requirements and chargeback exposure

Costco’s ASN timing requirements should be verified in the current supplier implementation guide. In many retail EDI programs, the ASN must be transmitted before the shipment arrives and often before or around shipment departure.

Common failures include:

• Late ASNs
• Missing ASNs
• Incorrect shipment data
• Missing or incorrect label identifiers
• ASN data that does not match the physical shipment

Each failure can create a separate compliance issue, and errors can compound quickly across large shipments. These failures are often the result of uncoordinated data flows across systems.

How to become EDI compliant with Costco

Achieving Costco EDI compliance is an integration implementation project.

The real challenge is connecting the following into a single synchronized workflow:

• ERP systems
• Warehouse systems
• Labeling processes
• Fulfillment workflows
• EDI transactions
• Finance and invoicing systems

Connecting your ERP to Costco EDI requirements

ERP systems like NetSuite typically require configuration, an EDI solution, or an integration layer to produce trading partner-compliant X12 EDI transactions.

Suppliers usually need to:

• Map ERP data to EDI segments
• Transform internal data structures into Costco’s required format
• Validate transactions before transmission
• Enforce system-of-record ownership
• Keep order, shipment, label, and invoice data synchronized

Typically:

• ERP owns order and invoice data.
• Warehouse or fulfillment systems own shipment, carton, pallet, carrier, tracking, and label data.
• EDI systems transmit structured X12 documents to Costco or the designated provider network.

If these systems are not synchronized, compliance can fail even when each individual system appears correct.

Provider selection, testing, and go-live

The implementation process typically includes:

• Obtaining Costco’s current EDI specifications and implementation guides
• Confirming required transaction sets
• Mapping to Costco EDI requirements
• Configuring transaction flows
• Setting up communication through AS2, VAN, or another approved provider network
• Testing sample files and business scenarios
• Completing required certification steps
• Going live with monitoring and error management in place

Certification requirements and timelines depend on Costco’s current supplier program and onboarding process.

Compliance does not end at go-live. It depends on how reliably the workflow operates under real production conditions.

Common Costco EDI compliance mistakes

Most failures come from integration gaps, not EDI itself.

Purchase order, ASN, receiving, and invoice mismatches Order, shipment, receiving, and invoice data do not align.

ASN errors and timing issues Advance ship notices are missing, late, incomplete, or inaccurate.

SSCC mismatches Labels and EDI data are out of sync.

Disconnected systems ERP, warehouse, labeling, fulfillment, finance, and EDI systems operate independently.

Manual processes Spreadsheets, rekeying, and batch uploads introduce errors.

Lack of monitoring Errors are detected only after rejection, delayed receiving, payment disruption, or chargeback exposure.

These are systemic failures caused by lack of orchestration and visibility.

How Celigo automates Costco EDI compliance workflows

Costco EDI compliance can break down when data moves between systems without coordination.

Celigo helps solve this by turning EDI from a document exchange into a governed, end-to-end data workflow across ERP, warehouse, fulfillment, labeling, finance, and trading partner systems.

Instead of managing EDI, labeling, ERP integration, and error handling separately, Celigo can provide a centralized control layer for the workflow.

Connecting systems into a unified pipeline

Celigo can connect:

• ERP systems like NetSuite
• Warehouse management systems
• Fulfillment systems
• Labeling processes
• EDI transactions
• Supplier and retailer systems

This helps keep purchase orders, shipments, labels, acknowledgments, and invoices synchronized across systems.

Orchestrating the full EDI lifecycle

A Costco EDI workflow may look like this:

Costco sends an EDI 850 purchase order
       ↓
Celigo parses the transaction and creates a sales order in NetSuite or another ERP
       ↓
Warehouse, ERP, or fulfillment systems provide shipment, carton, pallet, tracking, and label data
       ↓
SSCC and label data are synchronized across systems
       ↓
Celigo maps shipment and label data into the EDI 856 advance ship notice
       ↓
The ASN is transmitted according to Costco's timing and formatting requirements
       ↓
Celigo maps invoice data into the EDI 810 invoice
       ↓
Functional acknowledgments such as EDI 997 confirm EDI receipt and validation status

Celigo supports this by helping teams:

• Connect ERP, warehouse, fulfillment, labeling, finance, and EDI systems
• Turn EDI transactions into executable workflows
• Synchronize purchase orders, shipments, labels, and invoices
• Support SSCC and ASN data synchronization across systems
• Route exceptions into monitored error handling
• Manage partner-specific mapping and validation requirements

Operating EDI in production with visibility and control

Celigo provides capabilities for:

• Centralized monitoring of EDI flows
• Tracking functional acknowledgment statuses
• Viewing transaction-level EDI activity
• Managing errors and retries
• Using dashboards and notifications to detect issues
• Monitoring open, auto-resolved, and user-resolved errors

Instead of reacting to errors only after they affect receiving or payment, teams can detect and resolve issues earlier in the process.

Celigo treats EDI as an operational workflow, not just a file transfer.

The control layer that turns Costco EDI into an automated workflow

Costco EDI does not usually fail at the document level alone. It fails when the integration layer cannot keep systems synchronized.

When purchase orders, ASNs, labels, receiving data, and invoices are not aligned across systems, suppliers face avoidable operational and financial risk.

The suppliers that scale successfully are not only the ones with a working EDI setup. They are the ones with a governed integration architecture that keeps systems in sync under real-world conditions.

Celigo provides a control layer that helps turn Costco EDI from a source of risk into a reliable, automated workflow the business can run.

→ Request a demo to see how Celigo helps suppliers automate Costco EDI workflows, synchronize ASN and invoice data, and reduce chargeback risk.