EDI has existed since the 1980s and is still the way large retailers, automotive OEMs and logistics companies communicate with their suppliers. If you supply Albert Heijn, Jumbo, IKEA or a German car manufacturer, you don't get a choice: you connect via EDI or you don't get invoiced. At the same time, "EDI" isn't one single thing. It's a collection of standards (UN/EDIFACT, ANSI X12, UBL, VDA, TRADACOMS, XML variants such as cXML), a collection of transport protocols (AS2, OFTP2, SFTP, Peppol) and a collection of business rules per trading partner. For one company, an "EDI integration" means one XML file a day via SFTP; for another, it's a real-time AS2 feed of thousands of ORDERS messages with functional acknowledgements sent back.
Since 2015 we've been building custom integrations between ERP systems and the outside world. For EDI, that means a mapping engine between your own data model and the messages your trading partners require, a transport layer that handles both classic AS2 and modern Peppol, and archiving that meets the ten-year statutory retention requirement for tax records. We don't replace large EDI providers such as Babelway, Comarch or OpenText at enterprise volume, but we do build smaller stacks, add-ons to existing providers, and specific integrations that standard products simply don't include.
Our role doesn't end at "the message gets through". We think along with you about what happens when a supplier adds a field tomorrow, how rejected messages avoid getting stuck in a queue, and how your finance or operations team can see discrepancies without having to read raw EDIFACT. A well-built EDI integration is largely about catching exceptions: the standard case is done in a single sprint, and the deviations are where the real work lies.
The standards we work with most often are: UN/EDIFACT for classic retail and logistics; UBL for modern e-invoicing via Peppol; ANSI X12 for US trading partners in retail and healthcare; VDA for German automotive; cXML and xCBL for B2B marketplaces; HL7 for healthcare communication; SBR for Dutch tax reporting; and XBRL/EBR for energy reporting. We don't pick a standard in advance. We choose what your trading partners require and build the stack around it.