Costco EDI Integration
Costco Wholesale exchanges purchase orders, acknowledgments, ship notices and invoices with suppliers as X12 EDI, for many suppliers through SPS Commerce. We build the 850, 855, 856 and 810 inside your own ERP with the EdiFabric .NET library. Your system builds and reads every file, and SPS Commerce validates and delivers it.
+ RULES
- Top Rated PlusUpwork talent badge
- 100%Upwork Job Success score
- 17,800+Hours billed on Upwork
- 2012AppsXone established
“They integrated with multiple third-party systems and they did a great job with it. It’s stable, scalable, which was our goal, and we saved a lot of time and effort.”
Costco Wholesale EDI and Costco.com dropship are different integrations
In Costco Wholesale, Costco buys your stock and you ship it to Costco. That is the program this page covers, and we run it in production today through SPS Commerce.
In Costco.com dropship, Costco takes a customer order and you ship that single order to the customer, usually through CommerceHub rather than SPS Commerce. It is a separate integration, covered in our guide to Costco.com dropship for suppliers and brands.
Which program you are in, and which network it uses, is set by Costco for your account. Confirm it before planning the work.
What Costco EDI integration covers
-
850Purchase order. Costco orders stock from you. The ERP turns it into a real order, with Costco's item numbers mapped to your own. See EDI 850 purchase order. -
855Acknowledgment. You confirm what you can actually ship, with quantities and dates, before Costco plans against the order. -
856Advance ship notice. Sent when the goods ship. It has to describe what physically left the warehouse. See EDI 856 advance ship notice. -
810Invoice. Bills Costco for what shipped, matched line for line against the ship notice. See EDI 810 invoice. -
SPSSPS Commerce delivery. Outbound files uploaded to SPS Commerce's FTP and inbound files collected from it on a schedule. -
LOGMonitoring. Every scheduled job tracked on a dashboard: when it last ran, what it picked up and what was rejected.
What SPS Commerce does, and what stays in your ERP
SPS Commerce sits between your system and Costco. In the connection we run it does not translate anything. The ERP builds each outbound X12 file itself and uploads it to SPS Commerce's FTP, and it reads each inbound file SPS Commerce delivers. SPS Commerce validates the files and passes them between the two sides.
That split matters when a document is rejected. The file and the order record it came from sit in the same system, so finding the cause is a comparison inside your own data rather than a support ticket. There is a longer walk-through in Costco EDI integration through SPS Commerce.
How we build Costco EDI inside your ERP
Start from your Costco and SPS Commerce specification
The specification for your account sets the documents, fields and validation rules. We map it against your order, shipment and invoice data first, so missing data shows up before development.
Files built and read inside the ERP
Each X12 file is read and generated with the EdiFabric .NET library, and the mapping lives in your ERP's own code.
Ship notice and invoice follow the shipment
The 856 describes what the warehouse actually shipped, and the 810 bills for that, not for what was ordered.
Raw file kept with the parsed result
The original document is stored beside what was read from it, so a rejection is traced to the exact value that caused it.
One order queue for every partner
Costco orders land in the same order, inventory and shipment records as every other channel. There is no second copy of stock to reconcile.
Costco Wholesale EDI in a live ERP
- Costco Wholesale EDI (850, 855, 856 and 810) running through SPS Commerce for a US consumer electronics brand.
- Every X12 file read and generated inside the ERP using the EdiFabric .NET library, with the mapping in the ERP's own code.
- Costco is one of more than a dozen retail trading partners on the same ERP, sharing one order queue and one inventory position.
- Scheduled EDI jobs polling FTP on schedules as short as every ten minutes, tracked on a monitoring dashboard.
Where Costco EDI goes wrong
- The ship notice describes the order, not the shipment A common pattern on retail EDI. The warehouse changes a carrier, a carton count or a quantity after the order is confirmed, and the 856 still carries the original plan. Generating the 856 from the shipment record instead of the order closes the gap.
- Invoice lines that do not match what shipped A common pattern. A substitution at the warehouse never reaches the order record, and the 810 bills an item that was not on the truck. The invoice has to follow the shipment.
- An acknowledgment that promises what the warehouse cannot ship A common pattern when the 855 is sent automatically from the order as received. Confirming quantities and dates against live stock before the 855 goes out avoids a later shortfall against the purchase order.
- Nobody notices a job has stopped A common pattern with scheduled file exchange. A job fails quietly and the first sign is a call from the buyer. A dashboard that shows the last run and the last file for each job makes a stopped job visible the same day.
Costco EDI integration questions
Does Costco require EDI?
Costco Wholesale exchanges orders, ship notices and invoices with its suppliers as EDI. What your own account is required to exchange, and through which network, is set by Costco. Check the specification for your account.
Do we have to use SPS Commerce for Costco?
The Costco Wholesale connection we run goes through SPS Commerce. Your account's requirements come from Costco, so confirm the network with them. Either way, your ERP can build and read the X12 files itself.
Does SPS Commerce translate our documents?
Not in the connection we run. The ERP builds and reads the X12 files itself. SPS Commerce validates them and delivers them between the ERP and Costco.
Which documents does a Costco Wholesale connection exchange?
The connection we run exchanges the 850 purchase order, 855 acknowledgment, 856 ship notice and 810 invoice. Your own account's list is set by Costco and SPS Commerce.
Is Costco.com dropship the same integration?
No. Dropship is a separate program, where you ship each order to the customer, and it usually runs through CommerceHub. This page covers Costco Wholesale through SPS Commerce.
Can this be built into an ERP we already run?
Often yes. What matters is whether your order, shipment and invoice data is reachable, not who wrote the ERP. We confirm that during scoping.
Who owns the mapping code?
You do. It sits in your ERP codebase.
Related to Costco EDI integration
Has Costco asked you to go live on EDI?
Tell us which Costco program you are in, what the specification asks for and what your ERP runs on. We will tell you what the integration involves.