Skip to main content
All CollectionsRelease Notes2025
January 9th, 2025 Release Notes, Version 24.25 & 24.26
January 9th, 2025 Release Notes, Version 24.25 & 24.26

An overview of new features and bug fixes released on January 9th, 2025 for Shipwell version 24.25 & 24.26

S
Written by Shipwell TMS Support
Updated over 3 weeks ago

Support Order Releases for New Order Framework

Shipwell’s new order framework now supports multi-leveled order releases so that users can create a release off of an existing order. Further, they can create a release off of a released order. This provides the flexibility if users need to split orders onto different shipments whether because of capacity or availability of products being shipped.

Steps to create an order release

  1. Go into the order that you want to create a release and select Actions → Create Order Releases

  2. Modal populates with predefaulted pickup dates and address based off released order along with line items available.

  3. Make any modifications as needed and press ‘Save’

  4. New order release is created with a ‘-1’ appended to the Order Number. If a second release is done off the original order, then a ‘-2’ will be appended and so on. Note you can also create an additional release off of this current order and in this case it would create a KRJ9934T1-1-1 where it adds another ‘-1’ appended.

    Order releases will better support your users in managing and planning their freight appropriately.

Mixture Rules for Optimization

Shipwell’s load optimization supports leveraging mixture rules that can allow users to indicate criteria to be used in planning which orders can or cannot be planned with other orders to create shipping routes.

Mixture rules can only be leveraged if customers are using the new order framework that includes order tags. These order tags are used in identifying which orders can go with each other. This is done under the section ‘Logical Constraints' within the optimization rule creation.

Mixture rules can currently identify whether an ‘Order’ must go by itself and this is selected by choosing the mixture rule of ‘Individually’. Customers can also identify which orders do NOT go with other orders using the ‘Not With’ rule. For each of these rules you can identify one or multiple order tags for this rule.

When optimization is performed it will use all the mixture rules identified in the optimization configuration chosen.

Swifty Non-managed Freight Booking

Shipwell Dock Scheduling clients can save time by leveraging Swifty to seamlessly let suppliers or carriers book appointments for non-managed freight. The goal is to let Swifty book these appointments with no need to have a person in the loop. This allows your team to save time by not having to be on the lookout for emails or pickup phone calls while still managing to ensure your dock staff has the insights they need. Plus Swifty can do this work for you 24/7/365.

This gives the ability to do the following via Swifty

  1. Create an Appointment and Date/Time is Available

  2. Create an Appointment but Date/Time is NOT Available

  3. Cancel an Appointment

  4. Reschedule My Appointment and Date/Time is Available

  5. Reschedule My Appointment but Date/Time is NOT Available

  6. List Appointments

API Changes

  • Address Book / Locations

  • Contracts

    • Added new distance property to Contract and Contract Lane.

      • distance is a decimal value that represents the value part of a distance combined with a distance_unit (MILE or KILOMETER). For example, if distance is 123.45 and the distance_unit is MILE so this is 123.45 miles in the contract or contract lane. This distance and the distance_unit are used in charge line item calculations.

    • Added support for new stop charge currency codes (with continued support for "USD" and "CAD"):

      • "CNY" - Chinese Yuan

      • "EUR" - Euro

      • "MXN" - Mexican Peso

  • Events

    • Added shipment.document.created and shipment.document.updated events.

      • These events are also available as events that may be subscribed to through webhooks.

  • Orders (Modern/Next Gen)

    • Added new optional ADDRESS_BOOK_ENTRY_IDand ADDRESS_BOOK_ENTRY_REFERENCE_ID qualifier options to the available references in the order stops of ship_to and ship_from. When you provide a valid ADDRESS_BOOK_ENTRY_IDor ADDRESS_BOOK_ENTRY_REFERENCE_IDduring order creation or update, the system will automatically use the specified address book entry, eliminating the need to enter additional shipping details. If both of these address book entry-related properties are specified, the system will use the ADDRESS_BOOK_ENTRY_ID over the ADDRESS_BOOK_ENTRY_REFERENCE_ID.

    • Added new optional properties to order-level shipping_requirements:

      • non_managed_freight

      • required_delivery_date

      • ship_by_date

    • Added new optional querystring params to Orders (Modern/Next Gen) list/query endpoint to determine if order(s) match or do not match certain order tags.

      • tags__id__all

      • tags__id__not_all

      • tags__id__in

      • tags__id__not_in

      • tags__slug__all

      • tags__slug__not_all

      • tags__slug__in

      • tags__slug__not_in

  • Shipments

