Action Required: Review your integrations and workflows before the effective date.
What's Changing To support all product capabilities across J.B. Hunt's three main divisions, project44 is separating the existing J B Hunt Transport Inc capacity provider into three distinct records — one per operating division. This change is required to support new TMS products and capabilities, and will go into effect on April 16, 2026, at 12:00 AM CST.
J B HUNT TRANSPORT INC (INTERMODAL DIVISION) • Primary SCAC: HJBI • Master Carrier ID: L7LKKI65 • HJBI was previously nested under J B Hunt Transport Inc
J B HUNT TRANSPORT INC (BROKERAGE DIVISION) • Primary SCAC: HJBB • Master Carrier ID: MLZR3EVK • HJBB was previously nested under J B Hunt Transport Inc
Tracking Impact No tracking disruption. project44 deploys a single J.B. Hunt API tracking user that is already attached to all three capacity providers. Active and existing shipments will continue to receive tracking updates without interruption regardless of which SCAC is used.
What This Means for You Starting April 16, 2026, at 12:00 AM CST, any shipment created using HJBI or HJBB will be associated with the new division-level capacity provider — not the original J B Hunt Transport Inc record. Shipments created before April 16 are not affected and will retain their current carrier association.
This affects: • The carrier name returned in API responses • Carrier attribution in analytics and reporting • Webhook payloads that include carrier name • Any internal process or system that references the carrier by name
Your Options — What to Do Before April 16 Different customers have built different workflows. Here are the most common scenarios and what we recommend for each.
Scenario 1: You create intermodal shipments using HJBI and don't want to update your systems Switch to using HJBT for those shipments before April 16, 2026, at 12:00 AM CST. HJBT will remain on the original J B Hunt Transport Inc capacity provider, and your carrier name references will be unaffected. Tracking will not be impacted. That said, we recommend routing shipments under the correct division SCAC where possible.
Scenario 2: You create brokerage shipments using HJBB and don't want to update your systems Same approach — route those shipments under HJBT before April 16, 2026, at 12:00 AM CST to avoid any carrier name changes downstream. Tracking will not be impacted. That said, we recommend routing shipments under the correct division SCAC where possible.
Scenario 3: You're fine updating your systems Update any hardcoded carrier name references from J B Hunt Transport Inc to the appropriate division name — J B Hunt Transport Inc (Intermodal Division) or J B Hunt Transport Inc (Brokerage Division) — before April 16, 2026, at 12:00 AM CST.
Scenario 4: You use webhooks or API callbacks that include carrier name Audit your webhook consumers and API integrations. After April 16, 2026, at 12:00 AM CST, the carrier name field for HJBI and HJBB shipments will reflect the new division- level names. Update any downstream logic that matches or filters on carrier name.
Scenario 5: You have internal reporting or dashboards built on carrier name Shipments created after April 16, 2026, at 12:00 AM CST using HJBI or HJBB will appear under the new capacity provider names. If you need historical and future data to align under one name, plan that mapping in your reporting layer.
Timeline • Now: Review this article and assess impact on your workflows. • Before April 16, 2026, at 12:00 AM CST: Make any necessary updates to integrations, routing rules, or SCAC usage. • April 16, 2026, at 12:00 AM CST: Change goes live — new capacity providers become active. • After April 16, 2026: Shipments using HJBI or HJBB map to their respective division records automatically.
Questions? Contact support@project44.com or reach out to your account team before the effective date.
Posted Apr 03, 2026 - 16:20 UTC
This scheduled maintenance affects: NA - Movement, NA - Visibility Operations Center (VOC), Upstream Network Providers (TL Carrier/ELD), and NA - Truckload (Tracking API, Analytics).