🚀 Releases

6.2.1 - 02/12/25

Integrations

Carrier Shipper Credentials for a Specific Client

Update to carrier integration to allow deliveries for a specific client.

Missing Contact Name

Update to our platform service to mitigate an issue with some carriers not accepting deliveries when the shipper does not provide a contact name.

Specific Carrier as a Dynamic LP

Add the ability for the LP Team to leverage a specific carrier as a dynamic LP.

Specific Carrier Marketplace

Enable a carrier-specific marketplace to send deliveries to the OneRail platform and receive events. This functionality will be available for testing in UAT and disabled in production until testing is completed.

Enable New Client-Specific Markets for Events

Provide the ability for a specific client to receive events for the Boston, Memphis and Boca Raton markets.

Client-Specific Origin Store Number Enhancement

A specific client requested the ability to display Origin Store Number in all events coming from OneRail. This will be flagged and turned off in Production until approved by the client in UAT.

Client-Specific Isolation of a Specific Carrier

A specific client has requested to only allow a sole, specific carrier.

WM Parcel Pick Up Window Adjustments

Adjustment to allow parcel to shop rates from dispatch date for specific carriers.

General Fixes and Improvements

• Use contact info on delivery
• LP Contracts - Not found for adding SLA, submitting contracts
• Dwell Time exceptions being added despite attempts to add an event to the timeline getting thrown out
• PUT request to routes endpoint are failing for new route with existing orders
• Client-specific item parameters being under 1lb fails to edit delivery
• Truncate Trailing Decimals
• Update logic to group deliveries by date based on when the delivery needs to be delivered

6.1.2 - 01/29/25

Core

Update Manual Order Forms to Allow Any Service-Level to use Delivery Windows

We are introducing a new enhancement to both the manual order forms and our APIs to address a key issue related to delivery window accuracy. Currently, some logistics service providers (LSPs) would prefer to have deliveries dispatched to them a day in advance. While our system supports Delivery Windows, allowing users to schedule future pickups, we’ve found that the defined windows don't always align with the desired service level—such as meeting a 90-minute window for delivery.

To resolve this, we are implementing a "Pickup Window" feature that will automatically calculate the corresponding "Delivery Window" based on the selected service level.

Key Improvements:

• Pickup Window Definition: Users can now define a specific Pickup Window, and the system will automatically calculate the appropriate Dropoff Window.
• Service Level Alignment: This ensures that the dispatch windows meet the required service levels, such as a 90-minute window or any other defined timeframe.
• Operational Efficiency: By streamlining this process, OneRail can dispatch orders more efficiently to LSPs, improving overall operational effectiveness.

This enhancement helps ensure that service-level agreements are met consistently, providing more accurate scheduling and reducing the risk of misaligned delivery times.

Mobile

Mobile Fixes and Improvements

• Do Not Combine Non-Consecutive Pickup Stops
• Duplicate scans bug
• Changes in ORD Edit profile screen to include new service end point

Integrations

Client-Specific Carrier Label Updates

Fix to update a carrier's label for a specific client to list Name as the first data on the label for destination.

Client-Specific Carrier Residential Ground Service Level Enablement

Fix to ensure Ground service for a specific carrier is rate shopped correctly for residential deliveries.

General Fixes and Improvements

• LP Name not being masked
• Notes field character limit causes rejection without reason
• durationMin calculating on Delivered event received time
• Creating a simplified delivery details webpage for Non-ORD LSPs
• Generate URL for Delivery Details Lite webpage containing Barcodes
• Shipper and LP cannot access external route details
• Leader/Follower OrderID and Record Display (list page)
• Orders assigned to a specific LP using ‘Dispatch Immediately’ after location is closed ignores user selection

Client-Specific Fixes and Improvements

• *** Only
  • Carrier Issue - Street Lines Too Long
• ***** Only
  • Ensure routed event is triggered for all orders in client's route updates

6.1.1 - 01/15/25

Mobile

• Client-specific visibility deliveries not displayed on the driver screen after driver claims a delivery

General Fixes and Improvements

