Announcement: FFUI Dashboard and Returns
In 2024, Kibo made a new version of the Fulfiller UI dashboard available for enablement, which also enables you to implement Fulfillment SLAs if you want to use them. Another update in which the Admin UI's return dashboard is embedded within the Fulfiller UI was added to sandboxes as of Version 1.2510, giving fulfillers more robust return management.
As of April 30, both of these updates are enabled in all sandbox environments. Please begin testing these features. They will be deployed to production tenants on May 27, at which point all Fulfiller UI users will see the updated interfaces. Please contact Kibo Support if you have any questions.
Production Tenant Features
This production release is being postponed by two weeks, meaning that the updates listed here will be pushed to production tenants alongside the new sandbox updates on Tuesday, May 27.
Catalog
- Rules Performance Enhancement: When accessing product rules for Return Rules, Safety Stock Rules, and Purchase Limit Rules, the data will now load faster.
Fulfillment
- Digital Shipment Update: Digital shipments will now be marked as Fulfilled when their order is moved to the Accepted status, instead of immediately upon order creation.
- Shipment API Extensions: New before and after API extensions have been added that can interact with the Get Shipment and Get Shipments APIs. This allows you to leverage custom tasks such as rewriting shipments to display a total bundled quantity instead of the individual quantities within a bundle.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Commerce | A "shipment expected delivery date is not aligned with items expected delivery date" error was experienced on some implementations when creating shipments with estimated delivery dates. This has been corrected so that dates are set on the shipment items as intended, and shipments are split appropriately based on the full estimated date-time (instead of only the date). |
| Fulfillment | Users without the "Report Read" behavior were unable to access Fulfillment APIs. This has been updated so that this behavior is no longer required. |
| Fulfillment | The pick wave link was not appearing in the Fulfiller UI's navigation menu after the most recent release. This has been fixed so that pick waves are accessible as expected. |
| Order Routing | Some null errors were experienced when retrieving newly created locations' fulfillment capacities for Order Routing. This has been fixed so that these location capacities can be successfully accessed. |
Internal Production Details
Find more information about the client-facing updates at these Jira tickets:
- FFUI Migration Announcement: FFMT-4740
- Rules Performance Enhancement: CAT-6397
- Digital Shipment Update: FFMT-4723 (requested by Sun & Ski)
- Shipment API Extensions: FFMT-4756 (requested by Total Wine)
- Note that several updates have been made for adding Japanese localization support to the Admin UI, but this will not be listed in public release notes until all aspects are complete.
The following enhancements are internal-only and not exposed to clients:
- CAT-6425: Kibo.CatalogUI has been run locally on gdev environments.
Find more information about the client-facing bug fixes at these Jira tickets:
Production Sandbox Features
Catalog
- Category IDs in Google Feed: Additional category data related to Category IDs, such as those of parent product categories, are now included in Google Feed exports.
- Dynamic Category Expression Update: When configuring dynamic category expressions via the UI, the
productNamefield now supports using CONTAINS.
Commerce
- Custom Returns Error Message: If an error message is specified via the returns.actions.before API Extension (using
throw new Error('MESSAGE HERE')), then the custom text will now be displayed on the Admin UI's error notification banner when triggered.
Fulfillment
- Partial Consolidation Fulfillment: When an STH or Delivery consolidation shipment contains both available items and items awaiting transfer, you can now fulfill the available items right away. Once enabled in your consolidation site settings ("Allow Partial Fulfillment"), call the POST
.../api/commerce/shipments//itemsReadyForPackAPI endpoint with a list of line item quantities, such as in the below example. This will move those items to a new shipment that can immediately continue with fulfillment. The transfer items will remain in the original Waiting for Transfer shipment until they arrive and can be fulfilled. The ability to do this through the Fulfiller UI instead of an API call will be added in a future release.{ "items": [ { "lineId": 1, "quantity": 2 }, { "lineId": 2, "quantity": 1 } ] }
Search
- Similar Products in Vector Search: The vector search now supports a query where, if a specific product is specified, the results will return other similar products. This query is formatted with the starting pattern "products like productCode:{CODE}" where a valid product code is provided and the search settings have vector search enabled.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | Shipping subtotals were not being returned in priced orders when set to ship via flat rate shipping. This has been fixed so that order pricing always includes the appropriate shipping subtotal. |
| Catalog | Dragging and dropping member products within a collection didn't always generate the associated API call, meaning that deleted products sometimes were not removed from the collection. This has been corrected so that adjusting collection products retains updates as expected. |
| Catalog | The "Minimum Category Purchase Amount" setting didn't allow a value higher than $999.99, in which case it would automatically alter the value to fit. This has been updated so that you can successfully a higher minimum purchase value. |
| Commerce | The Get Login State API did not always update with the accurate latest login date. This has been fixed so that the login history is more accurately tracked. |
| Commerce | Order attributes were not being populated in the return data for some orders. This has been corrected so that returns going forward will always retain their attributes, though past returns will require that information to be retrieved via the corresponding order items instead. |
| Commerce | The Order ID was missing from the authorization interaction data on some orders for Order Management implementations. This has been fixed so that the ID is provided as expected. |
| Commerce | Declined orders were unable to be tested from the Kount application on sandboxes, as it did not register declined orders. This has been fixed so that orders can be tested and its errors can be viewed while Kount is enabled. |
| Fulfillment | Importing historical orders triggered shipment events, which were not necessary for past completed orders. This process has been updated so that fulfillment events will not be erroneously generated by historical order imports. |
| Fulfillment | Searching for an order or shipment outside of a Fulfiller UI user's store association by its shipment number or external order number did not return any results. This behavior was originally intended to be an opt-in setting, while the default Fulfiller UI behavior was to return search results for these cases. This has been corrected so that by default, results outside of a user's store associations will be returned. |
| Fulfillment | Delivery orders with transfer shipments were not getting created after order routing if inventory wasn't available, resulting in order cancellations. This was due to the pickupLocationCode missing from the Order Routing Suggestion data, which has now been fixed so that orders can be successfully created. |
Internal Sandbox Details
Find more information about the client-facing updates at these Jira tickets:
- Category IDs in Google Feed: CAT-6468 (requested by Al Futtaim)
- Dynamic Category Expression Update: CAT-4878
- Custom Returns Error Message: COM-9283 (requested by Perfaware)
- Partial Consolidation Fulfillment: FFMT-4733
- Similar Products in Vector Search: CAT-6477
- Note that several updates have been made for Consolidation with Reservations, but this will not be listed in public release notes until all aspects are complete.
The following enhancements are internal-only and not exposed to clients:
- CHAR-6166: A flyway script has been added for event status indexing.
- CHAR-6045: Some performance enhancements have been made on the Estimated Delivery Dates suggestion process.
- CHAR-5947: The Run Export Settings Job API has been ported to the Inventory Management service.
- CAT-6402: The old ProductCatalogRuntime implementation has been removed, with ProductCatalogRepository and CacheSplitProductRepository being combined instead.
- CAT-6478: GCP auth logic has been updated to allow AWS API calls to fall back onto GCP APIs.
- CHAR-5992: GCS credentials have been added to the Fetch File Config of legacy inventory.
- COM-9546: The API documentation login has been updated with a region selector to support GCP1 and EU.
- CHAR-6154: Kibo.Jobs has been updated to call the Order Routing proxy service.
- COM-9309: Enabling B2B order release and account priority settings are no longer dependent on the
catalog-admin-ProductRulesEnabledtenant attribute.
Find more information about the client-facing bug fixes at these Jira tickets:
- Shipping Subtotal Pricing: CAT-6476 (reported by Ace Hardware)
- Updating Product Collection: CAT-6369 (reported by Al Futtaim)
- Minimum Purchase Limit: CAT-6353 (reported by Ace Hardware)
- Get Login State API: COM-9225 (reported by Sun & Ski)
- Missing Return Attributes: COM-9018 (reported by Pearson VUE)
- Missing Order ID: COM-9542
- Testing Declined Orders in Kount: COM-9490 (reported by Mall of America)
- Historical Shipment Events: FFMT-4757
- Fulfiller UI Search Issue: FFMT-4796 (reported by AM Retail and Laura Canada)
- Delivery Order Cancellations: FFMT-4803 (reported by Ace Hardware)
The following bug fixes are internal-only and not exposed to clients: