Supplier and vendor access
Each supplier, 3PL and vendor connection has its own account and limited scope, so one compromised credential cannot reach other partners' data.
Retail integration
A guide for suppliers connecting with Costco, covering the core documents, depot and cross-dock shipping, labeling and ERP integration.
At a glance
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Costco program or a customer relationship.
Tell us which documents you exchange with Costco, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Costco.
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
Overview
Who this is for: Manufacturers and brands supplying Costco warehouses and depots, and the EDI, logistics and finance teams that support them.
Costco moves high volumes of a relatively small number of items through a network of depots and warehouses, and EDI keeps that model running. For most suppliers, the core documents are the purchase order from Costco, the advance ship notice describing each shipment, the invoice, and functional acknowledgments. Some programs also use purchase order acknowledgments, order changes or inventory documents.
Costco's depot and cross-dock operations make shipment data especially important. In cross-dock operations like Costco's, the ship notice is usually the most compliance-sensitive document, because depots plan receiving and cross-docking around it, and carton and pallet labels must match it. Invoices are expected to reconcile with the purchase order and the shipment.
Costco does not publish its EDI implementation guide publicly. Suppliers typically test before production, and the guide, obtained through Costco's buyer and vendor channels, defines the exact versions, segments and testing steps, so treat it as the authoritative reference.
Program summary
A summary in ECOM's own words. Requirements vary by program and change over time, so confirm the details with Costco during setup.
Workflows
A typical flow built from the documents below; your own program may differ.
Documents and APIs
Documents used in Costco's EDI program, seen from the supplier's side. Which ones apply depends on your program, so confirm the list with Costco.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Status | Purpose |
|---|---|---|---|---|
| 850 | Purchase Order | You receive from Costco | Program document | Places an order for goods. |
| 860 | Purchase Order Change | You receive from Costco | Program document | Changes an existing order. |
| 856 | Ship Notice/Manifest | You send to Costco | Program document | Describes a shipment before it arrives. |
| 810 | Invoice | You send to Costco | Program document | Bills for what shipped. |
| 820 | Payment Order/Remittance Advice | You receive from Costco | Program document | Explains what a payment covers. |
| 824 | Application Advice | You receive from Costco | Program document | Reports whether a document was accepted or has errors. |
| 997 | Functional Acknowledgment | Both directions | Program document | Confirms each file was received and readable. |
Connectivity
Suppliers can exchange documents with Costco over direct internet connections such as AS2 or SFTP.
General guidance
Many suppliers connect through an EDI provider or network that manages the Costco connection.
General guidance
Challenges
Depots plan receiving around the 856, so it must be accurate and sent before the shipment arrives.
GS1-128 labels on cartons and pallets must match the identifiers in the ship notice.
Invoices must line up with the purchase order and shipment to avoid payment delays.
Automation options for Costco suppliers
ECOM helps you automate them, meet Costco's labeling and ship notice requirements, and see what needs action. Costco sets its program's rules; ECOM confirms which options fit yours.
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/APIReceive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDIConvert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvertAutomate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
Learn more about WebConnectPRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.
ECOM integrates Costco documents with ERP and warehouse systems so ship notices and labels are generated from real pick and pack data and invoices match the order.
Monitor ship-notice timing and invoice matches for every Costco order.
Zero Trust for supplier data exchange
Supplier exchanges with Costco carry orders, ship notices, invoices and item data. A Zero Trust design assumes no connection, file or user is safe by default.
ECOM has implemented Zero Trust EDI and Zero Trust MFT in retail.
For supplier exchanges this means each supplier and vendor connection has its own scope, orders, ship notices and invoices are verified on arrival, late or altered files are noticed early, and the transfer log helps answer deduction and security-review questions.
Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.
Business outcome: A lost or reused credential affects one partner, not all of them.
Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.
Business outcome: A mistake or compromise in one account stays limited to what that account could reach.
Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.
Business outcome: Outside connections do not land directly on your internal systems.
Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.
Business outcome: Less exposure if a file is intercepted or a file store is reached.
Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.
Business outcome: Fewer outages caused by an expired certificate or key.
Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.
Business outcome: Late, missing or failed files are noticed early, before they hold up late shipments or deductions.
Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.
Business outcome: You can answer who sent what and when, for your own audits and partner reviews.
Each supplier, 3PL and vendor connection has its own account and limited scope, so one compromised credential cannot reach other partners' data.
Documents are verified when they arrive and every transfer is logged, so a missing or altered file shows up quickly.
Replace shared logins and open folders with named accounts, reviewed on a schedule you set.
Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Costco may set its own security requirements, which come first.
Talk to an EDI/API Expert about Zero Trust Managed file transferSecure proxy and DMZ designSecurity at ECOM
Next step
Each request goes to an ECOM EDI specialist with Costco's name attached, so the reply starts from your program.
Send us Costco's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements reviewOrders in, ship notices and invoices out, from the ERP and warehouse systems you already run.
Discuss ERP integrationBuild, test and certify each Costco document, then go live with monitoring from the first file.
Plan testing and certificationLabels and ship notices that match Costco's rules, to help avoid receiving problems and compliance deductions.
Review shipping complianceRetail suppliers typically exchange the 850 purchase order, 856 ship notice, 810 invoice and 997 functional acknowledgment, with the 855, 860 or 846 for some programs. Costco's own implementation guide, obtained through your Costco buyer, is the authoritative list.
Costco's depots and cross-dock operations plan receiving around the ship notice, so it needs to be accurate and to arrive before the shipment.
In retail EDI, carton and pallet GS1-128 labels must carry the same identifiers as the ship notice. Confirm Costco's label requirements in its guide.
This page is an integration guide and does not indicate an approval or partnership with Costco. ECOM builds integrations to Costco's published requirements.
This guide describes Costco's program in ECOM's own words as of November 2026. Costco sets its own requirements and can change them at any time; your Costco implementation guide, supplier portal or account contact is the authoritative source for your program.
Costco is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
How EDI and API integration with Metropolitan Market typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Metropolitan Market.
How EDI and API integration with Michaels typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Michaels.
How EDI and API integration with Miskelly Furniture typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Miskelly Furniture.
How EDI and API integration with Mitsuwa Marketplace typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Mitsuwa Marketplace.
How EDI and API integration with MOM's Organic Market typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with MOM's Organic Market.
How EDI and API integration with Mor Furniture for Less typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Mor Furniture for Less.
Tell us about your Costco program, documents and ERP. We will outline the connection, mapping and testing plan.