Carriers integration

ArcBest EDI 204, 210 and 214 integration

ArcBest publishes 204, 210 and 214 specifications and onboards shippers through a Trading Partner Form. See what flows between you and ArcBest and how ECOM connects it.

At a glance

ArcBest integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific ArcBest program or a customer relationship.

Illustration of a freight truck on a highway, representing the carriers industry that ArcBest operates in.
Industry. Carriers: where ArcBest operates.
Workflow diagram: your TMS, ERP and finance systems exchange documents with ArcBest through ECOM. You send 204, 211; you receive 214, 210, 990; 997 acknowledgments go both ways. Your systems TMS · ERP · finance ECOM integration map · validate · connect · monitor ArcBest 204 211 204 211 214 210 990 214 210 990 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 Tenders and invoices re-keyed 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 ArcBest

Tell us which documents you exchange with ArcBest, 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 ArcBest.

  • Review of ArcBest's requirements with you, once you have them
  • EDI and API integration with your TMS, ERP and finance 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
ArcBest

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 ArcBest integration fits your systems

Your systemsTMS, ERP and accounting
ECOMMapping, validation, connectivity and monitoringEDI with any X12 version, or XML and JSON · ArcBest API integrations · Trading Partner Form
ArcBestIts program, documents and requirements
  1. ConfirmConfirm your ArcBest 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 ArcBest integration

Who this is for: Shippers, brokers and logistics providers that tender freight to ArcBest, track it and receive its freight bills, and the transportation and finance teams that run those exchanges.

Scope: Other documents on this page (211, 990, 997) are not on ArcBest's published list. They are listed as commonly used in freight EDI.

If you ship with ArcBest, three exchanges matter: the load or bill of lading you send, the status you get back while freight moves, and the freight bill you audit and pay. ArcBest publishes its Shipping EDI program for exactly these three: ANSI X12 204 (shipment information, used to send bills of lading and load tenders to carriers), 210 (freight bills, for payment and auditing) and 214 (shipment status, for tracking and in-transit information). ArcBest states that any X12 version is supported and that it can also work with XML or JSON, and it offers API integrations as an alternative.

ArcBest publishes a specification PDF for each of the three documents, with the map and sample data. To start or change an integration you complete its Trading Partner Form, using the New Connection Form for a new integration or the Existing Connection Form for changes. The form gathers project details and the contact for your integration partner. ArcBest then assigns an EDI Support Specialist to work with you. ArcBest does not publish a testing procedure on that page.

ECOM helps you read those specifications, map the three documents to your TMS, ERP and payables systems, configure connectivity, test and monitor every file after go-live, as software, as a managed service or both. Because the 210 can differ from the quoted rate after weight or class corrections, ECOM matches each freight bill to its shipment and lists the differences.

Business scenarios

Where ArcBest integration gets complicated

Typical requirements—confirm with your trading partner.

Class and weight changes on the freight bill

LTL charges can change after the carrier reweighs or reclassifies a shipment, so the 210 may differ from what you expected.

How ECOM helps: ECOM matches each 210 to the bill of lading data you sent and lists the differences for review.

What you gain: Fewer overcharges paid.

Status inside your own systems

ArcBest publishes the 214 for tracking, performance monitoring and in-transit information.

How ECOM helps: ECOM maps 214 events into your TMS, WMS or customer-service views and flags shipments with missing events.

What you gain: Planners and service teams see current freight status.

Workflows

Typical ArcBest business workflows

The steps summarize the documents below. Where a step is not in ArcBest's published documents, it reflects common practice.

Tender to delivery

  1. 1Send 204 shipment information
  2. 2Receive 214 status
  3. 3Receive 214 delivery event
  4. 4Reconcile the freight bill

Freight bill audit

  1. 1Receive 210 freight bill
  2. 2Compare to the 204 data
  3. 3Spot class or weight change
  4. 4Approve or dispute

Onboarding

  1. 1Submit Trading Partner Form
  2. 2Work with EDI specialist
  3. 3Map 204, 210 and 214
  4. 4Test and go live

Documents and APIs

ArcBest documents by program

Every document this guide names, with the program it applies to and its status. Required, optional and conditional come from ArcBest's published documents cited below; documents marked general guidance are common in this industry but not confirmed for ArcBest.

