EDI (Electronic Data Interchange)
Electronic Data Interchange (EDI) is the structured exchange of business documents between trading partners in a machine-readable format. EDI predates the modern internet and remains foundational to B2B commerce, particularly in retail, wholesale, and supply chain operations.
Common X12 EDI document types include:
- 850 - Purchase Order (buyer to supplier)
- 855 - Purchase Order Acknowledgement
- 856 - Advance Shipping Notice (supplier to buyer)
- 810 - Invoice
- 846 - Inventory Inquiry/Advice
- 997 - Functional Acknowledgement
Shopify Plus integrations can connect EDI workflows through middleware or an ERP, rather than treating an EDI document as a native Shopify order import. Providers such as SPS Commerce, TrueCommerce, B2B Gateway and Cleo need to be assessed against the actual trading-partner requirements and supported Shopify connection. Define how documents map to Shopify Admin GraphQL operations and which system owns each record.
Choose the owner around the systems already handling orders, inventory, fulfilment and invoices. An ERP-led setup, middleware or a custom integration can each fit different requirements. Agree document versions, partner-specific mappings, acknowledgements, retries and exception handling, then test the complete order-to-invoice journey. See B2B Migration: Moving Wholesale to Shopify Plus Without Breaking Pricing.
Frequently asked questions
What are the most common EDI documents?
Common X12 examples are 850 purchase order, 855 purchase order acknowledgement, 856 ship notice or advance shipping notice, 810 invoice, 846 inventory inquiry/advice and 997 functional acknowledgement. Confirm the standard, version and partner-specific implementation guide; these numbers are not universal across all EDI standards.
Does Shopify Plus support EDI?
Shopify can participate in an EDI workflow through an integration, middleware or an ERP. Confirm the provider’s supported Shopify connection, document mappings and exception handling. EDI translation and trading-partner compliance are separate from creating or updating a Shopify record.
Who should own EDI in a Shopify Plus stack?
Choose the owner based on the systems and team already responsible for the relevant records. An ERP, middleware or a custom integration can own the connection. Document field ownership, acknowledgements, retries, monitoring and reconciliation before launch; there is no universal best owner for every business.
Related terms: Shopify B2B, Punchout, Shopify Admin API. For hands-on help, see Flux's Shopify Plus B2B work.
Shopify Plus development and AI search
We build Shopify Plus stores that customers and AI shopping agents can find, compare and buy from. 210+ stores since 2012.
Chosen by Shopify Plus brands worldwide.














