🚀 Releases

6.6.1 - 06/04/25

Updated Route ID Generation

We are updating to our Route ID generation system, designed to eliminate duplicate IDs and enhance reliability. This introduces a new, robust format for Route IDs while maintaining the seamless experience.

What’s New

• New Route ID Format: Route IDs are now generated case-sensitive Base30 string with 3 groups of 5 characters (e.g.,R-1m7k7-sm5fr-8tqdr). This new format ensures unique IDs every time.
• Case Sensitivity: The new Route IDs are case-sensitive to maximize uniqueness and clarity.
• Consistent Prefix: The familiar R- prefix remains, keeping things intuitive.

This update resolves the issue of duplicate Route IDs and sets the stage for continued growth and reliability. We’re confident it will make your experience smoother and more dependable.

Mobile

Mobile Fixes and Improvements

• Setup Android ProGuardminifyEnabled
• Manual Retry Trigger for Failed/Queued ORD Events
• Enhance TCP Request Retry Logic
• Update to provide orgSourceIdentifier

Client-Specific Mobile Fixes and Improvements

• *** Only
  • Client Android setup

General Fixes and Improvements

• Swapping delivery speed type selects default speeds
• Visibility delivery creation failure
• Route Stops & Route total items should reflect delivery items
• serviceLevelID missing for carrier auto exceptions
• Deliveries excluded from clubbing if it exceeds contract limits
• Route details - Est. Time Completed

Client-Specific Fixes and Improvements

• ** Only
  • get-rates endpoint should return a specific carrier for the shipper when that carrier returns an error.

6.5.2 - 05/21/25

Mobile Fixes and Improvements

• Squished POD images when being added to the ORD app
• Send scan data to mobile endpoint

Integrations

Provider-Specific Scheduled Window

Enable support for scheduled windows in the future for a specific provider.

Carrier B2C Customization

Enable a custom business identifier for a specific provider for a client-specific B2C project to ensure proper POD requirements are handled by the carrier.

General Fixes and Improvements

• Users are not allowed to search when users username length is more than 40 letters
• Control Tower - overlapped labels with text
• Fleet Assets - unnecessary option for speed
• Dispatch Platform Settings | Add/Edit page has duplicate entry fields
• Specific shipper's delivery edit does not auto-populate Service Level field
• Pagination | Landing Page
• Order Date carrot not centered on list views
• Display PickupOpensOn and DropoffClosesOn in the "Pickup Windows" Columns

Client-Specific Fixes and Improvements

• * Only
  • Custom Order Number Mapping for a specific client
• ***** Only
  • New account set up email includes oversized logo
• ********* Only
  • Hide Manually Input Address
  • Hide Manually Create Product

6.5.1 - 05/08/25

General Fixes and Improvements

• Enhance CSV Routing to Address Timeouts
• Hub Stop Marker in Route Details
• Display Vehicle Type "Assigned" and "Recommended" Vehicle on LP Control Tower
• Display Vehicle Type "Assigned" and "Recommended" Vehicle on Route Details
• Addition of Order ID to templates
• Route Costs Failing to Save and Display Updated Route Cost on Individual Deliveries on a Route

6.4.2 - 04/23/25

OmniPoint

New "Route Details" Page

We are enhancing our table views to include a "Route ID" column, which will now link to a newly created "Route Details" page. This page provides comprehensive insights similar to the "Order Details" and "Delivery Details" pages.

Key Features:

• Hyperlinked Route ID: Click on the Route ID in table views to navigate to the "Route Details" page.
• Enhanced Route Visibility: The "Route Details" page includes a granular break down of all route stops, mileage, ETA, etc.

This update offers increased visibility and control over route management, streamlining operations and improving user experience.

Mobile

• Ability for a specific client to see the newly scanned deliveries from the Control Tower on the Driver dashboard
• Send exceptionDefinitionTitle to cancel delivery endpoint
• LogRocket implementation
• Verify deliveries canceled from the Control Tower are removed from the driver app

Integrations

Standardized Visibility Carrier Event Handler

Enhancement to our visibility event offering to utilize a single configuration for many carriers for Visibility deliveries. 

Carrier-Specific Signature Capability

Updated a carrier-specific integration to support dynamic signature request from a shipper.

Carrier-Specific Declared Value

Updated a carrier-specific integration to be able to send a declared value to the carrier.

General Fixes and Improvements

• You are unable to edit a customer location that has a blank name

• Unable to add "E-mail" as a type if every trigger type saved is "SMS"

