Skip to main content

April 27, 2026 Release Notes, Version 26.05

An overview of new features and bug fixes released on April 27, 2026 for Shipwell version 26.05

S
Written by Shipwell TMS Support

Calendar UI - 25% More Visible

The Scheduling Calendar has been redesigned to put more of your schedule on screen. These changes add up to roughly 25% more visible calendar space. This work prepares the Scheduling Calendar for future enhancements planned later in the 2nd Quarter.

Streamlined Header

The calendar previously had two separate navigation bars stacked at the top of the page. These have been consolidated into a single row, so you spend less time scrolling past controls and more time looking at your appointments.

Collapsible Filter Panel

The filter panel on the left side of the calendar can now be collapsed and reopened with a single click. When collapsed, the calendar expands to fill the full width of your screen. This is especially helpful on TV monitors for teams to track their schedule throughout the day or smaller monitors when you want a wider view of your week.

Fuel Surcharge (FSC) - Freight Carrier Association of Canada

The Freight Carrier Association of Canada (FCA) is a trade association that compiles fuel prices throughout Canada and publishes a composite Fuel Surcharge recommendation on a weekly basis. Shippers and carriers agree to use the weekly published FSC rate and apply this to shipments as a percentage of linehaul costs. An example of the weekly data published by the FCA is shown below.


The fuel surcharge tables in the system have been updated to accommodate the shipper entering the recommended FSC percentage as the new rates are released by the FCA. A new field called Fuel Source has been added where the user can select from the standard source, US Energy Information Administration (EIA) or the Freight Carrier Association of Canada (FCA).

If the FCA option is selected, moving to the Rate Table tab will allow the user to enter the FCA surcharge percentage. The last percentage added is displayed by default, and the user can select the edit icon in order to create a new entry.

Once edit is selected, the user can enter a Start Date, End Date and the fuel surcharge percentage. Note that there is only 1 active FSC percentage that will be applied to all shipments, regardless of ship dates. This is in line with the current US EIA application where future fuel prices are not known. These dates are for historical record keeping purposes.

Once the data is saved, this becomes the active FSC percentage that will be applied to shipments.

To view the historical FSC data, click on the History icon and the past fuel surcharge percentages will be displayed along with the Start Date, and updated by information.

The standard FSC applications apply regardless of Fuel Source, including Recalculating FSC on pickup or delivery if that option is selected.

Swifty Order Planning Assistant: Order “Top-off” on Shipment Pages


Smart Shipment Context Awareness

Swifty now automatically detects when you're viewing a shipment detail page and uses that context to power intelligent order consolidation suggestions. No manual input required. Swifty seamlessly understands which shipment you're viewing and analyzes it for consolidation opportunities.

User benefit: Save time by getting relevant suggestions automatically when viewing any eligible shipment.

Intelligent Shipment Eligibility Filtering

Swifty only surfaces order suggestions for shipments where consolidation is safe and appropriate. The system evaluates each shipment against specific criteria before triggering recommendations.

Eligible shipments must have:

  • Status: Draft, Quoting, Carrier Confirmed, or Tendered

  • No rate confirmation or carrier financials entered yet

  • Equipment type: Dry Van

User benefit: Avoid risky consolidations by only seeing suggestions when it's appropriate to add orders to a shipment.

Order Matching

When viewing an eligible shipment, Swifty automatically identifies compatible open orders using intelligent matching logic that considers:

  • Geographic fit: Pickup and delivery locations align with the shipment's route

  • Time compatibility: Order pickup/delivery times work with the shipment's schedule

  • Capacity analysis: Order weight, volume, and pallet count fit within remaining Dry Van capacity (up to ~45,000 lbs)

  • Pallet count: Up to 26 pallets total (stackable pallets count as 0.5)

  • Equipment matching: Orders compatible with Dry Van equipment

User benefit: See only relevant consolidation candidates ranked by compatibility, eliminating manual searching through order lists.

Streamlined Order Review Interface

Order recommendations now appear directly in the Swifty chat panel with all the details you need to make quick decisions:

  • Order ID (clickable link to full order details)

  • Route: Pickup and delivery locations

  • Timing: Pickup date/time and Delivery date/time

  • Dimensions: Weight and volume

  • Match score: Percentage with plain-language explanation of why this order fits

Example:

User benefit: Evaluate consolidation opportunities without leaving the shipment page.

Quick Order Additions

Act on Swifty's recommendations instantly with the "Add to Shipment" button in the chat panel. A confirmation flow ensures you're in control before any changes are made.

User benefit: Consolidate shipments in seconds instead of navigating through multiple pages and forms.

