Trading partner network

Carriers EDI and API integration

LTL and truckload carriers, parcel networks and dedicated fleets. ECOM connects your business with carriers through EDI, APIs, managed file transfer and portal automation, integrated with your ERP.

Trading partner network

Carriers we connect with

Through its network, ECOM can connect your business with 3.1M+ trading partners. The 221 carriers below are highlights, by name and business segment. Companies with an integration guide link to it, and each guide says whether it rests on the company’s own documents or on typical industry practice.

How the exchange works

How carriers exchange business documents

Shippers and carriers exchange load tenders, responses, shipment status and freight invoices. Status updates drive customer delivery notices and dock planning, and matching each freight invoice to the tendered rate prevents overbilling.

Common documents with carriers
DocumentWhat it does in this relationship
EDI 204Motor Carrier Load Tender The load tender: pickup and delivery stops, dates, weights and equipment.
EDI 990Response to a Load Tender The carrier’s acceptance or rejection of the tender.
EDI 214Transportation Carrier Shipment Status Message Shipment status messages: picked up, in transit, delayed, delivered.
EDI 210Motor Carrier Freight Details and Invoice The freight invoice, checked against the tender and the agreed rate.
EDI 211Motor Carrier Bill of Lading The bill of lading sent electronically to the motor carrier.

What onboarding a new carriers partner usually involves

  1. Agree which status codes the carrier sends and when, and how stops and references are identified.
  2. Connect rates and invoice audit to your TMS or ERP so freight invoices can be matched automatically.
  3. Test tenders, cancellations and status updates on real lanes before switching from email or portal.

Integration guides

Carriers integration guides

Detailed guides covering documents, workflows, connectivity and ERP options for specific companies. A selection is shown here; search all 218 carriers guides in the directory above.

A. Duie Pyle EDI integration

How EDI and API integration with A. Duie Pyle typically works: LTL freight documents, workflows, onboarding and common problems, as typical practice to confirm with A. Duie Pyle.

Read the guide

AAA Cooper Transportation EDI integration

How EDI and API integration with AAA Cooper Transportation typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with AAA Cooper Transportation.

Read the guide

ABF Freight EDI integration

How EDI and API integration with ABF Freight typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with ABF Freight.

Read the guide

ACI Motor Freight EDI integration

How EDI and API integration with ACI Motor Freight typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with ACI Motor Freight.

Read the guide

Acme Truck Line EDI integration

How EDI and API integration with Acme Truck Line typically works: truckload freight documents, workflows, onboarding and common problems, as typical practice to confirm with Acme Truck Line.

Read the guide

Atlantic Container Line EDI integration

How EDI and API integration with Atlantic Container Line typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Atlantic Container Line.

Read the guide

Averitt EDI integration

Averitt combines LTL and truckload freight with warehousing and fulfillment, and says its warehouses connect by API or EDI. See typical documents and how ECOM helps connect them.

Read the guide

Barnhart Crane & Rigging EDI integration

How EDI and API integration with Barnhart Crane & Rigging typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Barnhart Crane & Rigging.

Read the guide

BNSF Railway EDI integration

BNSF publishes implementation guides for the 404 shipment, 322 ramp activity, 410 freight invoice and 820 payment. See how these rail documents flow and how ECOM connects them.

Read the guide

Boyd Bros. Transportation EDI integration

How EDI and API integration with Boyd Bros. Transportation typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Boyd Bros. Transportation.

Read the guide

C.R. England EDI integration

How EDI and API integration with C.R. England typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with C.R. England.

Read the guide

Canadian National Railway EDI integration

How EDI and API integration with Canadian National Railway typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Canadian National Railway.

Read the guide

General EDI flow

How EDI with your trading partner typically works

Many trading partners do not publish their EDI or API specifications. This is the general sequence most programs of this kind follow.

  1. 204 Load tender

    Shipper to carrier

    The shipper offers a load: pickup and delivery locations, dates and shipment details.

  2. 990 Response to the tender

    Carrier to shipper

    The carrier accepts or declines the load.

  3. 214 Shipment status

    Carrier to shipper

    The carrier reports pickup, location updates and delivery.

  4. 210 Freight invoice

    Carrier to shipper

    The carrier bills for the freight, in the format the shipper's payables system expects.

  5. 997 Functional acknowledgment

    Both directions

    Each side confirms that every file it received was readable. A rejected file is corrected and resent.

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.

Connecting with a carriers partner not listed here?

ECOM connects businesses with partners of every size using their published EDI, API or file requirements.