Production Tenant Features
Catalog
- Shipment Rules with Attribute Support: Merchants and administrators can now create and update shipment rules that include custom attributes via the Product Admin API. The new attribute-based CRUD endpoints accept rule attribute definitions as part of the shipment rule payload, persist them correctly, and return actionable validation messages for unsupported or invalid attribute inputs. The rule evaluation and preview APIs have been updated accordingly to correctly interpret attributes when assessing rule outcomes.
- Shorter Category Names Now Supported: The Admin UI and portal no longer enforce a minimum three-character length requirement when saving category names. Merchants working with languages such as Chinese, where semantically complete category names may be only one or two characters, can now create and save short category names without receiving a validation error. This change affects the category name input validation in the Admin portal; no backend API changes were required.
- Improved Error Handling for Complex Search Queries: The product search service now returns an HTTP 409 Conflict response with a clear
searchQueryTooComplexmessage key when a query exceeds the supported filter complexity threshold (for example, a filter containing more than 4,096 OR predicates). Previously, these overly complex queries produced an uninformative HTTP 500 Internal Server Error. The updated error response is consistently returned across regions and is structured to include the standard Kibo error envelope fields (errorCode,message,correlationId,MessageKey), making it easier for downstream callers to detect and handle this condition programmatically. Behavior for all other error types is unchanged.
Fulfillment
- Incremental, Line-Item-Level Stock Validation: The fulfillment system now supports stock validation at the individual line-item level across multiple scanning steps. Each item is independently assigned a stock availability status (fully available, partially available, or unavailable) when finalization is triggered, and the shipment automatically advances to the next workflow step once all items are resolved — no manual trigger required. Items can also be reset and re-validated as needed. The new behavior applies consistently across all shipment types and supports substitution workflows for line item stock validation.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | Fixed an issue where Admin users with their browser language set to Korean saw only the Home and Help menu options upon logging in — the full Admin navigation menu was missing. The root cause was a corrupted locale file (ko.json) produced by an automated translation package that incorrectly overwrote navigation-related keys. The locale files have been corrected, and the full Admin menu is now displayed correctly for Korean-locale users. Other affected language locales were also restored as part of this fix. |
| Catalog | Fixed an issue where a line item product discount configured with a MaxRedemptionsPerOrder limit was not applied at all when a second unlimited line item discount targeted the same items. For example, when a 30%-off discount (max 1 per order) and a 10%-off discount (no limit) were both active, items at quantities of 3 or more received only the 10% discount instead of the expected optimal combination (1 item at 30% + remaining items at 10%). The tiebreaker ordering logic has been corrected so that limited discounts are evaluated and applied alongside unlimited discounts as expected. |
| Catalog | Fixed an issue where the price list associated with a customer segment was not consistently applied for logged-in users. When a user closed and reopened their browser, the segment-based price list was intermittently ignored and the site default pricing was shown instead. The resolution ensures that price list resolution is correctly persisted and restored across browser sessions, so segment-based pricing is reliably applied on every request for authenticated users. |
| Commerce | Fixed an issue during cart takeover sessions where a customer’s assigned price list reverted to the default price list, causing price validation errors upon submission. The system now correctly retains the customer’s assigned price list throughout the agent session. |
| Fulfillment | Fixed an issue where enabling the http.commerce.fulfillment.getShipment.before Arc action caused the Fulfiller UI to fail when associates attempted to accept a shipment. Shipment acceptance and other fulfiller workflows now complete successfully when Arc actions are enabled on the getShipment endpoint. |
Production Sandbox Features
Inventory
- Future ATP — Cancel Future Inventory PO and Reassign Allocated Shipments: When a future inventory purchase order (PO) is cancelled, the system automatically reassigns any Ship-to-Home and Delivery shipments that were allocated to that PO. These shipments re-enter the standard fulfillment assignment process — checking for available inventory across eligible locations — so orders continue moving forward without any manual intervention. If the cancelled PO had no shipments allocated to it, the record is simply removed with no further impact.
- Future Inventory Fields in Delta and Full Inventory Exports: The delta and full inventory export jobs now include future inventory data alongside current inventory records. Exported records include future on-hand, available, and allocated quantities along with the expected future inventory date.
Order Routing
- Location Code and Express Flag Support in Order Routing Filters: Order Routing filters now support
Location Codeas a first-class attribute in the Location filter group. Merchants can build routing rules based on a location’s specific code without needing extensible attributes as a workaround. TheCan Fulfill Express Ordersflag has also been added as a first-class filter attribute in the same location dropdown, enabling more precise routing control for express fulfillment scenarios.
Reporting
- Fulfillment SLA Dashboard: A new Fulfillment SLA Dashboard is now available under Kibo Standard Reports > Shipment > Fulfillment SLA Dashboard. This dashboard provides historical analysis of SLA performance across locations, fulfillment types, and time periods. It also provides a breakdown of each SLA across Compliant, At-Risk, and Non-Compliant thresholds, along with the average time in hours each SLA takes to complete. Users can further drill down into individual shipment workflow steps within an SLA to view average time spent at each step.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | Fixed an issue where coupon sets added to a discount in the Admin UI disappeared after saving and reloading the page. Merchants can now save coupon set assignments to a discount and see them correctly reflected after the page is refreshed. |
| Catalog | Fixed an issue where searching for files using a partial keyword (substring) in the Admin File Manager returned incomplete or no results. Searches now correctly return all matching files across supported formats. |
| Catalog | Fixed an issue where the price list associated with a customer segment was not consistently applied for authenticated users. When a user closed and reopened their browser, they could intermittently see default pricing instead of their segment-assigned pricing. Segment-based pricing is now reliably applied on every request for authenticated users. |
| Commerce | Fixed an issue where shoppers with duplicate or legacy account records could encounter an error and fail to authenticate when using a one-time passcode. Affected users will now either complete OTP sign-in successfully or receive a clear error message at the time the code is requested. |
| Commerce | Fixed an issue where the Avalara Tax Connector required manual configuration updates when deployed under a new or changed URL path. The connector now automatically detects its deployment path, eliminating the need for code changes across environments. |
| Commerce | Fixed an issue where the createCheckout GraphQL API would fail on the first attempt with a “Missing reCAPTCHA Token” error for logged-in shoppers who had saved cards on their profiles. |
| Commerce | Fixed an issue where the “Notes” field values were missing from exported documents when performing a location data export. The system now ensures that location notes are correctly populated and visible in the exported CSV or Excel files. |
| Commerce | Fixed an issue where duplicate orders with the same external order ID were created during periods of high order volume, even when unique external order ID enforcement was enabled. The system now correctly prevents duplicate orders from being created under concurrent order submission scenarios. |
| Commerce | Fixed an issue where subscription details, including subscription IDs and creation event logs, were intermittently missing from order data. |
| Inventory | Fixed an issue where processing multiple inventory files placed simultaneously in an SFTP folder resulted in only some files being processed while others were left unprocessed. The file ingestion service now correctly picks up and processes all files present in the folder during each polling cycle. |
| Inventory | Fixed an issue where delta inventory exports did not filter locations by the configured location groups. The export query only filtered by tenant and timestamp, causing exports configured for a specific subset of locations to return records for all tenant locations instead. Delta exports now correctly apply location group filters, ensuring only the configured locations are included in the output. |
| Order Routing | Fixed an issue where editing the description of one routing strategy also updated the description of other strategies unexpectedly. Strategy descriptions are now saved independently and changes to one strategy no longer affect others. |
| Fulfillment | Fixed a UI rendering issue in the pick/validate step of the Fulfiller UI when a partial quantity cancel was performed on a multi-item, multi-source shipment. After the cancel, one item could appear missing or the item list area could disappear entirely. The correct item quantities are now displayed at all steps, and proceeding through the workflow functions as expected. |
| Fulfillment | Fixed an issue where cancelling a shipment via the BPM workflow did not propagate the blockAssignment and holdBlockAssignment flags to the inventory service. This left the affected location routable after cancellation, allowing subsequent orders to be incorrectly allocated to a location with no available inventory. The cancellation flow now correctly passes these flags to inventory, ensuring the location is blocked from further routing as intended. |
| Fulfillment | Fixed an issue where a BOPIS shipment that went through multiple transfer operations — specifically a first transfer cancelled followed by a second transfer for the same item — had its readyForPickupQuantity field incorrectly zeroed out. This caused all items to be backordered, including items physically available at the BOPIS location. The quantity calculation is now correctly maintained across sequential transfer and cancellation operations. |