July 8, 2025 — 1.2526 Service Update

Announcements

Cybersource Updates

Cybersource will soon be enforcing new security mandates for integrations currently using their SOAP APIs. As a result, Kibo is releasing a new payment gateway adapter and an updated version of the Decision Manager application that utilize REST API credentials. If you are integrated with Cybersource, you must take action to switch to the new gateway and application in your sandboxes and provide updated credentials according to the directions in the Payment Gateways and Decision Manager user guides.

You should test all relevant payment scenarios to make sure they still work as expected. You have until Cybersource's final deadline of July 16 to switch over your production gateway and application. Please contact Kibo Support if you have any questions.

Inventory API Migration

As part of ongoing migration of internal inventory endpoints, Kibo will be migrating the import inventory internal endpoints on production tenants from June 10 through July 15. The endpoints on sandboxes were already migrated.

This is the second of three phases of inventory migration planned for 2025. No action is required from you but if you have questions, please contact Kibo Support.

Production Tenant Features 

Commerce

  • Pending Shipment Order Edits: Order Management implementations can now edit orders and order items that are in the Pending Shipment status, where previously those actions were restricted to implementations with eCommerce. Repricing may occur depending on whether your implementation includes a catalog or not, and those with catalogs can enable or disable the behavior in their site settings. These updates went out to sandboxes early on Wednesday, June 18.
  • Subscription Pricing Updates: You can now configure subscriptions to offer more flexible pricing for continuity orders. New site settings can now be enabled to update pricing to the latest values at the moment a continuity is created and/or honor the lowest available price. The lowest available price is determined by comparing the updated continuity order total with the original subscription total. 

Fulfillment

  • Location Group Update: When configuring the fulfillment carriers of a location group, the list of carriers will now be sorted into those that offer Shipping and those that offer Delivery. This makes it easier to find specific carriers and identify their purpose.
  • Delivery Shipment Update: Minor tweaks have been made to the search results page in the Fulfiller UI for displaying Delivery shipments, such as changing labels from "Picked Up" to "Delivered" on completed shipments and removing the irrelevant Resend Shipment Fulfilled Email button.

Production Bug Fixes

Service Resolution
Catalog Variation product codes were not updated in the Admin UI after importing products through the Import/Export tool. This has been fixed so that variations are properly updated to match their imported data.
Catalog A sitewide promotion suddenly stopped appearing on product listing pages where it had been previously been displayed, though it was still active. This has been fixed so that these discounts properly appear on listing pages as expected.
Fulfillment Some store employees were able to see the shipments of other locations in the Fulfiller UI on their dashboards and search results. This has been corrected to ensure that only the shipments of the user's assigned location will be displayed.

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:

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

  • Variation Product Code Updates: CAT-6625 (reported by Skillnet)
  • Promotions on PLPs: CAT-6646 (reported by French Toast)
  • Other Location Shipments in FFUI: FFMT-4835 (reported by Sun & Ski)

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

  • COM-9075: Fixed an issue where orders in the queue were not being processed due to the missing QueuedOrderLocks collection.
  • CHAR-6242: Fixed an issue where the TransitionCartItem Java model was missing the transitionItemId field.
  • CHAR-6266: Fixed an issue where regression allocation jobs were getting stuck during automation test cases.
  • CAT-6637: Fixed an issue where crashes with SQL reader errors were experienced on Product Runtime.
  • CAT-6587: Fixed an issue where sonar scans weren't working with API Extensions.
  • CAT-6624: Fixed an issue where Site Builder was making excessive calls for theme metadata and inline CSS.

Production Sandbox Features 

Catalog

  • Google Feed Update: The Google feed integration has been updated to allow more than one brand attribute on an item, such as having three properties for tenant~brand, tenant~brand2, and tenant~brand3. In this case, each attribute will be displayed in its own column on the export file. Note that even if you only want to use one brand, it must be set up as tenant~brand or else its column in the export file will be empty.

Fulfillment

  • Block Assignment Update: Opting to exclude your location from future assignment while splitting an STH, Delivery, or Transfer shipment now offers the additional option to remain excluded even after inventory refreshes. Previously, excluded locations would always become available for assignment again at the next refresh by default. Any locations that have been blocked are displayed in a new Manage Blocked Locations page of the Fulfiller UI, where you can manage their block preferences as needed to better control assignment.
  • Delivery Updates: Some changes have been made to better support Delivery fulfillment.
    • Delivery shipments can now be included in pick waves as long as they are using the most updated Delivery fulfillment flow (the version that includes Dispatch and Delivery Confirmation steps).
    • Package Consolidation can now be used to consolidate Delivery shipments across multiple orders for the same customer, as long as they are using the most updated Delivery fulfillment flow. A "Package Consolidation Available" button will be displayed on qualifying Delivery shipments in the Fulfiller UI and allow you to proceed with consolidating all relevant packages in the same manner as STH shipments.

