Home > Knowledge Base > Topic: EDI in Transportation and Logistics: How It Works and Why It Matters
Topic: EDI in Transportation and Logistics: How It Works and Why It Matters
Updated: July 2026
Written by: EDI Support LLC Team with 100+ years of cumulative experience in the EDI space
Key Takeaways
- Transportation was one of the first industries to run on EDI, and it still uses the ANSI X12 standard maintained by the X12I subcommittee.
- Four documents carry a truckload move: the 204 tenders the load, the 990 responds, the 214 reports status, and the 210 invoices. A 997 confirms each one arrived.
- What you need depends on your role. A carrier, broker, shipper, and 3PL each send and receive a different mix.
- X12 also covers rail, ocean, and customs. Most companies only use the handful their partners require.
Why Transportation Runs on EDI
Transportation moves the physical economy, and it does it across a web of shippers, brokers, and carriers whose systems all have to agree with each other. Without a shared format, every load tender, status update, and invoice would be a phone call, a fax, or a re-keyed email. Thousands of them a day.
EDI fixed that. The industry adopted it early because the volume and the number of parties made manual handling impossible to sustain. Today a shipper can tender a load, a carrier can accept it, status can flow back on its own, and an invoice can settle, with nobody re-entering data between systems. It takes manual entry out of the TMS and billing, cuts the errors that come with it, and gives every party visibility into where a shipment is and what happens next.
Benefits of EDI in the Transportation and Logistics Industry
The value of EDI in transportation is easiest to see in the work it removes.
- Fewer manual touches: A load tender that arrives as EDI drops straight into a TMS as a load. Without EDI, someone reads an email or a portal and types it in, once per load, every load.
- Fewer errors: Every manual re-entry is a chance to fumble a weight, a PO number, or an address. EDI carries the same data between systems without a human retyping it, so the shipment the carrier sees is the shipment the shipper sent.
- Faster response: Load tenders often expire on a clock. When tenders arrive as EDI and can be accepted quickly, a carrier holds onto freight it would lose to a slow manual process.
- Real visibility: Status flows back automatically as the load moves, so a shipper can see where freight is without calling to ask. That same status trail is what large shippers grade carriers on.
- Faster payment: An electronic invoice that matches the original tender clears faster than a paper or email invoice that someone has to reconcile by hand.
The EDI Standard for Transportation
North American transportation runs on ANSI ASC X12. The Accredited Standards Committee has maintained the X12 standard since 1979, and the subcommittee that handles transportation transactions is X12I. Every document below is an X12 transaction identified by a number, the 204, the 214, and so on. Each trading partner publishes an implementation guide that spells out exactly how they expect each document formatted, which is why two partners rarely do it identically.
The video below walks through the definitions and the EDI documents most commonly used across transportation and logistics.
The Core Motor Carrier Documents
Most truckload freight moves on four documents, plus an acknowledgment.
| Document | Name | What it does |
| 204 | Motor Carrier Load Tender | Offers a specific load to a carrier |
| 990 | Response to a Load Tender | Accepts or declines the load |
| 214 | Shipment Status Message | Reports pickup, transit, and delivery status |
| 210 | Motor Carrier Freight Details and Invoice | Bills for the completed load |
| 997 | Functional Acknowledgment | Confirms a document arrived and was valid |
For a full breakdown of what each document carries, how they connect, and where they go wrong, read the Transportation EDI Guide: 204, 990, 214, and 210 Explained on Elevate.
How Transportation EDI Documents Flow from Tender to Payment
Here is a typical sequence with a shipper, a freight broker, and a carrier.
- The shipper sends an EDI 204 (Load Tender) to the broker.
- The broker’s TMS returns an EDI 997 (Functional Acknowledgment) confirming receipt.
- The broker accepts or declines the load with an EDI 990 (Response to a Load Tender).
- The broker tenders the load to a carrier, who accepts it.
- The carrier picks up the freight and notifies the broker.
- An EDI 211 (Bill of Lading) may be exchanged as proof the freight was received in good condition.
- The broker sends the shipper an EDI 214 (Shipment Status Message) reporting pickup.
- As the load moves, more 214s report status until delivery.
- Once the freight is delivered, the carrier or broker sends an EDI 210 (Freight Invoice) to bill it.
- After payment, the broker settles with the carrier.
The whole cycle can run without a phone call when every document carries the right references and each one is matched to the same load on both sides.
Which EDI Documents Do Shippers, Carriers and Brokers Send and Receive?
The same documents serve different parties in different directions.
|
Role |
Typically sends |
Typically receives |
|
Shipper |
204 |
990, 214, 210 |
|
Carrier |
990, 214, 210 |
204 |
|
Broker |
204 to carriers; 214 and 210 up to shippers |
204 from shippers; 990, 214, 210 from carriers |
|
3PL |
Varies by role on each lane |
Varies by role on each lane |
Brokers and 3PLs sit in the middle and often act as both shipper and carrier depending on the relationship, which is why they need EDI that works in both directions.
EDI Across Transportation Modes
Trucking is where most people meet transportation EDI, but every mode has its own transaction set, and a logistics operation that touches more than one mode touches more than one set.
Motor carrier (trucking) is the largest and most familiar, built around the 204, 990, 214, and 210, with supporting documents like the 211 bill of lading and 212 delivery manifest.
Rail runs on its own family, including the 404 rail carrier shipment information and the 417 waybill interchange, reflecting how rail freight is booked and interchanged between carriers.
Ocean covers container shipping, from the 300 booking request and 301 confirmation through the 310 freight receipt and invoice and 315 status details.
Customs documents like the 309 manifest and 350 status information handle the regulatory side of freight crossing borders.
Most companies work in one mode and only implement the documents that mode requires. An operation spanning several modes carries several transaction sets at once, which is part of why larger logistics providers treat EDI capability as core infrastructure rather than a feature.
The Wider Transportation Transaction Set
X12 defines a large family of transportation transactions across every mode of freight. Most companies use only the handful their partners require, but the full set shows how much of the industry runs on standardized documents. Here is the transportation set, grouped by area.
Motor carrier (trucking)
|
Code |
Name |
|
204 |
Motor Carrier Load Tender |
|
210 |
Motor Carrier Freight Details and Invoice |
|
211 |
Motor Carrier Bill of Lading |
|
212 |
Motor Carrier Delivery Trailer Manifest |
|
213 |
Motor Carrier Shipment Status Inquiry |
|
214 |
Transportation Carrier Shipment Status Message |
|
215 |
Motor Carrier Pickup Manifest |
|
216 |
Motor Carrier Shipment Pickup Notification |
|
217 |
Motor Carrier Loading and Route Guide |
|
219 |
Logistics Service Request |
|
220 |
Logistics Service Response |
|
222 |
Cartage Work Assignment |
|
223 |
Consolidators Freight Bill and Invoice |
|
224 |
Motor Carrier Summary Freight Bill Manifest |
|
225 |
Response to a Cartage Work Assignment |
|
240 |
Motor Carrier Package Status |
|
990 |
Response to a Load Tender |
Rail
|
Code |
Name |
|
404 |
Rail Carrier Shipment Information |
|
410 |
Rail Carrier Freight Details and Invoice |
|
414 |
Rail Carhire Settlements |
|
417 |
Rail Carrier Waybill Interchange |
|
418 |
Rail Advance Interchange Consist |
|
419 |
Advance Car Disposition |
|
420 |
Car Handling Information |
|
421 |
Estimated Time of Arrival and Car Scheduling |
|
425 |
Rail Waybill Request |
|
426 |
Rail Revenue Waybill |
|
404–494 |
Additional rail rate, routing, and settlement transactions |
Ocean
|
Code |
Name |
|
300 |
Reservation (Booking Request) |
|
301 |
Confirmation |
|
303 |
Booking Cancellation |
|
304 |
Shipping Instructions |
|
310 |
Freight Receipt and Invoice |
|
312 |
Arrival Notice |
|
315 |
Status Details |
|
317 |
Delivery/Pickup Order |
|
322 |
Terminal Operations and Intermodal Ramp Activity |
|
323 |
Vessel Schedule and Itinerary |
|
324 |
Vessel Stow Plan |
|
325 |
Consolidation of Goods in Container |
Air
|
Code |
Name |
|
104 |
Air Shipment Information |
|
110 |
Air Freight Details and Invoice |
|
120 |
Vehicle Shipping Order |
Customs
|
Code |
Name |
|
309 |
Customs Manifest |
|
350 |
Customs Status Information |
|
352 |
U.S. Customs Carrier General Order Status |
|
353 |
Customs Events Advisory Details |
|
355 |
U.S. Customs Acceptance/Rejection |
|
357 |
U.S. Customs In-Bond Information |
|
358 |
Customs Consist Information |
|
361 |
Carrier Interchange Agreement |
Claims and settlement
| Code | Name |
| 920 | Loss or Damage Claim: General Commodities |
| 924 | Loss or Damage Claim: Motor Vehicle |
| 925 | Claim Tracer |
| 926 | Claim Status Report and Tracer Reply |
Most operations touch only the documents their mode and their partners require. The value of the standard is that when a new partner or a new mode enters the picture, the format is already defined.
How The Transportation Documents Actually Move
Knowing the documents is one thing. Getting them between partners is another, and it comes down to connectivity. Transportation uses the same connection methods as the rest of EDI.
AS2 is a direct, encrypted connection common with large shippers and major brokers. SFTP is the most widespread method in transportation, simpler than AS2 and widely accepted by brokers and mid-size shippers. VAN, a value-added network, routes documents through a third party and is still common in older relationships. Some newer digital brokers offer API connections, though many run API and EDI side by side rather than replacing one with the other.
A practical reality worth naming: plenty of brokers still expect smaller carriers to accept load tenders through a web portal rather than EDI. That works at low volume and becomes a bottleneck as load count grows, because every tender is a manual login instead of a document a system can act on.
Who Needs Transportation EDI and When?
Not every operation needs EDI on day one, but most reach a point where they do.
-
- A small carrier usually needs it when a shipper or broker asks them to become EDI capable, which for larger shippers is a condition of hauling freight at volume rather than a nice-to-have.
- A freight broker needs it to sit between shippers and carriers at scale, receiving tenders from shippers and passing them to carriers without re-keying every load.