September 3, 2025 — 1.2534 Service Update

Production Tenant Features

Partial Backorder Release: You can now configure your backorder process to release some of a shipment's items or quantities for fulfillment even if others still aren't available. When enabled, the inventory that becomes available will move into a Ready shipment for immediate fulfillment while the remaining amount stays in backorder. You can release partial backorders based on either full line items or quantities.

Order Routing UI Upgrade: The Order Routing UI has been overhauled with an updated look and feel, as well as some functional changes. For instance, strategies now represent a single fulfillment type, all active Admin locations are now available in Order Routing instead of being managed separately, and filters are now created within the context of specific scenarios instead of globally. See the Order Routing documentation and this support article for more details.

All sandbox tenants will receive the new UI on September 3, unless you have specified to opt out by notifying Kibo Support. Coordinate with Kibo to migrate your production tenants at any point between September and end of January 2026.

Service	Resolution
Commerce	Some failed PayPal payments resulted in orders being put into the Processing status despite being in the Errored payment status, which caused customers to receive confirmation emails. This process has been updated to better handle this scenario and ensure the correct order statuses are utilized.
Commerce	Attempting to update the shipping or handling on an order in the Admin UI with an Avalara tax integration resulted in a generic error message. This has been corrected so that these values can be edited successfully from the UI.
Fulfillment	Searching for child shipments through the Shipments API resulted in a 404 Error even though the provided shipment numbers were valid. This has been fixed so that the appropriate shipment results will be returned as expected.
Fulfillment	After attempting to Order All Items Now on some subscriptions, an error message instead indicated that the continuity order failed to process. This was due to an issue with some order items being marked for both transfer and cancellation. This has been corrected so that these subscription orders can be successfully created.

Find more information about the client-facing updates at these Jira tickets:

Partial Backorder Release: CHAR-6322
Order Routing UI Upgrade: ICKY-1563 (See the internal Order Routing UI Migration guide for more details and guidelines for clients. This document can be downloaded as a PDF to share directly with clients as needed.)

The following enhancements are internal-only and not exposed to clients:

CHAR-6345 and FFMT-4917: Hardcoded RabbitMQ credentials have been replaced with config keys.
CAT-6742 and CAT-6667: Improvements have been made to reduce log noise in some Catalog APIs, as well as better handle rendering errors in production logs.
CHAR-6375: Optimizations have been made to the Refresh and Adjust APIs for maximum throughput to support Autozone and Office Depot inventory updates.
CHAR-6187: Sonar test coverage has been improved for Order Routing.
CHAR-6167: The inventory file processor has been improved to better handle multiple files simultaneously.
CAT-6800: URL endcoding for Search has been reverted due to unexpected impacts.
COM-9664: Performance improvements have been done on the Set Fulfillment Info API.
FFMT-4929: Performance improvements have been done on the ReplaceShipmentItemData response.

Find more information about the client-facing bug fixes at these Jira tickets:

The following bug fixes are internal-only and not exposed to clients:

FFMT-4936: Fixed an issue where Solr query execution failed when the number of the parameters exceeded the request header size limit. The request method has been switched from GET to POST to let parameters be sent in the request body instead of the URL to bypass limitations.
CHAR-6265: Failing test cases in the Kibo.Inventory develop branch have been fixed.
CHAR-6370: Fixed an issue where safety stock calculations were wrong for site availability queries when granular inventory was disabled.

Package Consolidation Update: Whenever a shipment is removed from a package consolidation group for any reason (such as if it's canceled, reassigned, or moved to Customer Care), the system will now check to see if only one shipment remains in the group. If so, that shipment will be released from the group so that it can be immediately fulfilled.
Search Pick Wave Rules: You can now use the search bar at the top of the Pick Wave Rules page to look up a rule name or rule code, as well as expand the Advanced filter menu to search by keyword, status, or creator. A filter button is also displayed on the pick wave creation screen which allows you to more quickly select the rule you want to use.

Service	Resolution
Catalog	The KRW currency symbol was displaying as a question mark (?) on the storefront and Admin UI. This has been fixed so that the correct symbol is displayed.
Commerce	Attempting to create a new customer account from the storefront resulted in an exception error indicating a missing Cart ID or User ID. This has been corrected so that accounts can be successfully created as expected.

Find more information about the client-facing updates at these Jira tickets:

The following enhancements are internal-only and not exposed to clients:

FFMT-4940: FFMT microservices have been updated to use the new inventory management service instead of legacy APIs.
COM-9752: Improvements have been made to attribute sorting and filtering logic, such as mapping to optimized Solr field formats.
CHAR-6378: Code formatting has been standardized across CHAR repositories.
CHAR-6397: New Inventory Refresh and Adjust API endpoints (.../v5/inventory/smart-adjust and .../v5/inventory/smart-refresh) have been created to dynamically route between sync and async operations based on payload size and performance.

Find more information about the client-facing bug fixes at these Jira tickets:

The following bug fixes are internal-only and not exposed to clients:

COM-9772: Fixed an issue where a deadlock caused errors during shipment creation.
COM-9770: Fixed an issue where EU DM pods were running at an unexpectedly high memory usage.