Skip to main content

March 16th, 2026 Release Notes, Version 26.03

An overview of new features and bug fixes released on March 16th, 2026 for Shipwell version 26.03

S
Written by Shipwell TMS Support
Updated over 2 weeks ago

Product Category on Order Line Items

Shipwell now supports product category on order line items and automatically carries that value through to the associated shipment. You no longer need to set product category manually on the shipment - it is populated from the order and its line items when an order is created, updated, or linked to a shipment.

  1. Product category is now a supported field on order line items. You can assign a product category directly to each line item within a v3 order.

  2. Product category is synced automatically from orders to their associated shipments in the following scenarios:

    • A v3 order with a product category is created and converted into a shipment

    • A v3 order is added to an existing shipment

    • A v3 order with a product category is updated while linked to a shipment

    • A v3 order is removed from a shipment

v2 Order Bulk Update Pickup/Delivery Times

Users can now update pickup and delivery dates and times for multiple orders at once directly from the Orders screen - no need to open each order individually on v2 orders. This feature was previously available for v3 orders and is now supported for v2 orders, giving v2 customers the same efficiency as they transition to v3.

How It Works

  1. Navigate to the Orders screen (v2).

  2. Select multiple orders using the checkboxes.

  3. Choose the Bulk Update action.

  4. Set the desired pickup and/or delivery dates and times.

  5. Apply - all selected orders are updated in one step.

Customers managing high volumes of orders who need to reschedule or adjust planned dates across multiple orders without editing each one manually.

Notes

  • Available on the v2 Orders screen.

  • Both pickup and delivery dates/times have to be updated simultaneously.

  • No changes to existing integrations or APIs.

Distance & Drive Time Between Stops

Shipwell now displays driving distance and drive time between consecutive stops on over-the-road shipments based on the distance provider service used. This gives dispatchers and planners instant visibility into leg-by-leg travel information without leaving the shipment creation, detail, or summary views - making driver assignment and appointment scheduling faster and more informed. We will be incorporating drive time and HOS calculations in appointment setting and planning windows in a later release.

Distance and drive time pills now appear between each stop on over the road shipments (FTL, LTL, Parcel, and Drayage).

Each pill shows:

  • Driving distance (miles or kilometers based on user unit preference)

  • Estimated drive time for that leg based on the distance and route provided by the distance service configured for the customer. (e.g. PC Miler version 3X versus HERE Maps versus Rand McNally)

Hovering over a pill displays a tooltip with full segment detail.

The pills are visible in the following areas for land shipment modes:

  1. Shipment detail: Stops section

2. Dashboard Shipment Summary

3. New Shipment Creation Page

Rearranging stops on the shipment detail page or shipment creation page will re-run the distance and travel time calculation.

Notes

  • Stops with incomplete or missing addresses will gracefully skip the pill with no gap or error shown.

  • Users configured for metric units will see distances in kilometers (km). All other users will see miles (mi). This respects existing account-level unit settings with no additional configuration required.

  • Distance and travel time pills do not appear on air, ocean, or rail shipments, as routing distance is not available for those modes yet.

  • Stop appointment dates and times now display in MM/DD/YYYY HH:mm (24-hour) format, correcting a previous DD/MM/YYYY display issue.

  • If your distance service is interrupted (e.g. Rand McNally isn’t available or doesn’t return a route we will not display a distance or drive time)

User and Company Level Unit Setting

Shipwell now supports a user-level preference for displaying units in either Imperial or Metric units. Users can set their own preference, and company admins can establish a company-wide default. Once set, the chosen unit system is reflected consistently across shipment pages, order pages,
and all associated side panels - no manual conversion required.

WHAT CHANGES WITH YOUR SETTING

The chosen unit system applies consistently across:

Type

Imperial

Metric

Weight

lb/lbs, ton

kg

Dimensions

in/ft

cm/m

Volume

ft3/gal

m3/L

Temperature

°F

°C

Distance

mi

km

Measurements are displayed in the selected unit across all tables, forms, tooltips, and side panels on affected pages. Mixed-unit display on the same page is not supported. If the unit preference is unavailable, the system defaults to Imperial.

SETTING YOUR UNIT PREFERENCE

A single "Default Units" field (Imperial / Metric) is now available in two places:

Company Profile (Manage → Company)

  • Visible and editable by company admins only

  • Sets the company-wide default for all new users

  • Defaults to Imperial

User Preferences (Manage → Users)

  • Available to all users

  • Each user can override the company default for themselves

  • New users inherit the company-level setting at account creation

PAGES UPDATED

