Announcements
Code Freeze
KIBO has entered its “code freeze” for the peak holiday season. The production release of Version 1.2640 was the final major update pushed to production tenants until January. Changes will continue to be added to sandbox environments per the below schedule and will be released to production on January 19, 2027:- Version 1.2642: October 27
- Version 1.2644: November 10
- Version 1.2646: November 24
- Version 1.2648: December 8
- Version 1.2650: January 5
- Version 1.2652: January 5
Order Routing — “Group Rank and Quantity” Sort Now Honors Location Rankings
KIBO has corrected behavior in Order Routing: when a strategy’s Candidate Sort Strategy is set to “Group Rank and Quantity”, location rankings assigned within a scenario are now respected. Locations are prioritized by scenario rank → location rank → available quantity, with quantity used only as a tiebreaker between equally ranked locations. Previously, location rankings were ignored and orders were assigned to whichever eligible location held the most inventory. The Routing Debugger already reflected the correct behavior; live assignment now matches it. No API, integration, or data changes are required. Who is affected: Clients whose routing strategies use the “Group Rank and Quantity” candidate sort in scenarios with more than one location. Note that every scenario built in the Order Routing UI carries rankings; the list order of locations is the ranking, even if you never set them explicitly. Strategies using Minimize Shipments, Quantity, or Distance are not affected, as are single-location scenarios and scenarios where all locations share the same rank. Review your location rankings and validate affected strategies in Sandbox before the Production release. Available for validation in Sandbox from October 27, 2026 (v1.2642), and takes effect in Production on January 19, 2027 — the first Production release after KIBO’s peak-season code freeze, giving approximately 12 weeks to test. To identify affected strategies, check the Candidate Sort Strategy field on the List Strategies page in the Order Routing UI. For a detailed before-and-after example, step-by-step testing instructions, and expected outcomes, see the Support Portal article Action Required: Order Routing — “Group Rank and Quantity” Sort Now Honors Location Rankings. Please contact Kibo Support if you have any questions.Production Sandbox Features
Commerce
- Payments – Support for Declining Credits from
- Async Payment Gateways: Added the ability to perform the Decline Payment action when a credit is performed by async payment gateway. When a payment service provider (PSP) asynchronously declines a credit transaction, merchants and integrations can now transition the payment to Declined—accurately reflecting the failed credit amount rather than leaving the payment indefinitely in CreditPending.
- Reinstate Returnable Quantity on Return Closure: Added the ability to automatically restore returnable item quantities when a return is closed. Closing a return now makes any remaining eligible item quantities returnable again for future return requests. Note: Returnable quantity reinstatement on return closure is controlled via a tenant-level setting. Contact KIBO Support to enable this capability.
Inventory
- In-Transfer Inventory Visibility: A new In-Transfer tab on inventory records in the Supply/Demand UI shows how many units of a product are on their way to a location via transfer shipments — split into Awaiting Fulfillment (created but not yet shipped from the source location) and In-Transit (shipped but not yet fully received). Click Allocation icon on either quantity to open the Shipments page pre-filtered to the underlying transfer shipments. Transfer shipment details now also display the Transfer To (destination) location alongside Transfer From, giving the full transfer route in one view. See In-Transfer Inventory documentation for more details.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Commerce | Fixed an issue where generating or downloading Swagger specifications for the Location and Customer APIs failed with an HTTP 500 error. API specifications for both services now generate and download properly. |
| Commerce | Fixed an issue where a shopper’s active cart still contained purchased items after order submission when they logged in mid-checkout. |
| Fulfillment | Fixed an issue where Fulfillment API requests referencing a missing or deleted order — for example, reassigning a shipment or creating a shipment with an invalid order identifier — returned a generic internal server error instead of a meaningful error response. These requests now return a clear, appropriate error response. |
| Fulfillment | Fixed an issue where a shipment containing an invalid date value could cause new shipments to stop appearing in shipment search results — in the Fulfiller UI and via the Shipments API — until a manual reindex was performed. Shipments now remain indexed and searchable regardless of invalid date value. |
| Inventory | Fixed an issue where the Refresh Inventory API silently dropped part numbers with a value of “0”. The API returned a success response, but the part number was not saved — inventory lookups by that part number returned no results, and inventory could not be matched for admin-created orders. Part numbers with a value of “0” are now saved and returned correctly. |
| Order Routing | Fixed an issue where order routing requests could periodically stall for several seconds — in some cases nearly a minute — slowing checkout responses and occasionally causing Estimated Delivery Date requests to fail with errors. Checkout routing and delivery-date responses no longer experience these periodic stalls, and response times are consistently fast. |

