Production Tenant Features
Fulfiller
- Substitution Partial Quantity Setting: Substitutions will now respect the “Do Not Allow Partial Quantity at Validate Stock” location group setting. If this setting is enabled, then fulfillers can only substitute the full quantity of the original product. They will not be able to substitute only part of the original quantity. More than one substitute product can be used, as long as they add up to the entire original quantity.
- Scan Substitute Quantity: When substituting an item in the Fulfiller UI, you can now use your scan gun to enter the substitute quantity instead of typing it in. This works the same way as scanning quantity in the standard Validate Stock step, and requires the theme level setting to allow scan guns (
isItemUPCScanAllowed) to be enabled. - Mobile UI Enhancement: Better support has been added for the mobile version of the Fulfiller UI, providing a more responsive UI that will not break during the substitution process.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | When a product attribute of the “list” type was assigned as a variant property with the multi-select option enabled, it wasn’t possible to actually select more than one option when applying the attribute to a product. This has been corrected so that multiple values can be selected as expected when the option is enabled for a list. |
| Inventory | After clicking the Manage Inventory link from a configurable product’s detail page in the Admin UI, a generic error message would be displayed. Attempting to search for inventory by the base product code would return an error saying that the code was invalid. This was due to the master catalog context of the Inventory UI being reset to the default even if the product was located in a different catalog. This has been corrected so that the proper catalog will be retained when navigating from the product to its inventory. |
| Order Routing | For a particular implementation’s routing configuration, products that were expected to be assigned to a particular group based on their prefix were not doing so during multi assignment. Order Routing only provided a suggestion for the first line item, and then skipped the remaining order items, resulting in shipment creation failures and the order going into the Validated state. This has been fixed so that all products in an order are evaluated and assigned appropriately. |
| Search | When editing the list of blocked products in Merchandizing Rules, the modal would experience an error if there were more than 200 product types in the implementation. This has been updated so that the system can better handle a large amount of product types when fetching products to display. |
| Search | It appeared that more than 20 products could not be added to the Blocked Products list from the Merchandizing Rules UI, even though additional products would be saved in the backend. This was due to only 20 results being returned from the API after performing the update. This has been fixed so that the full list of updated products is returned and displayed in the UI. Note that the UI still has a maximum limit of 100 limits. |
| Storefront | A Reverse Proxy error was experienced when clicking on a discount from a certain catalog in the Admin UI. This has been corrected so that you can successfully view and search for discounts in the affected catalog(s). |
Production Sandbox Features
Catalog
- Removed Product Ranking: Product ranking rules have been hidden on the Category edit page as well as from the Main > Marketing navigation menu, as that functionality is now available via Search Merchandizing Rules and has been migrated out of the Category service. The tooltip for sort definitions has now been updated to explain that they have been replaced by merchandizing rules.
- Do Not Apply Discounts to Handling: Previously, free shipping discounts applied to order-level handling fees which was not compatible with how some free shipping discounts were intended to be used. For example, a product with a $10 handling fee would receive both free shipping and free handling when the discount was applied. Now, a new tenant attribute (
DoNotApplyDiscountsToHandlingFees) can be enabled to exclude handling when calculating order-level shipping discounts. Contact Kibo Support or your enablement team for assistance enabling this if you need this behavior on your tenant.
Fulfiller
- Substitutes in Return Receipts: When an item has been substituted for another in a shipment, the substitute will now be displayed in a separate table on the return receipt. This table will give the name of the original item that was substituted, as well as the substitute item itself and the quantity. This makes it easier to identify substitutes in more aspects of the fulfillment process.
- Reallocation Error Message: If inventory for an originally-ordered product quantity is not available when a store associate attempts to remove its substitute(s), an error message will be displayed and the substitute quantity will not be removed from the shipment.
- Support for Substitutes with Assembly: If a substitute item requires preparation (aka assembly), then the Fulfiller UI will handle it appropriately during the fulfillment process. This means that it those items will be identified as both substitutes and assembly items, go into the Order Preparation step, and can also be transferred or split into another shipment as needed.
Inventory
- Item-Level Segmentation: Previously you could only apply tags at the order level when using inventory segmentation, meaning that the tag was applied to all order items. Now, tags are supported in item-level data instead. This allows you to specify different tags for each item in an order through the API.
- Segmentation in Order Admin: You can now select the inventory segmentation tags for order items when creating a new order through the Admin UI, as well as when creating a new shipment on an order. You can also view tags from the Order Details and edit them on Pending orders that have not been submitted yet. Additionally, validation has been added for specifically OMS-Only tenants so that if a tag name is provided for an item, then a value for that tag is required.
Search
- Search Schema Relocation: The link for Search Schema in the Admin navigation menu has been removed from the System tab. You should access the schema through Main > Search > Schema instead.
- Delete Merchandizing Rule: Previously, the only way to delete a merchandizing rule was from the action menu on the Merchandizing Rules page. Now, when you click a merchandizing rule to go to its individual configuration page then a Delete option will also be available in the dropdown menu in the top right of the page.
- Merchandizing Rule Limits: A limit has been set to restrict the amount of products included in one merchandizing rule to 100. This limit applies separately to ranked, buried, and blocked products, meaning that you can have up to 100 products in each of those three groups.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | The Get Product API did not consistently return the system~price-list-entry-type property for items with extras, as well as where promotions had expired. This has been fixed so that this property is always returned in the product data for these items as expected. |
| Orders | For implementations upgraded from the previous version of OMS and making API calls through the translation layer, duplicate orders were created when multiple Create Order API requests were received for the same External Order ID. This process has been updated so that a duplicate request will not be passed through to generate a second order. |
| Orders | If a refund needed to be made for an amount of 0.01, there was a rounding issue that resulted in an error when that amount was entered in the UI. This has been fixed so that values of 0.01 can be successfully validated, as well as similar numbers in three-decimal currencies. |
| Order Routing | The Suggestion Logs API did not return the expected location while testing a particular implementation’s filter configuration, due to issues with the inventory service cache. This has been corrected so that the process is more efficient and reduces the number of inventory calls made. |
| Transaction Logs | Shipping data in the Sales Tlogs did not contain the customer phone number, as expected based on the previous version of OMS. This has been corrected so that the appropriate phone number will be included in the log. |