Container glossary
What is EDI in shipping?
EDI (Electronic Data Interchange) is the exchange of standardised, machine-readable messages between the computer systems of terminals, shipping lines, customs and forwarders. Every event on a container tracking page began as one of those messages, which is why a timeline moves in steps and not continuously.
How an EDI message travels from the quay to a tracking page
Nobody types a tracking event. When a truck passes a terminal gate or a crane sets a box on a ship, the terminal’s system records the move and sends a structured message to the shipping line. Most of the industry writes these in UN/EDIFACT, where each message type has a fixed name: CODECO reports a gate move, COARRI reports a container loaded or discharged, BAPLIE describes where every box sits on a vessel. North American parties often use the ANSI X12 standard for the same job.
The line’s system receives the message, matches it to a booking and only then shows it on its tracker. Messages are commonly sent in batches, and each system in the chain processes them on its own schedule. That is the whole reason for the delay: terminal events typically reach public trackers 6 to 24 hours after they happened.
Where a shipper runs into EDI
Mostly you see its output, not the thing itself. The dated lines on a carrier’s tracking page — gate-in, loaded, discharged, gate-out — are EDI messages turned into sentences. A forwarder’s portal showing the same milestones is reading the same feed one step later.
You meet the word itself when a carrier lists the channels it accepts for shipping instructions or for a VGM declaration: web form, email, or “EDI”, meaning a direct system-to-system connection. That option is for companies shipping enough to build an integration; everyone else uses the web form and the result is the same record.
Reading a tracking timeline as if it were live
The usual mistake is treating the last line of a timeline as the present moment. A container that left the port this morning can still read “discharged” tonight, because the gate-out message has not been processed yet. People conclude the box is stuck, call the terminal, or delay sending a truck — and lose a day of free time over a message in a queue.
Read each event with its own timestamp, which records when the move happened and not when it was published, and expect a gap before the next one. The shipping line’s own page is the first to receive the message; our container tracking checker validates the number and points you to that page, and the tracker study records what each line’s tracker accepts.
Frequently asked questions
Is EDI the same as real-time tracking?
No — EDI reports events after they happen, usually in batches, so a tracker built on it shows the last reported step and not a live position. Terminal events typically appear on public trackers 6 to 24 hours after the move.
What EDI standards does container shipping use?
Two: UN/EDIFACT, used by most terminals and shipping lines worldwide, and ANSI X12, common in North America. Both define fixed message types, so that a gate report from any terminal can be read by any line’s system.
Do I need EDI to ship a container?
No — a shipper can book, send shipping instructions and declare a VGM through the carrier’s website or a forwarder. A direct EDI connection is worth building only for companies that send documents in volume.