EDI (Electronic Data Interchange) is the transfer of orders, despatch advices, invoices, bookings and status messages between two companies' computer systems in a standard format, without human intervention. The most widely used standards in logistics are UN/EDIFACT and ANSI X12. Most of the data flow between port, shipping line, carrier and customs systems runs on EDI.
What exactly does EDI change?
Before EDI, a shipping instruction arrived by e-mail, operations staff typed it into their own system by hand and then entered the same information once more on the shipping line's portal. With EDI, data is sent instead of documents: the sender's system produces the message in a standard structure, and the recipient's system reads it and converts it directly into a record. Once re-keying disappears, speed increases and typing errors in fields such as container number, weight or GTİP (Turkish HS/tariff code) decrease.
Which standards are used?
| Standard | Who maintains it? | Where is it common? |
|---|---|---|
| UN/EDIFACT | United Nations, UN/CEFACT | Europe, Asia, shipping lines and ports; directories are published twice a year (e.g. D.21A, D.21B) |
| ANSI X12 | ASC X12 (USA) | North American retail, trucking and logistics |
| EANCOM | GS1 | Retail and supply-chain subset of EDIFACT |
Which messages flow in logistics?
- Commercial flow: ORDERS (purchase order), DESADV (despatch advice), INVOIC (invoice). Their X12 equivalents are 850, 856 and 810. DESADV speeds up goods receipt when matched with the SSCC labels on the pallets.
- Transport instruction and status: IFTMIN (transport instruction), IFTSTA (status reports such as loaded, in transit, delivered). In X12, 204 is the load tender and 214 the shipment status message.
- Ocean and port: IFTMBF/IFTMBC (booking request and confirmation), CODECO (container gate-in/gate-out), COPRAR (loading/discharge list), BAPLIE (vessel stowage plan), VERMAS (VGM submission).
- Customs: CUSCAR (cargo manifest), CUSDEC (customs declaration). In Türkiye, declarations are submitted electronically to the BİLGE system of the Ministry of Trade (Ticaret Bakanlığı); NCTS uses numbered messages such as IE015 for the declaration and IE029 for release.
How is EDI set up?
- Partner and message selection: It is agreed which messages will be exchanged with which business partner, and in which version.
- Implementation guide: The partner provides an "implementation guide" showing mandatory fields and code lists. Two shipping lines may require the same IFTMIN message with different fields.
- Mapping: The company's ERP or TMS fields are mapped to the standard segments.
- Transmission channel: AS2, SFTP or a value-added network (VAN) is chosen.
- Testing and go-live: Sample messages are validated by both sides, and error and acknowledgement messages (CONTRL, 997 in X12) are configured.
EDI or API?
| EDI | API | |
|---|---|---|
| Data structure | Fixed, standard segments | Mostly JSON, provider-specific |
| Timing | Batch or event-based files | Real-time request and response |
| Strength | Established acceptance among shipping lines, ports and large retailers | Quick setup, live location and rate queries |
| Weakness | Long mapping and testing process | Separate integration for each provider |
The two technologies are not rivals. Many companies receive bookings and invoices via EDI and live vehicle location via API. How carrier and customer systems are connected is planned separately under API integration. Domestic electronic documents are a separate area; the e-waybill (e-irsaliye) works with the Revenue Administration's (GİB) own format.
Common mistakes
- Filling code lists with local values. UN/LOCODE (e.g. TRMER) should be used for ports and the standard package code for packaging.
- Not monitoring error messages. A rejected IFTSTA can disappear without anyone being notified.
- Not changing versions in sync with the partner.
On the customs side, the electronic declaration flow falls under the digital customs service, and shipment status data under the daily vehicle tracking and reporting service.
Frequently Asked Questions
Does a small exporter need to set up EDI?
What does an EDIFACT message look like?
Sources
- UNECE – UN/EDIFACT
- X12 – Accredited Standards Committee X12
- GS1 – EANCOM standard