May 29, 2024 — 1.2420 Service Update


As part of ongoing enhancements to the Real-Time Inventory Service, Kibo is continuing to migrate our internal inventory endpoints.  We will be migrating the aggregate inventory internal endpoints from April 30 through May 31. No action is required, but if you have questions then please contact Kibo Support.

Production Tenant Features 


  • Reject Shipments in Payment Error: The "Reject Shipment" button is now available for Substitution flows in alignment with existing functionality for payment errors during fulfillment. A shipment may go into payment error due to substitute's price being higher than the original product. While the fulfiller cannot proceed with actions to fulfill it, they should still have the flexibility to reject a shipment.


  • BOPIS Subscriptions: Subscriptions can now be created with pickup items (or a combination of pickup and direct ship), where previously only direct ship was supported. You can quickly switch between pickup and direct ship fulfillment when viewing the items table in the subscription details, including when updating the next order only or placing an order now. Delivery and alternate pickup contacts are not currently supported, only in-store pickup by the primary contact. 

Production Bug Fixes

Service Resolution
Catalog Errors were experienced when placing large orders through the Admin UI (such as those with 30 or more items), due to database issues caused by the amount of order data. This has been fixed so that large orders can be successfully created.
Catalog Some errors were experienced when retrieving vocabulary values via API in which mapped values were missing from the response. This has been corrected so that the correct amount of values are returned.
Commerce BOPIS shipments with no inventory were incorrectly handled when inventory reservation was enabled, resulting in duplicating the item between the parent shipment and the resultant Customer Care shipment. This has been fixed so that the unavailable item is properly moved to the Customer Care shipment.
Commerce Duplicate shipments were being created due to unexpected behavior from bulk shipment creation APIs. This process has been fixed so that extra shipments are no longer created.
Commerce The inventory allocation process could not handle cases where there was negative available inventory for reservations, resulting in erroneous allocation of the negative inventory plus the order quantity. This has been corrected.
Fulfillment When a return was created via API with a specific return processing fee applied, the fee was not taken into account by Fulfiller UI returns and thus the customer was refunded more than the intended amount. This has been fixed so that fulfiller returns appropriately subtract the processing fee from the total refund.
Inventory Sorting fields were not working in the real-time inventory service, resulting in a broken Inventory UI page that did not allow page sorting. This has been corrected so that real-time inventory records can be sorted as expected.


Restricted Content

Internal Production Details

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

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

  • CHAR-5477: The Suggestion Log API can now be used with or without a trailing slash in the endpoint, where previously a slash was required even though that was against REST standards and prevented test calls from being made through the documentation site.
  • CAT-3519: The SolrSchemaManager has been updated to .NET6.
  • CHAR-5312: Internal fulfillment calls being made to the PHP version of Get Inventory API have been switched to the new Java version of Get Inventory to utilize real-time inventory.
  • More work has been done as part of the Import File Processor project to parse CSV imports, de-duplicate inventory, and transform files to standard XML format.

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

  • COM-8551: Fixed an issue where the installment service was throwing null reference exceptions around payment data, as well as a related problem where jobs would hang after adding a duplicate Account ID and not logging the error.
  • FFMT-4278: Inventory allocation and deallocation was not being properly logged for non-RIC implementations, making it difficult to investigate overallocation for These logs have now been added so that allocation cleanup can occur for the client soon. 
  • CAT-4548: Some older environments were using a different Namespace ID for "tenant" than newer environments. The system will now check the second ID if it does not find the expected tenant in the first ID it looks at.

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

  • Errors with Large Orders: CAT-4598 (reported by French Toast)
  • Missing Vocabulary Values: CAT-4695 (reported by Specialty Commerce)
  • BOPIS Item Duplication: COM-8638 (reported by Honey Birdette)
  • Duplicate Shipments from Bulk API: COM-8625 (reported by Honey Birdette)
  • Negative Inventory Allocation: COM-8624
  • Return Processing Fee: FFMT-4311
  • RIS Inventory Sorting: CHAR-5248 (note: usually defect tickets are not reported in release notes, but this was specifically requested to be included)

