Overview
Understanding Knight-Swift Transportation Holdings integration
Who this is for: Shippers, brokers and logistics teams that tender truckload, dedicated or logistics freight with Knight-Swift, and the transportation, IT and finance staff who connect those shipments to a TMS or ERP.
Scope: API and EDI integration is described on Knight's services page and in its 10-K. EDI set numbers and onboarding are not published there; the documents shown are typical practice.
Shippers using Knight-Swift services need tenders, tracking and invoices to move between their systems and the carrier. The exchange that matters is the load tender out and status, proof of delivery and billing back.
Knight's services page lists dry van, refrigerated, port services (drayage), dedicated, logistics, expedited and warehousing, and names API and EDI integration under customized solutions. Knight-Swift's annual reports say customers can track shipments and get shipping documents on its website and that it provides electronic data interchange services to customers who want them; its customers are typically large corporations in retail, food and beverage, consumer products, housing and building, automotive and manufacturing. No EDI set numbers or onboarding steps are published in the pages read, so the documents below are typical practice.
ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications. It then monitors every file after go-live and handles partner changes, as software, as a managed service or both.