A complete guide to CDW's EDI requirements, the new API connection option, onboarding timelines, and common mistakes to avoid. Written for suppliers who need clear answers without the jargon.
Last updated: August 2026
CDW requires suppliers to exchange four X12 EDI documents: the 850 purchase order (CDW sends to you), and the 810 invoice, 856 advance ship notice, and — for some divisions — the 855 PO acknowledgment (you send to CDW). You can connect over traditional AS2 or CDW's newer API, which delivers documents in real time with no certificate management. Onboarding typically takes 2 to 4 weeks with an experienced provider; migrations from another provider usually take 2 to 3 weeks.
If CDW just told you that you need to be EDI compliant, you probably have questions. Maybe a lot of them.
What documents do they require? How do you connect? How long will this take? What does it cost? And what happens if you miss the deadline?
We've helped dozens of suppliers get live with CDW. Some had years of EDI experience. Others had never heard the term before CDW mentioned it. This guide covers everything you need to know, written for the person who needs clear answers without the jargon.
CDW uses Electronic Data Interchange to exchange business documents with suppliers electronically. Instead of emailing purchase orders and faxing invoices, everything flows through a structured digital format called X12.
A structured version of a purchase order containing item numbers, quantities, pricing, ship-to addresses, and delivery dates. Your EDI system receives and processes these automatically.
After you ship an order, your system generates a structured invoice that matches the original purchase order. This replaces the manual process of creating and emailing PDF invoices.
Tells CDW exactly what you shipped, when, and how. Includes tracking numbers, carton contents, and weight. CDW uses this to prepare their warehouse for receiving your shipment.
Confirms that you received the purchase order and can fulfill it. Think of it as a digital handshake confirming the order. Required by some CDW divisions but not all.
This is where things have changed significantly. CDW now offers two connection methods, and the one you choose affects your day-to-day experience.
AS2 is the traditional method for exchanging EDI documents. It works, but it comes with overhead.
Your EDI provider sets up an AS2 connection with CDW, which involves exchanging digital certificates between both parties. Documents are transmitted in batches, meaning there's a delay between when CDW sends a purchase order and when you see it in your system.
AS2 certificates expire and need to be renewed periodically. When a certificate expires or a connection breaks, transactions stop flowing until the issue is resolved. For small teams without dedicated IT staff, this can create stressful disruptions.
Most EDI providers in the market today still connect to CDW exclusively through AS2 or SFTP.
CDW now offers an API-based connection for EDI transactions. This is a significant upgrade over traditional AS2, and ActionEDI is one of the first providers fully integrated with it.
Purchase orders arrive the moment CDW sends them. No batch delays. Your team sees orders instantly instead of waiting for the next processing cycle.
The API connection doesn't rely on AS2 certificates. This eliminates certificate expiration issues, renewal headaches, and the connection failures that come with them.
When a document has a validation issue, the API flags it at the point of exchange. With traditional AS2, you might not discover an error until a batch has been processed and rejected hours later.
| Feature | Traditional AS2/SFTP | ActionEDI CDW API |
|---|---|---|
| Data delivery | Batch (periodic) | Real-time |
| Setup complexity | AS2 certificates, connection testing | API key, one-time setup |
| Certificate management | Required, periodic renewals | Not needed |
| Error detection | After batch processing | Immediate |
| Order visibility | Delayed | Instant |
| Maintenance | Certificate renewals, connection monitoring | Minimal |
Before anything technical happens, you need an EDI provider. When evaluating providers for CDW specifically, ask: Does the provider have experience with CDW's specific requirements? Do they support CDW's API or only AS2? What is their typical onboarding timeline for CDW? Can they show references from other CDW suppliers?
Your provider reviews CDW's specifications for your specific division. This is important because CDW domestic, CDW Canada, and CDW Government may have different requirements. Your provider will also need information from you: item numbers, standard pricing, warehouse locations, shipping methods, and any special handling requirements.
Your provider configures the EDI system to translate between CDW's required format and your internal data. This step requires attention to detail, particularly with the 856 Advance Ship Notice. CDW has specific segment requirements in the ASN that differ from other retailers.
CDW has a formal testing process. You submit test transactions for each document type and CDW's team reviews them for compliance. Most suppliers pass testing in 1 to 2 rounds if the initial mapping was done correctly. The speed of this phase depends on how quickly your EDI provider responds to testing feedback.
Once CDW approves your test transactions, real purchase orders start flowing. Monitor closely for the first few weeks. Your provider should be available for rapid support during this transition period.
They don't. CDW domestic and CDW Government can have meaningfully different requirements. Confirm all your CDW divisions upfront before starting setup.
The 856 Advance Ship Notice is where most testing failures happen with CDW. CDW has specific segment requirements for carton contents, weight, and tracking information that are more detailed than some other retailers.
A provider that's $100 per month cheaper but takes 3 months longer to onboard you costs far more in missed orders and retailer relationship strain.
EDI isn't set-it-and-forget-it. CDW periodically updates their specifications. Make sure your provider includes ongoing support and spec updates in their service, not as expensive add-ons.
If CDW gives you 60 days to become EDI compliant, starting at day 45 puts enormous pressure on the process. Begin evaluating providers the day you receive the requirement.
The extra time accounts for learning the basics and gathering internal data your provider needs.
Your team already understands EDI concepts, so the process moves faster.
Your existing trading partner data and document history can accelerate the setup.
These timelines assume your EDI provider responds to issues within hours, not days. If your provider's support response time is measured in days, multiply these timelines accordingly.
If you're currently connected to CDW through AS2 or SFTP with another provider, switching to ActionEDI's API integration is straightforward. We handle the migration, testing, and validation. Your CDW trading relationship stays the same. The connection method gets better. Most migrations complete in 2 to 3 weeks with zero disruption to your existing CDW orders.
Check CDW EDI fitCosts vary by provider and your specific requirements. Some providers charge per document, which means costs grow with your order volume. Others, including ActionEDI, use flat-rate annual pricing: with ActionEDI your first year is free, then $99/mo per trading partner (billed annually) with 2,400 transactions a year included account-wide and $0.50 each beyond that, quoted in writing before renewal. Most SMBs spend a few hundred dollars per month on EDI.
Technically possible but not practical for most SMBs. Managing your own EDI requires X12 expertise, AS2 or API infrastructure, ongoing maintenance, and the ability to respond to specification changes. For most small businesses, the cost of a provider is far less than the cost of building and maintaining internal EDI capability.
CDW now offers an API-based connection for EDI transactions. Unlike traditional AS2/SFTP which processes documents in batches, the API enables real-time data exchange. This means faster order processing, immediate error detection, and no AS2 certificate management. ActionEDI is one of the first providers fully integrated with this API.
Yes. ActionEDI handles the migration from your current AS2/SFTP connection to CDW's API. The transition typically takes 2 to 3 weeks and ensures zero disruption to your existing order flow.
You can switch your CDW connection to a provider that supports the API while keeping your existing provider for other trading partners. Or you can migrate entirely. Either approach works without disrupting your CDW trading relationship.
Yes. CDW domestic, CDW Canada, and CDW Government may have different specifications. Confirm which divisions you're supplying to before starting setup.
Three most common: incorrect ASN segment requirements, UPC or item number formatting mismatches, and missing or incorrect ship-to location codes. Providers with CDW experience typically avoid these because they've already mapped CDW's specific requirements.
No. We work with trading partners across retail and manufacturing. However, CDW is one of our strongest areas of expertise, and our full API integration with CDW is a specific advantage for CDW suppliers.
CDW requires suppliers to send and receive specific EDI documents in the correct X12 format through an approved connection method. Non-compliance can result in paused purchase orders, chargebacks, or removal from the vendor program.
Typically 2 to 4 weeks for new CDW suppliers. For migrations from another provider, 2 to 3 weeks. Timeline depends on document complexity and testing cycles.
Our CDW fit check takes about two minutes. We'll tell you honestly whether we can help with your specific setup.
Written by Ramesh Nuti, founder and CEO of ActionEDI. ActionEDI is one of the first EDI providers fully integrated with CDW's API.