Data Science/Analytics Model Updates

  • Real-time update

    • Analytics based on star schema should be a max of 15 minutes delayed (most likely ~5)

  • Data Share Additions

    • Internal notes to Star Schema as DIM_SHIPMENT_NOTE

      • Company_id

      • Created_at

      • Creator_id

      • Deleted_at

      • Dim_shipment_detail_key

      • Id

      • Is_pinned

      • Message

      • Note_creator_name

      • Shipment_id

      • Shipment_note_key

      • updated_at

    • Length Unit and Volume Cu Ft added to Star Schema on DIM_ORDER_LINEITEM

    • Add shipment bill-to data into Star Schema as DIM_SHIPMENT_BILL_TO

      • Billing_id

      • Company_address

      • Company_name

      • contact _email

      • Contact_phone

      • Created_at

      • Dim_shipment_detail_key

      • Direction

      • Shipment_bill_to_key

      • Updated_at

    • Audited Data Share Create/Update scripts

    • Shipwell_data_model now gets fully refreshed every 15 min and on Weekends

  • Builder User Additions

    • Report on a shipment’s sequence stop on a single row using columns for stops 1-4. For example, on a shipment with 4 stops the report would show one row for that shipment and each stop as a column. Previously it listed these stops as additional rows duplicating on the shipment.

      • Stop 1

      • Stop 2

      • Stop 3

      • Stop 4

    • Hardcoded measures that are commonly used in custom measures by report builders to increase performance. The custom measures are providing a list of unique values for that row.

      • Order_number_list

      • Lineitem_description_list

      • Tag_name_list

    • Added fields to dim_order_lineitem

      • Lineitem dimension string as “dimension”

Other Minor Bug and Enhancements

Bug or Enhancement

Description

Bug

backend-core authentication middleware input sanitization for X-Company-ID http header (uncaught ValidationError: ['“badvalue” is not a valid UUID.'] should be a 400 bad request)

Feature Request

Expose SHIPMENT_DOCUMENT_UPDATED webhook

Feature Request

Expose SHIPMENT_DOCUMENT_CREATED webhook

Feature Request

[DevDocs] Document shipment.document.created and shipment.document.updated events

Story

Add the 'Currency of Record' to be present in the Shipment Details page and allow editing under certain criteria

Story

QA Automation- Not Delivered Invoice

Story

Create a By Handling Unit configuration for Template Builder for document generation

Bug

BOL Autogenerates without having the "Trigger Events" enabled and overrides BOL #

Story

Dock Scheduling Calendar UI viewing updates

Story

Remove Restriction on Booking Party to Edit/Delete Shipment Documents

Story

Add a Release option for releasing an order even for non-supplier accessible orders (new/v3)

Bug

Dock Scheduling cards have text running over sometimes

Bug

Line Items Falling off of PO after successfully syncing to Shipwell from Netsuite

Story

Create an 'AND' filter for order lists tags to be used by order (new/v3) FE

Bug

UI updates to order when assigned on shipment latency

Story

Update shipment assembly endpoints to pass in order tag information

Story

Pass in tag information within shipment assembly

Story

Implement an optional or required Bill-To information in Shipment Creation

Story

Restrict carrier from modifying Invoice that is in Approved status when feature flag active

Story

Shipment Dashboard - Include Total Pallet Quantity Column

Bug

Settlements: The requested resource was not found on this server.

Story

Create script to enter Billing ID and Bill To Information on Shipment Creation

Story

Add in user's auto add tags to new shipments within the new shipment creation page

Story

When a user selects 'Save' for saving a dashboard then we should have a toast that confirms the settings have been saved

Story

Update New Shipment Creation Form (New) to Support Leveraging Only Having the Primary Point of Contact for Dock Scheduling Facility Addresses

Story

[iOS] - Refactor Auth0 and driver login flows

Story

Fix Timezone Bug in Calendar Display

Story

Shipment Dashboard - Include Total Pallet Quantity Column

Story

Update New Shipment form and Quote Confirm Details Page to NOT require contact information, company name, and location type

Story

New Shipment Creation Experience Cleanup Ticket

Bug

Dock Scheduling Calendar Not Bringing in All Appointments for Calendar Days Shown

Bug

Orders to shipment bulk action issues

Bug

Order not showing assigned to shipment

Bug

Dashboard weight different than Shipment Weight

Story

Script to Add "Customer" Data Field to Custom Data Field

Bug

Dates and times not being passed within new shipment creation experience anymore when creating a shipment

Bug

Saved Dashboard view not sticking when a user moves between Shipments

Bug

Resolve error when 2 character region code despite it working in all other areas of the platform

Story

Update the modern Custom Data Input component fields to wrap data based on input maximizing the field width

Bug

Order to Shipment Creation FTL /LTL- creating DRAFT status rather than QUOTING status

Bug

Revert changes of KRKN-1871

Bug

New Shipment Creation is not leveraging the Decimal feature flag and passing in header information

Bug

Appointments not visible in Day View in Dock Scheduling Calendar

Bug

Total Shipment Distance not calculating when zip codes are duplicated

Bug

Power Unit is removed during shipment creation, requiring user to re-add

Story

Tracking map doesn’t render correctly if there are breadcrumbs present with no lat/lon coordinates

Story

Address Book now displays time zone for each Address Book Entry

Story

Address Book dashboard now displays time zone in the Operating Hours hover box

Bug

Address Book alignment - Saturday/Sunday Open and Close times displaying correctly in the platform and API

Feature Request

Disable Part of order to shipment auto-build rule for CPU orders

Bug

Script Error - Linear Feet Calculation & Carrier Exclusions

Bug

Excessive Length - LTL Shipment not rating (Part of Return to Green for Ultra Source)

Bug

Dont allow a carrier that has accepted a tender to reject it

Bug

No instant rates available

Bug

Unable to dispatch shipments

Bug

Distance in contract not used when calculating FSC

Bug

Account blocked, unable to log in

Bug

Shipments cancelled once carrier tracking starts

Enhancement

Add distance and distance unit to contract lanes

Enhancement

Add all supported currencies to contracts

Bug

Drayage stop planned dates getting updated


​

Did this answer your question?