Announcements
Payment Services Update
Back-end updates were done to containerize the payment services with Version 1.2514 and held in sandbox for additional time to allow for further testing. These updates are now targeted to release to production tenants on June 24. This should not affect your payment behavior, but you should test your payment gateways in the production environment after that date to verify that they work as expected.
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. Once this update goes to production tenants on June 24, you will 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
- Consolidation with Reservations: Both STH and Delivery Consolidation now work with inventory reservations, though this may result in multiple consolidated shipments as items are evaluated individually. For example, if the quantity of a line item reserved in the cart is increased or a new item is added, then Order Routing may make a new consolidation suggestion for the additional quantity or new item. This would result in multiple consolidated shipments at the time of shipment creation.
Fulfillment
- Multiple Location Consolidation: If a single consolidation location cannot be identified due to location network restrictions (such as if you have transfer hubs that can only transfer inventory to specific shipping locations), then multiple consolidation locations can be used instead. When enabled, Order Routing will be able to filter for an extensible location attribute that you configure to define location relationships in your network.
- Location Cutoff API Update: The
.../commerce/locations/cutoffoverrides
endpoint used for location overrides with the Estimated Delivery Dates feature has been changed to.../commerce/admin/locations/cutoffoverrides
. This will be reflected in the API documentation soon, such as for the associated GET and POST calls.
Order Routing
- Highest Available Inventory Sort: A new sorting option for routing scenarios, Highest Available Inventory, is now available that allows you to prioritize locations with the most available inventory.
Production Bug Fixes
Service | Resolution |
---|---|
Catalog | After removing all of the member products from a collection via the Admin UI, the collection would not be saved properly and the items would still be displayed. This has been fixed so that products can be successfully removed from collections. |
Catalog | Order-level shipping discounts weren't being applied to orders if any products had a discount restriction. This has been corrected so that order-level discounts are still applied as expected (and only line item discounts are restricted). |
Catalog | The localized properties page only displayed an empty grid instead of a full list of properties and their localizations. This has been fixed so that properties will appear as expected. |
Commerce | No search results would be returned if a space was was included in a zip code. This has been fixed so that spaces are handled properly and the correct results will be returned. |
Fulfillment | When inventory was available at only one location, attempting to split the shipment during Validate Stock resulted in an error. This has been corrected so that the remaining quantities will go to Customer Care as expected if inventory cannot be found anywhere. |
Internal Production Details
Find more information about the client-facing updates at these Jira tickets:
- Consolidation with Reservations: COM-9428
- Multiple Location Consolidation: CHAR-6114
- Location Cutoff API Update: CHAR-6202
- Highest Available Inventory Sort: CHAR-6161 (requested by Autozone)
The following enhancements are internal-only and not exposed to clients:
- ICKY-1668: The QZ Tray certification has been updated for the next three years.
- CHAR-6228 and CAT-6547: Nexus repository URLs have been updated to the new primary backend.
- CHAR-6174: Performance enhancements have been done to Order Routing by updating it to use the real-time location shipment count API when checking location capacity during suggestion generation.
- CHAR-6211: All redistribution jobs in production have been removed, as they are being replaced by inventory segmentation updates.
- FFMT-4742: End-to-end QA has been done on the updated Delivery BPM.
- COM-9545: Test Containers support has been added to Commerce Runtime.
- CAT-6589: The gemini-embedding-001 model has been enabled for vector search to allow clients like Ace to experiment and avoid indexing problems from rate limits.
- CAT-6384: Input validation been added to sanitize information in searching, as requested by Ace Hardware.
- FFMT-4665: Some fulfillment-related API logs have been cleaned up.
Find more information about the client-facing bug fixes at these Jira tickets:
Production Sandbox 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
- Exclude Assignment Update: If a fulfiller user chooses to exclude their location from further Order Routing assignment while splitting or reassigning a shipment, they can now opt to keep the location excluded instead of automatically re-enabling it for assignment after the next inventory refresh (which is the default behavior). All blocked locations are now displayed on a new Manage Blocked Locations page of the Fulfiller UI, where they can be manually unblocked as needed.
- Location Groups Update: When configurations 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.
Sandbox 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. |
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. |
Internal Sandbox Details
Find more information about the client-facing updates at these Jira tickets:
- Pending Shipment Order Edits: COM-9592 and COM-9583
- Best Available Subscription Price: COM-9443
- Exclude Assignment Update: CHAR-5611
- Location Groups Update: COM-9337
The following enhancements are internal-only and not exposed to clients:
- FFMT-4777: Some fulfillment tests have been added to increase code coverage.
- CAT-6578, CAT-6576, CAT-6529: Work has been done to reduce API log noise.
Find more information about the client-facing bug fixes at these Jira tickets:
- Variation Product Code Updates: CAT-6625 (reported by Skillnet)
- 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.
- 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.