April 15, 2025 — 1.2514 Service Update

Announcement: FFUI Dashboard Migration

In 2024, Kibo made a new version of the Fulfiller UI dashboard available for enablement. We will now begin the process of upgrading all clients who use the FFUI to this new dashboard. Dates will be communicated soon.

This version also enables you to implement Fulfillment SLAs if you want to use them. Please review the Fulfiller documentation for more information about both the dashboard and SLAs.

Announcement: FFUI Returns Update

An update in which the Admin UI's return dashboard is embedded within the Fulfiller UI has been added to sandboxes as of Version 1.2510, giving fulfillers more robust return management. This is not yet enabled on all implementations, but Kibo will be upgrading all Fulfiller users to the new process over the next few weeks. Dates will be communicated soon.

See the Fulfiller and Admin return guides for more information about these processes. Please contact Kibo Support if you have any questions.

Production Tenant Features 

Catalog

  • Discount Properties: You can now create up to 10 custom properties for discounts via the Admin UI or Catalog Admin APIs. Once created, these properties will be available on all discounts in the master catalog and can have their values set at the individual discount level.

Fulfillment

  • Location Dropdown Update: When you uncheck all locations in the location dropdown of the FFUI dashboard, an error message will no longer be displayed immediately. You can now continue interacting with the dropdown without interruption, allowing you to more easily select new locations. The error message will only be displayed if you click the Filter button to apply the filter with no locations selected.
  • Mobile UI Improvements: Some elements of the FFUI are now collapsible on the mobile view of the FFUI to allow for a better user experience and maximize screen space. This includes the header, footer, shipment and customer details on the pick screen, and filters on the shipment listing page.
  • Pick Wave Updates: A couple more updates have been made to pick waves:
    • You can now change whether the Print Pick Sheet, Print Packing Slip, and Print Single Order Sheets options are checked by default when creating a pick wave. When defaultPrintPickSheetCheckBox, defaultPrintPackingSlipCheckbox, or defaultPrintSingleOrderSheets are set to 1 in your theme settings, then the corresponding option will be checked. 
    • If product identifiers have been set for any shipment items, then an additional Product Identifiers column will be displayed in the pick wave details. This allows item details such as a product code to be displayed for reference alongside the existing UPC and SKU columns.

Production Bug Fixes

Service Resolution
Catalog Product options were not updating in the Admin UI after bulk imports. This process has been updated so that imported data is properly displayed.
Catalog After importing product variants without any localized content, product names were not being displayed on the pricelist entry details. This has been corrected so that product names are not left blank in this case.
Catalog Object reference errors were experienced when updating some sales prices on product variants through the Admin UI. This has been corrected so that product variations can be updated successfully.
Order Routing Product attributes that were set up for Order Routing were not being applied during the suggestion process, which caused some issues fulfilling backorder products with extended product information. This has been fixed so that product attributes are correctly carried over into routing results.

 

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:

  • CAT-6226: The Return Rules endpoints now support a filter for customer rules that will retrieve only the return rules that utilize a matching customer rule. Note that while clients can access this filter, the API docs for these endpoints are currently not available to provide them with a reference. Thus, this update is not announced in the client-facing release notes yet. We are trying to get them updated soon.

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

  • Outdated Product Options: CAT-6281 (reported by Skillnet)
  • Blank Product Names: CAT-6282 (reported by Skillnet)
  • Object Reference Errors: CAT-6289 (reported by French Toast)
  • Routing Product Attributes: CHAR-6036 (reported by Perfaware)


Production Sandbox Features 

Catalog

  • Discount API Update: The GET Discounts API has been updated with better error messaging, so that the missing information is more clearly listed when experiencing a 404.

Commerce

  • Reverse Logistics Update: Some labels in the receive a return process with Reverse Logistics have been updated to replace "handle" with "disposition."
  • Product Rules Update: When creating product rules as part of your Return, Safety Stock, or Purchase Limit Rules, they are now limited to a name with a maximum length of 80 characters.
  • Payment Services Update: Back-end updates have been done to containerize the payment services. This should not affect your payment behavior, but Kibo recommends testing your payment gateways in the sandbox to verify that they work as expected.

Fulfillment

  • Shipment Search Restriction: Currently, the Fulfiller UI will display shipments from all existing stores in the search results. This will continue to be the default behavior, but the option has now been created for Kibo to set your implementation to only display shipment results from the user's assigned store(s) instead.

    Restricted Content
    Internal-Only Note: The tenant setting to enable this behavior is restrictShipmentSearchToUserStore. See the Tenant Attributes resource for more details.
  • Enhanced Delivery Method: The Delivery fulfillment method has been updated to no longer require being set up as a service item. The updated Delivery BPM accounts for new steps to transfer items to a delivery consolidation location, prepare for delivery, dispatch to a delivery provider, and confirm completed delivery. Additionally, Order Routing can now suggest the optimal delivery location based on a Delivery routing scenario and the shopper's zip code. 

    Restricted Content
    Internal-Only Note: Clients (currently only Ace Hardware) who are dependent on the existing Delivery behavior are being kept on the legacy version via the tenant setting classicDeliveryFulfillmentEnabled.
  • Estimated Delivery Dates: The feature previously called Accurate Fulfillment Dates has been replaced by Estimated Delivery Dates, which includes all-new calculations and fulfillment considerations. This version calculates estimated dates for any STH, BOPIS, and Delivery items that can be displayed on your storefront's product details, cart, and checkout pages. This takes into account all transfers that may be required for the shipment as well as the assigned location's daily cut off times in which it is not fulfilling orders. As part of this, locations will now be restricted to one location type going forwards unless specially enabled otherwise for your tenant. The existing Accurate Fulfillment Dates documentation will be replaced by updated content and linked here by the time of release.

    Restricted Content
    Internal-Only Note: If a client needs to continue using multiple location types, the tenant attribute to enable this is AllowMultipleLocationTypes. If they use multiple location types and also begin to use the enhanced Delivery, only the first set location type will be considered while calculating transfer times.

Sandbox Bug Fixes

Service Resolution
Catalog Page rules were not being evaluated properly, resulting in only the base pages being displayed on the storefront and not category page variations.
Catalog If a custom property was removed from a discount via API, the discount configurations could not be saved successfully on the Admin UI. To prevent this, the ability to delete custom properties has been removed.

 

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:

  • FFMT-4736: Location settings are now included in the data returned by filterOptions.locations for the Aggregation API, better supporting the Modern FFUI that doesn't make a separate location call.
  • CAT-5150: Previously, the SQLjob Mongo collection didn't update the table status after a job completed. This is now updated to provide more clarity during debugging.

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

  • Page Rule Evaluations: CAT-6318 (reported by Boscov's and Ace Hardware)
  • Custom Property Deletion: CAT-6343 

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

  • FFMT-4717: Fixed an issue with failures in Rabbit that were associated with excessive SLA shipment notification queue lengths.
  • CAT-6148: Fixed an issue where re-indexing was not working correctly on a dev environment after deleting a product rule and causing a 404.