The unit preference is now reflected on the following shipment pages:

  • New Shipment Dashboard (including side panel)

  • New Shipment Creation page

  • Shipment Detail page — View, Edit (including side panel)

  • Order Dashboard (v3, including side panel)

  • Order Detail pages — Create, View, Edit (v3, including side panel)

Notes

  • A single "Default Units" field controls all measurement types. There are no separate fields for weight, dimensions, volume, or temperature.

  • The country settings field has been removed from the Manage → Company page. Currencies are managed through: International Configuration:

  • The platform and related pages contain many different fields. There is the possibility that during this enablement, we have missed some. Please let us know if you find any.

Multiple Order Stop Consolidation Strategy

We've improved how Shipwell consolidates orders into shipments when those orders share the same pickup and delivery addresses but have different scheduled dates or times.

Previously, adding multiple orders with different dates to a single shipment would create duplicate stops when the pickup or delivery times were different for each order, even when the
addresses were identical. For example, 3 orders all going from Warehouse X to Store Y would result in 6 stops instead of 2, causing confusion for dispatchers, drivers, and carriers.

Scenario:

  • Customer has 3 orders (Order A, B, C)

  • All orders: Pickup from Warehouse X, Deliver to Store Y

  • Order A: Pickup date 2026-01-22

  • Order B: Pickup date 2026-01-23

  • Order C: Pickup date 2026-01-24

Current Result (Problematic):

Shipment #12345: Stop 1: Warehouse X (Pickup) - 2026-01-22 [Order A] Stop 2: Warehouse X (Pickup) - 2026-01-23 [Order B] <- DUPLICATE ADDRESS Stop 3: Warehouse X (Pickup) - 2026-01-24 [Order C] <- DUPLICATE ADDRESS Stop 4: Store Y (Delivery) - 2026-01-22 [Order A] Stop 5: Store Y (Delivery) - 2026-01-23 [Order B] <- DUPLICATE ADDRESS Stop 6: Store Y (Delivery) - 2026-01-24 [Order C] <- DUPLICATE ADDRESS

Consolidation Strategy Latest Turned On:

Shipment #12345: Stop 1: Warehouse X (Pickup) - 2026-01-24 [Order A, B, C] <- Consolidated orders/stops Stop 2: Store Y (Delivery) - 2026-01-24 [Order A, B, C] <- Consolidated orders/stops

Stop Consolidation Strategy - Three Options

Customers can now choose how orders with the same address but different date/times are handled when creating a shipment manually:

  1. SEPARATE (Default): Orders with different date/times create separate stops. This is the existing behavior and remains the default.

  2. LATEST: All orders at the same address are consolidated into a single stop using the latest scheduled date/time across those orders.

  3. EARLIEST: All orders at the same address are consolidated into a single stop using the earliest scheduled date/time across those orders.

How to Setup

Admins can now configure a default Stop Consolidation Strategy at the company/tenant level via Company Preferences. This setting applies automatically whenever orders are consolidated into shipments, eliminating the need to manually select a strategy each time.

  • New field: stop_consolidation_strategy in Company Preferences

  • Available via the Company Preferences API (read/update)

  • Default for all existing companies: SEPARATE (no change
    to current behavior)

To configure your company's default stop consolidation strategy:

  1. Navigate to Company Preferences (Admin settings)

2. Locate the "Stop Consolidation Strategy" field

3. Select SEPARATE, LATEST, or EARLIEST

4. Save changes

The consolidation strategy selector has been added to all relevant order management screens :

  • Create Shipment Flow: A consolidation strategy selector (LATEST / EARLIEST / SEPARATE) is now shown when creating a shipment from orders. It defaults to the company setting.

  • Update Order Flow: Changing an order on a shipment re-runs consolidation logic using the company default strategy.

  • Remove Order Flow: Removing an order re-runs consolidation logic using the company default strategy.

  • Modify Orders Screen: The consolidation strategy field is now available when modifying orders on an existing shipment.

BENEFIT TO CUSTOMERS

  • Eliminates duplicate stops on shipments when consolidating orders that share the same locations but have different dates.

  • Reduces operational confusion for dispatchers and drivers.

  • Gives companies the flexibility to set a default consolidation behavior that matches their operational workflows.

Notes

  • Existing companies default to SEPARATE - no change in behavior until the setting is explicitly updated.

  • This setting is configurable per company/tenant and can be updated via the Company Preferences API.

Track & Trace AI Worker Enhancements

These are "Quality of Life" improvements across the AI Studio. We’ve streamlined the Track & Trace configuration workflow, improved data visibility in the Activity Logs, and refined the Worker management interface to ensure a smoother administrative experience.

AI Studio Workers Page

