Industry verticals and EDI: 2026 landscape

EDI is not a single topic. Each industry vertical has inherited its own standards, pivotal flows and operational practices. This page maps seven major sectors and points to the specifics worth knowing before any integration project.

Retail and large-scale distribution

Retail is probably the most historically deployed EDI vertical. Dominant standards are EDIFACT in Europe (ORDERS, ORDRSP, DESADV, INVOIC, RECADV, REMADV sets) and X12 in the United States (850, 855, 856, 810, 820 sets). The pivotal business saga is the PO/ASN/INVOIC triplet: a purchase order triggers a shipment advice, which triggers the invoice, which triggers payment. Major chains (Carrefour, Walmart, Tesco, Aldi, Lidl) often impose their own specifications (subsets or supersets of world standards), sometimes as binding implementation guides.

Retail specifics: the GS1 ecosystem provides pivotal identifiers (GLN for locations, GTIN for items) and EANCOM recommendations (an EDIFACT subset specified by GS1). Most retail hubs use AS2 for transport, sometimes still SFTP for historical flows.

Automotive

Automotive probably pushed EDI the furthest: Just-in-Time flows, sequencing down to the piece, deliveries synchronised with the production line. Dominant standards are EDIFACT automotive sets (DELFOR, DELJIT, DESADV, INVOIC, IFCSUM), often enriched by the German VDA profile (notably VDA 4905, 4915, 4938) and the American AIAG (ANSI X12 830, 862, 856). The historical transport protocol is OFTP2, still very used by European OEMs (Renault, Stellantis, Volkswagen, BMW, Daimler).

Automotive specifics: DELJIT message cadence can reach several hundred messages per day for a single supplier, with tight contractual latencies. Operational discipline (monitoring, retry, sequencing control) is demanding. Catena-X and Manufacturing-X programmes bring a data-sharing dimension complementary to the traditional EDI flow.

Healthcare

Healthcare combines several standard families. For clinical flows (admissions, observations, lab results, prescriptions), HL7 v2.x remains dominant in hospitals, with FHIR R4 / R5 rising fast, notably for national ecosystems (US Core, IPA, IPS, France SI-DMP). For administrative and financial flows (claims, remittance, eligibility), X12 HIPAA (837, 835, 270/271, 276/277 sets) has been mandatory in the United States since HIPAA Administrative Simplification (1996 + 5010 mandatory in 2012).

Healthcare specifics: regulatory compliance is central (HIPAA in the US, GDPR and HDS hosting in France, national equivalents elsewhere). Privacy translates into end-to-end encryption requirements, access traceability and certified hosting. Healthcare gateways must manage HL7 v2 / FHIR coexistence for probably another decade.

Banking and financial services

Banking has two main families. For inter-bank payment and settlement flows, ISO 20022 (published as early as 2004) has become the reference standard: SWIFT MT messages are migrating to MX (ISO 20022) over 2023-2025, SEPA SCT/SDD natively use ISO 20022, and RTGS systems (TARGET2 then T2 in March 2023) have moved to ISO 20022. For client flows (statements), historical national formats persist (BAI2, MT940, CFONB in France).

Banking specifics: volumes are massive (several million transactions per day for a tier-1 actor), reversibility and reconciliation requirements are absolute. Sector-specific protocols (EBICS in central Europe, SwiftNet for cross-border, FileAct) coexist with AS2 and SFTP. Cryptography is regulated (HSM mandatory, signature by nominative certificate).

Energy and utilities

Energy uses specific EDIFACT standards for flows between regulated actors (suppliers, network operators, metering operators). In France, R3 flows (Enedis readings) and the variants of the Echanges Marche between Gestionnaire and Fournisseur reference (PEN, FNR, RNN) flow over protocols specified by sector authorities. At European scale, the sector is gradually organising around more modern standards (XML, REST APIs) pushed by smart metering programmes.

Energy specifics: sector regulation is strong (CRE in France, BNetzA in Germany, Ofgem in the UK), and formats are often imposed by the regulator. Volumes increase rapidly with the generalisation of Linky, Gazpar and European-equivalent meters, pushing toward event-driven architectures.

Public sector

The public sector is pulled by European electronic invoicing and by public procurement standards (PEPPOL BIS, UBL, national CIUS). In France, Chorus Pro has been mandatory since 2017 for invoices to public buyers; in Italy, the SdI covers B2B and B2G; in Spain, the FACe system plays an equivalent role. Standards converge toward EN 16931, with PEPPOL eDelivery as preferred transport.

Public sector specifics: administrative compliance is central (multi-decade legal archival, send traceability, mandatory mentions). Obligation timelines are set by decree and rarely slide once published. ViDA (adopted in March 2025) consolidates the intra-EU trajectory.

Logistics and transport

Logistics combines EDIFACT (IFCSUM, IFTMIN, IFTSTA, COREOR, COPRAR for containers) and business sectoral standards (UN/CEFACT MMT for multimodal, AnNa Stack for ports). Maritime massively uses COPARN, BAPLIE, MOVINS messages for terminal operations. Air cargo has its own ecosystem (Cargo-IMP, Cargo-XML, and the ONE Record transition described in the dedicated article).

Logistics specifics: end-to-end traceability is critical (cold chain, dangerous, sensitive), and volumes can explode on container or e-commerce flows. Major actors (Maersk, MSC, CMA-CGM, DHL) publish their own implementation profiles. Customs impose their own declarations (ICS2 for the EU since 2023, ACE in the US), often in specific XML.

Further reading

• Standards landscape — the transverse orientation map, by standard family.
• Standards landscape (Foundations) — the conceptual introduction.
• Countries — the country hub, with dominant sectoral obligations per country.
• EDI vendors comparative 2026 — the platforms that address these verticals.