Version 2025.1

Colin Updated by Colin

March 18, 2025

Location Default Priorities

To give you more control over your location priorities and simplify managing them, we've added a Default Priority field to Locations. This value, if not empty, is used to set the Priority any time a location is unassigned or assigned to a new product, or when you trigger an update with the new Apply Default Priorities mass action.

By setting a Default Priority for your Locations, you can still make overrides when necessary but then easily revert to the default priority when your override is no longer needed.

Additionally, we've changed how Priority values are numbered relative to other locations for the same product and warehouse so that you can more easily organize your warehouse layout by setting priority values anywhere from 1 to 65,536.

A few other related changes were made as well:

  • Added Priority and Default Priority columns to the Locations grid.
  • Added support for setting Priority and Default Priority with the Location Import tool.
  • Added an Edit Location link to the locations list on the Product Inventory tab - saving the location navigates back to the Product Inventory tab.
  • Added "Apply Default Priority" mass action to the Locations grid.
  • Added "Apply Location Default Priority" mass action to the Racks grid (this is suitable for updating thousands of racks/locations all at once).
  • Locations are no longer implicitly sorted by pickable first, then non-pickable, so you can now place non-pickable locations before pickable locations.
  • The "Pick Source: Strict By Location Priorities" option now ignores pickable status, which previously didn't matter due to the forced sorting between pickable and non-pickable locations.
Update Impact: None. All existing and new locations have an empty Default Priority value.

Automatically Mark Shipped

We've added an option called Automatically Mark Shipped to the External Shipping Methods which helps you mark your offline shipments as Shipped when you add a primary tracking number.

Update Impact: The merchant integrations push tracking information when a package is packed with a tracking number (whether online or offline), or in the case of offline shipping without tracking, it waits until it is marked Shipped to push the tracking information. It is strongly recommended to enable Automatically Mark Shipped if you do not use the Loading feature or manually marking Shipped is not part of your SOP.

Other Improvements

  • Various UX improvements were made to the delivery processing workflows and Put-Aways feature from the 2025.0 release.
  • Fixed syncing tracking numbers to integrations when the shipment is shipped offline and tracking numbers are added after packing.
  • Fixed a bug where it was possible to submit a non-numeric value from the Counter, corrupting the Packing UI.
  • Fixed a bug where reverting packing on a shipment with confirmed Packing Instructions caused errors in the Scanner UI.
  • Fixed a bug causing errors when finishing packing after reloading the page and resuming from saved data in the Packing UI.
  • Fixed put-away when a lot was recorded, but the product's Lot Type has been unset.
  • Improve an error message when trying to reduce count more than the sum of unapproved overages.
  • Fixed "The count could not be applied." when putting away under some circumstances.
  • Fixed an error when approving exceptions related to BOMs.
  • Updated an error message when processing a shipment, and a stocked item is not linked to any other SKUs via a Kit on Demand BOM, so a fractional pick can't be resolved into pickable units.
  • Avoided race condition for the order.create Merchant API method with the unique_ref flag.
  • Fixed an unexpected error thrown after reducing an overage in some cases.

Grid Changes

  • Added columns to the Delivery Container Items export
    • RMAs
      • Order #
      • Order Ref #
      • Merchant RMA #
      • Merchant Order #
    • ASNs
      • Merchant Ref
      • Supplier Order Ref
  • When sorting the Shipments grid by Brand Name, the sort order will be the Merchant Name first, followed by the Brand Name.
  • Fixed Container Index on Delivery Containers export to match the index numbers in the UI.

API Changes

  • Added qty_on_hand to inventory.list and inventory.detailed response formats.

How did we do?

Device Hub Client Updates

Contact