EDI for trucking: the four messages small carriers need to know

Most small carriers book freight by phone, email and load board. Rate confirmations arrive as PDFs, updates go out by text, and invoices go out with scanned paperwork. That works with most brokers.

Large shippers and some brokers work differently. Their systems send load offers electronically, expect electronic answers, track shipments through electronic status messages and pay from electronic invoices. That's EDI: electronic data interchange. When a customer like that wants to work with you, EDI becomes a requirement rather than an option.

The message flow, one load

The transaction sets, in one table

Names and purposes from X12's published list of transaction sets X12, transaction setsCore trucking EDI transaction sets (X12)204 load tender, 990 response to load tender, 214 shipment status, 210 freight details and invoiceX12 transaction sets: 204 Motor Carrier Load Tender (offer a shipment to a carrier); 990 Response to a Load Tender (accept or decline); 214 Transportation Carrier Shipment Status Message (where the shipment is, with dates and times); 210 Motor Carrier Freight Details and Invoice (charges and payment request).X12, transaction setsChecked Oct 2026Close.

Who requires EDI

• Large shippers, especially retailers, manufacturers and food companies that tender freight from their own systems.
• Some brokers, particularly large ones, for contract or dedicated freight.
• Dedicated and contract customers, where tenders, status and invoices repeat every week. If you're pursuing dedicated trucking contracts, expect EDI questions.

Most spot freight from brokers doesn't need EDI. A carrier with only spot broker freight can go years without it.

How a small carrier connects

Through a TMS. Many transportation management systems include or sell EDI modules that send and receive messages from your load records. If you already run a TMS, start there. See TMS for trucking.

Through an EDI provider. Service providers translate X12 messages and connect to each trading partner, sometimes through a web portal where you accept tenders and enter status updates by hand.

Through the partner's portal. Some shippers and brokers offer a web portal for carriers without EDI. It's not true EDI, but it may be enough to start.

Whichever route, each trading partner sends an implementation guide (which fields they require, how fast responses must be, which status codes they expect) and runs tests before going live. Your Standard Carrier Alpha Code (SCAC) is the identifier most partners use in these messages NMFTA, SCAC pricingSCAC assignment fee$110 online ($127 by phone or mail); renewal $104 onlineNMFTA fee schedule effective July 1, 2026 through June 30, 2027 for assigning a Standard Carrier Alpha Code. Codes renew annually. Non-Class 8 carriers pay an extra $5 identity verification fee.NMFTA, SCAC pricing, 2026Checked Oct 2026Close; see trucking dispatch software for how EDI fits with the rest of your systems.

What it costs and what it saves

EDI costs vary by provider and number of trading partners: often a setup fee per partner and a monthly or per-message fee. Check each provider's own pricing. What it saves is the cost of losing a customer that requires it, plus faster invoicing and fewer status calls. Use the dispatch ROI calculator alongside any EDI quote if you're weighing new systems against outsourced dispatch.

Getting status messages right

Most EDI problems for small carriers aren't technical. They're late or missing 214s. Partners measure on-time status updates, and missing updates can cost you tenders. Make it a habit:

• Arrival and departure at every stop, sent promptly.
• Delay updates as soon as you know, with a new estimated time.
• Delivered status with the delivery time, followed by proof of delivery.

Telematics or ELD location data can automate some updates; see trucking telematics.

Terms you'll hear

• Trading partner: the shipper or broker you exchange EDI messages with.
• Implementation guide: the partner's document listing exactly which fields and codes they require in each message.
• SCAC: your Standard Carrier Alpha Code, a short letter code used to identify you in tenders and invoices.
• Translator: software that turns X12 messages into data your TMS can use, and back.
• VAN (value-added network): a service that routes EDI messages between partners, often for a per-message fee.
• AS2 or SFTP: direct connection methods some partners use instead of a VAN.
• Testing: the partner sends sample tenders and checks your responses before going live.

Who in your company owns EDI

EDI fails quietly. A tender that sits unanswered for two hours simply goes to another carrier, and nobody calls to ask why. Before going live, name one person who watches for tenders every business day, one backup, and the hours they cover. Decide in advance which tenders can be accepted without calling the owner (lanes, minimum rate, equipment) and which need a decision. Review missed tenders and late status messages every week for the first few months.

EDI, APIs and tracking links

Not every electronic connection is EDI. Some brokers and shippers now connect through APIs (direct software connections) or ask carriers to share a tracking link from their ELD or telematics provider. These often take less setup than EDI. Ask each customer what they accept; you may not need a full EDI setup to meet their tracking requirement.

A short checklist before saying yes to EDI

1. Does the customer's freight justify the setup (several loads a week, steady lanes)?
2. Does your TMS support EDI, or will you need a provider?
3. Can you respond to tenders within the partner's required time, every day?
4. Can your drivers' status events reach the system without delays?
5. Do you have the paperwork process to back 210 invoices with proof of delivery?

EXAMPLE A six-truck reefer carrier wins a weekly lane with a regional grocery distributor that tenders by EDI. The carrier adds an EDI module to its existing TMS, completes testing with the distributor over three weeks, and assigns one office person to watch for 204s each morning. Status messages come from the trucks' telematics, and invoices go out as 210s the day after delivery.

EDI and the truck still have to match

Electronic messages don't replace the basics: equipment that's ready and inspected before pickup (see what is PTI in trucking), the right trailer for the freight (see trucking equipment), and a driver who arrives on time. A perfect 990 followed by a late truck loses the customer just as fast.

When EDI is worth adding

EDI plugs into the dispatch and billing systems described in truck fleet management. Our view: add EDI when a customer worth having requires it, not before. Most small fleets get more from fast email rate cons and good tracking links than from an EDI project nobody asked for.