Updates to the primary worker overview page.

  • Logic Correction for Monitoring: Fixed a data discrepancy where the "Monitored" count would occasionally display as zero or less than the "Exceptions" count. This ensures the monitoring bucket accurately reflects the total volume of shipments being monitored.

  • Connection Controls: Resolved an issue with the Track & Trace Card connect/disconnect toggle for more responsive control.

  • Tenant Clean-up: Removed the "Purchase Agent" flow for net-new configuration tenants to simplify the onboarding path.

Track & Trace Configuration Page

Refinements to the setup and management workflow.

  • Smart Defaults: Applied preset values for required fields to speed up the configuration process.

  • Global Naming: Updating a Worker Name now propagates automatically across all relevant fields and displays.

  • Enhanced UX Components: * Improved the Search/Select flow for the Carrier Card.

    • Optimized day selection within the Time Window card.

    • Reordered the Communication Card for a more logical setup sequence.

  • Clearer Guidance: Added descriptive text to the Agent User Account and Verify Changes sections to provide better context for admins. Refined the description logic for the Communication Priority card

  • Streamlined Permissions: Removed the unnecessary view.driver requirement for Agent User Accounts. The remaining permissions can be configured on the User Management page. (view.company, view.shipment, update.shipment)

  • Action Logic: Adjusted the "Save" button behavior.

AI Studio Activity Log

Improvements to the activity log and exception tracking.

  • Direct Navigation: Added a direct link to the Shipment Details Page from individual Activity Log rows, allowing for faster troubleshooting.

  • Filter Precision: Resolved an issue where the "Failed" status filter would occasionally include successful rows. Filtering for "Failed" now exclusively returns rows containing the "Failed" label.

Address Book Table and View Improvements

The Address Book has been refreshed with a modernized layout that improves usability, organization, and visual clarity. Updates span both the list view and the detail/edit view, making it easier to manage, find, and update saved addresses.

  1. List View Improvements

    • New columns: "External Reference" now appears alongside Company Name, and "Created" and "Updated" date columns are visible in the list for quick reference.

    • Sortable by date: The Created and Updated columns are sortable - ascending order shows oldest entries first, descending shows newest first.

    • Improved Actions menu: The Actions column now displays a 3-dot overflow menu (replacing the previous trash icon), with clearly labeled Edit and Delete options.

    • Safer deletions: Clicking Delete opens a confirmation modal before removing an address. On success, the modal closes and the list refreshes automatically. On failure, an error is shown and the modal stays open so you can retry without losing your place.

  2. Detail / Edit View Improvements

    • Map display: The map now renders as a square that fills the right column and stays sticky while you scroll through the form - keeping the location in view at all times.

    • Accurate map pins: Addresses located at 0° latitude or 0° longitude (equator or prime meridian) now correctly display a pin on the map.

    • Schedule visibility: The Schedule card is shown when the form is active and the user has update permissions. It is automatically hidden for addresses linked to a dock-scheduling facility.

    • Contacts card: The Contacts section is always visible and clearly labeled "Contacts."

    • Save confirmation: A success toast notification appears in the top-right corner after saving changes to an address.

Auto-Populate Freight Class in Handling Unit Builder and Orders

When building handling units in Shipwell, users currently must manually select or enter a freight class. This update will automatically calculate and populate the freight class field based on the pallets line item details - reducing manual entry and the risk of incorrect freight class selection.

  1. Automatic Freight Class Calculation

    The Handling Unit Builder will now auto-populate the freight class field based on the dimensions and weight of the line items entered. This is consistent with the existing behavior on the New Quote flow, where freight class is already calculated automatically. Users will no longer need to manually look up or enter a freight class - the system will suggest the correct class as line item details are filled in.

  2. Consistent Experience Across Flows

    This change brings the Handling Unit Builder in line with the quoting experience, where auto-population of freight class is already supported. Customers building handling units will now have the same streamlined workflow.

Order Entry

Handling Unit Builder

Edit Line Items/Shipment Line Items

New Quote

API Changes

Added Shipment delivery_date Support

We added support for an optional delivery_date field across multiple Shipment-related APIs.

What’s new

  • delivery_date can now be included when creating or updating shipments.

  • The field is now returned in responses across multiple shipment-related endpoints.

Affected endpoints include

  • POST /shipments/

  • PUT /shipments/{shipmentId}/

  • GET /shipments/

  • GET /shipments/{shipmentId}/

  • PUT /shipments/{shipmentId}/add-orders/

  • PUT /shipments/pickups/{shipmentPickupId}/

  • Spot negotiation shipment endpoints

  • Shipment pickup endpoints

  • Carrier power unit shipment endpoints

  • Purchase order shipment build/update endpoints

Impact

  • Backward compatible. The field is optional and existing integrations will continue to work without modification.


Added order_mappings Support for Shipments