How It Works

  1. Navigate to a shipment detail page - Swifty automatically detects the shipment context

  2. Eligibility check - Swifty evaluates if the shipment is eligible for consolidation

  3. Smart matching - If eligible, Swifty analyzes open orders and identifies compatible candidates (up to 5 suggestions)

  4. Review recommendations - Compatible orders appear in the chat panel with match scores and key details

  5. Add orders - Click "Add to Shipment" on any recommended order to consolidate

Note: If no compatible orders are found, Swifty remains silent and available for other queries—you won't see "no matches" messages.

Known Limitations

  • Order suggestions are currently limited to Dry Van equipment type only

  • Suggestions cap at 5 orders per shipment to maintain chat readability

  • Geographic matching uses exact location matching; future releases may support flexible detour distance thresholds

  • Only available for shipments in pre-carrier-commitment stages (Draft, Quoting, Carrier Confirmed, Tendered)

API Changes

Fixes

Freight Invoice: charge_code Now Returned Correctly

A bug caused charge_code to be silently dropped from charge_line_items in freight invoice responses. This has been resolved — charge_code is now correctly returned on POST /invoicing/shipments/{shipmentId}/freight-invoices/ responses.


What's New

Barge / Ocean Timeline Event Types

Five new event_type values are now supported on shipment timeline events for ocean and barge tracking:

Value

Meaning

ARRIVED_BARGE

Barge has arrived

BERTHED

Barge has berthed at port

LOADED_BARGE

Cargo loaded onto barge

DEPARTED_BARGE

Barge has departed

DISCHARGED_BARGE

Cargo discharged from barge

These values may appear in timeline_events[].event_type responses across all shipment-related endpoints. If your integration performs exhaustive enum validation on event_type, add these values to avoid parse errors.

Affected endpoints: GET/POST /shipments/, GET /shipments/{shipmentId}/, shipment pickups, spot negotiations, purchase order build/update, and carrier power unit shipment lists.

Description

VLTL Rating issue and Dispatch Error

ESTES Direct Guaranteed Rates Not Populating

CH Robinson LTL Integration - Missing FedEx Service Types

LTL: Direct ESTES request omits shipment-level total weight (only handling-unit weights sent) → downstream weight not displayed

CH Robinson API

Parcel Quoting - "Get Quotes" Action Failing without Error

Estes Direct API: GUARANTEED accessorial causes "Failed to Quote" error instead of graceful handling

Direct Estes Dispatch Error

Charge Code showing null

Carrier Assignment Failure & Shipment Data Corruption

Tracking Issue - Shipment changed to DELIVERED, but hasn't yet arrived at pickup location

[Samsara] Actual Arrival Date is showing a future date & time

VDS shipments are not dispatching

Remove Luciq shake-to-report SDK

FrontEnd: Driver does not have mobile app installed" alert persists after driver installs app

Error when using Delivery Address filter on Shipments Dashboard

XPO: Add Support for GCD (Grocery Consolidation Delivery) Accessorial Code

Invoice Matching Issue with N9 Segment – Inconsistent Processing

Carrier Contact: Cannot re-send Load Board invite email after initial invite sent

Estimated Port of Loading Departure displays Port ETA instead of origin ETD on FCL/Drayage shipment details

SFTP order import shows planning dates 5 hours late (double timezone conversion)

Shipment detail page inaccessible - serialization crash for Drayage shipment

Activity Log Hover Over text is expanding outside the hover-over window

Activity Log shows exception rows for shipments that don't have carriers assigned

Order # Links Not Working in Load Optimizer Load Plan page

Internal Override Contact Not Respected for Approval Emails. Still being sent to users on shipments.

Outreach Sent to Carrier Not in Carrier Selected List and Without Carrier Contacts

Activity Log "Worker" column not abiding by custom Worker Name

Twilio Text/SMS communication channel went down for Shipwell

Shipment declared value was not adding up correctly when line items were grouped into combined handling units.

Carrier users were unable to save changes to shipment stops because the system required planning window fields that were greyed out and not editable by carriers.

After using the bulk action to update pickup and delivery dates, the times on stops were showing in the wrong time zone.

An order could not be added to a shipment due to a stale stop reference in the shipment data.

Adding orders to an existing shipment was failing during stop consolidation.

Estimated and actual delivery dates were not showing up on the NetSuite shipment record after carrier tracking updates.

Custom field mappings in the NetSuite SuiteApp were being overwritten with default values instead of using the configured mapping.

The shipment assembly service experienced a database performance issue caused by unoptimized queries running at the same time.

An error occurred when processing shipments where stop custom data fields had missing values.

Date columns on the v3 Orders list are now sortable by pickup and delivery dates.

Users can now select and download orders from the v3 Orders dashboard as a CSV file.

Did this answer your question?