• Add Filter - Service Level disappear/appear

• Limit Logo Uploads to jpg/png/webp

• Limit Uploads to jpg/png/webp

• Holiday Hours Collapse Items- Markets

• Holiday Hours Collapse Items- Locations

• Add COD Accessorial

• update the edit delivery from to send opensOnPassedCorrectly

• Unable to add "E-mail" as a type if every trigger type saved is "SMS"

• Filtering Enhancements - Display Relationships

• Service Level disappear/appear

• New routes over API do not skip optimizer

• Delivery edit changes cumulative route stop distance

Client-Specific Fixes and Improvements

• * Only
  • Store associations are reversed in table filters

6.4.1 - 04/09/25

Integrations

Carrier-Specific Enhanced Delivery Instructions

Enable support for accessorial and barcode URLs in delivery instructions for a specific carrier.

Client-Specific Shipper Events

Provide the ability for OneRail to send visibility carrier events back to a specific client.

Carrier-Specific Integration

Completed the freight carrier integration for a specific carrier to be leveraged by a specific client.

Carrier-Specific Integration

Completed the freight carrier integration for a specific carrier to be leveraged by a specific client and potentially an additional client as well.

Carrier-Specific International Deliveries

Enabled our integration for specific carriers to support international deliveries adding support for customs.

General Fixes and Improvements

• Hide the "Delivery Deadline" data point on route details
• Items should reflect Delivery items
• One way street routes shown on Delivery Details map are reversed
• Table data updates on Route Details
• CX logo not saving

⏱️Coming Soon

OmniPoint

Foreign Language

In order to expand our services globally, we need to be able to translate the platform into the language of the areas in the countries we do business in. This requires us to set the platform up in a way that language can be configurable by organization, user or location.

New Filtering Experience

We are introducing a new filtering experience on various pages in the platform to provide a more seamless filtering experience. This new version will allow users to more easily apply filters and see what filters are applied currently.

Expanding Service Level Dropoff Speeds

Total Weight Column Added to Dashboard, Delivery, and Orders Pages

OmniPoint users can now view and sort orders/deliveries by their total weight directly in the table views!

What’s New

• Total Weight Column: A new "Total Weight" column has been added to the Dashboard, Delivery, and Orders pages, positioned after the "Service Level" column.
• Sort: Easily sort orders by weight values for faster processing.
• Manage Columns: The "Total Weight" column is available in the "Manage Columns" settings, appearing after "Service Level." It’s disabled by default, giving you the flexibility to enable it when needed.

Updated Route ID Generation

We are updating to our Route ID generation system, designed to eliminate duplicate IDs and enhance reliability. This introduces a new, robust format for Route IDs while maintaining the seamless experience.

What’s New

• New Route ID Format: Route IDs are now generated case-sensitive Base30 string with 3 groups of 5 characters (e.g.,R-1m7k7-sm5fr-8tqdr). This new format ensures unique IDs every time.
• Case Sensitivity: The new Route IDs are case-sensitive to maximize uniqueness and clarity.
• Consistent Prefix: The familiar R- prefix remains, keeping things intuitive.

This update resolves the issue of duplicate Route IDs and sets the stage for continued growth and reliability. We’re confident it will make your experience smoother and more dependable.

Control Tower Enhancements for Shipper + LP Organizations

Updates to the Control Tower for the carrier are coming to now enable shippers to use the newer version of the control tower that is designed to make it easier for Shipper + LP organizations to transition and manage their operations with greater efficiency and clarity. These updates for Shipper + LP organizations will improve usability, streamline data handling, and offer more flexibility for organizations with large datasets.

What’s New

• Location Filtering:
  • Front-End: When selecting a Shipper + LP as the carrier, users can now choose a specific location. Only data relevant to that location (Driver Names, Driver Geo Data, Deliveries/Routes) will populate in the carrier's Control Tower, reducing clutter and improving performance.
  • Back-End: Updated APIs now support location filtering, ensuring a seamless and lightweight data experience, especially for organizations with extensive user geo data.
• Route Selection:
  • Assigned driver pins are now visually distinct from unassigned driver pins when a route is selected, making it easier to identify drivers at a glance.
• Route Status Columns:
  • Organizations can now hide the "No Driver" column and set the "Assigned" column as the default view, customizable at the organization level for a tailored experience.
• Enable Control Tower:
  • Shipper + LP organizations can now access the carrier's Control Tower, with configurable settings at the organization level. This removes previous hardcoded restrictions, offering greater flexibility.

