Skip to main content

Chain Release Notes — January 2026

Written by Madhav M
Updated yesterday

_Release window: January 1, 2026 to January 31, 2026_

New features

  • Added bulk shipment status updates in workspace views. Teams can update more shipments at once instead of changing each one individually. This helps reduce repetitive actions during daily operations.

  • Added a reference number field in shipment records. Teams can store and search a clearer external reference on each shipment. This makes shipment lookup and handoffs easier.

  • Added trip history visibility in connection records. Users can review more shipment movement history in one place. This helps teams confirm recent activity faster.

  • Expanded tracking coverage with additional provider support. Teams can connect more fleets and still monitor shipment progress in Chain. This reduces manual tracking work across mixed providers.

  • Added support for enabling the 3PLSystems app. Teams using 3PLSystems can complete setup through standard app configuration. This makes onboarding the integration more consistent.

  • Added support for enabling the Apollo ELD app. Teams can connect Apollo ELD for shipment tracking workflows. This broadens supported ELD options without custom setup.

  • Added carrier broadcast exclusion controls. Teams can avoid sending updates to carriers that should be excluded. This gives dispatchers more control over outbound communication.

  • Added a confirmed rate field in shipments. Teams can record a finalized shipment rate in the shipment details. This improves visibility for rate confirmation during execution.

  • Added filters in the apps list. Users can find the right app configuration faster. This improves navigation when many integrations are enabled.

Bug fixes

  • Fixed an issue that could affect shipment-related actions in some cases. Shipment workflows now complete more consistently. Teams should see fewer retries during routine updates.

Behind the scenes

  • Internal reliability improvements were applied across core workflows. No extra setup is required from customer teams. No user-facing configuration changes are needed.

Did this answer your question?