EDI is anything but dead
Global commerce still runs on EDI. Decades of adoption, internet transports such as AS2, XML-oriented B2B standards, and managed-service / iPaaS delivery have expanded who can participate.
APIs and EDI. API-based B2B has mostly complemented EDI rather than replaced it. EDI remains the most broadly accepted B2B pattern for many industries; APIs excel where synchronous, interactive calls matter.
Example (logistics): A transportation planning system may call carrier APIs for real-time rating while the planner works, then book via EDI or API depending on carrier capability. Visibility might come from telematics/APIs or EDI; freight settlement often still favors EDI invoicing. The winning pattern is a platform that supports multiple integration styles for one vertical process.
EDI is evolving
Existing and emerging EDI-related standards remain part of the digital ecosystem. Managed services and cloud platforms lower the operational barrier. Government mandates (e.g. cross-border e-procurement, e-invoicing, tax reporting) push XML and UBL-style formats forward.
PEPPOL illustrates reuse: businesses connect for B2G and then extend the same rails for B2B. E-invoicing rules continue to tighten globally (real-time tax access, integrity, retention).
EDI’s asynchronous, point-to-point, document-centric model is not ideal for every emerging use case (e.g. continuous IoT event streams). Platforms that unify EDI, APIs, and other patterns help enterprises cover both classic supply-chain milestones and newer event-driven scenarios.
Emerging technologies
Research firms project strong ROI from modernized B2B integration. Alongside EDI and APIs, enterprises invest in RPA (automating repetitive office work), IoT (more telemetry), blockchain / shared ledgers for multi-party auditability, and AI for analytics and automation.
These technologies can sit on top of established integration: for example, a shared ledger can add visibility across parties that still exchange EDI or XML documents underneath.