EDI for ecommerce is the use of Electronic Data Interchange to exchange purchase orders, invoices, and shipping notices between an ecommerce store and its retailer or wholesaler trading partners. If you sell on Shopify, WooCommerce, BigCommerce, or Magento and have moved beyond DTC into B2B wholesale or dropship, you'll hit retailer EDI requirements within your first ten wholesale accounts.
This guide covers what EDI in ecommerce actually means, how it differs from API integrations, and the patterns for each major ecommerce platform.
What is EDI in ecommerce?
EDI in ecommerce is the automated exchange of standardized X12 business documents between an ecommerce store and trading partners, replacing manual PO entry and email handoffs with a direct, auditable data pipeline. The most common documents are:
- EDI 850 (Purchase Order): the wholesale buyer sends this to your store
- EDI 855 (PO Acknowledgment): you confirm receipt and item availability
- EDI 856 (Advance Ship Notice): you tell the buyer what shipped, when, with carton-level detail
- EDI 810 (Invoice): the financial settlement document
- EDI 997 (Functional Acknowledgment): low-level "I got your message" confirmation
- EDI 846 (Inventory Inquiry): stock levels for dropship retailers like Costco and Target+
Key authoritative context on why EDI remains the standard for ecommerce B2B:
- The ASC X12 standards body maintains the transaction sets that every major retailer uses, from Walmart to Whole Foods, making X12 the universal B2B retail protocol
- GS1 US standards govern the GTIN/UPC identifiers and SSCC-18 carton labels that compliant ASN (856) documents require for retail receiving
For an ecommerce store, EDI usually shows up in two scenarios. First, you sell wholesale to retailers and a buyer like Whole Foods Market sends 850 POs that need to flow into your fulfillment workflow. Second, you dropship for retailers like Walmart Marketplace or Target+, where the retailer sends orders to you via 850 and expects 856 ASN responses.
How EDI differs from API integrations
People sometimes ask why EDI exists when modern ecommerce uses REST APIs. Two reasons.
First, EDI is the established standard for B2B retail trading. Walmart, Target, Costco, Kroger, Albertsons, and most other major retailers exchange documents in X12 format because that's what their internal systems and their thousands of other suppliers use. They won't accept REST API submissions. Your store's API doesn't matter; the retailer dictates the protocol.
Second, EDI is batch-friendly and idempotent in ways that suit B2B retail volume. A 5,000-line PO from a major retailer is one EDI document, not 5,000 API calls. Returns, chargebacks, and ASN mismatches all work against well-defined X12 segments rather than against an evolving API contract.
For comparison, the AWS Electronic Data Interchange overview covers the historical context of why EDI persisted as the B2B retail standard.
EDI by ecommerce platform
Shopify and Shopify Plus
Shopify has the largest ecommerce-EDI ecosystem because of Shopify Plus B2B's traction with wholesale brands. Most Shopify Plus brands that hit a retail wholesale channel pick one of three patterns: a Shopify App Store EDI app like Crstl or SPS Commerce, a managed platform that runs alongside Shopify, or a direct ERP-side integration if the brand also runs NetSuite or Acumatica behind the storefront. See the Shopify EDI integration and EDI for Shopify pages for the full breakdown.
Time to first wholesale partner: 1 to 3 weeks via App Store or managed platform.
WooCommerce
WooCommerce powers the WordPress ecommerce ecosystem, which skews smaller and more SMB-focused than Shopify Plus. EDI on WooCommerce typically goes through a WordPress plugin or a managed platform connected via the WooCommerce REST API. There's less SaaS app saturation than Shopify, which means lower competition for the platform-specific EDI plugin keyword. See the WooCommerce EDI integration and EDI for WooCommerce pages.
Time to first wholesale partner: 1 to 3 weeks.
BigCommerce
BigCommerce skews toward mid-market B2B and headless commerce setups. Its REST and GraphQL APIs make it integration-friendly, but the EDI ecosystem is smaller than Shopify's. Most BigCommerce B2B brands use a managed EDI platform that connects via the BigCommerce API rather than installing a marketplace app.
Magento (Adobe Commerce)
Magento has a long history of B2B usage and a long history of complex ERP integrations. Most Magento B2B installs run an ERP behind the storefront (Sage, NetSuite, SAP), and EDI integration usually happens at the ERP layer, not the Magento layer. The Magento store stays focused on order capture and product catalog while the ERP handles the EDI document flow.
Common EDI documents for ecommerce sellers
A typical wholesale or dropship ecommerce flow uses five core documents:
- EDI 850 (Purchase Order): the buyer sends this when they want to buy. For dropship, this is the customer order. For wholesale, this is a bulk order from a retailer's purchasing system.
- EDI 855 (PO Acknowledgment): you respond confirming the order, with availability and any pricing exceptions.
- EDI 856 (Advance Ship Notice): at pack time, you tell the buyer what's in the box, in carton-level detail with UCC-128 labels for compliant retailers. ASN timing is the #1 chargeback driver in ecommerce-B2B.
- EDI 810 (Invoice): post-shipment, you bill the buyer.
- EDI 997 (Functional Acknowledgment): every inbound document gets a 997 confirming you received and parsed it.
Detailed guides for each: EDI 850, EDI 855, EDI 856, EDI 810, EDI 997.
EDI vs API for Ecommerce: Quick Reference
| Factor | EDI | API |
|---|---|---|
| Required by retailers | Yes (Walmart, Target, Costco, Kroger) | No |
| Data format | X12 (850, 856, 810, 997) | JSON/REST |
| Communication style | Batch documents | Real-time requests |
| Setup time per partner | 1-3 weeks | Days to weeks |
| Dropship support | Yes (850 PO, 856 ASN required) | Platform-dependent |
| Best for | B2B wholesale, retail compliance | Inventory sync, DTC platforms |
Key rule: Retailers dictate the protocol. If Walmart or Target is in your customer pipeline, you need EDI regardless of your ecommerce platform's API capabilities.
Practical split: Most ecommerce sellers end up using both: EDI for retail trading partners and APIs for inventory sync with their warehouse or ecommerce platform. These are complementary layers, not competing choices.
When you need EDI vs. when API integrations are enough
If your wholesale buyers are small independent retailers and they place orders through a B2B portal or via email, you don't need EDI. Stick with order capture through the ecommerce platform's standard B2B features.
You need EDI when:
- A major retailer (Walmart, Target, Costco, Kroger, Whole Foods, Amazon Vendor Central) is in your customer pipeline. They'll require it during onboarding.
- You're selling on a dropship marketplace (Walmart Marketplace, Target+) that uses EDI for order routing.
- You have more than 20 wholesale accounts and are spending real time keying POs from emails and spreadsheets.
- A 3PL is involved and they need 856 ASN data flowing back to retailers automatically.
The Cleo "EDI in eCommerce" guide goes deeper on the marketplace-specific scenarios.
Common pitfalls
Three patterns trip up ecommerce sellers during EDI rollout:
- Underestimating compliance work per retailer. Each major retailer has its own routing guide. Walmart's spec is not Target's spec is not Costco's spec. Plan for partner-specific configuration, not a generic implementation.
- Skipping ASN testing. ASN timing and content drive chargebacks. Test against the retailer's pre-production environment until they sign off, not just against your own validator.
- Treating EDI as a Shopify app problem. If you also run an ERP (NetSuite, Sage, Acumatica) behind your Shopify store, EDI integration belongs at the ERP layer, not the Shopify layer. The ERP is the system of record. See the ERP EDI integration guide for the integration architecture decisions.
Test your inbound and outbound EDI files against partner specs with the free EDI Inspector before going live.
Frequently Asked Questions
Do I need EDI if I only sell on Shopify?
Not for DTC sales. Shopify orders flow through Shopify's own APIs. You need EDI when a wholesale buyer or retail trading partner requires it during onboarding. That threshold typically arrives when you land your first major retail account (Walmart, Target, Whole Foods) or when you start dropshipping for a marketplace that routes orders via 850 purchase order.
What is the difference between EDI and API for ecommerce?
EDI is a batch-oriented document exchange standard that retailers mandate for purchase orders, invoices, and ship notices. APIs are real-time, request-response interfaces used by modern platforms. Major retailers will not accept REST API submissions for their core transactions. Your ecommerce platform's API is irrelevant to Walmart's EDI requirement. Most ecommerce sellers end up using both: EDI for retail compliance and APIs for inventory sync with modern tools.
How long does EDI setup take for an ecommerce store?
For a Shopify Plus brand using a managed platform or App Store app, plan 1 to 3 weeks to go live with the first trading partner. Each additional partner requires partner-specific configuration (routing guides, UCC-128 label formats, ASN timing rules) that adds days, not weeks, once your platform is connected. Custom ERP-side integrations take longer.
What is the ASN and why does it cause chargebacks?
The EDI 856 Advance Ship Notice (ASN) tells the retailer what is on the truck before it arrives, including carton-level detail and UCC-128 labels. Retailers use it to automate receiving. If the ASN arrives late, has wrong carton counts, or references incorrect SKUs, the retailer's system cannot match the delivery and issues a chargeback. ASN accuracy is the single biggest compliance variable for ecommerce sellers in their first year of retail EDI.
Can I use the same EDI setup for multiple retailers?
Yes. A single EDI platform connection covers all your trading partners. The transport layer (your AS2 connection or VAN) is shared. What changes per retailer is the implementation guide: each retailer has specific segment requirements, reference codes, and timing rules. A managed EDI platform handles those per-partner configurations so you do not rebuild the integration each time.
Where to go next
Pick the platform you're on:
- EDI for Shopify and the Shopify integration page
- EDI for WooCommerce and the WooCommerce integration page
Or jump to a retailer compliance page if you have a specific partner you're onboarding: Walmart, Target, Costco, Kroger, Amazon, Whole Foods.