May 28, 2025 - 1.2520 Service Update

​

Announcement: FFUI Dashboard and Returns

​

Announcement: Cybersource Updates

​

Production Tenant Features 

​

Catalog

• Category IDs in Google Feed: Additional category data related to Category IDs, such as those of parent product categories, are now included in Google Feed exports.
• Dynamic Category Expression Update: When configuring dynamic category expressions via the UI, the productName field now supports using CONTAINS.

​

Commerce

• Custom Returns Error Message: If an error message is specified via the returns.actions.before API Extension (using throw new Error('MESSAGE HERE')), then the custom text will now be displayed on the Admin UI’s error notification banner when triggered.

​

Fulfillment

• Partial Consolidation Fulfillment: When an STH or Delivery consolidation shipment contains both available items and items awaiting transfer, you can now fulfill the available items right away. Once enabled in your consolidation site settings (“Allow Partial Fulfillment”), call the POST .../api/commerce/shipments/{{snipmentNumber}}/itemsReadyForPack API endpoint with a list of line item quantities, such as in the below example. This will move those items to a new shipment that can immediately continue with fulfillment. The transfer items will remain in the original Waiting for Transfer shipment until they arrive and can be fulfilled. The ability to do this through the Fulfiller UI instead of an API call will be added in a future release. { “items”: [ { “lineId”: 1, “quantity”: 2 }, { “lineId”: 2, “quantity”: 1 } ] }

​

Search

• Similar Products in Vector Search: The vector search now supports a query where, if a specific product is specified, the results will return other similar products. This query is formatted with the starting pattern “products like productCode:{CODE}” where a valid product code is provided and the search settings have vector search enabled.

​

Production Bug Fixes

​

Production Sandbox Features 

​

Catalog

• Discounts by Customer Segment: You can now display discounts based on customer segments in the product details, product listing, and search pages of your storefront. When calling the Get Product, Get Products, or Configure Product endpoints with a list of customer segment IDs (such as in .../products/1234?customerSegments=silver), then the API will consider discounts with those customer segment conditions in addition to those without any customer-specific conditions. A similar list can be provided in the Product Search API call (.../productsearch/search?customerSegments=silver) for the search results. Refer to this Core theme branch as an example of how to update your storefront theme accordingly.

​

Commerce

• Estimated Delivery Date Update: The store hours of a BOPIS pickup location are now factored into the Estimated Delivery Date for BOPIS orders with transfers, where previously any transfers that would arrive at the store outside of its BOPIS cut off hours were not accounted for. Calculations will reflect that if a transfer comes in after the store is closed then it will not be processed until the next opening.
• Location Settings Update: Previously, clearing a location’s Fulfillment Capacity setting required the user to double click the Hours dropdown option after deleting the text. Otherwise, an error message would appear stating that a value was required. This UI has been updated so that a blank value can be easily selected from the dropdown menu, allowing for more efficient clearing of location capacity settings.

​

Fulfillment

• Delivery Shipments in Pick Waves: If Delivery is enabled under a location group’s Pick and Pack settings, you can now initiate pick waves via API for those shipments that are using the updated Delivery BPM. To do this, call the Create Pick Wave endpoint and set shipmentType to “DELIVERY” in the request body. All pick wave actions will remain the same as for other shipment types, and these shipments will automatically move to the Prepare for Delivery step upon successful closure of the pick wave. The ability to create pick waves with Delivery shipments in the Fulfiller UI will be added in a future update.
• Custom BPM Update: If you have custom fulfillment BPMs that will be used with pick waves, a signal component called “picked” is now required be included after a pick wave is closed. This must be routed to the appropriate user task in the custom workflow, as it allows shipment progression to follow your configured routing logic. 

​

Order Routing

• Order Routing Settings Update: The defaultStateChange and tooManyAssignsAction options of Order Routing settings, which determine what happens when an assignment cannot be found for a routing suggestion as well as what happens when the auto assign limit is reached, now support the “BACKORDER” value. The default defaultStateChange value is also now “CUSTOMER_CARE.”

​

Sandbox Bug Fixes