EDI 204, 990, 214, and 210 are the four electronic document types that carry a typical freight shipment from tender to invoice between a shipper and a motor carrier. In plain terms: the 204 offers the load, the 990 accepts or rejects it, the 214 reports status updates as the shipment moves, and the 210 is the carrier's invoice once it's delivered.
The four documents, in order
EDI 204 — Motor Carrier Load Tender. This is the shipper (or broker) offering a load to a carrier: origin, destination, pickup and delivery windows, equipment needed, weight, and commodity details. It's the electronic equivalent of "here's a load, do you want it?"
EDI 990 — Response to a Load Tender. The carrier's reply to the 204 — accept or reject the load. If accepted, this is effectively the carrier's confirmation that they're committed to the pickup.
EDI 214 — Transportation Carrier Shipment Status Message. Once a load is moving, the 214 carries status updates: pickup, in transit, arrival at a stop, delivery, and sometimes exceptions like a delay. A single shipment typically generates several 214 messages over its life, one per status event.
EDI 210 — Motor Carrier Freight Details and Invoice. After delivery, the carrier sends a 210 to bill for the shipment — the electronic version of a freight invoice, including charges and accessorials.
How they fit together
A typical flow looks like: 204 (load offered) then 990 (carrier accepts) then a series of 214s (pickup, in-transit updates, delivery) then 210 (invoice). Each document type has one job, which is part of why the system has stayed standard across the industry for decades — a shipper's system and a carrier's system don't need to agree on much beyond the format of these four documents to exchange freight information reliably.
Why EDI still matters even with modern software
Modern scheduling and visibility platforms haven't replaced EDI — they typically sit alongside it, because EDI is how freight data moves between two different companies' systems, not within one company's own operations. A dock scheduling platform can give your own team a great internal view of a load, but if your trading partners run their own transportation management systems, EDI is usually still the language those systems speak to each other.
What "EDI support" actually requires
It's worth knowing that EDI isn't something a piece of software turns on by itself — it requires a real trading relationship: your EDI number, your trading partner's EDI number, agreed-upon document formats (often with partner-specific customizations), and typically a connection through an EDI VAN (value-added network) or a direct connection both sides have configured. Any system claiming EDI capability, Docking Buddy included, needs those trading-partner details and credentials configured before documents can actually flow — it's a supported capability, not something that works automatically the moment you sign up.
The short version
204, 990, 214, and 210 map onto the natural life of a shipment: offer, acceptance, status updates, and invoice. Understanding what each one does makes it much easier to have an informed conversation with a carrier, a broker, or a software vendor about what your EDI setup actually needs — and to know what still requires trading-partner configuration versus what's automatic.