June 4, 2020 — 1.2021 Service Update

Production Tenant Features

Order Admin and Fulfiller Functionality

• Bronto Fulfillment Emails: Support for Bronto has been extended to the Kibo Composable Commerce Platform. Shipment transactional emails are now supported by the Bronto application, so that email messages can be triggered upon different events in the shipment fulfillment process. Sample templates exist for these new emails and can be customized. The following emails are now available in Bronto: Shipment Shipped, Shipment Assigned To A Location, Transfer Shipment Created, Transfer Shipment Shipped, Backorder, Backorder Date Changed, Order Pickup Ready, Order Pickup Reminder, Partial Pickup Ready, Transfer Created On Inventory Reject, and Item Cancelled.
• Filter Orders by Shipment Status: When searching for orders in the Order Admin UI, orders can now be filtered by shipment status. This allows the user to easily find orders whose shipments need attention, such as customer care. These statuses are Ready, Backorder, Fulfilled, Customer Care, and Cancelled. This includes transfer shipments and cases such as where an order has multiple shipments and only one is cancelled – that order would still be displayed in the results if filtered for Cancelled shipment statuses.
• Fulfiller Error Messages: Improvements have been made to the error messages of the Kibo Composable Commerce Platform Fulfiller UI, which appear as red popups. These messages now remain visible for 10 seconds, at which point they automatically close, unless manually closed before 10 seconds. The appearance of these messages has also been updated to display an exclamation point icon instead of an X, reducing confusion on how to close the popup.
• Translated Gift Information: Shopper notes and other order gift fields were not populated in the translated APIs used by clients upgrading from a previous version of OMS, meaning that gift information could not be provided in KCCP order data. The upgraded OMS Create Order API has been extended to support these fields and properly transmit gift information into KCCP at the order and shipment level.

Production Sandbox Features

eCommerce Functionality

• Slicing: With the Slicing feature, a configurable product can be “sliced” based on selecting the values of one of its options. These slices can then be displayed separately without creating individual product listings. This allows a site to appear more robust and makes it easier for shoppers to find what they may be looking for without adversely affecting SEO or user experience. Sliced items share the same single product details page, so if the shopper clicks the red slice to view the product details then they will be able to select the other options as well. For instance, a sweater could come in various options for color. Each option value is a slice, so that the red variation of the sweater and the blue variation could be displayed separately in search results when “sweater” is searched for.
• Mapping Attributes: Mapping attributes are a new type of product attribute type that allow a set of specific product attribute values to be aliased (“mapped”) to one generic attribute, simplifying complex product options. As shoppers are more likely to be searching for an item in generic terms, it is efficient to map the individual values to one attribute so that a search for the generic value would return all specifications. One example would be a product that comes in many different shades of green. This product could have each of those shades mapped to one generic green attribute so that all shades will be returned when a shopper searches for “green.” When a mapping attribute is used to associate sets of specific options with generic attributes, then faceting and filtering will be able to work more efficiently with slicing.
• eCommerce Order Import: Clients using the eCommerce element of the Kibo Composable Commerce Platform with Borderfree integration can now fully import orders into the platform. These orders are denoted in the Create Order API by an isImport flag set to true. Both completed and incomplete orders (such as those in the Accepted state) can be imported, but completed orders will not have new shipments created and assigned to a location.

Order Admin and Fulfiller Functionality

• Manual Reassignment Override: When an Admin user chooses to manually reassign a shipment or item, they now have the ability to select the location it is currently assigned to. This triggers the shipment to immediately enter the Ready state for fulfillment at the same location, rather than being reassigned to a separate location. This is useful as an override during cases where the indicated inventory level might have been incorrect, and the assigned location actually does have the inventory in stock. For clients with eCommerce, marking a product as “backorderable” is an option. However, this is not available for order management-only implementations.
• Fulfiller Permission Enhancement: The permissions for fulfiller users (specifically, a user is that only has a “fulfiller employee” or “fulfiller manager” role and no other roles) have been enhanced to limit the shipments that they can view in the Order Admin UI. If a fulfiller has access to shipments in the Admin, they are limited to only being able to view or update shipments for locations that they are assigned to. This applies to BOPIS and Transfer shipments in addition to Ship from Store (Ship to Home) shipments.
• Specify Carrier for Tracking: When manually adding tracking numbers to shipments in the Fulfiller UI, only the “Other” carrier was supported as the carrier option associated with the tracking number. This dropdown option now displays the full list of carriers enabled for the location group, allowing better accuracy in recording tracking details.
• Secure Trading Gateways: The platform now supports gateways to be set up for processing payments via secure trading. Auth, Capture, Void, and Credit actions can all be performed via a new payment gateway configured for the implementation when desired.
• Billing Information in Order Data: Billing information was not previously exposed in GET calls to retrieve order and shipment information through the translated OMS APIs, which are used by implementations upgrading to KCCP from a previous version of OMS. This forced users to get billing information by performing a Get Payment call followed by a Get Customer Address call. Now, billing information is returned in the Get Order Information response as a “billingAddressInformation” object.

Bug Fixes

The following list summarizes resolved issues for this release.