Production Tenant 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.
Production Sandbox Features
eCommerce and Order Management Functionality
- User Management Updates: It is possible to search the list of all Kibo Composable Commerce Platform user accounts in the user management interface, filtering the list of users with access to the KCCP Admin by first name, last name, and email address. See the User Management documentation for more information about this interface.
- Klarna, CrowdTwist, and Sezzle Payment Types: Support for payment via Klarna, CrowdTwist, and Sezzle has been added for clients upgrading from a previous version of OMS where these payment methods were used. These are processed through NoOp gateways and can be used as credit card types if configured in the Payment Types settings. See the Payment documentation for more information about gateways and payment types.
- Future Inventory in Inquiry: With inventory tagging and segmentation, the ability to set a deliveryDate to indicate when future inventory will be available was added to the Inventory Refresh and Adjust capabilities. Now, future inventory information can be retrieved from the Get Inventory API call if a deliveryDate was set during inventory refresh.
Fulfiller and Translated OMS Functionality
- Block Assignment from Transfer Shipments: The “Exclude location from future assignments” option was previously only available for Ship to Home shipments but has now been added to Transfer shipments as a checkbox next to the Assign Shipment button of the Validate Stock step. When selected, order routing will not assign any more shipments to that location until inventory is refreshed. This setting correlates to the blockAssignment parameter of Shipment API data, and thus can be set if updating shipments via API.
- Translated Shipment Transitions: The API calls to transition shipments through their BOPIS and Transfer BPM states are now fully supported in the translation layer, allowing some implementations that upgraded from the previous version of OMS to use their legacy API request bodies on KCCP endpoints for these actions. This includes the transitions waitForTransfer (or wait_for_transfer) on BOPIS shipments and shipped for Transfer shipments. See the Translated OMS API documentation for a template of these shipment calls.
- Translated Orders with Multiple Payments: Support for multiple payment types within an order has been improved in the translated APIs, allowing clients who have upgraded from a previous version of OMS and are using translated APIs to continue using their existing order import and payment processes for multiple payment methods.
Bug Fixes
The following list summarizes resolved issues for this release.
| Status | Resolution |
|---|---|
| Targeted for Production Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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 Tenants | 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. |
| Targeted for Production Sandboxes | When a handling override amount was set, there would be a mismatch in the Admin interface between the balance listed in the order summary (at the top corner of the order view) and the order total in the order details tab. This was due to the order summary not taking the handling amount into account when calculating the payment balance, and has been corrected so that it displays the accurate total. |
| Targeted for Production Sandboxes | Theme packages were not deleting successfully in the Dev Center, even if there was a success message after clicking Delete, as the package would still be listed and selectable in the dropdown menu. This has been fixed so that deleting a package will fully remove it from the Dev Center options. |
| Targeted for Production Sandboxes | Creating a return in the Fulfiller UI did not always include the refund amount in the API data, preventing the product loss amount from being calculated. This process has been updated so that refund amounts will be properly calculated and returned by the APIs. |
| Targeted for Production Sandboxes | When an order included multiple shipments and one was returned, the returns transaction log would include all shipments for the order – even those that were not returned. This has been corrected so that returns transaction logs will only report shipments that were actually returned. |
| Targeted for Production Sandboxes | The cancel transaction log was not returning any entries, despite the existence of canceled orders and shipments in the system. This was due to missing identifiers in the payment authorization information that this log uses to search for cancelations. This has been fixed so that the log will be properly populated. |
| Targeted for Production Sandboxes | The Fulfiller UI would not display all labels if the browser’s default language was set to a language other than French or English, meaning that text would be missing from the UI. This has been fixed so that browser languages other than French or English will default to the English version of the UI. |
| Targeted for Production Sandboxes | The SMART_POST service type was being stored incorrectly in the KCCP database, causing errors while generating shipping labels for FedEx SmartPost shipments. The service type data has been updated so that SmartPost shipments can be properly retrieved and labels can be properly created. |