June 29, 2026 Release Notes, Version 26.08

Product Catalog - Custom Data Fields

Summary

This release introduces Custom Fields for the Product Catalog, letting you attach business-specific attributes to the products in your catalog. Until now, product records supported only a standard set of fields — description, dimensions, weight, freight class, hazmat, and the like — with no way to capture attributes unique to your organization.

Now you can define your own custom fields for products and populate them on individual product records, in bulk via product import, or through the API — capturing data like internal SKU codes, compliance flags, storage requirements, or supplier references right alongside the product. Those values travel with the product, so they're available when you build shipments using your catalog.

Key Capabilities:

Define custom fields for products — configure company-specific custom fields for the product entity using any of Shipwell's existing custom field types, the same way you already do for shipments and other records. This can be a single text field or a list. Users can also make this field required, or not.

Populate custom fields on a product — add and edit your custom field values directly on individual product records in the product catalog, through both the UI and the API.

Bulk import custom field values — set custom field values across many products at once using the product bulk import, so you don't have to update records one at a time.

Available on your products everywhere they're used — once populated, custom product attributes are stored on the product record and available when those products are referenced, including when creating shipments from your catalog.

How It Works:

Custom fields for products build on the same custom-data foundation Shipwell already uses for shipments, line items, stops, and purchase orders. An admin defines the custom fields for the product entity; users then populate those fields on individual product records — manually in the catalog UI, in bulk through product import, or via the API. The values are saved to each product's record and carried with it throughout the platform.

Benefits:

Capture what's unique to your business — store organization-specific product attributes (SKUs, compliance flags, storage needs, supplier references) that don't fit Shipwell's standard product fields.

One source of truth for product data — keep custom attributes on the product record itself instead of tracking them in spreadsheets or external systems.

Bulk-ready — populate custom values across your catalog at scale through product import.

Consistent with the rest of Shipwell — uses the same custom fields framework you already know from shipments and other records, so there's nothing new to learn.

Known Limitations:

Custom fields use Shipwell's existing custom field types — no new field types are introduced in this release.
Custom field versioning and audit history are not available for product custom fields in this release.
Custom fields are scoped to your own company; cross-company custom field sharing is not supported.

AI Studio Email Integration — Gmail Support Added

Summary

AI Studio workers can now send emails from a customer's business email account using Google Gmail, in addition to the previously supported Microsoft Outlook. This expands the Email Integration options available under AI Studio > Global Configuration > Email Integration, giving teams the flexibility to use whichever email provider their organization relies on.

How It Works:

Users can connect either a Microsoft Outlook account or a Gmail account from the Email Integration configuration page. Once connected, AI Studio workers will send communications using the company's own email address rather than a generic Shipwell address, ensuring consistent branding and deliverability for automated outreach.

To connect Gmail:

Navigate to AI Studio > Global Configuration > Email Integration.
Click Connect under the Google Gmail option.
Sign in with Google and authorize Shipwell to send email on your behalf.

Benefits:

Provider flexibility - organizations running on Google Workspace can now connect Gmail just as Outlook users could before.

Consistent sender identity - automated worker emails arrive from your company's domain, not a Shipwell address.

Swifty Slack & Teams Integration — Setup Moved to Company Integrations

Summary

The setup page for connecting Swifty to Slack and Microsoft Teams channels has moved from AI Studio to a more intuitive location: Manage > Company > Integrations. The Slack and Microsoft Teams connection cards now appear alongside other company-level integrations, making it easier to find and manage all your connected tools in one place.

How It Works:

To connect or manage Swifty's Slack or Teams integration, navigate to Manage > Company > Integrations and click Connect on the Slack or Microsoft Teams card. The connection flow and configuration options are unchanged — only the location has moved.

Benefits:

More discoverable - company integrations are now consolidated under the Company settings area where admins already manage other connections.

More accessible - no longer hidden behind the AI Studio feature flag

API Changes

Overview

This release introduces enhancements to dock scheduling appointment data, order filtering, tender search, and tracking schedule visibility. The update is fully backward compatible.

Summary:

New Feature: Expanded tracking schedule modal data and new tender BOL filter (backend-core, 103 changes)
New Feature: New order stop external reference autocomplete endpoint and address book reference filters (corrogo, 77 changes)
New Feature: Shipment data embedded on appointment list items; product_reference deprecated in favor of product_references array (tempus, 224 changes)

New Features