• Resolve dispatch errors by ensuring accurate line item weight for deliveries
• Enhance fleet flexibility for multi-location market coverage
• Geo events applying to re-routed deliveries
• Multi-Pickup routing utilizing multiple vehicles

Client-Specific Fixes and Improvements

• *** Only
  • Add Liftgate Accessorials for a client-specific brand's ordersss
• ******* Only
  • Delivery Details enhancement
  • Ops API Location Endpoints
• ******** Only
  • Modify CREATE_DELIVERY Payload to Include Additional Fields

⏱️Coming Soon

Core

Foreign Currency

As part of Internationalization, we must implement Foreign Currency support to cater to new markets. It is essential that our platform is capable of handling multiple types of currency as per the region that it caters to. We are adding a configuration option for currency at both the organization and location levels so that the setting can be inherited by the associated locations and users, respectively.

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 "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.

CX By Service Level

Currently the CX management interface is only configurable by status. This is a limitation for our shippers because shippers want the ability to provide specific CX notifications for a specific service level. This is another step towards allowing customers to configure CX to better fit their needs. When this goes live, it will also be applied to previous service levels so all CX notifications currently configured in the platform will default to all under the Service Level selection.

Mobile

Mobile Fixes and Enhancements

• Not valid role error during login for client-specific builds
• Unable to cancel deliveries in a route
• Newly assigned delivery on the top left corner menu list button not displaying
• Changes in ORD Edit profile screen to include new service end point
• New backend service that allows a driver user to edit their own profile data
• Newly assigned delivery on the top left corner menu list button not displaying
• Client-specific ability to see the newly scanned delivery from the Control Tower on the Driver dashboard
• Show Quantities for Service Accessorials
• Display URL for Delivery Details Lite webpage in ORD
• Add alternate location accounting for stop consolidation

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
• Updates to Delivery Details Page
• Geo-Ping Not Updating PickupETA on Subsequent Triggers
• When I refresh the page, I can not see the green checkmark sign in front of the view
• Save RouteCost data to new data points
• New data column for Routes and the Geopath json
• Update Error Handling Message When User Already Exists
• Bug - Saved View does not retain selected pickup location
• Display Drivers current location on the Route Details Map
• Route CSV Pre-Check Validation
• Add "Container ID" Column to Table Views
• Scheduled Dispatch Enhancement to Account for Timezone
• Update Logic to Group Deliveries by Date Based on When the Delivery Needs to be Delivered
• Required front end fields should be required API fields
• Bug - Scheduled Deliveries - Editing a delivery
• Fix windows payload for "Pickup window" feature
• Merge Carrier DeliveryDetail Component[s]
• Route Details - Estimated Time Completed
• Ability to search on the "Organizations" page
• Do Not Combine Non-Consecutive Pickup Stops
• Switch to Trimble map
• Mitigate Duplicate State Changes in Delivery Attempts
• Enhance Tracking of Failure Reasons in Delivery Attempts
• Ability to search on Users page
• Dispatch errors from LPs when deliveries with containers are sent
• Return delivery displays all items from all order's deliveries
• Copied deliveries display duplicate items on both Control Tower pages
• Add alternate locations to Routes response
• Mismatch in mileage data between LP and OR user views
• Exclude deliveries that are using customer defined "Delivery Windows" from recalculation on dispatch
• Precise weight not passed to FE
• When an LP cancels, we no longer automatically add exceptions
• Operations throwing 404's when attempting to fetch driver-location
• Returns - "An LP could not be found to fulfill the delivery"
• Investigate issues around fetching permissions
• 'Delivery Date/Time' column displaying last received event
• One way street routes shown on Delivery Details map are reversed
• Handle EOD time zones when generating delivery windows
• Display driver's current location on the Route Details page
• Display driver's current location on the Control Tower page
• Hyperlink Route ID to Route Details page

Client-Specific Fixes and Improvements

• * Only
  • Ability to configure CX by Service Level
  • Visibility deliveries do not display on LP Control Tower
  • Issue with Leader Delivery Order ID
  • Create subdomain for a client-specific CX
• ** Only
  • Add "Driver Name" Column to Table Views
  • Add "Distance" Column to Table Views
  • Push-api 400s when attempting to find deliveries with order IDs matching X012345 format