Carriers integration
XPO EDI integration for shippers
A guide for shippers connecting with XPO for tenders, shipment status and freight invoices through EDI and APIs.
Overview
Understanding XPO integration
Who this is for: Shippers moving freight with XPO who want tendering, tracking and invoicing automated between their systems and XPO.
XPO is a major less-than-truckload carrier in North America, and like most large carriers it exchanges transportation documents with customers electronically. The common pattern is a load tender from the shipper, a tender response from the carrier, shipment status messages as freight moves, and a freight invoice when the shipment is complete.
Third-party EDI catalogs list XPO channels supporting the 204 load tender, 990 tender response, 214 shipment status and 210 freight invoice, with connections over AS2, SFTP or API. Tender responses are time-sensitive in many tendering processes, and shippers rely on status messages for tracking, dock scheduling and carrier performance measurement. Freight invoices are checked against the tender and status before payment.
Carrier industry restructuring means some legacy XPO channels now relate to separate companies, so shippers should confirm current EDI specifications and identifiers directly with XPO.
Workflows
Typical XPO business workflows
Tender to payment
- 1Send 204 load tender
- 2Receive 990 tender response
- 3Receive 214 status updates
- 4Receive 210 freight invoice
- 5Audit and pay
Documents and APIs
Common XPO transactions
Documents commonly exchanged with XPO, based on the public sources listed below. Exact requirements depend on your program, so always confirm against XPO's current implementation guide.
| Document | Name | Direction | Purpose |
|---|---|---|---|
| 204 | Motor Carrier Load Tender | To XPO | The shipper offers a shipment to XPO. |
| 990 | Response to a Load Tender | From XPO | XPO accepts or declines the tender. |
| 214 | Shipment Status Message | From XPO | Reports pickup, transit and delivery events. |
| 210 | Motor Carrier Freight Details and Invoice | From XPO | Bills for the shipment. |
Connectivity
How companies connect
AS2 or SFTP
Third-party catalogs list AS2 and SFTP connections for XPO EDI.
APIs
API connectivity is also listed as an option for some XPO channels.
Challenges
Common integration challenges
Timely tender responses
Tendering processes often depend on prompt 990 responses before loads are re-tendered.
Status consistency
Status codes and timing must be consistent for reliable tracking and performance reporting.
Invoice validation
Freight invoices must be matched to tenders and agreed rates.
How ECOM helps
How ECOM can support your XPO integration
Logistics Automation
Automate tenders, status and invoices between your TMS and XPO.
ProductPRISM-SCV
Monitor tender responses and missing status updates.
SolutionFinancial Document Automation
Route freight invoices into your audit and payment process.
ERP integration options
ECOM integrates XPO tenders, status messages and invoices with your TMS and ERP so shipments are tracked and freight costs reconciled automatically.
Visibility and exception management
PRISM-SCV, ECOM's supply chain visibility product, is designed to follow each XPO 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-SCVXPO integration FAQs
Which EDI documents are used with XPO?
Third-party catalogs list the 204 load tender, 990 tender response, 214 status message and 210 freight invoice. Confirm current specifications with XPO.
Can shippers connect to XPO by API?
Third-party catalogs list API connectivity for some XPO channels. Check with XPO for current API options.
Why confirm XPO identifiers before building?
Some legacy XPO business units now operate as separate companies, so shippers should confirm which entity and identifiers apply.
Is ECOM an XPO partner?
This page is an integration guide and does not indicate a partnership with XPO. ECOM builds integrations to published specifications.
Sources and accuracy
This guide summarizes publicly available information as of October 2026. XPO sets its own requirements and can change them at any time; your XPO implementation guide, supplier portal or account contact is the authoritative source for your program.
- Stacksync, XPO EDI channels Third-party source
XPO 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.
Old Dominion Freight Line EDI
A guide for shippers connecting with Old Dominion Freight Line for LTL pickups, bills of lading, shipment status and freight invoices.
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.
Request XPO integration assistance
Tell us about your XPO program, documents and ERP. We will outline the connection, mapping and testing plan.