Retailers
Retail order, fulfilment, inventory, and invoice workflows.
Browse EDIXT trading partner pages by category, search for a specific retailer or supplier, and move into profiles that cover common transaction sets, onboarding flow, communication methods, validation risks, and related integration paths. This page is designed to help teams researching Electronic Data Interchange (EDI) partner requirements before implementation work starts.
The directory spans the kinds of trading relationships teams most often need to support in real-world B2B programs, from retailers and grocery groups to suppliers, distributors, carriers, and marketplace platforms.
Each category hub groups similar trading partner pages together so you can move directly into the part of the Electronic Data Interchange (EDI) network that matters most, whether you are researching retailers, suppliers, wholesalers, logistics providers, carriers, or marketplaces.
Retail order, fulfilment, inventory, and invoice workflows.
Wholesale order, stock, fulfilment, and invoice control.
Warehouse, shipment, status, and fulfilment coordination.
Shipment events, transport billing, labels, and proof-of-delivery flow.
Marketplace order, inventory, settlement, and return coordination.
Platform-led integration, operational sync, and downstream data movement.
Distribution order flow, stock movement, and account visibility.
Demand, planning, despatch, and invoice flow for manufacturing operations.
Supplier onboarding, order confirmation, despatch, and invoice control.
Healthcare supply, auditability, and critical operational messaging.
Automotive schedules, parts movement, despatch, and invoice control.
Hospitality purchasing, stock, and supplier coordination.
This directory is designed to help users do more than find a company name. The goal is to support better Electronic Data Interchange (EDI) research, better scoping, and better conversations before implementation work starts.
The strongest partner pages help teams focus quickly on the documents that normally drive rollout work, such as 850 purchase orders, 810 invoices, 856 advance ship notices, 855 acknowledgements, 846 inventory, 940 warehouse shipping orders, 945 warehouse shipping advice, and functional acknowledgements like 997 or 999.
Trading partner research is not only about document numbers. Teams usually need to understand whether the relationship leans toward AS2, SFTP, API, VAN, portal-based exchange, or a mixed setup that ties partner data into ERP, WMS, finance, or commerce platforms.
A useful directory page should help you walk into onboarding with better questions: what data fields are likely to be sensitive, where document validation usually fails, which internal systems are affected, and what testing path the implementation team should expect.
These partner pages highlight recognisable trading partners that teams commonly search for first, including major retailers and established wholesale operators already active in EDI programs.
Walmart US Electronic Data Interchange (EDI) retailer profile built around purchase order, purchase order acknowledgement, advance ship notice, and invoice, transport design, and downstream handoff into ERP, Warehouse management, and Carrier systems.
Tesco UK Electronic Data Interchange (EDI) retailer profile built around purchase order, purchase order acknowledgement, advance ship notice, and invoice, transport design, and downstream handoff into ERP, Warehouse management, and Carrier systems.
Lidl UK Electronic Data Interchange (EDI) retailer profile built around purchase order, purchase order acknowledgement, advance ship notice, and invoice, transport design, and downstream handoff into ERP, Warehouse management, and Carrier systems.
Lidl US Electronic Data Interchange (EDI) retailer profile built around purchase order, purchase order acknowledgement, advance ship notice, and invoice, transport design, and downstream handoff into ERP, Warehouse management, and Carrier systems.
Carrefour France Electronic Data Interchange (EDI) retailer profile built around purchase order, purchase order acknowledgement, advance ship notice, and invoice, transport design, and downstream handoff into ERP, Warehouse management, and Carrier systems.
Aldi UK Electronic Data Interchange (EDI) retailer profile built around purchase order, purchase order acknowledgement, advance ship notice, and invoice, transport design, and downstream handoff into ERP, Warehouse management, and Carrier systems.
Aldi US Electronic Data Interchange (EDI) trading profile covering X12 810, 850, 997, rollout checkpoints, and downstream handoff into ERP, Warehouse management, and Carrier systems.
Target US Electronic Data Interchange (EDI) trading profile covering X12 850, 856, 810, 860, rollout checkpoints, and downstream handoff into ERP, Warehouse management, and Carrier systems.
These are the questions teams usually ask when they are evaluating a new retailer, supplier, wholesaler, carrier, or marketplace connection.
An EDI trading partner directory is a structured way to research the businesses you exchange documents with, including retailers, wholesalers, suppliers, logistics providers, marketplaces, and carriers. Instead of a flat list of names, a useful directory helps teams understand document scope, onboarding expectations, and which systems or workflows are likely to be touched.
A useful partner page should go beyond a company name. It should help teams understand common transaction sets, likely communication methods, rollout and testing considerations, and the surrounding systems that may need integration support. That is why EDIXT partner pages are designed to connect partner research to operational planning.
After identifying the right partner page, most teams move into one of three next steps: reviewing related integrations, checking a relevant solution path, or using the contact page to discuss onboarding, document mapping, or rollout support.