Skip to main content
Table of Contents

Version 2025.6

October 30, 2025. Asset Policies and Batching Presets. We've added two new features to give you better control over which shipments go into your batches and to which locations they are reserved. Asse…

Colin
Updated by Colin
October 30, 2025

Asset Policies and Batching Presets

We've added two new features to give you better control over which shipments go into your batches and to which locations they are reserved. Asset Policies allow you to define which Asset Types can access which Location Types and for which types of operations.

Batching Presets allow you to restrict a batch generation process to a handful of criteria, including:

  • Asset Types and Location Types according to the Asset Policies and whether the intenvory is accessible or not
  • Warehouse Zones for narrowing the footprint of your batches
  • Picking Classes
  • Manifest Couriers
  • Merchants
  • Service Levels
  • Batch Tags

So, if you find yourself repeatedly applying the same filters when creating a batch, or wishing you could have your pickers avoid certain areas, that is now possible using Batching Presets!

Update Impact: None. However, we did rename Cart Types to Asset Types in the process of this update.

Delivery Photos

A picture is worth a thousand words, so an entire gallery is priceless! You can now capture and upload photos to ShipStream for your ASNs, RMAs and Other Deliveries. Each photo may be associated with the delivery in general, a specific container, a specific SKU in a specific container, or an exception. Each photo may also have a caption, with the caption being easy to fill with your own presets.

You clients can, of course, access the photo galleries directly from the Client UI. Making your photos readily available streamlines your communication and builds trust.

Update Impact: None.

FedEx RESTful API

FedEx announced that their Web Services are now deprecated and will be shut down in June of 2026. This release includes support for FedEx's RESTful API using "Client Credentials" authorization with a seamless transition for existing shipping accounts.

Update Impact: None. We will be implementing the "Authorization Code" type of authorization in a future release. This will enable users to connect their FedEx account by simply logging in one time with their normal fedex.com credentials and not have to obtain keys by signing up for a developer account. So, it is our recommendation to not migrate all of your accounts yet.

Separate Grids by Shipment Type

To better accomodate operational specialization for Parcel and Freight teams, you can now access separate pre-filtered grids for each type in both the Admin UI and the Client UI.

Additionally, the Shipment Custom Fields can be customized separately for each shipment type, allowing you to create more fields without cluttering up the data for irrelevant shipments.

Updated fields:

  • Display in Admin Form
  • Display in Admin Grid
  • Export in Admin Grid
  • Display in Client Form
  • Display in Client Grid
  • Export in Client Grid
Update Impact: None. Existing Shipment Custom Fields were update to include both Parcel and Freight in the updated options which were previously Yes/No options. This retains the exact behavior as before.

Email Notifications by Shipment Type

You can now configure your New Shipment and Shipment Comment email notifications separately for Parcel and Freight shipments which can be useful if you have separate responsible parties for each.

Update Impact: None. The old configuration will be copied to the new fields upon migration so the behavior is the same.

Other Improvements

  • Updated Shopify integration to use API version 2025-10.
  • Improved status reporting and error recovery of Product Velocity statistics refresh.
  • Optimized updates of product attributes which had the potential to result in large and slow updates of related Packing Solutions which would cause long lock waits for actions on the affected orders.
  • Optimized order allocations when updating an older order has a snowball effect of updating lots of other orders.
  • Optimized order allocations to defer pick location updates until after the commit is completed to reduce lock time.
  • Fixed Velocity tab does not load heatmap data when switching tabs.
  • Fixed UPS and FedEx new dimension rounding method should have applied to all dimensions, not only dimensional weight.
  • Fixed two Shopify tracking data issues related to kit-type BOMs:
    • When Shopify already has tracking data, compare the existing tracking data with the new tracking data and update it in Shopify if there are any differences (may occur when an order with a kit-type BOM requires multiple packages and the tracking data is added in multiple occurences).
    • Do not throw an error when a suitable fulfillment order cannot be found for a shipment if the order contains BOM items, since multiple shipments may map to one Shopify fulfillment. That is, the items may all already be accounted for by previous shipments due to partial quantities rounding up, and we can't add tracking for the same items twice.
  • Fixed Shopify notify customer flag from the FulfillmentRequest not persisting trhough to the final Fulfillment creation.
  • Fixed a rounding error for BOM products with a large number of components (e.g. 35) which prevented processing shipments for orders containing such products.
  • Fixed proper error handling when attempting to create an order with a product which has an empty SKU.
  • Fix Tracker page layout in Safari.
  • Updated the maximum dimensions allowed for the DHL SmartMail family of services.
  • Fixed BFO Group By: Carrier option to use the shipment shipping method instead of the order shipping method for correctness when used with virtual shipping methods.
  • Increased max packages shown per shipment on the View Shipment page from 50 to 100.

Merchant API Changes

  • Fixed product history comments not included in stock_movement.list response.
  • Added delivery.gallery Merchant API endpoint to retrieve user-uploaded photos.
  • Added inventory.detailed_packaging Merchant API endpoint to retrieve inventory levels for merchant-owned packaging.
  • Updated shipment_custom_field.list Merchant API endpoint to remove binary display fields and add multi-option display fields and export fields.

How did we do?

ShipStream Releases

Version 2025.5

Contact