Carrier onboarding
Each carrier or broker gets its own identity and scope. A new carrier is tested before it reaches production, and a removed carrier loses access without affecting the others.
Carriers integration
A guide for shippers connecting with Old Dominion Freight Line for LTL pickups, bills of lading, shipment status and freight invoices.
At a glance
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Old Dominion Freight Line program or a customer relationship.
Tell us which documents you exchange with Old Dominion Freight Line, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Old Dominion Freight Line.
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
Overview
Who this is for: Shippers and consignees moving less-than-truckload freight with Old Dominion Freight Line who want pickups, status and invoices automated.
Old Dominion Freight Line is one of the largest less-than-truckload carriers in the United States, and it publishes its EDI capabilities for customers. According to ODFL, shippers can send load tenders to request freight pickups and send bill of lading, rating and scheduling information, while ODFL sends shipment status updates to shippers and consignees and sends freight invoices requesting payment. Tender responses and functional acknowledgments complete the exchange.
ODFL also describes a set of web service APIs for customers and says it can exchange data in formats beyond EDI, including XML, flat files and SAP IDocs, over FTP, SFTP, AS2 or VAN services. That flexibility lets shippers choose an approach that fits their transportation and ERP systems.
For a shipper, the value is fewer manual bookings, automatic status updates for customer service, and freight invoices that can be audited and paid electronically.
Workflows
General guidance: typical flows in this industry, not Old Dominion Freight Line's published process.
Documents and APIs
General guidance. We could not verify Old Dominion Freight Line's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Old Dominion Freight Line's confirmed requirements. Confirm the list, versions and programs with Old Dominion Freight Line.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Program | Status | Purpose |
|---|---|---|---|---|---|
| 204 | Motor Carrier Load Tender | To Old Dominion Freight Line | Not stated | General guidance | The shipper requests a freight pickup. |
| 211 | Motor Carrier Bill of Lading | To Old Dominion Freight Line | Not stated | General guidance | The shipper sends bill of lading, rating and scheduling details. |
| 990 | Response to a Load Tender | From Old Dominion Freight Line | Not stated | General guidance | ODFL responds to the pickup request. |
| 214 | Shipment Status Message | From Old Dominion Freight Line | Not stated | General guidance | ODFL reports shipment status to shippers and consignees. |
| 210 | Motor Carrier Freight Details and Invoice | From Old Dominion Freight Line | Not stated | General guidance | ODFL bills for the shipment. |
| 997 | Functional Acknowledgment | Both directions | Not stated | General guidance | Confirms documents were received. |
Connectivity
ODFL lists FTP, SFTP, AS2 and VAN services for EDI exchange.
General guidance
ODFL offers web service APIs for customers alongside EDI.
General guidance
ODFL states it can exchange XML, flat files and SAP IDocs as well as EDI.
General guidance
Challenges
Rating and billing depend on correct weights, classes and accessorials in the bill of lading.
Status messages must be linked to orders so customer service sees current delivery information.
LTL invoices must be checked against rates and accessorial charges.
Automation options for Old Dominion Freight Line shippers
ECOM helps you automate the exchange, connect it to your systems, and see what needs action. Old Dominion Freight Line sets its own requirements; ECOM confirms which options fit yours.
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/APIReceive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDIConvert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvertAutomate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
Learn more about WebConnectPRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.
ECOM integrates ODFL pickups, bills of lading, status messages and invoices with your ERP and TMS, using EDI, APIs or IDocs depending on your systems.
Automate pickups, bills of lading, status and invoices with ODFL.
SolutionBring ODFL freight invoices into accounts payable automatically.
SolutionCombine ODFL status updates with your order lifecycle.
Zero Trust for freight data exchange
Freight exchanges with Old Dominion Freight Line carry tenders, status events, rates and freight invoices. A Zero Trust design assumes no connection, file or user is safe by default.
ECOM has implemented Zero Trust EDI and Zero Trust MFT in trucking.
For freight exchanges this means each carrier has its own scope, tenders, status messages and invoices are checked at the connection and the file, a late or missing file is noticed early, and every transfer has a record for freight billing disputes and security reviews.
Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.
Business outcome: A lost or reused credential affects one partner, not all of them.
Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.
Business outcome: A mistake or compromise in one account stays limited to what that account could reach.
Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.
Business outcome: Outside connections do not land directly on your internal systems.
Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.
Business outcome: Less exposure if a file is intercepted or a file store is reached.
Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.
Business outcome: Fewer outages caused by an expired certificate or key.
Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.
Business outcome: Late, missing or failed files are noticed early, before they hold up tenders, status or freight billing.
Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.
Business outcome: You can answer who sent what and when, for your own audits and partner reviews.
Each carrier or broker gets its own identity and scope. A new carrier is tested before it reaches production, and a removed carrier loses access without affecting the others.
Load tenders, status messages and freight invoices are checked at the connection and the file, and every transfer is logged.
Rate and accessorial files are limited to the roles that need them.
Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Old Dominion Freight Line may set its own security requirements, which come first.
Talk to an EDI/API Expert about Zero Trust Managed file transferSecure proxy and DMZ designSecurity at ECOM
General EDI flow
The documents, their order and the timing are Old Dominion Freight Line's to set; this is the general sequence most programs of this kind follow.
204 Motor Carrier Load Tender
From you to Old Dominion Freight Line
The shipper requests a freight pickup.
211 Motor Carrier Bill of Lading
From you to Old Dominion Freight Line
The shipper sends bill of lading, rating and scheduling details.
990 Response to a Load Tender
From Old Dominion Freight Line to you
ODFL responds to the pickup request.
214 Shipment Status Message
From Old Dominion Freight Line to you
ODFL reports shipment status to shippers and consignees.
210 Motor Carrier Freight Details and Invoice
From Old Dominion Freight Line to you
ODFL bills for the shipment.
Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.
Next step
Each request goes to an ECOM EDI specialist with Old Dominion Freight Line's name attached, so the reply starts from your program.
Send us Old Dominion Freight Line's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements reviewOrders in, ship notices and invoices out, from the ERP and warehouse systems you already run.
Discuss ERP integrationBuild, test and certify each Old Dominion Freight Line document, then go live with monitoring from the first file.
Plan testing and certificationODFL lists the 204, 210, 211, 214, 990, 997 and 820 for shipping and payment, plus the 810, 850, 856, 940 and 945 for other trading programs. Its web services brochure also mentions the 212.
Yes. ODFL describes a set of web service APIs for customers in addition to EDI.
ODFL states it can exchange data in formats including SAP IDocs. ECOM can integrate ODFL with SAP and other ERPs.
This page is an integration guide and does not indicate a partnership with Old Dominion Freight Line. ECOM builds integrations to ODFL's published specifications.
This guide summarizes publicly available information as of October 2026. Old Dominion Freight Line sets its own requirements and can change them at any time; your Old Dominion Freight Line implementation guide, supplier portal or account contact is the authoritative source for your program.
Old Dominion Freight Line is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
How EDI and API integration with CTSI-Global typically works: freight brokerage and logistics documents, workflows, onboarding and common problems, as typical practice to confirm with CTSI-Global.
How EDI and API integration with Daily Express typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Daily Express.
How EDI and API integration with Daseke typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Daseke.
How EDI and API integration with Davis Cartage Co. works in practice: documents, workflows, onboarding and common problems, and where ECOM helps.
How EDI and API integration with Day & Ross typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Day & Ross.
How EDI and API integration with Daylight Transport typically works: LTL freight documents, workflows, onboarding and common problems, as typical practice to confirm with Daylight Transport.
Tell us about your Old Dominion Freight Line program, documents and ERP. We will outline the connection, mapping and testing plan.