Production Tenant 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.
Production Sandbox Features
Order Admin and Fulfiller Functionality
- Quick Search by Shipment Number: The quick search options in the Fulfiller interface previously supported searching by order numbers and external identifiers, but not specific shipment numbers. Searching for a shipment number resulted in no shipments being returned, even if the number was a valid one. This search functionality has been enhanced to enable searching by shipment number and properly return the matching results.
- Upgraded OMS API Updates: In addition to other OMS APIs that are already supported by the translation layer, the ability to submit a POST request to the Create Location API and GET/POST/UDPATE calls to the Custom Order Data API has been added. Clients upgrading to KCCP from a previous version of OMS can make these calls and their requests will automatically be made compatible with the new version of the APIs on KCCP.
- Filter Order API by Status: Support has been added to ensure that GET calls to the translated Order API can be filtered by status, allowing orders to be searched for and retrieved based on a specific status such as Ready. This filter would be applied like “…/?orderStatus=READY”, just as it was in the APIs used by the previous version of OMS.
- Express Shipping: An express shipping flag at the shipment level (shipment.isExpress) can now be passed to the Order Routing and Shipment APIs. If the shipping method is set as any kind of express shipping (1day, 2day, or 3day) during order submit, shipment transfer, or reassignment, then the flag will be active and used to enable this fulfillment. To further support this, shipments can be filtered by “express” in the Fulfiller UI. Fulfillment locations must have express enabled in their location configs when orders are being routed.
Bug Fixes
The following list summarizes resolved issues for this release.
| Status | Resolution |
|---|---|
| Targeted for Production Tenants | Custom schema values were unable to be edited in the schema edit menu of the Order Admin System settings, due to the text fields being displayed as read-only instead of editable. This has been fixed so that schema fields can be properly edited and customized. |
| Targeted for Production Tenants | When clicking the Prepare for Shipment step for transfers from the assigned shipments section of the Fulfiller UI dashboard, the Shipment API was repetitively called until it timed out. This caused the user to be stuck on the dashboard, and has been corrected. |
| Targeted for Production Tenants | When performing a Get Shipment API call, the workflowState object did not return the correct times for the completedDate field in each completed state. This has been fixed so that the completeDate information is returned accurately. |
| Targeted for Production Tenants | The default service type in the Fulfiller UI did not match the configured default set for the location group, which also meant that some shipping options selected by the customer were not always accurately displayed. This has been corrected so that the proper service types are referenced for shipments. |
| Targeted for Production Tenants | Custom schema values were unable to be edited in the schema edit menu of the Order Admin System settings, due to the text fields being displayed as read-only instead of editable. This has been fixed so that schema fields can be properly edited and customized. |
| Targeted for Production Tenants | For clients upgrading from a previous version of OMS and using the translated OMS APIs, orders with no-operation payment methods are submitted without an associated payment interaction which prevented any refunding or voiding to be done to the order if anything were canceled. This process has been updated to permit voiding payments – in the event of a cancellation, the payment should be voided before the cancel action is successful. This void must be performed manually if the cancellation is being done through the Order Admin UI. |
| Targeted for Production Sandboxes | The KCCP Create Order API experienced intermittent failures with an error code of 400, indicating that a customer address already existed in the system and the new data was invalid. This has been corrected so that the API can properly handle these cases and submit those orders more consistently. |
| Targeted for Production Sandboxes | For a particular implementation upgraded from a previous version of OMS, if a store had no inventory for a product available and the customer clicked “Find Another Store” from the product page then no new results would be returned. The catalog has been updated to properly retrieve this information based on the arc action in place for the implementation. |
| Targeted for Production Sandboxes | When a B2B user copied a wishlist into a new list and attempted to remove an item, an error code 404 would be returned. This has been fixed so that items can be successfully removed from any copied wishlists. |
| Targeted for Production Sandboxes | The Super Admin role did not have behavior permissions enabled for customer password change, order updates (for items, pricing, discounts, etc.), or currency management (read, write, etc.), which also prevented these permissions from being added to any custom roles. These behaviors have been added to the role. |
| Targeted for Production Sandboxes | Updating products with localized properties resulted in the non-English entries being removed from the product, even if only the English value was edited. This has been corrected so that localized product data is not lost when updating the product data. |