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.