EDI glossary: the transport EDI dictionary
EDI is the automated exchange of orders, statuses and invoices between systems. Below we explain the terms you come across in transport integrations — message types, formats and protocols.
Basic terms
EDI
EDI (Electronic Data Interchange) is the structured, automated exchange of business documents — such as orders, statuses and invoices — directly between the computer systems of two parties, without manual input.
In transport, this is how transport orders, status updates and invoices flow automatically between shipper, carrier and platform.
API
An API (Application Programming Interface) is an interface through which two systems request and send data in real time, usually over the internet using HTTP/REST.
Where classic EDI often works in batches, an API enables direct, real-time exchange — for example for live track & trace.
Integration / connection
An integration (or connection) is the link that lets two systems exchange data automatically, so that data does not have to be entered twice.
Mapping / conversion
Mapping is translating data from the format of one system into that of another — for example from an EDIFACT message to the fields in your TMS.
Good mapping is the core of a reliable integration: every field has to come across correctly and consistently.
Onboarding
Onboarding is the process in which a new integration partner — customer, carrier or platform — is connected: agreements on messages, formats and protocol, followed by testing and go-live.
Formats
EDIFACT
EDIFACT (UN/EDIFACT) is the international EDI standard for the format of business messages and the most widely used in the European transport sector.
Message types such as IFTMIN, IFTSTA and INVOIC are EDIFACT messages.
XML
XML is a text format that records data in a tree structure with tags; it is widely used in integrations because it is both readable and flexible.
CSV
CSV is a simple table format in which each line is a record and fields are separated by commas or semicolons — often used for simple imports and exports.
JSON
JSON is a compact, machine-readable format that many APIs use to exchange data between web services.
Message types (EDIFACT, transport)
IFTMIN (transport order)
IFTMIN is the EDIFACT message for a transport order: with it, the shipper hands over a shipment with all transport details to the carrier.
IFTSTA (status message)
IFTSTA is the EDIFACT status message in freight transport, with which a carrier reports back the status of a shipment — for example collected, in transit or delivered.
INVOIC (invoice)
INVOIC is the EDIFACT message for an invoice, used to exchange invoicing between parties automatically.
DESADV (packing slip)
DESADV (despatch advice) is the EDIFACT despatch message or packing slip: it announces what has been shipped, usually ahead of the delivery.
APERAK / CONTRL (acknowledgement)
APERAK and CONTRL are EDIFACT acknowledgement messages: CONTRL confirms whether a message has been received syntactically correctly, APERAK reports how its content was processed or flags an error.
Protocols
AS2
AS2 is a secure protocol for sending EDI messages over the internet, with encryption and a signed receipt (MDN).
SFTP
SFTP is file transfer over an encrypted SSH connection: a widely used, straightforward way to exchange EDI files securely.
OFTP2
OFTP2 is a secure transfer protocol (Odette) that originally comes from the automotive industry and is also used in transport for reliable, acknowledged exchange.
FTP / FTPS
FTP is a classic protocol for file transfer; FTPS adds encryption. FTP without security is not recommended for business data.
TCP socket
A TCP socket is a direct, permanent network connection between two systems, sometimes used for real-time message flows between fixed integration partners.
VAN (Value Added Network)
A VAN (Value Added Network) is an intermediary that forwards and manages EDI messages between companies, as an alternative to a direct connection.
Systems
TMS
A TMS (Transport Management System) is the software a carrier or shipper uses to manage trips, orders and planning.
WMS
A WMS (Warehouse Management System) is the software that controls warehouse processes: receiving, storage, order picking and shipping.
EDI vs. API
| Aspect | EDI | API |
|---|---|---|
| Format | EDIFACT, XML, CSV | JSON, XML |
| Exchange | Often in batches | Real time, on request |
| Protocol | AS2, SFTP, OFTP2 | HTTP(S) / REST |
| Typical use | Orders, statuses, invoices between fixed partners | Live track & trace, real-time queries |
| Standardisation | Highly standardised (UN/EDIFACT) | Varies per supplier |
Protocols compared
| Protocol | Security | Receipt acknowledgement | Typical use |
|---|---|---|---|
| AS2 | Encrypted + signed | Yes (MDN) | EDI over the internet |
| SFTP | Encrypted (SSH) | At file level | Secure file exchange |
| OFTP2 | Encrypted | Yes | Reliable, acknowledged exchange |
| FTPS | Encrypted (TLS) | No | File transfer |
| TCP socket | Depends on set-up | Depends on set-up | Real-time message flow |
Come across a term you want to integrate?
Tell us which systems and messages you want to connect. We will think along with you about the best approach, without obligation.