Tender Filter by BOL Number (Core API)

Added support for filtering tenders by the associated shipment's BOL number.

New Query Parameter on GET /v2/tenders/:

Parameter	Type	Description
`shipment__bol_number`	string	Filter tenders by the associated shipment's BOL number

Order Stop External Reference Autocomplete (Orders API)

A new autocomplete endpoint has been added for stop external reference IDs, enabling prefix-based search for use in UI typeaheads and integrations.

New Endpoint: GET /orders/stops/external-reference

Parameter	Type	Description
`q`	string	Case-insensitive prefix to search. Only values that start with `q` are returned.
`limit`	integer (1–100, default 20)	Maximum number of results to return

Response: 200 OK — array of matching strings.

New Order List Filters: Four new query parameters have been added to order list endpoints for filtering by address book entry reference ID on ship-from and ship-to stops.

Parameter	Type	Description
`ship_from__references__address_book_entry_reference_id`	array of strings	Filter by ship-from address book entry reference ID
`ship_from__references__address_book_entry_reference_id__in`	string	Comma-separated ship-from reference IDs
`ship_to__references__address_book_entry_reference_id`	array of strings	Filter by ship-to address book entry reference ID
`ship_to__references__address_book_entry_reference_id__in`	string	Comma-separated ship-to reference IDs

API version: 0.8.26 → 0.8.27

Appointment Shipment Data & Product References (Dock Scheduling API)

Shipment-sourced data is now embedded directly on each appointment list item, eliminating the need for a separate shipment lookup when displaying appointment lists.

New Schema: AppointmentShipmentData

The following shipment fields are now available on each appointment:

Field	Type	Description
`reference_id`	string	Shipment reference ID
`bol_number`	string	Bill of lading number
`customer_reference_number`	string	Customer reference number
`pro_number`	string	PRO number
`purchase_order_number`	string	Purchase order number
`order_number`	string	Order number
`mode`	object	Shipment mode
`equipment_type`	object	Equipment type
`temperature_lower_limit` / `temperature_upper_limit` / `temperature_unit`	number / number / string	Temperature range and unit for reefer shipments
`trailer_name`	string	Trailer identifier
`custom_data`	object	Shipment custom data
`product_categories`	array of strings	Product categories on the shipment
`line_items`	array of `BeCoreShipmentLineItem`	Shipment line items

Deprecation: product_reference (singular)

The product_reference field (single string) is deprecated across multiple schemas in favor of product_references (array, 1–10 items, max 256 characters each).

On input: the singular product_reference value is folded into product_references. If both are provided, product_references wins.
On output: product_reference mirrors the first element of product_references for backwards compatibility.

Consumers should migrate to product_references at their earliest convenience.

API version: 0.4.8 → 0.4.10

Analytics Model Updates

Field Adjustments

Changes to the “Actual Date” field logic. This field returns a coalesce or the first non-null value it finds in the following order.

Current formula: COALESCE(Completed Date, Arrival Date, Planned Date)

Past formula: COALESCE(Arrival Date, Completed Date, Planned Date)

Report Builder

Field Name	Field Description
All Stop Full Address Pickup Stops Full Address Delivery Stops Full Address Purchase Order Pickup Stop Full Address Purchase Order Delivery Stop Full Address Stop 1-6 Full Address	Combines Stop Address, City, State, Postal Code, State Province, and Country into one column
Stop 1 - 6 Stop Type	Boolean for whether a stop is a pickup or a delivery
Shipment Details All Order Count on shipment Shipment Details All Order Numbers on Shipment	Used for when orders are assigned to more than one shipment
Purchase Order All Shipment Count for Order Purchase Order All Shipment References for Order	Used for when orders are assigned to more than one shipment
Shipment Line Item Total Declared Value Purchase Order Total Order Value	Multiply values per piece and piece count for each line item, and then sum.

Note: Field Adjustment

Changes to the “Actual Date” field logic. This field returns a coalesce or the first non-null value it finds in the following order.

Current formula: COALESCE(Completed Date, Arrival Date, Planned Date)

Past formula: COALESCE(Arrival Date, Completed Date, Planned Date)

Data Share

Table: dim_shipment_detail

Field Name	Field Description
all_order_count_on_shipment	Total count of distinct orders assigned to a shipment. Includes orders assigned to multiple shipments. Both V2 and V3 orders.
all_order_numbers_on_shipment	Comma-separated list of all order numbers assigned to this shipment, ordered alphabetically. Useful for viewing all orders consolidated onto a single shipment. Includes orders assigned to multiple shipments.

