Carriers integration
Old Dominion Freight Line EDI and API integration
A guide for shippers connecting with Old Dominion Freight Line for LTL pickups, bills of lading, shipment status and freight invoices.
Overview
Understanding Old Dominion Freight Line integration
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
Typical Old Dominion Freight Line business workflows
LTL shipment lifecycle
- 1Send 204 pickup request
- 2Send 211 bill of lading data
- 3Receive 990 response
- 4Receive 214 status updates
- 5Receive 210 freight invoice
Documents and APIs
Common Old Dominion Freight Line transactions
Documents commonly exchanged with Old Dominion Freight Line, based on the public sources listed below. Exact requirements depend on your program, so always confirm against Old Dominion Freight Line's current implementation guide.
| Document | Name | Direction | Purpose |
|---|---|---|---|
| 204 | Motor Carrier Load Tender | To Old Dominion Freight Line | The shipper requests a freight pickup. |
| 211 | Motor Carrier Bill of Lading | 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 | ODFL responds to the pickup request. |
| 214 | Shipment Status Message | From Old Dominion Freight Line | ODFL reports shipment status to shippers and consignees. |
| 210 | Motor Carrier Freight Details and Invoice | From Old Dominion Freight Line | ODFL bills for the shipment. |
| 997 | Functional Acknowledgment | Both directions | Confirms documents were received. |
Connectivity
How companies connect
EDI over FTP SFTP AS2 or VAN
ODFL lists FTP, SFTP, AS2 and VAN services for EDI exchange.
ODFL APIs
ODFL offers web service APIs for customers alongside EDI.
Other formats
ODFL states it can exchange XML, flat files and SAP IDocs as well as EDI.
Challenges
Common integration challenges
Accurate bill of lading data
Rating and billing depend on correct weights, classes and accessorials in the bill of lading.
Status visibility
Status messages must be linked to orders so customer service sees current delivery information.
Freight audit
LTL invoices must be checked against rates and accessorial charges.
How ECOM helps
How ECOM can support your Old Dominion Freight Line integration
Logistics Automation
Automate pickups, bills of lading, status and invoices with ODFL.
SolutionFinancial Document Automation
Bring ODFL freight invoices into accounts payable automatically.
SolutionSupply Chain Visibility
Combine ODFL status updates with your order lifecycle.
ERP integration options
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.
Visibility and exception management
PRISM-SCV, ECOM's supply chain visibility product, is designed to follow each Old Dominion Freight Line document from receipt to response and flag late or missing documents and mismatches, so your team can resolve exceptions before they affect the relationship.
Explore PRISM-SCVOld Dominion Freight Line integration FAQs
Which EDI documents does Old Dominion support?
ODFL lists the 204, 210, 211, 214, 990 and 997 on its EDI page, and its web services brochure also mentions the 212.
Does ODFL offer APIs?
Yes. ODFL describes a set of web service APIs for customers in addition to EDI.
Can ODFL exchange data with SAP?
ODFL states it can exchange data in formats including SAP IDocs. ECOM can integrate ODFL with SAP and other ERPs.
Is ECOM an ODFL partner?
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.
Sources and accuracy
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.
- ODFL, Electronic Data Interchange Official Old Dominion Freight Line source
- ODFL, Web Services brochure Official Old Dominion Freight Line source
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
More carriers integration guides
FedEx EDI
A guide for shippers automating FedEx invoices and payments through EDI and connecting FedEx shipping and tracking data to their systems.
Schneider EDI
A guide for shippers and brokers connecting with Schneider for truckload and intermodal tendering, tracking and invoicing.
UPS EDI
A guide for shippers connecting UPS shipping, tracking and billing data to their ERP, warehouse and customer service systems.
XPO EDI
A guide for shippers connecting with XPO for tenders, shipment status and freight invoices through EDI and APIs.
Request Old Dominion Freight Line integration assistance
Tell us about your Old Dominion Freight Line program, documents and ERP. We will outline the connection, mapping and testing plan.