Production Tenant Features
eCommerce and Order Management Functionality
- Edit Shipment Permissions Update: The ability for a user to edit shipment items in an order has been updated to more accurately reflect site settings and user permissions. If the site setting “Edit data on shipment” is enabled but the user does not have the “Order Update – Pricing” behavior in their user permissions, then they will not be able to edit a shipment item’s price even though they can edit the other item data.
Previously, users that did not have the “Order Update – Pricing” behavior were still able to perform price edits. With this update, they will no longer be allowed to do this. Anyone who needs to perform this action must have that behavior enabled in their user permissions.
If the site setting “Edit data on shipment” is turned off, then stores cannot edit a shipment item at all. See the User Permissions documentation for more information on how to manage roles and behaviors. - Inventory Code Tooltip: The “Code” column header of the Inventory UI now has a tooltip to help clarify the purpose of this code. Click the “i” icon in the column header to view the tooltip explaining that this code represents the Product Code, UPC, or Variant Product Code of the inventory product.
Fulfiller Functionality
- Canceled Items in Shipment View: When a shipment is canceled in the Customer Pickup step of the Fulfiller UI (via the “Customer wants to cancel” button), the Fulfiller UI previously did not display any details about the items if the user went back to view the canceled shipment. Now, a list of canceled items is included in the details view with pricing details zeroed out to $0.00. This applies to the shipment information displayed on both the search result listings and the shipment details page.
- French Translation Update: Based on feedback from French users, the Fulfiller title “Partenaire” has now been replaced with “Exécution des commandes” in the French version of the Admin UI’s navigation menu.
Production Sandbox Features
eCommerce Functionality
- Collections: Collections are a group of complementary or related ‘member products’ that can be marketed as one, even across categories. For example, a beach-themed apparel collection could include products from the catalog’s Footwear, Accessories, and Shirts categories. On the storefront, collections are displayed on their own details page as well as the details page of all products within the collection, and in search results. This allows customer to easily purchase collection products from one page, allowing the retailer to cross-sell more products as well as enhance the customer experience and convenience. For more information, see the Collections user guide.
Contact your Kibo Project Team if you want to use collections, so that Kibo Engineering can apply the required schema migrations to your tenant. Then, you will have to re-index your site and be sure to follow the steps in the user guide to configure search settings. Displaying collections on your storefront will also require a core theme update.
Order Management Functionality
- Laser Scanning Highlights: When using a barcode laser scanner such as a Zebra device in the Validate Stock step of the Fulfiller UI for STH, BOPIS, Transfer, and Curbside shipments, line items whose in stock amounts match the desired quantity of the shipment are now highlighted green. This helps provide more visual validation of shipment item availability to store associates fulfilling shipments with mobile scanners.
- Translated Payeezy Integration: Payeezy gift cards are now supported for clients upgrading from a previous version of OMS who are using the translated APIs for backwards compatibility. Payments of the “GiftCard” type can now be used in the Import Order API when the Payeezy gateway is configured, and this is also reflected in the response from GET calls made to the Payment API. The translated APIs are documented here.
- Order Routing UI Updates: Order Routing UI updates are in progress but not yet complete across the whole UI. In this release, the routing group view has been updated with a new layout. Some groups may be greyed out when they are no longer applicable to after-actions (e.g., if the first group are not set to “look for match in the next group”), to make it clear to the user that those groups will not be used during routing. There is also now an “Add filter” button for each group, allowing filters to be more easily applied to a routing group. The ranking number is displayed in the top right corner.
- Suggestion Log Updates: The Get Suggestion Log API for Order Routing has been updated to return location codes in areas where previously only the location ID was provided in the payload. Notably, the ranked location candidate objects and events such as GROUP_SORT and RESPONSE now include location codes.
Bug Fixes
The following list summarizes resolved issues for this release.
| Status | Resolution |
|---|---|
| Targeted for Production Tenants | The Welcome and Password Reset email templates could not load in the Site Editor, due to an error about a missing object reference. Additionally, Return email templates experienced a 404 Not Found error. This has been resolved so that the templates can successfully load in the editor. |
| Targeted for Production Tenants | The BPM fulfillment step names were not translated in the French version of the Fulfiller UI. For example, the UI still said “Pickup – Accept Shipment” or “Ship to Home – Prepare for Shipment” as the title of the fulfillment step, even when the other text was properly translated. This has been corrected so that these fulfillment steps are displayed with their French names instead of English. |
| Targeted for Production Tenants | Minimum match search settings were not being properly utilized by the Site Search. This has been corrected so that minimum match configurations are properly sent to the search function and used in determining search results. |
| Targeted for Production Sandboxes | The storefront search had a mismatch between the total count of search results and the actual number of results for certain pricelists when the user had a store selected. This caused searches to indicate that there was at least one result while not actually displaying any. The Search API has been updated to fix this discrepancy and display the proper count of search results when a specific store has been selected. |
| Targeted for Production Sandboxes | The Product page used the value “N/A” sometimes for columns that lacked data, and this value was not overridden by localized data. This has been updated to respect the localization files so that translated versions in other languages, particularly French, can be displayed. |
| Targeted for Production Sandboxes | For a particular implementation, the Publish button was not automatically enabling after saving a change to a template in the site editor. This prevented users from making any changes to the site without refreshing the page first, after which publishing would be enabled. The editor has been fixed so that the Publish button will become available immediately after saving a new draft. |
| Targeted for Production Sandboxes | The Pick Up In Store Ready email was not being sent to the address designated as the pickup contact in the fulfillment information for that shipment, and was instead sent to the address of the customer who placed the order. This has been corrected so that BOPIS emails go to the proper contact, if different from the shopper who placed the order. |
| Targeted for Production Sandboxes | Some improvements have been made to the Customer Pickup step of the Fulfiller UI to clarify the behavior when modifying shipments. Previously, the UI would remain stuck in edit mode after modifying the shipment until the page was refreshed. The UI would also appear to accept increases to the quantity or price, though this was not actually supported and the shipment information would not be updated in the system. Now, this page will properly exit the edit mode as well as display a validation error message if the user attempts to increase the quantity or price. |
| Targeted for Production Sandboxes | When a site had multiple stores with the same name but different location codes, fulfiller users could not be assigned or removed to only one of those stores at a time. This was due to the assignments being based on a name match, so attempting to assign or remove the user from one store would assign or remove them from the other store as well. This has been changed so that user assignments are based on location codes instead of exact names. |
| Targeted for Production Sandboxes | Transfer shipments were not always being included in shipment manifests, as the system looked only for Fulfilled shipments when creating a manifest but transfers follow a different BPM. Manifests have now been updated to include transfer shipments that are ready to be picked up by Canada Post after their Prepare for Shipment step. |
| Targeted for Production Sandboxes | The Fulfiller UI experienced intermittent performance issues when processing transfer shipments and when opening the user management page, due to a large number of API requests causing the page to be very slow to load. Optimizations have been made to improve the UI’s performance in these areas. |
| Targeted for Production Sandboxes | Pack sheets were sometimes unable to be printed because they were unable to be opened in a webpage for the printer application. This occurred for a particular implementation because the page relied on a cookie instead of the Site ID for the context, which has now been fixed to ensure that pack sheets can be opened. |
| Targeted for Production Sandboxes | There were some discrepancies in the changeMessage log information returned from the translated GET Shipment State Log API. Empty changeMessages were returned for newly-created orders instead of ACCEPTED_SHIPMENT as expected, while the Print Packing Slip changeMessage not include the PREPARE_FOR_SHIPMENT step in the fulfillment flow. This has been updated so that changeMessages more accurately follow the expected steps. |
| Targeted for Production Sandboxes | Inventory levels were still being tracked and updated for products where the “Track stock level” setting was disabled. This has been fixed so that inventory stock more accurately follows the product settings and will not be managed if tracking is turned off. |
| Targeted for Production Sandboxes | Some users were unable to access Reports from the navigation menu in the Kibo Composable Commerce Platform Admin UI, as an Error 404 would be returned instead. This has been corrected so that users with appropriate permissions can view the reporting dashboard from the Reports link in the menu. |