Skip to main content

Chain Release Notes — March 2026

Written by Madhav M
Updated this week

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

New features

  • Added a new View all locations button on shipment tracking maps. It opens a paginated table of received location pings, with All sources as the default view and filters for individual tracking sources. This makes it easier to review full location history when map markers are dense or overlapping.

  • Expanded tracking and transportation-system support with ZippyELD, Under Control SA, SecurePath ELD, GPS Insight, ELD Mandate, Trucker Tools, and Priority1. Teams can connect these providers through Chain's standard setup flows for tracking and app onboarding. This expands shipment-visibility coverage across more carrier and system combinations.

  • Added shipment file capture and organization from chat, email, and SMS. Bills of lading, PODs, receipts, and images can now attach to shipments more consistently. This makes shipment documents easier to find while work is in motion.

  • Added equipment counts and descriptions in carrier network and CRM views. Teams can now store a count and note for each equipment type, see the type and count in lists, and keep the description attached in detail views. This gives more context when reviewing carrier capabilities and lane fit.

  • Added a new Block notifications option in carrier exclusions for outbound email and SMS messages. Teams can now suppress dispatcher assignment, load post, shipment chat, offer chat, and offer accepted or declined notifications for excluded carriers. This gives admins more control over which carriers receive outbound communication.

Improvements

  • Updated the driver app load and stop-details experience. Drivers now see redesigned shipment and stop-detail screens, clearer actions such as Mark arrived, Mark departed, and Swipe to mark arrived, plus a shared departure confirmation flow. This makes stop updates easier to follow in the field.

  • Added an in-route current-location state to the driver shipment timeline. The timeline now shows a pulsing in-route marker between the last completed stop and the next active stop, with clearer stop-card interactions while a stop is still upcoming. This helps drivers understand route progress before arrival.

  • Updated the make-offer flow with a clearer company confirmation step, refreshed offer-details copy, and fixes for duplicate or stale submission state. Users should see a smoother path from reviewing a post to sending an offer. This reduces confusion in the final steps before submission.

  • Added timezone labels to stop-related dates and appointment times. Appointment, ETA, arrival, and departure times now display with timezone abbreviations such as CDT. This helps teams avoid timing mistakes across regions.

  • Updated inbox and shipment views so shipment and inbox pages share the same details, files, and stops layout, and simplified archived-chat handling for the current inbox flow. Users can review shipment files more reliably and navigate active conversations with less confusion. This makes day-to-day communication workflows more consistent.

  • Improved how forwarded tracking links are recognized. Supported links copied from wrapped email URLs, including Outlook SafeLinks, can now resolve to the original tracking provider more reliably. This helps preserve shipment visibility when links are forwarded between inboxes.

Bug fixes

  • Fixed next-stop calculations after a final destination is completed. Shipment timelines no longer point back to the wrong stop after delivery is done. This improves ETA and remaining-distance accuracy late in the trip.

  • Fixed shipment map route rendering and initial tracking viewport behavior. Route lines and map positioning now appear more reliably when a shipment loads. Users should see fewer cases where tracking context is missing on first view.

  • Fixed driver stop actions so arrival can only be marked when the driver is within 2 miles of the stop location, and departure uses a clearer confirmation flow instead of a rushed tap path. This helps reduce early or accidental stop updates from the field. It also makes arrival and departure behavior more predictable for drivers.

  • Fixed integration and setup issues across supported apps, including Infios and Trucker Tools. Tracking setup, shipment-number mapping, and customer-specific configuration handling are more reliable across these flows. This reduces avoidable onboarding and shipment-visibility issues.

Behind the scenes

  • Reliability, analytics, and performance work continued across web and mobile experiences. These updates support faster load times, cleaner reporting, and more stable shipment workflows. No additional setup is required from customer teams.

Did this answer your question?