EDI
Updated Jul 26, 2026
EDIEDI
Electronic Data Interchange lets you exchange business documents with your trading partners as structured files rather than as paper, PDFs or email. A customer sends a purchase order your system can read; you send back a shipment notice and an invoice the same way. Nobody rekeys anything.
DataMagik reads and writes both X12 and EDIFACT, maps documents to business objects you define, routes them, acknowledges them, and logs every one in both directions.
Where to start
- Concepts and Vocabulary — the envelope, transaction sets, control numbers and acknowledgements. Short, and the rest assumes it.
- Mapping Specs — teach DataMagik to read a partner's document. Start from one of the 26 built-in templates.
- Trading Partners — register who you exchange with and what should happen to each document type.
- The EDI Console — watch it work, and fix what does not.
Everything in this section
| Page | Covers |
|---|---|
| Concepts and Vocabulary | X12 vs EDIFACT, ISA/GS/ST, control numbers, why acknowledgements exist. |
| Trading Partners | Identity, routing, delivery, pickup schedules, exception approvers. |
| Mapping Specs | The spec designer, the starter library, AI discover, test mapping. |
| The Inbound Pipeline | Every stage a received document goes through, and what to do when one fails. |
| Sending Documents | Control numbers, every transport, and re-sending. |
| EDI and Plex | Retrieving from a Plex mailbox, and writing documents into Plex. |
| Acknowledgements | 997/999/CONTRL in both directions. |
| The EDI Console | The transaction log, drill-down, replay and the exceptions queue. |
Partners can deliver files straight into DataMagik over SFTP or FTPS
using the Hosted File Gateway, which feeds this pipeline
automatically.