Trading partner directory

EDI trading partner directory for retailers, suppliers, wholesalers, logistics providers, and marketplaces

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.

12 category hubs 6800 live partner pages Built around Electronic Data Interchange (EDI) onboarding and partner research

Common EDI trading partners across retail, wholesale, logistics, and marketplaces.

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.

Amazon logo
Tesco logo
Walmart logo
Target logo
Lidl logo
Carrefour logo
DHL logo
UPS logo

Browse EDI trading partners by category instead of working through one flat directory

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.

4800 pages

Retailers

Retail order, fulfilment, inventory, and invoice workflows.

Open category hub
313 pages

Wholesale partners

Wholesale order, stock, fulfilment, and invoice control.

Open category hub
272 pages

Logistics

Warehouse, shipment, status, and fulfilment coordination.

Open category hub
21 pages

Carriers

Shipment events, transport billing, labels, and proof-of-delivery flow.

Open category hub
10 pages

Marketplaces

Marketplace order, inventory, settlement, and return coordination.

Open category hub
57 pages

Platforms

Platform-led integration, operational sync, and downstream data movement.

Open category hub
94 pages

Distributors

Distribution order flow, stock movement, and account visibility.

Open category hub
572 pages

Manufacturers

Demand, planning, despatch, and invoice flow for manufacturing operations.

Open category hub
157 pages

Suppliers

Supplier onboarding, order confirmation, despatch, and invoice control.

Open category hub
306 pages

Healthcare partners

Healthcare supply, auditability, and critical operational messaging.

Open category hub
149 pages

Automotive partners

Automotive schedules, parts movement, despatch, and invoice control.

Open category hub
49 pages

Hospitality partners

Hospitality purchasing, stock, and supplier coordination.

Open category hub

What teams can learn from a trading partner page before onboarding begins

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.

Document scope

See which EDI transaction sets usually matter first

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.

Connectivity

Understand the likely communication pattern before testing starts

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.

Onboarding

Use the directory to prepare validation and onboarding conversations

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.

Popular EDI trading partner pages

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.

Popular trading partner Retailer · the United States
US

Walmart US

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.

Retailer · Standard rollout scope
Popular trading partner Retailer · the United Kingdom
UK

Tesco UK

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.

Retailer · Standard rollout scope
Popular trading partner Retailer · the United Kingdom
UK

Lidl UK

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.

Retailer · Standard rollout scope
Popular trading partner Retailer · the United States
US

Lidl US

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.

Retailer · Standard rollout scope
Popular trading partner Retailer · France
FR

Carrefour France

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.

Retailer · Standard rollout scope
AU Popular trading partner Retailer · the United Kingdom
UK

Aldi UK

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.

Retailer · Standard rollout scope
AU Popular trading partner Retailer · the United States
US

Aldi US

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.

Retailer · 3 documented transactions
Popular trading partner Retailer · the United States
US

Target US

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.

Retailer · 4 documented transactions

EDI trading partner directory FAQs

These are the questions teams usually ask when they are evaluating a new retailer, supplier, wholesaler, carrier, or marketplace connection.

FAQ

What is an EDI trading partner directory?

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.

FAQ

What should a useful trading partner page include?

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.

FAQ

Where should I go after finding the partner I need?

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.