Production Tenant Features
eCommerce and Order Management Functionality
- 15 Day Subscription Frequency: An additional subscription frequency option for 15 Days is now available, allowing subscribed products to be ordered every 15 days if selected.
- Site Settings UI Rework: As a follow-up to the site settings reorganization in the previous release, some minor corrections have been made to the capitalization of labels such as email templates and setting names.
- Search Orders by Shipment Number: The Advanced Filter menu of the Order Admin search barnow supports searching for orders by shipment number. This is an exact search that will return orders that contain a shipment with that exact number.
- Get Inventory Response Update: The Get Inventory response now returns the
taggedInventorylist with the default tag displayed first. This means that the inventory record for the default tag (such as if STH is the default tag for the OrderType category) will always be displayed at the top of the list instead of at the end. This makes it easier to identify which inventory record is the default and select the ideal future inventory. - Rate Limit Update: Some UI adjustments have been made to the API rate limit tables in the Dev Center. The table headers have been changed to “API Request Limits” and statuses have been changed to “Throttled” and “Ok.” Additionally, the RPM/RPH line has been removed from the production tenant limits.
Fulfiller Functionality
- Ship to Home Consolidation Setting: A new site setting is now dedicated to Ship to Home Consolidation, under the Transfer Shipments section of the general settings. This toggle is disabled by default, but can be enabled to allow STH Consolidation on your site (meaning that transfer shipments can be created for STH parent shipments). Previously, this was enabled with the same settings as BOPIS. The “Always Create Transfer Shipment” setting has also been renamed to “Always Create BOPIS Transfer Shipments” to better clarify these settings. These site settings were added to the UI in a previous update but did not affect the fulfillment behavior – they have now been fully implemented and will determine the behavior of STH-C shipments.
- UPS Declared Values: A new option has been added to the UPS settings of location group configurations, called Use Declared Value. Implementations that need to use a declared value for UPS shipments can enable this option (which is disabled by default) and must then provide Kibo with the maximum value they want to insure. This value is currently set to $7500 and can only be changed by contacting the Kibo team. Then, the declared value will be defined as:
- If the shipment value is less than the maximum insured value, then the shipment value will be used as the declared value.
- If the shipment value is greater than or equal to the maximum insured value, the maximum insured value will be used as the declared value.
Search Functionality
- Merchandizing Rules API Filter: The Get Search Merchandizing Rules API now supports filters to search the rules by their
startDateorendDate. Both filters support gt (greater than), ge (greater than or equals), lt (less than), and le (less than or equals). You can apply this filter with the standard filter format, such as in/?filter=startDate gt DATE.
Production Sandbox Features
eCommerce and Order Management Functionality
- Bundled Item Images: Images can now be displayed for bundled items when viewing order and shipment details tabs, as well as modals for editing orders and creating shipments. Adding a product bundle will display the images of the components if available, where previously nothing would be displayed. If there are multiple images available, then the first one will be shown. Any product extra images will also be displayed in a lower section, and clicking one of these images will add the extra to the order/shipment.
- Editable Refund Quantity: When issuing a refund on a return, you can now edit the quantity of the line items being returned and refunded. The product table now displays three columns for the Returned Quantity, Refunded Quantity, and Refund Quantity. The Refund Quantity defaults to the difference between the Returned Quantity and the Refunded Quantity, but is an editable field. However, validation will ensure that the edited quantity is not greater than the returnable quantity on the order. The system will then calculate the appropriate refund amount based on that quantity.
- Refund Status Updates: The Partially Refunded and Fully Refunded refund statuses have been updated. Previously, the status was determined based on how many line items had completed refunds. Now, these statuses compare the total refund that has been made against the total price and tax amount of the order. If the total refund is greater than or equal to the total price and tax, the return is Fully Refunded. If the total refund is less than the total price and tax, the return is Partially Refunded.
- Returnable Item Update: After rejecting a return, the item quantity is no longer considered returnable for the order. When viewing the Returnable Items tab of return details after a rejection, the quantity is longer listed in the Returnable column and is instead moved to the Rejected column. This prevents any future returns from being created for that quantity.
- Future Inventory in Aggregate: The Aggregate Inventory API, which returns the total inventory across all locations for a given site(s) and product(s), has been updated to include Future inventory when an includeFutureInventory field is included in the request. This parameter can be set to “futureAndCurrent” or “futureOnly” and if not provided, only current inventory will be returned without Future inventory.
OMS-Only Functionality
- Reserve Inventory in Cart: This new feature allows you to reserve inventory for products in a shopper’s cart for a specified amount of time, during which the inventory will be allocated for that customer even if the order is not yet placed. This allows you to guarantee inventory for low inventory items, such as concert tickets or other popular items. This feature is currently only supported for OMS-only implementations, who must leverage the new Reservation API service to create and manage reservation requests from an external checkout, but support for eCommerce implementations will be added in a future release.
- Product Bundle Support: Support for product bundles has been added to OMS-only implementations that include catalogs. When a product bundle is added to an order, the individual components of the bundle will be retrieved. OMS will then calculate item pricing based on those components, in which the difference between the bundle price and the sum of the items’ catalog prices is subtracted from the prices of each item based on the item’s percentage of the overall price. For more information about how this works and how inventory is determined for bundles, see the Product Bundles inventory guide.
Search Functionality
- Case Insensitive Search Terms: Search terms are no longer case sensitive in API queries, allowing Search to match any merchandizing rules that are configured with that term regardless of capitalization.
- Search Merchandizing Updates: More enhancements have been done to support the change from Search Campaigns to Search Merchandizing Rules, ensuring that the Merchandizing Rules UI and APIs support sorting, searching, and create/update/delete actions in addition to the updates below.
- Minor visual enhancements such as greying out invalid start dates, removing mentions of campaigns, the ability to scroll when picking categories, and adjustments to tables and fonts.
- Support for the searchType filter has been added to the Get Search Merchandizing Rules API, allowing you to retrieve rules only for specific search types. For instance, appending
?filter=searchType eq CategorySearchwill only return rules for category searches. - The Search Merchandizing page is now properly localized and will be displayed in the browser language, if a localized version of the page exists for that language. Error messages in the Product Suggestion and Listing sections are also now localized.
- Pagination has been added to the search results preview, with a default page size of 100 results per page.
- You now have the ability to clone a merchandizing rule from either the UI (the Clone button in a rule’s dropdown action menu) or API (
…/commerce/catalog/admin/searchmerchandizingrules/{code}/clone). This will create a new merchandizing rule with the same configurations as the existing rule.
Bug Fixes
The following list summarizes resolved issues for this release.| Status | Resolution |
|---|---|
| Targeted for Production Tenants | Tax codes were unable to be added in the Avalara Tax Calculator and Address Validator, as nothing would happen after clicking “add” in the tax code table. This has been corrected so that tax codes can be successfully added. |
| Targeted for Production Tenants | Errors with item quantities were experienced after performing a short pick on a parent shipment that had transfers created prior to the pick. The parent shipment still displayed the original quantity amount, while the quantity that was not picked was incorrectly cancelled off of the transfer shipment. This has been improved so that parent shipment quantities will be properly reduced if the entire amount isn’t picked, and a new transfer shipment will be created for that quantity. |
| Targeted for Production Tenants | The sorting function was not working as expected on the Customers UI. This has been fixed so that sorting by that column will correctly order the customers in the table based on that field. |
| Targeted for Production Tenants | If a customer entered their credit card and then also selected Gift Card on the checkout page, the credit card information would disappear. This required customers to re-input their credit card if they wanted to use both payment methods. This has been corrected so that applying a gift card in checkout will not remove any existing credit card information. |
| Targeted for Production Sandboxes | New fulfiller users could not be added if they already existed as a fulfiller user at some point (even in another sandbox), due to their email address already being in use. Improvements have been made to user management processes to ensure that if a user record already exists but is disabled or deleted, it can be reactivated successfully. |
| Targeted for Production Sandboxes | Redirects were not being uploaded from CSV files, even though the import gave a successful response. This has been fixed so that redirects are properly uploaded and existing redirects are modified based on the import file. |
| Targeted for Production Sandboxes | The wrong location attribute ID would be updated while attempting to edit a location, preventing the location from being saved. This has been corrected so that locations can be properly saved with the proper attribute definition ID and to prevent this issue from recurring in the future. |
| Targeted for Production Sandboxes | A sale item was conflicting with discounted items, in which adding the sale item to the order caused other items to lose their applied discounts. The logic for applying discount redemptions has now been fixed so that adding a sale item will not remove valid discounts on other items. |
| Targeted for Production Sandboxes | The modal to create a new boost expression in Search Settings did not display the expected attributes to choose from, often returning no results even though valid attributes existed. This has been corrected so that attributes are properly displayed and selectable as options for boost expressions. |
| Targeted for Production Sandboxes | After adding a facet to a category, the category image was removed if the image had been uploaded and mapped directly through the API via middleware. Category images uploaded from the Admin UI were not affected. This has been fixed so that images uploaded this way are better supported and will be retained after a category is updated. |
| Targeted for Production Sandboxes | Calling the Site Search API with a search term included in a merchandizing rule would not return fieldList data, and relevancy scores would be populated under the productCode. This has been fixed so that search merchandizing the fieldList and product data are returned as expected. |
| Targeted for Production Sandboxes | When creating a continuity order from a subscription, custom data for billing data would overwrite general payment data. This has been fixed so that billing data remains in the billing object and payment data is maintained onto new orders. |
| Targeted for Production Sandboxes | Price facet ranges were not updating correctly, as the interface still displayed old price ranges in the search results template after attempting to change the facet’s configuration. This has been corrected so that price range changes are properly saved. |