We introduced a new optional order_mappings property for shipment-related APIs to support mapping orders within shipment payloads.

What’s new

  • order_mappings can now be passed in requests when creating or updating shipments.

  • The property is also available in responses for shipment-related endpoints.

Affected endpoints include

  • POST /shipments/

  • PUT /shipments/{shipmentId}/

  • PUT /shipments/{shipmentId}/add-orders/

  • Shipment quoting and negotiation endpoints

  • Purchase order shipment build/update endpoints

  • Shipment retrieval endpoints

Impact

  • Backward compatible. The property is optional and will not affect existing integrations.


Added consolidation_strategy to Add Orders Endpoint

A new optional request parameter was added to support order consolidation behavior.

Endpoint

  • PUT /shipments/{shipmentId}/add-orders/

New parameter

  • consolidation_strategy (optional)

Impact

  • Backward compatible.


Distance API Response Units Updated

We updated the response format for the distance calculation endpoint.

Endpoint

  • POST /locations/distance/

Changes

  • Removed:

    • distance_meters

    • duration_seconds

  • Added:

    • distance_miles

    • duration_minutes


New Shipment Round Trip Job Response Fields

Additional response details were added for the round-trip shipment job endpoint.

Endpoint

  • GET /shipments/round-trip-job/{roundTripJobId}

New fields

  • not_updated_shipment_details
    not_updated_shipment_details[].reference_id

Impact

  • Backward compatible.


New Corrogo Release Outbox Endpoints

Two new endpoints were introduced to support Corrogo release outbox access.

New endpoints

  • GET /shipments/corrogo-release-outbox/

  • GET /shipments/corrogo-release-outbox/{corrogoReleaseOutboxId}/


Summary

  • Added shipment delivery_date support across APIs

  • Added order_mappings for shipment-order relationships
    Added consolidation_strategy to shipment order additions
    Updated distance API response units

  • Added new round-trip job response fields

  • Introduced Corrogo release outbox endpoints

Description

Incorrect Average Spend Data Displayed in RFP Automation

Recognize TON weight units on shipments

CH Robinson duplicate items for return trips

Carrier Accounts - Allow an account to encompass all shipments

Unable to tender to LTL carriers in the instant rates

Shipment Equipment Type Changes After Tendering to WWEX Group/GlobalTranz (Flatbed → Dry Van)

UPS account generating error, "reference key already taken" and will not save

XPO Web/Pre Pro Number Does Not Generate

Incorrect Fuel Calculation

Shipments Disappearing After Tendering

Issue: 214 Status and Appointment Times Not Updating for all carriers

Tive Tracker data not showing in Shipwell

Stop Times duplicating on MacroPoint shipments

Mobile App mismatch with UI and current location error

Create Round Trips Bulk Action failing

Shipment Dashboard error when clicking on "Shipment Status"

ELD Power Unit sync Refinments

Add 10 Specialized Equipment Types (part 2)

Shipment is showing all phone #'s on each stop

Update the "Request Bids" Modal, remove the “message” component as this is a redundant field to the “preview email” button and remove the “Send to Shipwell Carrier Network” checkbox, as we no longer use Shipwell Logistics.

Shipment Details Action Panel: When the user clicks "Request Bids."

Shipment Dashboard Right-Side Details Panel: When the user clicks overflow button (⋮) → “Request Bids”

Shipment Creation Action Button: When the user clicks “Request Bids”

Send the supplier information when creating an order on the new order form as supplierWhen users create a Purchase Order and select a supplier from the dropdown, we're only capturing the supplier's name and ID. We're not capturing their email address and other contact details, even though this information is available in our system.

Unexpected Settlement Status Changes for Califia Farms

Incorrect Financial Tally and Variance Reporting on Partial Payments The Shipwell platform is incorrectly calculating the "Difference" tally for shipments with multiple invoices. When an initial invoice is marked as Paid, the system does not subtract that amount from the "Expected" cost summary. Consequently, when a second invoice is received for a remaining balance, the system reports a massive variance as if the first payment never occurred.

Template Dashboard: Table does not update after editing template settings without a full page refresh. When editing a template's settings via the "Edit Settings" modal on the Template Dashboard (Manage > Templates), saving the changes does not update the table row in place. The user must perform a full page refresh to see the updated data reflected in the table, which creates a confusing and misleading experience.

Give T&T Worker ability to update multiple stop times from one update communication

Worker Name field is currently being set across all tenants

Fix issue preventing automated Langgraph deployments

Investigate T&T SMS not sending

Investigate Swifty carrier filtering issue.

Stop the front-end UI from repeating the shipment creation loading icon

Load Optimization Drive time calculation fix

Did this answer your question?