Overview
Understanding Knight Transportation integration
Who this is for: Shippers, brokers and logistics providers that tender freight to Knight Transportation, and their transportation and finance teams.
Scope: This guide describes typical practice for this kind of trading relationship; Knight Transportation's own program details are confirmed during onboarding.
Knight Transportation was a truckload carrier that merged with Swift Transportation in 2017 to form Knight-Swift Transportation. See the Knight-Swift guide for the current company. ECOM's directory lists it under truckload. Shippers working with truckload and specialized carriers typically tender loads, receive acceptance and status updates, and receive freight invoices.
Teams that work with a truckload or specialized trucking carrier gain most from fast tender responses and status they can trust. Knight Transportation's own EDI or API specification is not part of this guide and no Knight Transportation document was read: treat what follows as typical practice for a truckload or specialized trucking carrier, and confirm the documents, X12 version, delivery method and testing steps with Knight Transportation.
ECOM maps the documents to your TMS, ERP and finance systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.