Production Sandbox Features 


  • Multi-Locale Catalogs (EU Sandbox Hold): This feature allows you to configure catalogs that support multiple locales. You will be able to switch to any of the supported locales when viewing the product, product attribute, category, and discount configuration pages. Then you can change language-specific fields, such as product names and descriptions, to easily localize the content for that locale. For more general information, see the Catalog Structure guide.

    If you want to use this feature on an existing implementation, then you must contact Kibo Support to be upgraded to a new version of the Catalog Admin APIs and then rewrite your requests to provide a localizedContent object. The API documentation has been updated to reflect the new request models. If you upgrade and still need to manage product data that hasn't been rewritten to the new model, you will be able to call the original version of the APIs without localization by including an x-api-version header set to "1" in your request. If you do not upgrade, then your current calls will not require any changes.

    This update was released to European sandboxes for stability testing on May 21. It will remain there for additional time. Once fully released, it will be available out-of-the-box for all new implementations and existing implementations will be able to upgrade if desired.


  • External Discounts: An application is now available that allows you to apply order and item-level discounts from an external system to orders in Kibo. When this capability is enabled, Kibo will make an API request to the endpoint you provide to retrieve discount information. See the External Discounts documentation for more details about the API request and your expected response, external discount behavior, and installment instructions.
  • Auto Capture Future Shipments: When configuring flexible auto capture, you can now select Future as a shipment state on which to capture the shipment amount. Future shipments are not included in forced auto capture by default, so if you want to capture future shipments then you must do so via flexible auto capture. 


  • Signature Option Expansion: More signature options have been added to the UPS package signature integration, such as direct and indirect signatures. These options are now supported for FedEx as well, so packages being delivered by either carrier can make use of these delivery requirements.

Order Routing

  • UI Enhancements: Following recent changes to the Order Routing UI, additional enhancements have been made to improve user experience. A link back to the routing strategy is now available when viewing the Scenarios page, making it easier to return to that page without re-navigating through the main routes page. The "Transfer to Store" fulfillment option has also been renamed to the more comprehensive "Transfer to Location." Finally, some theme colors have been changed.

Sandbox Bug Fixes

Service Resolution
Catalog Attributes could not be removed from the base product type because they were configured to be inherited from that product type. This is corrected so that attributes are not incorrectly marked as inherited and the base product type is not blocked from editing.
Catalog Merchandizing rules did not allow more categories to be added after the initial set of categories was saved, as they would not be displayed in the UI. This has been fixed so that all categories added to a merchandizing rule are properly displayed.
Import/Export Exports were timing out across all Import/Export categories. Performance improvements have now been implemented so that files can be successfully generated and downloaded.
Order Routing When exporting custom data lists as a CSV file from the Order Routing UI, a Bad Request error was experienced that prevented download. This has been fixed so that the data is successfully converted to CSV and downloaded.
Order RoutingSetting up a distance-based filter was not working as expected, as fulfillment locations would be returned that were more than than the maximum distance from the shipping address. This has been corrected so that location distances are properly calculated and filtered out.


Restricted Content

Internal Sandbox Details

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

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

  • CHAR-5514: Indexes have been added to the inventory databases to enable Singer ingestion for the inventory turnover report.
  • FFMT-4268: The Fulfillment WebApi service has been migrated to Solr 9.
  • COM-8457: Sample test implementation has been created in CRT or Customer.
  • COM-8652: Order Date and Order Date Item APIs have now been marked public.

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

  • CHAR-5419: Fixed an issue where Order Routing error logs did not include the correction ID.
  • TECR-365: Fixed an issue in about circular reference in the headless app build log.

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

  • Inherited Product Attributes: CAT-4819 (reported by Pearson VUE)
  • Merchandizing Rule Categories: CAT-4678 (reported by Peak Activity)
  • Import/Export Performance: CAT-4478 and CAT-4921 (reported by United Hardware and Al Futtaim)
  • Order Routing Export: CHAR-5436 (reported by French Toast)
  • Distance Filter Not Working: CHAR-5505 (reported by London Drugs)