Inventory

  • ATS and ATP: Granular inventory fields for conditions and/or expiration dates can now be used to adjust how Available inventory counts are calculated, letting you reflect more accurate Available-to-Sell (ATS) and Available-to-Promise (ATP) levels on your storefront. Once these fields are set up, the Inventory UI will display filters that let you select whether to exclude expired products or include condition availability in inventory results. You can display ATS and ATP counts on your storefront by providing similar flags when calling the real-time inventory service APIs.
  • Redistribution API: A new API endpoint,  POST .../v1/inventory/redistribute, is now available that accepts a list of UPCs and/or location codes to redistribute segmented inventory across on demand. This lets you react quickly to inventory depletion in sales channels, as it will trigger asynchronous redistribution at the next Refresh or Adjust update and restore the appropriate amount of inventory to those channels (based on their configured allocation percentages). This functionality replaces the the nightly redistribution job that Kibo previously performed for all implementations. The API documentation will be updated soon, but refer to the Inventory API Overview guide for an example and how the scope is determined based on the fields you provide.

Order Routing

  • Location Type Filter: When configuring Order Routing filters, Location Type can now be selected as an attribute under the Location options. This allows you to create filters that assign shipments to locations that belong (or don't belong) to a specific type you have set up, such as warehouses or retail stores.

Sandbox Bug Fixes

Service Resolution
Commerce Timeouts were occasionally experienced from the Get Accounts API when two calls were made within a second of each other. This process has been improved with better asynchronous handling to avoid this issue in the future.
Commerce When navigating between orders in the Order Admin UI using the Next Order button, the Site ID was not always updated correctly and thus order audit logs and shipments failed to load. This has been corrected so that order details will be able to retrieve the appropriate context and load all order information.
Commerce Unnecessary emails (such as account creation, status changes, and welcome notifications) were being sent when creating B2B users, instead of being suppressed according to the site settings. This has been fixed so that all B2B email types properly respect their corresponding site setting toggle.
Commerce Some custom data points on order lines could not be edited after shipments were created if they were strings with number values. This has been corrected so that all non-boolean custom data values can be updated as expected.
Commerce The fulfilled quantity of Digital shipments (which are automatically fulfilled upon order placement) was not being updated in the order summary details. This has been fixed so that the quantity displayed in the summary is consistent with the actual quantity.
Commerce Disabled STH Consolidation in the site settings did not automatically disable its nested settings as expected, causing issues such as forced consolidation still being attempted. This behavior has been updated so that the system always verifies whether the STH Consolidation feature is disabled or not before implementing any of its related actions.
Fulfillment Shipment item quantities were not adjusted as expected after attempting to split a shipment with parent and child items during the Validate Stock step. In this case, the shipment progressed to Print Packing Slip with the full item quantities instead of actually being split. This has been fixed so that partial stock situations with parent and child item relationships can be split successfully.
Subscriptions Some subscriptions experienced a "system does not permit the attempted action" error that prevented them from creating an order. This was due to a caching issue, which has now been corrected so orders can be successfully submitted.

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:

  • COM-9617: Actions that should not be available to OMS Only and OMS + Catalog (with Refresh Pricing on Order site setting disabled) are now blocked on the Order Admin UI when editing a Pending Shipment order. This includes changing the fulfillment type or shipping method, adding or removing coupons, and removing order-level discounts.
  • COM-9591: Incompatible cgroupv2 applications have been updated.
  • COM-9601: EDD data has now been exposed to email templates.
  • FFMT-4755: Kibo.Fulfillment is now hardcoded to always call the Order Routing proxy service.
  • FFMT-4839: Cleanup has been done to fulfillment-related API logs.
  • CHAR-6189: Performance testing and improvements have been done on safety stock rules.
  • CHAR-6184: Suggestion logs have been updated to improve persistence and better work with deserialized data.
  • CHAR-5906: Aggregate and GraphQL Inventory APIs have been updated to take into account safety stock, in which granular inventory will only calculate it a single time per UPC.

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