Archived what's new in 2025
Important new features and enhancements that were introduced in 2025.
The capabilities that are introduced in 2024 and previous years are archived. For more information, see Archived what's new.
For defects that are addressed in major and minor updates, see Archived resolved issues in 2025.
28 October 2025 (Store Inventory Management update)
The nonproduction environments were upgraded on 28 October 2025. The production environments will be upgraded on 30 October 2025.
- Enhancement for move inventory events
-
You can now track inventory movements between store locations using Move inventory events in Store Inventory Management. The code for this event is
moveInventory. For more information, see Move inventory event.
16 October 2025 (Store Inventory Management update)
The nonproduction environments were upgraded on 16 October 2025. The production environments will be upgraded on 30 October 2025.
- Enhancement for putaway preference
-
You can create a putaway preference by specifying the lineType as one of the input parameters. For more information on doing this action, see Create putaway preference.
The include and exclude locations that are defined in the preference are used to determine the target location for putaway, with any dedications configured. If no suitable location is identified through dedications, the system automatically uses the defined putaway preferences to determine the target location.
Priority is given to the dedications. This logic is also applicable for move request of type PUTAWAY. If you prefer to disable this behavior, a configuration setting is available to prevent the system from using preferences when no dedications are found. Currently if you use putaway preferences, the configuration is set in such a way that the preferences are not used. If you want to use them, you can modify the configuration by using the Putaway preference configuration API.
Issues were fixed in this release. For more information, see 16 October 2025 (Store Inventory Management update).
13 October 2025 (Release 25.3.9.1-10.0.2509.1)
Issues were fixed in this release. For more information, see 13 October 2025 (25.3.9.1-10.0.2509.1).
5 September 2025 (Release 25.3.9.0-10.0.2509.0)
- Custom redirect for mashup errors
- You can now execute custom redirection logic for mashup errors such as System_Timeout and
CSRF Token validation failed, instead of the default login page. For more information, see Custom mashup error redirects.
- Resolved issues
- Issues were fixed in this release. For more information, see 5 September 2025 (25.3.9.0-10.0.2509.0).
1 August 2025 (Release 25.2.6.2-10.0.2506.2)
- Barcode tooltip toggle
- Support is added to disable tooltips on the barcode scanner input and button. Include the disableTooltip configuration options in the
extension-config.jsonfile. For more information, see Disabling tooltips for barcode scanner.
- Resolved issues
- Issues were fixed in this release. For more information, see 1 August 2025 (25.3.9.2-10.0.2506.2).
8 July 2025 (Release 25.2.6.1-10.0.2506.1)
Issues were fixed in this release. For more information, see 8 July 2025 (25.2.6.1-10.0.2506.1).
3 July 2025 (Store Inventory Management update)
The nonproduction environments were upgraded on 3 July 2025. The production environments will be upgraded on 8 July 2025.
- Enhancement on Delete Schedule API
-
The Delete Schedule API now supports the deletion of one-time jobs after they are triggered. Previously, only recurring jobs could be deleted. For more information, see Delete Inventory Snapshot Schedule.
Issues were fixed in this release. For more information, see 3 July 2025 (Store Inventory Management update).
6 June 2025 (Release 25.2.6.0-10.0.2506.0)
- Option to override the application name IBM Store literal with an image
- A new option lets you override the literal for application name IBM Store with a custom image, allowing for enhanced branding customization. For more information, see Overriding default logos and application name literals in navigation bars.
- Deposit All button added to Putaway Deposit page
- The newly added Deposit All button on the Deposit page for each Putaway task, allows you to deposit all items in one click. For more information, see Configuring putaway inventory.
- Deprecated Sterling Store Engagement (legacy)
- The Sterling Store Engagement (legacy) application that is built on Angular 11 with the URL https://<domain-name>/isf/store/index.html is deprecated. Effective from the 25.2.6.0-10.0.2406.0 major update release, the legacy custom code will be removed from the deployment, and access to the legacy application will no longer be available.
- Resolved issues
- Issues were fixed in this release. For more information, see 6 June 2025 (25.2.6.0-10.0.2506.0).
2 May 2025 (Release 25.1.3.2-10.0.2503.2)
Issues were fixed in this release. For more information, see 2 May 2025 (25.1.3.2-10.0.2503).
10 April 2025 (Store Inventory Management update)
The nonproduction environments were upgraded on 10 April 2025. The production environments will be upgraded on 16 April 2025.
- Enhancement on Count Program endDate
-
The
endDateof a Count Program was previously interpreted as the beginning of the day. For example, anendDateof2024-10-11means the program ends at2024-10-11T00:00:00Z. Now, theendDatereflects theend of the day. This action means the program remains active until2024-10-11T23:59:59Z. For more information, see Count Program API.
Issues were fixed in this release. For more information, see 10 April 2025 (Store Inventory Management update).
4 April 2025 (Release 25.1.3.1-10.0.2503.1)
Issues were fixed in this release. For more information, see 4 April 2025 (25.1.3.1-10.0.2503.1).
7 March 2025 (Release 25.1.3.0-10.0.2503.0)
- Angular v18 upgrade
-
The Angular version for IBM® Sterling Store Engagement application is upgraded to version 18. Upgrade your customizations to get the Angular 18 version with the most recent features and bug fixes. For more see Upgrading to Angular version 18.
- Resolved issues
-
Issues were fixed in this release. For more information, see 7 March 2025 (25.1.3.0-10.0.2503.0).
7 March 2025 (Store Inventory Management update)
The nonproduction environments were upgraded on 07 March 2025. The production environments were upgraded on 13 March 2025.
- GET List of Putaway Preferences API
-
The GET List of Putaway Preferences API allows fetching putaway preferences for a specific tenant. These preferences can be retrieved at the store level, for a particular type, or based on both store and type.
- Enhancing pick-preference
-
To enhance inventory selection and task optimization, the pick-preference API now supports priority-based picking.
- Priority-based picking
- Locations can be included or excluded based on zone, type, or location ID.
- The system now considers location priority when multiple locations meet the picking criteria.
- Eligible locations with a higher numeric priority are selected first.
- Priority over a primary-picking preference
- Location priority takes precedence over
pickFromMaxInventoryandpickFromMinInventory. - If multiple locations share priority, the system applies the primary-picking preference to determine the final selection.
- Location priority takes precedence over
- Primary-picking preferences
pickFromMaxInventoryis the default preference. This preference selects items from locations with the highest available inventory.pickFromMinInventoryselects items from locations with the lowest available inventory.
- Priority-based picking
Include Locations.17 February 2025 (Store Inventory Management update)
The nonproduction environments were upgraded on 17 February 2025. The production environments were upgraded on 13 March 2025.
- Stamping zones in pick-task references
-
In task references, the
sourceLocationzone is captured as a key-value pair under the following conditions- If the
sourceLocationzone isBAY, it is stored in the task reference as{ "zone": "BAY" }. This behavior also applies to move tasks and putaway tasks. - If the
sourceLocationzone changes after the pick-task is created, you can update the zone in the task reference by using thePATCH API. This behavior also applies to both move tasks and putaway tasks. - If a zone is specified in the
requestedProductreference, it takes precedence over thesourceLocationIdzone in the task references.
- If the
sourceLocation itself does not have a predefined zone, the task reference is not included to a zone by default. This means, it is only stamped in a task reference when explicitly specified in the requestedProduct reference.24 January 2025 (Release 24.3.9.2-10.0.2409.2)
- Capability to build a hybrid app by using Cordova
- Using Cordova, you can set up integration between Sterling Store Engagement and the peripheral devices, such as bar code scanners. For more information, see Integrating peripheral devices.
- Payment capture during order creation is optional
- A new rule is introduced to make payment capture optional during order creation. For more information, see Payment capture during order creation.
- Resolved issues
-
Issues were fixed in this release. For more information, see 24 January 2025 (24.3.9.2-10.0.2509.2) .