These changes to the carrier's Control Tower provides our shipper customers that have their own internal fleet a more intuitive and efficiently than the legacy Control Tower.

Mobile

New Optimized Sequence View for Multi-Day Routes in the OneRail Driver App

A new view option for routed sequence will be available in the OneRail Driver App (ORD) that enhances delivery sequencing for routes spanning multiple days. Designed with feedback from ORD users, this update ensures drivers can follow the optimized route path with clarity and efficiency, reducing operational confusion when fulfilling routes with deliveries for future dates & times.

What’s New

• Optimized Sequence View: A new view replaces the current date-based delivery list, displaying deliveries in the exact order of the route stop sequence as shown in the LP Control Tower, Control Tower, and Route Details pages.
• Multi-Day Route Support: The view accurately reflects the optimized multi-day route path, including future “Scheduled” deliveries, as determined by OneRail’s routing optimizer.
• Route Stop Numbers: Each delivery now includes its corresponding route stop number for easy reference.
• Organization-Specific Enablement: This view is enabled by organization in the ORD app and is an optional view.

This enhancement aligns the mobile app’s delivery sequencing with the optimized route path, making it easier for ORD users/drivers to navigate complex, multi-day routes.

Mobile Fixes and Improvements

• Ingest Correct Delivery Items Field

• ORD Duplicate Carrier Events Resolution

• Audible alerts when notifications for new deliveries come in

• Phone Number field does not allow/save values in Mobile that Core does

General Fixes and Improvements

• Enhancements to "Delivery Cost Info" Section
• METRICS_DELIVERY_API converting imperial values to incorrect values when not requested
• CX preview does not show POD image on delivered page
• Saved views - Green checkmark sign in front of the view
• New data column for Routes and the Geopath json
• Bug - Saved View does not retain selected pickup location
• Add "Container ID" Column to Table Views
• "An LP could not be found to fulfill the delivery"
• Investigate issues around fetching permissions
• Clicking cancel button behaves as Save button
• Permissions field not filtering correctly
• Support Flexible Input Formats
• Filter Groups-UI
• Routing - Market Hours
• You are unable to edit a Customer location that has a blank name
• Language Selection - CX Pages
• Language Selection - Login Page
• Exclude Functionality/BE
• Exclude Functionality/FE
• Filter Groups-Logic
• Sameday orders aren't reflecting the correct 'before' time
• Packing Container Dimensions - Negatives
• Clicking to Open Delivery in New Tab Automatically Selects the Checkbox
• Differentiate between Complete and Incomplete stops
• Permission names missspelling
• Pass the pickupOpensOn to the happensOn for the "Assigned" Event on Dispatched "Scheduled" Deliveries
• Returns should match original shipperContractSla
• Route - Removing the drop-off stop associated with pick-up removes the remaining route from Control Tower Routes
• Copy/Return Creation Duplicates Veh Line Item
• The network tab is giving out sensitive information
• Use new endpoint for fetching Associated Locations
• Migrate from await-to-js to Native Async/Await Error Handling
• When creating a new order from an existing order, it gives a Validation Error
• Drop-off Location
• Manage Incomplete Organizations
• Unable to add new product
• Add / Edit product
• Disabling the 'Enable Consolidation?' toggle does not deactivate its nested toggles.
• Add Product, Edit Product | Price allows minus amount
• West Marine Load Report isn't showing all Order Ids in route
• Save/Edit a product/description to have a name as a space
• When Typing Shipping Mode For New SLA, Shipping Mode Input Does Not Give Options
• Users page visual defects
• Contract Cancel returns blank contracts list
• Rework to Align Models for Routes & Route Stops to actual present-day meaning and usage
• Fix Event Routing for v1/routes/claim Endpoint
• Load Report showing incorrect route information
• Visual Matches Prod/UAT/Staging - [OneRail] | [Visual test] | [Control Tower/Total Mileages]
• Updating Delivery Attempts for Both Routed and Hot Shot Deliveries
• Org/CX Logo-Favicon Logo Upload
• Order creation forum allows for Item Identifier field to have a name as a space

Client-Specific Fixes and Improvements

• * Only
  
  • Visibility deliveries do not display on LP Control Tower
  • Issue with Leader Delivery Order ID
• ** Only
  • Push-api 400s when attempting to find deliveries with order IDs matching X012345 format
  • Get-rates endpoint should return a specific carrier when that carrier returns an erro