Electronic data interchange (EDI) is how tenders, status, and invoices move between shippers, brokers, and carriers on retail and brokered lanes. Each message is an X12 transaction set identified by a number. These pages cover the sets Trailflow's EDI product handles today — Trailflow EDI is in beta.
- EDI 204 — Motor Carrier Load Tender
The EDI 204 is the electronic load tender a shipper or broker sends to a motor carrier to offer a specific shipment — the digital equivalent of the phone call and rate confirmation that offers a load.
- EDI 210 — Motor Carrier Freight Invoice
The EDI 210 is the carrier’s freight invoice sent electronically to the shipper, broker, or a paying third party — the linehaul charge, accessorials, and totals for a completed shipment.
- EDI 214 — Transportation Carrier Shipment Status Message
The EDI 214 is the status update a carrier sends during a shipment — pickup, in transit, arrival, delivery, and exceptions — so the shipper or broker can track the load without a check call.
- EDI 990 — Response to a Load Tender
The EDI 990 is the carrier’s reply to a 204 load tender — accept, decline, or (where the partner allows it) accept with conditions.
- EDI 997 — Functional Acknowledgment
The EDI 997 is the technical receipt one system sends back for another’s transmission — confirming the message arrived and whether it was structurally accepted, rejected, or accepted with errors.
- EDI 999 — Implementation Acknowledgment
The EDI 999 is a stricter acknowledgment than the 997 — it confirms a transaction not only parsed as valid X12 but conformed to the specific implementation guideline agreed with the trading partner.