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.

At a glance

Old Dominion Freight Line integration, in three pictures

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.

Illustration of a freight truck on a highway, representing the carriers industry that Old Dominion Freight Line operates in.
Industry. Carriers: where Old Dominion Freight Line operates.
Workflow diagram: your ERP and warehouse systems exchange documents with Old Dominion Freight Line through ECOM. You send 204, 211; you receive 990, 214, 210; 997 acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor Old Dominion Freight Line 204 211 204 211 990 214 210 990 214 210 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Old Dominion Freight Line

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.

  • Review of Old Dominion Freight Line's requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Old Dominion Freight Line

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Old Dominion Freight Line integration fits your systems

Your systemsTMS, ERP and accounting
ECOMMapping, validation, connectivity and monitoringEDI over FTP SFTP AS2 or VAN · ODFL APIs · Other formats
Old Dominion Freight LineIts program, documents and requirements
  1. ConfirmConfirm your Old Dominion Freight Line program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

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

General guidance: typical flows in this industry, not Old Dominion Freight Line's published process.

LTL shipment lifecycle

  1. 1Send 204 pickup request
  2. 2Send 211 bill of lading data
  3. 3Receive 990 response
  4. 4Receive 214 status updates
  5. 5Receive 210 freight invoice

Documents and APIs

Old Dominion Freight Line documents by program

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.

DocumentNameDirectionProgramStatusPurpose
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

How companies connect

  • EDI over FTP SFTP AS2 or VAN

    ODFL lists FTP, SFTP, AS2 and VAN services for EDI exchange.

    General guidance

  • ODFL APIs

    ODFL offers web service APIs for customers alongside EDI.

    General guidance

  • Other formats

    ODFL states it can exchange XML, flat files and SAP IDocs as well as EDI.

    General guidance

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.

Automation options for Old Dominion Freight Line shippers

Four ways to automate. One foundation.

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.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

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.

Discuss Your Trading Partner Requirements

Zero Trust for freight data exchange

Zero Trust EDI and MFT for your Old Dominion Freight Line connection

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.

  • Authentication

    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.

  • Least privilege

    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.

  • Isolation

    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.

  • Encryption

    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.

  • Certificate and key management

    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.

  • Monitoring and access controls

    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.

  • Audit trail

    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.

What this means for your data

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.

Tenders, status and invoices

Load tenders, status messages and freight invoices are checked at the connection and the file, and every transfer is logged.

Rates and contract data

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.

General EDI flow

How EDI with Old Dominion Freight Line typically works

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.

  1. 204 Motor Carrier Load Tender

    From you to Old Dominion Freight Line

    The shipper requests a freight pickup.

  2. 211 Motor Carrier Bill of Lading

    From you to Old Dominion Freight Line

    The shipper sends bill of lading, rating and scheduling details.

  3. 990 Response to a Load Tender

    From Old Dominion Freight Line to you

    ODFL responds to the pickup request.

  4. 214 Shipment Status Message

    From Old Dominion Freight Line to you

    ODFL reports shipment status to shippers and consignees.

  5. 210 Motor Carrier Freight Details and Invoice

    From Old Dominion Freight Line to you

    ODFL bills for the shipment.

  6. 997 Functional Acknowledgment

    Both directions

    Confirms documents were received.

Need help with the specification?

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

Get help with your Old Dominion Freight Line program

Each request goes to an ECOM EDI specialist with Old Dominion Freight Line's name attached, so the reply starts from your program.

  • Review Old Dominion Freight Line's requirements

    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 review
  • Connect Old Dominion Freight Line to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Old Dominion Freight Line document, then go live with monitoring from the first file.

    Plan testing and certification

Old Dominion Freight Line integration FAQs

Which EDI documents does Old Dominion support?

ODFL 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.

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.

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.