Road freight integration
Trucking EDI and API Integration
Every shipper and broker has its own implementation guide, test process and connection method, and onboarding each new carrier is usually the slowest step. ECOM connects your TMS, ERP and WMS to those partners and brings carriers live with Freight Onboarding and self-service Trading Partner Onboarding, so tenders, status, delivery evidence and invoices move without re-keying.
Overview
What is road freight EDI?
Road freight EDI is the exchange of standardized messages between shippers, brokers, carriers and consignees for truckload, less-than-truckload (LTL), parcel and last-mile moves. In ANSI X12 the core messages are the 204 Motor Carrier Load Tender, the 990 Response to a Load Tender, the 214 Transportation Carrier Shipment Status Message and the 210 Motor Carrier Freight Details and Invoice. Many partners also offer or require APIs for tendering, tracking or proof of delivery. Requirements differ by partner, so each connection is scoped from the partner’s own guide.
Overview
Built for the teams that tender, haul and bill freight
The same load looks different to each party. Pick the role closest to yours; many companies play more than one.
Motor carriers
You are asked to meet a different EDI or API requirement by each new shipper or broker, and every one wants testing before the first load.
Freight brokers and 3PL transportation teams
You tender in both directions, so tenders, status and invoices have to flow between shippers and carriers of very different capability.
Shippers
You tender to contracted carriers, need consistent status and delivery evidence, and audit freight invoices against what was moved.
Parcel and last-mile operations
You depend on carrier APIs and files for labels, tracking and proof of delivery, often alongside truckload partners.
Teams onboarding many carriers
Each carrier needs setup, protocol configuration and test cycles, which tie up your integration staff.
How ECOM helps
The offerings behind a lighter onboarding process
Carrier onboarding is where most trucking integrations lose time. These separate ECOM offerings apply to the road freight workflow.
Faster, lighter carrier onboarding
Click-through onboarding, protocol-specific setup and automated transaction testing in ECOM’s self-service Trading Partner Onboarding portal reduce the manual coordination and test cycles between your team and each carrier.
Tenders that get answered
A tender without a timely response is often re-tendered to another carrier. Connecting the TMS removes manual tender handling from the critical path.
Clearer status and faster exception handling
Pickup, in-transit and delivery events reach your systems in a consistent form, and exceptions are visible before a customer calls about them.
Delivery evidence that stays with the shipment
Proof of delivery, signatures and damage or shortage reports are kept with the shipment paperwork for invoice questions and claims.
How ECOM delivers it
Freight Onboarding and Trading Partner Onboarding
Freight Onboarding brings carriers live. The self-service Trading Partner Onboarding portal adds click-through onboarding, protocol-specific setup and automated transaction testing.
TMS, ERP and WMS connectivity
The ECOM Systems Integrator connects the platforms that create tenders, record status and bill freight.
Exception and SLA management
The Exception Management Center supports automated exception handling and internal and customer-facing SLAs.
Shipment paperwork and evidence
The Transaction Life Cycle Manager holds proof of delivery, signatures, damage reports and shortage reports.
EDI and APIs together
Messages and APIs are handled per partner, because many carriers and brokers support both and some require one.
Support
ECOM offers 24×7 support, with coverage hours and response targets defined in each service agreement.
ECOM offerings for this workflow
Systems Integrator
The ECOM Systems Integrator connects your TMS, ERP and WMS platforms, so tenders, responses, status events and freight invoices move between those systems and your carriers without re-keying. Hundreds of customers use the Systems Integrator today, and ECOM performs these integrations for customers.
Exception Management Center
Late pickups, declined tenders, rejected documents and missing status can be handled as exceptions, with internal and customer-facing SLAs managed in one place instead of in inboxes and spreadsheets.
Transaction Life Cycle Manager
Proof of delivery, signatures, damage reports and shortage reports are held with the shipment paperwork, so the evidence is at hand when a delivery, claim or invoice is questioned.
Freight Onboarding
Brings carriers and other freight partners live.
Trading Partner Onboarding
A self-service portal that supports almost all verticals, with customer click-through onboarding, protocol-specific setup and automated transaction testing.
Reconcile360 (invoice-to-cash)
Invoice-to-cash automation across all verticals, including air and ocean partners, so freight billing connects to cash.
Which offerings apply, and the partners, protocols and systems in scope, are agreed with you during scoping.
Workflow
From carrier onboarding to freight invoice
A road shipment passes through the stages below. Which messages or APIs a partner uses at each stage is that partner’s decision, so the list is a typical pattern, not a fixed sequence.
- 01
Onboard the carrier
Before the first load, the carrier is set up for the shipper’s or broker’s connection method and the documents or APIs are tested.
Typical messages: Setup and automated tests (Freight Onboarding)
- 02
Tender the load
The shipper or broker offers the load with stops, dates, equipment and references. Updates and cancellations are sent against the same shipment.
Typical messages: X12 204 Motor Carrier Load Tender, or API
- 03
Accept or decline
The carrier answers within the partner’s response window, echoing the shipment identification.
Typical messages: X12 990 Response to a Load Tender; 997 or 999 acknowledgment
- 04
Pickup and appointments
Pickup and appointment events are reported as the driver arrives and loads.
Typical messages: X12 214 status, or API events
- 05
In transit
Checkpoints and delay reasons keep the shipper and consignee informed.
Typical messages: X12 214; 213 status inquiry where used
- 06
Delivery and evidence
Delivery is reported and the signed proof of delivery, with any damage or shortage notes, is captured.
Typical messages: X12 214 delivered; POD and reports
- 07
Invoice
The carrier bills base freight and accessorial charges, referencing the same shipment.
Typical messages: X12 210, or 859 where specified
- 08
Exceptions and disputes
Late, declined, damaged, short or mismatched loads are resolved using the shipment record and its evidence.
Typical messages: Exception queue; evidence on file
Who sends what in a brokered truckload
In a brokered load, the broker sits between the shipper and the carrier and exchanges the same message types on both sides. Direct shipper-to-carrier moves use the same messages without the broker lane.
Illustrative example: one brokered truckload
An illustrative brokered truckload, followed step by step. Partners define their own messages and sequence.
| Step | Message or event | From → to | What the integration checks |
|---|---|---|---|
| Tender the load | Load tender (204 or API) | Broker → carrier | Stops, dates and equipment are present and the shipment reference is stored. |
| Accept | Response (990) | Carrier → broker | The response echoes the reference and arrives inside the window. |
| Pick up | Status (214) | Carrier → broker → shipper | The event code is mapped to the shipper’s milestone. |
| Deliver | Status (214) and proof of delivery | Carrier → broker | Delivery is recorded and the signed proof is attached to the shipment. |
| Bill | Invoice (210) | Carrier → broker | The invoice carries the same reference and can be compared with the tender. |
Messages
Transactions and messages
Typical requirements—confirm with your trading partner.
The four core truckload messages
Most truckload partners use these four, either as X12 or through an API that carries the same information.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| 204 Motor Carrier Load Tender ANSI X12 | Offers a shipment to a motor carrier. | Shipper, broker or 3PL to Motor carrier | A load is ready to tender or changes | Stops, dates, equipment, weights, references | TMS, ERP | Loads reach carriers without phone or e-mail |
| 990 Response to a Load Tender ANSI X12 | Accepts or declines the tender. | Motor carrier to Shipper, broker or 3PL | Carrier decision inside the response window | Shipment identification, accept or decline, reason | Carrier TMS | Fewer expired tenders and re-tenders |
| 214 Transportation Carrier Shipment Status Message ANSI X12 | Reports pickup, in-transit checkpoints, appointments and delivery. | Carrier to Shipper, consignee, broker or 3PL | Each shipment event | Status and reason codes, time, location | Dispatch, telematics, TMS | Consistent status across partners |
| 210 Motor Carrier Freight Details and Invoice ANSI X12 | Bills the shipper or broker for the freight. | Motor carrier to Shipper, broker or 3PL | Delivery completed | Base freight, accessorial charges, references | Carrier billing, ERP | Invoices that can be matched to the tender |
| 997 Functional Acknowledgment ANSI X12 | Acknowledges that a document arrived and was syntactically valid; the 999 adds implementation-guide checks. Neither shows the carrier accepted a load; that is the 990. | Receiver of any document to Original sender | Each document received | Accepted or rejected, error detail | EDI translator | Unreadable documents are seen at once |
Supporting truckload messages
Some truckload partners add these messages to the core flow; they are not part of every partner's requirements.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| 211 Motor Carrier Bill of Lading ANSI X12 | Gives the carrier the legal bill of lading for a shipment. | Shipper or contracting party to Motor carrier | Shipment released for carriage | Consignor, consignee, freight description, terms | ERP, WMS, shipping system | Bill of lading data is not re-keyed |
| 213 Motor Carrier Shipment Status Inquiry ANSI X12 | Asks a carrier for the status of a shipment. | Shipper or consignee to Motor carrier | Status needed without waiting for an update | Shipment references | TMS, customer service tools | Status requests are automated |
| 216 Motor Carrier Shipment Pickup Notification ANSI X12 | Tells a carrier that a shipment is available for pickup. | Shipper or interested party to Motor carrier | Freight is ready at the dock | Pickup location, time window, shipment details | WMS, shipping system | Pickups are requested from the system that knows readiness |
Truckload, LTL, parcel and last-mile: how the workflows differ
The same shipper often uses all four. The 204, 990, 214 and 210 sequence describes truckload; LTL, parcel and last-mile partners often use different messages or partner APIs.
| Criteria | Truckload | LTL | Parcel and last-mile |
|---|---|---|---|
| How the move starts | A load tender to a carrier or broker, often a 204 or API | A pickup request or bill of lading, often through a portal, API or EDI | A shipment or label request through the carrier’s system or API |
| Status events | Pickup, in transit, appointments, delivery | Pickup, terminal scans, out for delivery, delivery | Scan events, out for delivery, delivery attempts |
| Delivery evidence | Signed proof of delivery, notes on damage or shortage | Signed delivery receipt, exception notes | Delivery confirmation or signature, depending on the carrier |
| Billing | Per-load freight invoice, often a 210 | Freight invoice with accessorial charges | Periodic carrier invoice; format per carrier |
Systems
How ECOM offerings connect your systems and carriers
The diagram shows where each confirmed ECOM offering sits between your TMS, ERP and WMS and the carriers and customers you serve. The offerings can be combined, and each is scoped to your requirements.
Systems a road freight integration connects
Trucking data starts in planning, dispatch and warehouse systems and ends in finance. Scope typically covers these.
| System | What flows | What to plan for |
|---|---|---|
| TMS | Load creation, tenders, acceptances, status events, appointments and freight bills. | Connector availability depends on the TMS product and version; confirmed during scoping. |
| ERP | Orders, shipment references, freight invoices and payments. | Shippers audit freight invoices against tenders and status; carriers reconcile payments against invoices. |
| WMS | Dock appointments, pickup readiness, shipping and receiving confirmations. | Warehouse events often drive pickup and delivery status. |
| Carrier and broker portals and APIs | Tendering, tracking, proof of delivery and rating where a partner offers them. | Some partners require portal or API use; the connection method is chosen per partner. |
Problems and exceptions
Problems road freight teams recognize
These come up in nearly every truckload and brokerage integration.
| Problem | Why it hurts | How ECOM addresses it |
|---|---|---|
| Every new carrier restarts onboarding | Setup, protocol questions and test cycles repeat for each partner and tie up integration staff. | Click-through onboarding, protocol-specific setup and automated transaction testing in the self-service Trading Partner Onboarding portal. |
| Tenders without a timely response | The load is re-tendered, scorecards suffer and planners work from phone calls. | TMS integration lets responses leave the TMS automatically; missing responses are raised as exceptions. |
| Status that means different things to different partners | Customers see inconsistent or missing events and call customer service. | Status events from each partner are mapped to the milestones your systems expect. |
| Proof of delivery that cannot be found | Invoice questions and damage claims wait while someone searches e-mail and shared drives. | The Transaction Life Cycle Manager keeps proof of delivery, signatures and damage or shortage reports with the shipment. |
| Invoices that do not match the load | Freight invoices without the tender’s references cannot be audited automatically. | References are carried from tender to status to invoice so the documents can be compared. |
Common road freight exceptions and what is needed to resolve them
Exceptions are resolved faster when the shipment record, the messages and the delivery evidence are in one place.
| Exception | Typical cause | How it is handled |
|---|---|---|
| Late pickup or delivery | Appointment missed, delay at the dock or on the road. | Needs the appointment, the last status event and the SLA that applies, so the right party is told. |
| Damage or shortage at delivery | Freight noted as damaged or short on the signed receipt. | Needs the signed proof of delivery and the damage or shortage report, linked to the shipment. |
| Rejected status or invoice | Invalid code, missing reference or a version the partner does not accept. | Needs the acknowledgment or application error and the original document, so it can be corrected and resent. |
Get started
How a road freight engagement starts
A short conversation is enough to begin. Your partner, your systems and the problem you are solving are all we need.
- 01
Tell us the carriers, systems and problem
Use the contact form or call, and describe who you move freight with and where onboarding, status or invoices cause trouble.
- 02
Review the partner requirements
An ECOM specialist reviews each partner’s guide or API, and the connection method and versions.
- 03
Agree scope
Which offerings apply, which systems connect and how partners will be onboarded are agreed before work begins.
- 04
Onboard and test
Partners are set up and transactions tested, using the self-service onboarding portal where it fits.
- 05
Go live and support
Go-live arrangements are agreed with you and the partner, with 24×7 support defined in your service agreement.
Helpful to share, never required
- Your role: carrier, broker, shipper or 3PL
- The carriers, brokers or shippers you work with, and their requirements if you have them
- Your TMS, ERP and WMS
- The documents or APIs involved (tender, response, status, proof of delivery, invoice)
- Where manual steps, onboarding delays or exceptions occur today
- Your target timeline
Have a carrier specification? Send it for review Call Sales: 972-836-7750
Sources
Sources and related pages
Standards and partner requirements are revised over time, and each trading partner publishes its own. Confirm current versions with the partner before you build.
Standards and public sources
- ASC X12 transaction setsOfficial names of the 204, 210, 211, 213, 214, 216, 859, 990, 997 and 999 sets; names match ECOM’s transaction guides.
Related pages
- Carriers and Freight Transportation hubAll six modes and processes.
- Transportation and LogisticsTruck, rail, ocean and air at a glance.
- Carrier guidesPartner guides for UPS, FedEx and other carriers.
- EDI 204 Motor Carrier Load TenderThe tender in detail.
- EDI 214 Shipment Status MessageThe status message in detail.
- Intermodal transportationWhen a truck is one leg of a longer move.
- 3PL and warehousingWarehouse orders, shipping advice and WMS.
- Trading Partner OnboardingEDI certification and automation onboarding for customers, suppliers and carriers, by whichever method each partner can support.
- Logistics AutomationAutomate tenders, status updates, freight invoices and warehouse orders with logistics partners.
FAQs
Frequently asked questions
What is the fastest way to onboard a new trucking carrier?
Use Freight Onboarding with ECOM’s self-service Trading Partner Onboarding portal. Your team follows click-through steps with protocol-specific setup, and automated transaction testing replaces much of the manual test coordination. Actual timing depends on the partner and scope.
Do carriers have to be involved in testing?
Some involvement is normal, because a carrier must set up its side. Automated transaction testing reduces the e-mail and phone coordination between your team and each carrier.
What is the difference between the 204, 990, 214 and 210?
The 204 offers a load to a carrier, the 990 accepts or declines it, 214 messages report status such as pickup, appointments and delivery, and the 210 invoices the freight. Partners may use APIs for some of these steps.
Does ECOM integrate our TMS, ERP and WMS?
The ECOM Systems Integrator connects TMS, ERP and WMS platforms, and Hundreds of customers use the Systems Integrator today, and ECOM performs these integrations for customers. Support for your specific products and versions is confirmed during scoping.
How are late or rejected loads handled?
The Exception Management Center helps customers automate exception handling and manage internal and customer-facing SLAs. Which exceptions are raised, and to whom, is agreed during implementation.
Where is proof of delivery kept?
The Transaction Life Cycle Manager holds shipment paperwork and supporting evidence, including proof of delivery, signatures, damage reports and shortage reports.
Does ECOM provide a transportation management system?
No. ECOM integrates the TMS, ERP and WMS you already use rather than replacing them.
Discuss the carriers you need to connect or onboard
Tell us which carriers, brokers or shippers you work with, which TMS you run and where onboarding or testing slows you down. An ECOM specialist will outline the documents, onboarding and testing involved.