Table: dim_order_lineitem

all_shipment_count_for_order	Total count of distinct shipments this order is assigned to. Useful for multi-leg scenarios where a single order spans multiple shipments.
all_shipment_references_for_order	Comma-separated list of all shipment reference IDs that this order is assigned to, ordered alphabetically. Shows the complete shipment journey for multi-leg orders.

Other Minor Enhancements and Bug Fixes

Improved billing accuracy for Worldwide Express (WWEX) brokered shipments by ensuring "Bill-To" details are correctly applied.

Resolved an issue where Pitt Ohio (POGL) rates were missing from the Instant Rates view.

Fixed a bug where ABF shipments would incorrectly revert from "Delivered" status.

Enhanced tracking reliability to ensure "Delivered" statuses are accurately reflected across all carriers.

Resolved a tracking issue where SAIA shipments were not automatically updating to "Delivered" status.

Fixed an issue that prevented electronic Bills of Lading (eBOL) from generating correctly for Estes shipments.

Ensured that PRO numbers received at the time of dispatch are correctly saved and displayed on the shipment record.

Corrected a status mapping issue for R&L Carriers to ensure shipment progress is accurately displayed.

Improved the consistency of automated status updates for LTL carrier connections.

Cleaned up rate results and financial views by hiding $0 line items that do not impact the total cost.

Fixed a rating failure that occurred when adding a "Delivery Appointment" requirement to R&L Carrier shipments.

Resolved a conflict that caused rating errors when both "Notify Before Delivery" and "Delivery Appointment" were selected for ODFL.

Updated R+L Carrier results to clearly indicate whether the service is "Direct" or "Interline."

Improved rate clarity for Estes by correctly separating Volume LTL (VLTL) rates from standard LTL rates.

Resolved a dispatching error that occurred when sending small-volume loads to direct LTL connections.

Fixed an issue where custom markups were not being applied to Cloudtrucks rates.

Updated carrier configurations to prevent the selection of unsupported service options for ACT.

Synchronized rating logic to ensure consistency between direct ABF connections and third-party tracking services.

Resolved a synchronization issue with ABF Freight to ensure tracking milestones are updated in real-time.

Improved rating compatibility by ensuring ZIP codes are formatted correctly for carrier systems during dispatch.

Updated Southeastern Freight Lines (SEFL) results to specify "Direct" vs. "Interline" service types.

Resolved a technical issue that prevented Uber Freight bookings from completing successfully.

Fixed a data transmission error to ensure R&L Carriers receive the correct pallet count during dispatch.

Resolved a validation error that prevented dispatching XPO shipments with specific billing and postal code combinations.

Fixed a bug that prevented users from successfully linking Tive tracking devices to shipments.

Improved the Tive device list to ensure all available devices are loaded and visible to the user.

Resolved an issue where bulk-updating shipments to "Delivered" would fail if multiple stops had the same time window.

Fixed a tracking integration issue for carriers using Samsara ELD

Corrected an issue where ocean container (FCL) statuses would incorrectly revert after being marked as returned.

Added "Grocery Consolidation Delivery" (GCD) as a selectable option in the required service menus.

Fixed a bug where appointment times were displaying incorrectly due to time zone differences.

Improved the shipment map view to ensure all location markers are contained within the map boundaries.

Fixed a UI issue where error icons in text fields were not displaying correctly.

Enable custom data fields in the product catalog

Enable custom data fields in the product catalog (bulk import)

Enable custom data fields in the product catalog (configs)

Added the ability to resubmit shipments for fuel surcharge calculations to ensure accurate financial records.

Improved the accuracy of automated tracking updates for pre-assigned shipments.

Swifty Teams Channel Setup

Duplicate rows on the Invoice Table per Invoice Status

Swifty Email Setup

Database not refreshing

Fixed an issue so you can now set or edit a stop’s appointment date/time independently of the planned window

Appointment times entered on a shipment stop save correctly to the Appointment field instead of the planning window

Cloned shipments now carry the correct appointment date.

Appointment window is no longer required when creating an FTL shipment from orders. This was previously blocking FTL Shipment creation from orders.

Order forms now display all custom fields instead of only the first 20 custom fields.

New users now receive their email verification email. Previously, there were issues receiving the email-verification and password-setup emails, so they could not log in.