DocumentNameDirectionProgramStatusPurpose
204 Motor Carrier Load Tender To ArcBest Shipping EDI Named; level not stated ArcBest describes the 204 as the document used to send bills of lading and load tenders to carriers. It carries the shipment details you send.
214 Transportation Carrier Shipment Status Message From ArcBest Shipping EDI Named; level not stated ArcBest describes the 214 as shipment status for tracking, performance monitoring and in-transit information.
210 Motor Carrier Freight Details and Invoice From ArcBest Shipping EDI Named; level not stated ArcBest describes the 210 as the freight bill, used for payment and auditing.
211 Motor Carrier Bill of Lading To ArcBest Not stated General guidance Commonly used in LTL freight to send bill of lading data. ArcBest does not list it on its EDI page.
990 Response to a Load Tender From ArcBest Not stated General guidance Commonly used to accept or decline a tendered load. ArcBest does not list it on its EDI page.
997 Functional Acknowledgment Both directions Not stated General guidance Commonly used to confirm that each file was received and could be read.

Connectivity

How companies connect

  • EDI with any X12 version, or XML and JSON

    ArcBest states that its EDI connections support any ANSI X12 version and can also accept XML or JSON.

    From ArcBest's published documents

  • ArcBest API integrations

    ArcBest offers API integrations as an alternative to EDI. It also publishes a comparison of EDI and API for choosing between them.

    From ArcBest's published documents

  • Trading Partner Form

    You start or change an integration by submitting the New Connection Form or the Existing Connection Form. ArcBest then assigns an EDI Support Specialist.

    From ArcBest's published documents

  • Transport protocol

    ArcBest's EDI page does not name AS2, SFTP or a value-added network. Agree the transport with the assigned EDI specialist.

    General guidance

Challenges

Common integration challenges

  • Three documents, three owners

    Operations owns the 204, customer service the 214 and accounts payable the 210. Keep identifiers consistent so each can be matched to the others.

  • Class and weight corrections

    Corrections after pickup change the final invoice. Matching the 210 to the 204 data makes the change visible before payment.

  • Specification versions

    ArcBest supports any X12 version, so agree the version your systems produce and consume, and test with the posted sample data.

  • Form details

    The Trading Partner Form asks for project details and your integration partner's contact. Have both ready to avoid delays.

Automation options for ArcBest shippers

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. ArcBest 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 ArcBest connection

Freight exchanges with ArcBest 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. ArcBest may set its own security requirements, which come first.

General EDI flow

How EDI with ArcBest typically works

The documents, their order and the timing are ArcBest's to set; this is the general sequence most programs of this kind follow.

  1. 204 Motor Carrier Load Tender

    From you to ArcBest

    ArcBest describes the 204 as the document used to send bills of lading and load tenders to carriers. It carries the shipment details you send.

  2. 214 Transportation Carrier Shipment Status Message

    From ArcBest to you

    ArcBest describes the 214 as shipment status for tracking, performance monitoring and in-transit information.

  3. 210 Motor Carrier Freight Details and Invoice

    From ArcBest to you

    ArcBest describes the 210 as the freight bill, used for payment and auditing.

  4. 211 Motor Carrier Bill of Lading

    From you to ArcBest

    Commonly used in LTL freight to send bill of lading data. ArcBest does not list it on its EDI page.

  5. 990 Response to a Load Tender

    From ArcBest to you

    Commonly used to accept or decline a tendered load. ArcBest does not list it on its EDI page.

  6. 997 Functional Acknowledgment

    Both directions

    Commonly used to confirm that each file was received and could be read.

Working from ArcBest's published specification?

Tell ECOM which program and documents apply to you. We read the published specification with you, map it to your systems and test against it. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your ArcBest program

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

  • Review ArcBest's requirements

    Send us ArcBest's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect ArcBest to your ERP

    Tenders, status and freight invoices in and out of the TMS, ERP and finance systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each ArcBest document, then go live with monitoring from the first file.

    Plan testing and certification

ArcBest integration FAQs

Which EDI documents does ArcBest publish?

ArcBest publishes specifications for the ANSI X12 204, 210 and 214 on its Shipping EDI page, each with a map and sample data.

How do I start an EDI connection with ArcBest?

ArcBest requires its Trading Partner Form, either the New Connection Form for a new integration or the Existing Connection Form for changes. ArcBest then assigns an EDI Support Specialist.

Can I use an API instead of EDI with ArcBest?

ArcBest offers API integrations as an alternative and also accepts XML or JSON alongside EDI.

Does ArcBest use 990 or 211 documents?

ArcBest does not list the 990, 211 or 997 on its EDI page. They are commonly used in freight EDI, so confirm with the assigned EDI specialist whether your program uses them.

Which X12 version does ArcBest support?

ArcBest states that any X12 version is supported. Agree the version with your EDI specialist.

Is this page an endorsement by ArcBest?

This is an independent integration guide. It does not indicate an endorsement, partnership or approval by ArcBest.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. ArcBest sets its own requirements and can change them at any time; your ArcBest implementation guide, supplier portal or account contact is the authoritative source for your program.

Request ArcBest integration assistance

Tell us about your ArcBest program, documents and ERP. We will outline the connection, mapping and testing plan.