Production Tenant 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 return 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.
Production Sandbox Features
eCommerce and Order Management Functionality
- Category Attributes: You can now configure custom attributes for static and dynamic categories on the Category Attributes page. Similar to customer and location attributes, these allow you to identify categories with custom labels or apply other values to them as needed. These will be displayed on the Admin UI (including support for filtering categories by attribute) and Storefront.
- Subscription One-Time Changes: You can now perform a one-time change on subscriptions to add a one-time purchase product to the next continuity order. This product will not persist on following future orders. The order's discount, tax, shipping, and handling will be re-evaluated and any applicable one-time purchase discounts that are available will be applied.
- Order Admin Logs: Order audit logs will now record when an internal order note is created, when an order confirmation email is resent, and when the order’s email address is edited. Each of these log additions will include the user who initiated the change and the date/time it occurred. Additionally, a new tab called Shipment History has been added to the shipment details when viewing an order in Admin. This tab displays the same shipment log as the Fulfiller UI, including changes in fulfillment, tracking numbers, item edits, etc.
- Delete Future Inventory API: A new API now allows you to delete future inventory records at POST
.../inventory/deleteFuture. In this request, providing a list of location codes along with the part number, UPC/SKU, and future inventory start/end date will delete all future inventory within that given criteria. This API is not yet available in documentation but will be added soon.
Fulfiller Functionality
- Fulfiller Refund Status Support: The Fulfiller UI now fully supports the redefined refund statuses from Version 1.2236. Refunding full or partial shipments in the FFUI will count as Fully Refunded and Partially Refunded respectively, as long as the refunded amount is less than the total order amount in partial cases. The status will not update to Fully Refunded if the total of all refunds is less than the price of the order.
- Future Shipment Date Behavior: The behavior of shipments created with future inventory has been updated. When the expected delivery date of the inventory is changed to a point beyond the configured future date limit, STH shipments will now be reassigned while BOPIS shipments will be moved into the appropriate state (such as Customer Care or Backorder).
- Rejected Shipment Notes: When a shipment is rejected (including when any items are split, reassigned, or transferred), the location that rejected it is now logged in the shipment notes. This note also includes the UPC, Part Number, SKU, Quantity Declined, and the Reason for each rejected product and applies to all shipment types. This helps prevent any confusion when reassigning the shipment, so that it doesn’t get reassigned back to a location that already rejected it.
- Future Inventory on Delivery Shipments: Delivery shipments are now compatible with future inventory, and thus can have inventory allocated to it for future use.
Search Functionality
- Search Merchandizing Updates: Further updates have been made to the new Search Merchandizing feature. The search type filter is no longer case sensitive, some minor cosmetic and rendering changes have been made to the UI, sort definitions have been removed from the Category UI now that they are available in Search Merchandizing, and up to 100 search terms are now allowed per rule. Additionally, the
merchRuleCodeparameter for the Search Debug API has been renamed tomerchandizingRuleCodeand the API documentation will be updated soon.
Bug Fixes
The following list summarizes resolved issues for this release.
| Status | Resolution |
|---|---|
| Targeted for Production Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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. |
| Targeted for Production Sandboxes | After saving a search term that includes a space in a merchandizing rule, the site search results would not reflect that rule’s logic. This has been fixed so that merchandizing rules properly support search terms with multiple words and return expected search results. |
| Targeted for Production Sandboxes | It was possible for quantities larger than the shipped quantity to be input when creating and processing returns in the Fulfiller UI. This has been corrected and validation has been added so that an error will be displayed if a user attempts to return a larger quantity then what was fulfilled. |
| Targeted for Production Sandboxes | The order status field broke on implementations using the “synthesized” mode from a previous version of eCommerce. This has been fixed so that order and order item statuses can be properly updated and maintained, and issues will not be experienced with data imports. |
| Targeted for Production Sandboxes | Avalara defaulted to USD currency to all returns because the currency code was not being provided in requests from Kibo. The Avalara integration has been updated so that the currency code will be provided and returns made in currencies other than USD will be reflected properly. |
| Targeted for Production Sandboxes | After a user failed to successfully login 15 times and was locked out of their account, attempting to reset their password would fail and put them in a loop. This is because locked accounts were not intended to unlock their own accounts via password reset, as it must be manually unlocked by Kibo. The login page has been updated so that a locked user will not be able to click Next and reach the password reset page. |
| Targeted for Production Sandboxes | Returns created in the previous version of eCommerce and imported into KCCP could not be properly loaded, even after switching to the Classic Admin UI as prompted. This has been corrected so that you can successfully load and process the return after switching UIs. |
| Targeted for Production Sandboxes | In a previous release, a fix corrected an issue where the system only checked within the first 200 users on the tenant, and if the user was beyond 200 in the user list then their username would not be displayed in order notes. However, it still required a page refresh for the username to appear. Now, usernames are successfully displayed in order notes the first time without requiring a refresh. |
| Targeted for Production Sandboxes | When a discount was applied to a cart, the expectation was that it would go to the lowest-priced item as configured on the discount. However, this occurred inconsistently across different orders. This has been fixed so that discounts are consistently applied to the lowest-priced item as expected. |
| Targeted for Production Sandboxes | The Price Range facet was not displaying price ranges in order from lowest to highest. Instead, it displayed prices based on the number of products in each range which was not numeric order. This has been corrected so that price ranges are displayed in the logical order instead. |
| Targeted for Production Sandboxes | When price lists were used to have both a regular price and a MAP (minimum advertised price) price on products, the MAP prices were not being honored and a lower price was displayed on the product details page instead. This has been corrected so that when the regular price goes below the MAP, the MAP will be displayed on the storefront instead. |
| Targeted for Production Sandboxes | The “No products blocked” message on the Search Merchandizing Rules page was not localized for French like the rest of the page. This has been fixed so that this text is successfully translated when French is the browser language. |
| Targeted for Production Sandboxes | The user field of shipment notes was blank, instead of displaying the name of the user who created the shipment note. This has been fixed so that user information is successfully retrieved and listed in these notes. |
| Targeted for Production Sandboxes | While trying to set up Vantiv payment gateways for OMS-Only, authentication failures were received. This gateway integration has been updated to better implement transaction authentication. |
| Targeted for Production Sandboxes | The shipping cost was not carrying onto continuity orders for imported subscriptions. This has been fixed so that shipping costs are reflected on new orders as expected. |
| Targeted for Production Sandboxes | When auth failures occurred on subscriptions, its status did not change to reflect the errored state. Now, when a continuity order fails to be created due to an auth failure, the subscription and order payment rollup statuses will be Errored. |
| Targeted for Production Sandboxes | Tax codes could not be added in the Avalara application, as nothing would happen when the user clicked Add and the console returned an error. This has been corrected so that tax codes can be successfully added. |
Internal Release Notes
Production Tenant Features
Client-Facing Updates
- Reserve Inventory in Cart (COM-5826): 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.
- Bundled Item Images (COM-6226 and COM-6201): 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.
- OMS-Only Bundle Support (COM-6160 and COM-6159): 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 its 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.
- Editable Refund Quantity (COM-6100): 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 (COM-6098): 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 Items Update (COM-833): 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.
- Case Insensitive Search Terms (SU-2850): 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.
- Future Inventory in Aggregate (CHAR-4108): 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.
- Search Merchandizing Updates (SU-2615, SU-2253, SU-2480, SU-2367, SU-2738, and SU-2828): 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. There are lots of individual tickets included with this release, so for the full list please refer to Jira.
- 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. - SU-2848 and SU-2765: 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.
- SU-2833 and SU-2831: Pagination has been added to the search results preview, with a default page size of 100 results per page.
- SU-2633 and SU-2569: 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.
Internal Updates
The following enhancements are internal-only and not exposed to clients. As with the client-facing updates, refer to the Search epics and full Jira list for the individual search enhancements done with the updated Search Merchandizing Rules system.
- CHAR-4175: A flyway script has been added to Order Routing to automatically set the
autoAssignLimitsetting to null by default. Previously, some defaults were mistakenly set to 10 which caused failures during smoke tests. This script will prevent those issues from happening again by setting all defaults to the intended null value. - FFMT-3438: Retryable logic for acquiring shipment locks has been implemented, allowing for a maximum of three attempts for acquiring the lock.
- CAT-1725: The number of locations and product codes has been restricted to a maximum of 200 each in the Location Inventory API calls of Product Runtime (POST
…/storefront/products/locationinventoryand GET…/storefront/products/{productCode}/locationinventory?locationCodes={locationCodes}). These limits are configurable in tenant configurations asinventories_endpoint_max_productsandinventories_endpoint_max_locations. - COM-6236 and CAT-1669: Navigational changes have been made to support the updated Inventory UI, redirecting users after clicking Manage Inventory from product details and allowing the page to maintain the product context from the tenant.
Production Sandbox Features
Client-Facing Updates
- Category Attributes (CAT-1448): You can now configure custom attributes for static and dynamic categories on the Category Attributes page. Similar to customer and location attributes, these allow you to identify categories with custom labels or apply other values to them as needed. These will be displayed on the Admin UI (including support for filtering categories by attribute) and Storefront.
- Future Inventory on Delivery Shipments (COM-6302): Delivery shipments are now compatible with future inventory, and can have inventory allocated to them for future use.
- Subscription One-Time Change (COM-6383 and COM-6249): You can now perform a one-time change on subscriptions to add a one-time purchase product to the next continuity order. This product will not persist on following future orders. The order's discount, tax, shipping, and handling will be re-evaluated and any applicable one-time purchase discounts that are available will be applied.
- Rejected Shipment Notes (FFMT-3450): When a shipment is rejected (including when any items are split, reassigned, or transferred), the location that rejected it is now logged in the shipment notes. This note also includes the UPC, Part Number, SKU, Quantity Declined, and the Reason for each rejected product and applies to all shipment types. This helps prevent any confusion when reassigning the shipment, so that it doesn’t get reassigned back to a location that already rejected it.
- Order Admin Logs (COM-6332 and COM-6330): Order audit logs will now record when an internal order note is created, when an order confirmation email is resent, and when the order’s email address is edited. Each of these log additions will include the user who initiated the change and the date/time it occurred. Additionally, a new tab called Shipment History has been added to the shipment details when viewing an order in Admin. This tab displays the same shipment log as the Fulfiller UI, including changes in fulfillment, tracking numbers, item edits, etc.
- Fulfiller Refund Status Support (FFMT-3451): The Fulfiller UI now fully supports the redefined refund statuses from Version 1.2236. Refunding full or partial shipments in the FFUI will count as Fully Refunded and Partially Refunded respectively, as long as the refunded amount is less than the total order amount in partial cases. The status will not update to Fully Refunded if the total of all refunds is less than the price of the order.
- Future Shipment Date Behavior (CHAR-3971): The behavior of shipments created with future inventory has been updated. When the expected delivery date of the inventory is changed to a point beyond the configured future date limit, STH shipments will now be reassigned while BOPIS shipments will be moved into the appropriate state (such as Customer Care or Backorder).
- Delete Future Inventory API (CHAR-4109): A new API now allows you to delete future inventory records at POST
.../inventory/deleteFuture. In this request, providing a list of location codes along with the part number, UPC/SKU, and future inventory start/end date will delete all future inventory within that given criteria. This API is not yet available in documentation but will be added soon. - Search Merchandizing Updates (SU-2738, SU-2272, SU-2906, SU-2896, SU-2630, and CAT-1749): Further updates have been made to the new Search Merchandizing feature. The search type filter is no longer case sensitive, some minor cosmetic and rendering changes have been made to the UI, sort definitions have been removed from the Category UI now that they are available in Search Merchandizing, and up to 100 search terms are now allowed per rule. Additionally, the
merchRuleCodeparameter for the Search Debug API has been renamed tomerchandizingRuleCodeand the API documentation will be updated soon.
Internal Updates
The following enhancements are internal-only and not exposed to clients. For the full list of search merchandizing edits, see the Jira list. Note that FFMT-3380 (Assembly Partial Pickup) will be announced when its counterpart is complete in Version 1.2242.
- CHAR-4214: The message type of the future date changed inventory event has been updated from ShipmentDateChanged to FutureInventoryDateChanged, as well as the topic (inventory.shipmentdatechanged) and name. This makes it more accurate.
- SU-2922: Some endpoints have been hidden from Swagger, including
.../admin/attributes/getcoreandcustomattributes,.../storefront/searchmerchandizingrules, and.../storefront/searchmerchandizingrules/{code}. - COM-6110: A webhook has been added to update pending items in the cart, in which items will be marked out of stock in the cart and checkout object.
- COM-6071: SOLR has been enabled for subscriptions, and changes deployed for the Mongo Connector and Kibo.Config change.
- CHAR-4164: CARS has been updated with a Kibo config to support changing the S3 region, as previously this value was hardcoded. With this new config, the default is us-east-1 and the EU region can be set to eu-west-1 for European implementations.
- CHAR-3941, CHAR-4195, and CHAR-4186: Several optimizations have been made to the inventory service. Inventory crons would sometimes take extra time to close and not finish deployment for an extra 10 minutes, but this update improves the efficiency of inventory crons so that they no longer have to wait those 10 minutes. The inventory event log also now delete records once the events have been processed, and Inventory Deleted events are now published when the old Inventory Delete job runs.
- COM-6531: While importing subscriptions, the Get Shipping Rates call will be skipped.
- CHAR-4214: A Future Available to Promise event has been renamed to be more accurate. When the future date is changed, the resultant ShipmentDateChanged event is now FutureInventoryDateChanged.
- SU-2629 and SU-2740: QA testing has been done to the recent ProductSortDefinitions migration to Mechandizing Rules to ensure that the database is populated with the proper merchandizing rule data, as well as QA testing for Merchandizing Rule CRUD links.
- Additional improvements have been made as part of ongoing work for extending product attribute access to Order Routing for core extensibility. This project is still a WIP.
Bug Fixes
The following list summarizes resolved issues for this release.
| Status | JIRA Ticket | Resolution |
|---|---|---|
| Targeted for Production Tenants | FFMT-3392 | 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 Tenants | COM-6224 (reported by Home Hardware and Nivel) | 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 Tenants | COM-6168 (reported by Home Hardware) | 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 Tenants | CAT-1616 (reported by The Room Place) | 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 Tenants | SU-2809 | 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 Tenants | COM-6501 | 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 Tenants | SU-2956 | 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 Tenants | CAT-1764 (reported by Home Hardware) | 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. |
| Targeted for Production Sandboxes | SU-2962 | After saving a search term that includes a space in a merchandizing rule, the site search results would not reflect that rule’s logic. This has been fixed so that merchandizing rules properly support search terms with multiple words and return expected search results. |
| Targeted for Production Sandboxes | FFMT-3449 | It was possible for quantities larger than the shipped quantity to be input when creating and processing returns in the Fulfiller UI. This has been corrected and validation has been added so that an error will be displayed if a user attempts to return a larger quantity then what was fulfilled. |
| Targeted for Production Sandboxes | COM-6480 (reported by French Toast) | The order status field broke on implementations using the “synthesized” mode from a previous version of eCommerce. This has been fixed so that order and order item statuses can be properly updated and maintained, and issues will not be experienced with data imports. |
| Targeted for Production Sandboxes | COM-6397 (reported by Pearson Vue) | Avalara defaulted to USD currency to all returns because the currency code was not being provided in requests from Kibo. The Avalara integration has been updated so that the currency code will be provided and returns made in currencies other than USD will be reflected properly. |
| Targeted for Production Sandboxes | COM-6352 | After a user failed to successfully login 15 times and was locked out of their account, attempting to reset their password would fail and put them in a loop. This is because locked accounts were not intended to unlock their own accounts via password reset, as it must be manually unlocked by Kibo. The login page has been updated so that a locked user will not be able to click Next and reach the password reset page. |
| Targeted for Production Sandboxes | COM-6223 (reported by Calendars, Sun & Ski, and Far Bank) | Returns created in the previous version of eCommerce and imported into KCCP could not be properly loaded, even after switching to the Classic Admin UI as prompted. This has been corrected so that you can successfully load and process the return after switching UIs. |
| Targeted for Production Sandboxes | COM-5948 | In a previous release, a fix corrected an issue where the system only checked within the first 200 users on the tenant, and if the user was beyond 200 in the user list then their username would not be displayed in order notes. However, it still required a page refresh for the username to appear. Now, usernames are successfully displayed in order notes the first time without requiring a refresh. |
| Targeted for Production Sandboxes | CAT-1803 (reported by Specialty Commerce) | When a discount was applied to a cart, the expectation was that it would go to the lowest-priced item as configured on the discount. However, this occurred inconsistently across different orders. This has been fixed so that discounts are consistently applied to the lowest-priced item as expected. |
| Targeted for Production Sandboxes | CAT-1802 (reported by Crazy Shirts, Boscov's, and Franchesca's) | The Price Range facet was not displaying price ranges in order from lowest to highest. Instead, it displayed prices based on the number of products in each range which was not numeric order. This has been corrected so that price ranges are displayed in the logical order instead. |
| Targeted for Production Sandboxes | CAT-1754 (reported by Ace Hardware) | When price lists were used to have both a regular price and a MAP (minimum advertised price) price on products, the MAP prices were not being honored and a lower price was displayed on the product details page instead. This has been corrected so that when the regular price goes below the MAP, the MAP will be displayed on the storefront instead. |
| Targeted for Production Sandboxes | SU-2921 | The “No products blocked” message on the Search Merchandizing Rules page was not localized for French like the rest of the page. This has been fixed so that this text is successfully translated when French is the browser language. |
| Targeted for Production Sandboxes | FFMT-3440 | The user field of shipment notes was blank, instead of displaying the name of the user who created the shipment note. This has been fixed so that user information is successfully retrieved and listed in these notes. |
| Targeted for Production Sandboxes | COM-6386 (reported by Reeds and Ignitiv) | While trying to set up Vantiv payment gateways for OMS-Only, authentication failures were received. This gateway integration has been updated to better implement transaction authentication. |
| Targeted for Production Sandboxes | COM-6551 | The shipping cost was not carrying onto continuity orders for imported subscriptions. This has been fixed so that shipping costs are reflected on new orders as expected. |
| Targeted for Production Sandboxes | COM-6542 | When auth failures occurred on subscriptions, its status did not change to reflect the errored state. Now, when a continuity order fails to be created due to an auth failure, the subscription and order payment rollup statuses will be Errored. |
| Targeted for Production Sandboxes | COM-6192 (reported by Pearson VUE) | Tax codes could not be added in the Avalara application, as nothing would happen when the user clicked Add and the console returned an error. This has been corrected so that tax codes can be successfully added. |