Planned
EDI integration for freight brokers, with the transactions explained
Shippers that run on EDI send tenders and expect status and invoices back in standard formats. EDI for the FreightVero TMS is planned. Here’s how each transaction works and what’s planned.
Short answer
EDI integration connects a broker’s TMS to a shipper’s system using standard X12 messages instead of email. In freight, the core sets are the 204 load tender, 990 tender response, 214 shipment status and 210 freight invoice. EDI for the FreightVero TMS is planned and not built. Today your team enters loads in the TMS.
The four EDI transactions brokers use most
Transaction names follow the X12 standard.
| Set | X12 name | Usual direction for a broker | What it does |
|---|---|---|---|
| 204 | Motor Carrier Load Tender | Shipper to broker, or broker to carrier | Offers a load with stops, dates, equipment, weight and references |
| 990 | Response to a Load Tender | Broker back to shipper | Accepts or declines the tender |
| 214 | Transportation Carrier Shipment Status Message | Broker to shipper | Reports status such as picked up, in transit and delivered, with times |
| 210 | Motor Carrier Freight Details and Invoice | Broker to shipper | Sends the freight invoice for the load |
Each shipper publishes its own implementation guide with required fields and response times.
How EDI would fit the load workflow
For a shipper that runs on EDI, a load starts as a 204. The broker answers with a 990 inside a window the shipper sets, then owes a 214 at each status change and a 210 once the load delivers. Miss a 214 and the shipper’s system shows a load that never moved.
The FreightVero TMS already has the pieces those messages would come from. Status changes go through one database function, which gives each change a clean event for a 214. The billing queue checks each customer’s paperwork rules before a load is ready to bill, which is where a 210 would start.
None of this runs today. There’s no EDI connection and no public API, and tenders by email aren’t built. For background, read our EDI 204 and EDI 214 definitions and the EDI guide for freight brokers.
What the EDI integration is planned to cover
Inbound 204 tenders Planned
Tenders arrive as draft loads for a person to accept, with fields mapped from the 204.
990 responses Planned
Accept or decline from the draft, with the 990 sent back to the shipper.
214 status messages Planned
Status changes on the load sent to shippers that require 214s.
210 invoices Planned
Invoices sent as 210s for customers that bill by EDI.
Request EDI for your shippers
Tell us which shippers need EDI and which transactions they require. Requests help set the order we build in.
Frequently asked questions
Does FreightVero support EDI today?
No. EDI is planned and not built. Loads are entered in the TMS by your team, with required-field checks for every stop. If a shipper requires EDI before it will tender, tell us on a demo call so we can be clear about timing.
Do I need a VAN or an EDI provider?
Often, yes. Many EDI connections run through a value-added network or an EDI provider that handles the connection and mapping with each trading partner. How FreightVero will connect is decided when EDI is built.
Is an EDI 214 the same as tracking?
No. A 214 is a status message the broker sends to the shipper. The data behind it can come from tracking. In FreightVero, tracking comes from Load Market, which is live, and status changes pass the database checkpoints before they'd be reported.
What can I do with shipper tenders now?
Enter the load in the TMS, which checks required fields for every stop. For brokerages that receive rate cons and delivery orders as documents, the Load Entry agent is live, and a person confirms each draft.