March 18, 2025 — 1.2510 Service Update

Announcement: FFUI Dashboard Migration

In 2024, Kibo released a new and improved version of the Fulfiller UI dashboard. We will now begin the process of upgrading all clients who use the FFUI to this new dashboard. Sandboxes can begin upgrading as of February 24 and we ask that you test in sandbox once yours is upgraded. Please contact Kibo Support to schedule your upgrade before the target deadline for production cutover, which is currently planned for April 16.

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 is now available in sandboxes with Version 1.2510, giving fulfillers access to more robust return management. The existing functions to create and process returns within the Fulfiller UI will be removed by the end of April 2025. Over the next few weeks, Kibo will be upgrading all Fulfiller implementations to the new process.

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 

Commerce

• B2B Order Release: You can now extend configurable shipment release to hold B2B orders for a period of time before releasing them in a certain order based on the priority that you assign to each B2B account. This allows you to prioritize fulfilling certain B2B account's orders over other B2B or B2C orders with the same items when needed. You can either manually release orders from the Admin UI or set it to occur automatically at a specific interval of time. 
• Rules Configuration: You can now set up "rules" that automatically set safety stock values on location inventory, enforce purchase limits on B2B accounts when releasing their orders, or configure custom return policies. These rules are built on expressions and depending on the type, can be based on product type, code, variant, static category, attribute, customer account, customer segment, or other first class fields. See the Purchase Limit Rules, Return Rules, and Safety Stock Rules documentation for more details about how each rule type works.
  
  

  The sandbox release of all rules have been pushed back to Wednesday, March 5.

• Handling Fee Retention: You can now have your tenant configured to retain an item's handling fee when it is cancelled. In OMS-Only implementations, the line item's handling fee will be redistributed onto other items in the shipment (or onto another active STH shipment in the order, if the entire shipment was cancelled). In eCommerce+OMS implementations that do not distinguish between order-level and item-level handling fees, the total handling fee will be retained.

Fulfillment

• SLA Tracking Update: In addition to the Shipment Status and Shipment Workflow State, you can now also configure your SLAs to track shipments based on their Shipment Workflow Task. 
• SLA User Permissions: Behaviors for SLA Create, SLA Read, SLA Update, and SLA Delete have been added to let you fine-tune which users are able to access and modify SLAs. These behaviors are automatically included on Admin and SuperAdmin user roles.
• Location Fulfillment Limits: Previously, Order Routing scenarios included a configuration that restricted how many shipments a location could fulfill before being temporarily cut off from assignment. That option has now been moved to the Admin UI location configurations under the name Fulfillment Capacity. Locations are unlimited by default, but if you enter a number of shipments and unit of time (hours, days, weeks, or months) then Order Routing will use it as a constraint. Once the limit is reached, Order Routing will exclude the location from assignment when evaluating orders for the time period.
  
  

  This change allows for more accurate application of a location's limits across all routes, but certain implementations who rely on the Order Routing setting will need to update their configurations. Kibo is reaching out to those implementations to provide more details and determine a migration plan before updating your tenants, so your functionality will not be immediately affected.

Order Routing

• STH Consolidation Grouping: The Suggestion API now supports inclusion of STH Consolidation transfer shipments in its shipment grouping.

Production Bug Fixes

Production Sandbox Features 

Commerce

• Substitute Bundles: Bundles can now be selected as substitute products, allowing cases such as substituting a 90oz product with a bundle that consists of a 60oz and a 30oz product. Each bundle component will be displayed in the Order Admin and Fulfiller shipment details and substitution selection options, labelled under the bundle name. See the Substitutions documentation for more details and examples, including how repricing works.

Fulfillment

• Pick Wave Updates: A couple updates have been made to pick waves:
  • The UPC column of the pick sheet now includes a scan field, in which scanning the barcode of those items will update the current picked quantity. This scannable field can be enabled  or disabled with the isItemUPCScanAllowed tenant setting in your Fulfiller UI theme (in which "1" is enabled). Note that this setting also controls scanning functionality in the Validate Stock step.
  • The Close Pick Wave API now supports a quantities.shortageReason such as in the example shown below, which will also be included in GET data. An option to select a reason will be displayed when closing a pick wave via the Fulfiller UI. This is mandatory when the actual picked quantity is less than the required quantity, as it explains the difference in inventory. The API documentation will be updated soon.

    {
    "createRecovery":false,
    "quantities":
     [
      {
       "actualQuantity":1,
       "binName":"Default",
       "productCode":"12345",
       "shipmentNumber":111,
       "shortageReason":
         {
    	  "reasonCode":"ItemNotAvailable",
    	  "moreInfo":""
    	 }
       }
     ]
    }

  • STH shipments can now be moved to a configured fulfillment step upon closing a pick wave, where previously they were always taken to Prepare for Shipment. Shipments are still moved into Prepare for Shipment step by default, so the current functionality is not affected for existing implementations. If you want to change your implementation's behavior, contact your Kibo team for more details.
    
    
    Restricted Content

    
    The tenant attribute for this configuration is fulfillment.pickwave.onCloseSth. If populated with a valid STH BPM step, the shipment will be moved to the appropriate step. If left blank, it will default to Prepare for Shipment. If the BPM step is set to Print Packing Slip, then fulfiller users should not also check the "Print packing slip" option when creating a pick wave.
    

Inventory

• Inventory Locator Update: The character limit of the items.inventoryLocatorName field in Inventory APIs, such as the Refresh call, has been raised to 5000 characters. This allows more flexibility in tracking custom attributes and sorting pick waves.

1.2506 Updates

The following feature was released to sandboxes in Version 1.2506 and is being held there for additional time before releasing to production, which is currently targeted for April 1.

• Reverse Logistics: When this feature is enabled, Order Routing will be integrated into the return process. Upon initiating a return in the Admin UI, Order Routing will automatically suggest the best location to accept the items. Then, you can decide how to handle items (such as restock or disposition) and retrieve Order Routing suggestions for the best location to do so based on the item's condition and your configured routing logic. As part of this update, the return and restock process has been slightly modified for all users even if not using Reverse Logistics. Refer to the Reverse Logistics overview and Receive a Return for more information.

Sandbox Bug Fixes