Table of Contents

Version 2025.2

Colin Updated by Colin

May 15, 2025

Mass-Cancel Specific Items

For those times when you need to for whatever reason remove one or more items from any number of orders containing them, we have updated the following order mass actions to accomodate a "Specific SKUs" field.

  • Cancel All Items
  • Cancel Backordered Items
  • Cancel Unprocessed Items

Whether you supply one or more SKUs or Advanced Grid Filter patterns to this field, after clicking Submit you will be able to preview the changes on the following page and click Submit to apply the changes.

In the Result column you will see one of the following expected end results for each order:

  • Fully Canceled
  • Partially Canceled
  • Complete
  • Cancel Requested
  • Not affected
Update Impact: None. However, note that canceling specific SKUs introduces a new condition where some unprocessed or backordered items may be canceled from an order while other items are still unprocessed or backordered. This could impact workflows or integrations that do not account for this possibility.

Change Shipping Method per-Shipment

You can now override the shipping method for one or more shipments on an order via the Change Shipping Method mass action on the Shipments tab. This can greatly simplify trying to get out complex orders that require multiple shipping methods such as mixed Parcel and LTL orders.

If you select a Virtual Shipping Method, it will immediately be resolved to the correct real shipping method, so you don't need to give up rate shopping when overriding shipping methods.

Update Impact: None

Shipping Estimate Total

You can now view the Shipping Estimate Total in the Order History. This comment is added each time an order's shipments are generated or updated as long as all of the the required rating data is present for orders with either Virtual Shipping Methods or real shipping methods that have sufficient Rating data.

Update Impact: None. This feature is disabled by default and must be enabled at System > Configuration > Shipping > Orders > General > Add Shipping Estimate Comments.

Streamline RMA Processing

We added a button at the end of the processing workflow to allow one to easily jump straight to accepting another RMA after finishing processing an RMA.

Update Impact: None.

Advanced Grid Filters List

You may not have even known about Advanced Grid Filters, but if you did, you probably easily forget all of the options! Not anymore!

Update Impact: None.

Other Improvements

  • Fixed the NOT NULL Advanced Grid Filter, but also added "+" as a shorter and better alternative meaning "not empty".
  • Improve pack processing time for shipments with Data Collections with Collected Data Unique feature.
  • Improve error messages when postcode ranges in rating maps overlap.
  • Fixed a regression with the Bulk Fulfill Order mode of the Packing UI which caused the packing to not be auto-submitted after scanning the products if Auto-Pack is not enabled (requiring the user to re-scan the packaging for each shipment).
  • Fixed the "Could not load stock lot." error which would occur when putting away deliveries with no lot numbers but multiple expiration dates.
  • Fixed tapping Back button from Finished Processing page should navigate back to the main Processing page rather than the delivery that was just processed.
  • Fixed a bug causing double-subtraction of Qty Processed when a processed delivery is canceled. Existing discrepancies will be corrected automatically.
  • Fixed ZPL conversion rate limit hit when generating lots of labels for a delivery return.
  • Fixed internal error when generating labels for multi-package international shipments with extremely low customs value per-unit.
  • Fixed Put-Away progress not set to 100% when processing is complete in some cases.
  • Added dynamic updating of the Destination select options after submitting the count during delivery processing via the Admin UI.
  • Fixed an issue where the last column of a rating map import was dropped (no impact if it was empty).
  • Fixed a rounding error when customs value divided by qty ordered is less than 0.01.
  • Fixed an occasional deadlock updating an order during daily backorders cleanup.
  • Improved performance of location import and reduced impact to inventory users.
  • Fixed bug with stock movement log when the product in the log is different than the product assigned to the location.
  • Download a file with the location import results if the location import result grid is too large to render in the browser.
  • Fixed SPS Commerce Shipping Labels and ASNs for orders using BOMs which ship out with split cases of inner/outer packs.
  • Improved performance of loading serial numbers.
  • Cleaned up goods types:
    • Added "Limited Quantity" to the "Always Apply to Goods Type" attribute options
    • Filtered the "Always Apply to Goods Type" and "Never Apply to Goods Type" options by the "Allowed Goods Types" config setting (hides options that are not allowed by config)
    • Relabeled "Limited Quantities: Consumer Commodities" to "Limited Quantity"
    • Relabeled "ORM-D: Consumer Commodities" to "ORM-D"
  • You can now click the thumbnail on the product page Images tab to view the full size image. Webp and AVIF image formats are now supported and images are resized upon upload to a maximum of 2560px x 2560px.

Grid Changes

  • In the Packages grid export format, we changed "Dimensional Weight Unit" to "Rating Weight Unit" so that it applies to both the Dimensional Weight and the Billable Weight columns. We also corrected cases where the the units should have been stored with 'oz' rather than 'lb'.

API Changes

  • Added an order:items_updated webhook topic to be notified when order items are partially canceled.
  • Added a delivery.close endpoint and a $close parameter to the delivery.commit endpoint.
  • Added support for item_ref as a property of delivery items in delivery.create to allow for storing external references to individual line items.
  • Improved validation of order.create parameters to provide a better error response when an argument is missing.

How did we do?

ShipStream Releases

Contact