Table of Contents

Version 2024.1

Colin Updated by Colin

April 10, 2024

New Permissions

We've added new permissions for features that already existed but could not be revoked from a user role without revoking broader permissions to give you finer-grained control over features that perhaps not all users should have access to.

  • Operations > Picking Batches > Force Compose
    • Required to use the "Force Compose Picking Batch" mass action.
  • Shipping > Shipments > Choose Locations
    • If a user can create BFOs but lacks Choose Locations then all inputs should be disabled so they must accept the auto-filled locations
    • Required to use the Choose Locations button on the Shipment page.
  • Shipping > Shipments > Choose Locations > Violate Burn Order
    • If a user is lacking this permission, the quantity inputs for all locations that would result in an out-of-order pick are disabled unless that location has a non-empty value (so the user can set it to 0 if needed).
Update Impact: These permissions will not be granted to any user roles by default so you should add them back to the roles that need them after deployment.

UPS Account Authorization

UPS upgraded their API offering in 2023 to provide two new authentication methods which are more secure and more reliable than the old method which required sharing your username and password. The UPS Integration now has an Access Key Type field with new options Authorization Code and Client Credentials which implement the latest UPS authorization methods of providing authorization to a UPS account. These are safer and more convenient and won't break if you change your account password!

Additionally, these integration methods now use the latest UPS REST API endpoints.

Update Impact: No immediate impact. However, if you use UPS you must update your accounts to use one of the new access key types before June 3, 2024, to avoid any interruption of service.

USPS First Class Mail

The USPS First Class service was relabeled to USPS First Class Mail in version 2024.0 but still supported parcels (mapped to USPS Ground Advantage) for backwards-compatibility. In version 2024.1 this service will no longer support parcel, it will only support letters, cards and flats weighing 13 ounces or less.

Update Impact: If you have any integrations depending on USPS First Class Mail for shipping you should transition them to USPS Ground Advantage before deploying this update.

SPS Commerce Shipping Labels

We've implemented the Shipping Labels API provided by SPS Commerce on top of our Outbound SSCC Barcodes feature so that you can effortlessly generate and print vendor-specific SSCC labels for your outbound shipments to your EDI-using trading partners.

Update Impact: None.

Allow Barcodeless Shipments Updated

Some improvements to the way items are allocated for BOM order items were made to address some rare conditions:

  • When "Allow Barcodeless Shipments" is disabled
    • Order allocation will prefer BOMs over pre-kitted if the pre-kitted item has no barcode. If the BOM allocation is insufficient then pre-kitted will be used to make up the difference.
    • Shipments will require all BOM components to be barcoded and will throw an error like Unable to split "{qty}" of "{sku}" into scannable whole items with Allow Barcodeless Shipments disabled.
  • When "Allow Barcodeless Shipments" is enabled
    • Order allocation will prefer pre-kitted over BOMs
    • Shipments will not require any BOM components to be barcoded. If there are no unbarcoded components either, then an error will be thrown like Unable to split "{qty}" of "{sku}" into whole items to be fulfilled. Please check that a Bill of Materials exists.
    Update Impact: None. This update was also backported to 2024.0.

Employee ID Field

To aid in integrations that map users in ShipStream to users in other systems, we've added an Employee ID field to the user form and grid. This field can contain any character data up to 64 characters long and will enforce that the value is unique for each user.

The Employee ID field is available to both organization users and client users. For client users, the field's uniqueness will only be enforced for the client user's merchant so your clients may also use this field to their advantage.

Update Impact: None.

Void Relocation Improvements

When voiding a relocation, a comment is now mandatory and will be added to the Relocation Information section on the page for future reference as well as the Product History.

Additionally, the relocated amount and voided amount are now accounted for separately to make it clear how many items were successfully relocated vs being voided. Any partially completed Relocations will be set to Complete status once voided.

Update Impact: None.

Other Improvements


  • Fixed a bug where putting away a product with a lot to an empty location with a different product would throw a product validation error before checking if the location was empty.
  • Fixed some rare conditions that could cause the Backordered and/or Locked quantity to become inaccurate or negative.
  • Fixed a bug where validation errors should have been thrown in some cases when users attempted to mix incompatible lots.
  • Fixed some conditions where shipment items may get re-reserved to new locations that were not following the correct Burn Order.
  • Fixed a bug where reservations were always locked if a lot was used, even if fulfillment lot mixing was allowed.
  • Fixed a BOM rounding error and bug where order reallocation may not properly account for indirectly related BOM products.


  • Improve error handling during label generation so that if any step of submitting a shipment fails, canceling the shipment will be done in the background with a retry mechanism to ensure that it is eventually canceled.
  • Fixed a potential bug in processing Easypost and eHub shipping label images that represent two or three labels in one image. We are not aware of any situations currently exhibiting this behavior.
  • Fixed a bug that would sometimes occur when creating eHub manifests causing the request to fail.
  • Improve handling of connection failures while waiting for manifests to be generated.


  • Improved handling of duplicate EDI Document file names in the SPS Commerce integration. Clicking Retry for a duplicate file name error will now force the file to be imported.
  • Errors generated by the Shipment Transform Script for SPS Commerce are now logged as Integration Errors.


  • Added a "Deactivate" mass action on the users grid and replaced the "This account is" form field with Deactivate/Activate buttons with confirmations.
  • Applied "Container Weight Input" configuration logic to the Add Container dialog on the Admin UI.
  • Fixed a bug where overriding the dim weight divisor for a rating plan caused a dim weight to be applied when it should not have been applied.
  • Updated telephone number validation to be more strict and throw a more detailed error message. The "Recipient Phone Number Fallback" configuration was used for invalid phone numbers but was not used in cases where the validation was too lenient so the more strict validation will result in fewer errors from downstream carrier APIs:
    • Local-only numbers in the US are no longer considered valid.
    • Too-short, too-long or invalid length numbers are no longer considered possibly valid.
    • Invalid country codes are no longer considered valid.
  • Fixed updating packing solutions for existing orders after changing container sets.
  • Improved performance of updating container sets and packing solutions.
  • Improved performance of loading an item on Relocation when the item has many occupied locations.
  • Reduce lock contention for packing solution updates simultaneously to other shipment operations.
  • Removed inactive merchants from the list of merchants on the Create New Picking Batch dialog.
  • Fixed an issue where some translations may not be shown correctly after switching languages.
Some of these changes have already been backported to previous versions.

API Changes

  • Fixed a consistently slow response time in the Merchant API method.

How did we do?

ShipStream Releases

Version 2024.0