Announcement
As part of ongoing enhancements to the Real-Time Inventory Service, Kibo is continuing to migrate our internal inventory endpoints. We will be migrating the aggregate inventory internal endpoints from April 30 through May 31. No action is required, but if you have questions then please contact Kibo Support.Production Tenant Features
Commerce
- Bulk Action Confirmation: When performing bulk actions on the Orders dashboard, a pop-up will now ask you to confirm before continuing with the action.
- Future Inventory in Order Admin: Future inventory levels will now be displayed when editing offline order details or creating new shipments, allowing admins and customer service representatives to make more informed fulfillment location assignments that consider incoming inventory.
- Future Inventory Validation: Any time inventory is validated in the cart, checkout, or order processes, the system will now take future inventory into account in addition to current inventory. Current inventory will always be prioritized for assignment. See the Future Inventory documentation for more details about these validation processes.
- External Pricing: You can now place orders with line items whose pricing is set by an external system, not the Kibo catalog. To do so, you should still maintain a catalog that lists all your products but does not configure their prices. Pricing details can then be sent to Kibo in the line item data as a
tenantOverridePricefield when calling the Cart, Checkout, Order, Quote, and Wishlist APIs. See the user guide for more information about how to use external prices, as well as links to the relevant API documentation.
Fulfillment
- Multi Piece Shipment Enhancement: When entering the a tracking number for multi piece shipments, you can now enter individual package tracking numbers alongside the master tracking number. The UI clearly labels these different types of tracking numbers and supports other minor enhancements to user experience.
- External Return IDs: If you provide an External ID value when creating a return via API, that ID will now be displayed when viewing or processing active returns in the Fulfiller UI.
Reporting
- Reporting Changes: The reporting dashboard will no longer be the default homepage for the KCCP Admin. Instead, the landing page will now display links to key documentation and other resources. Reporting will only be accessible via the Reports link on the main menu. Additional changes have also been made to user roles. This will include adding a Report Super User role (which is pre-populated with users that have created or modified a report within the past year), the removal of Report Edit and Report View behaviors from existing roles, and the ability to give new Report Read or Report Definition behaviors to licensed Looker users. See the User Roles documentation for more information about these behaviors.
Search
- Stopwords API: You can now upload and retrieve custom stopwords to the search schema using PUT and GET calls to the new
/commerce/catalog/admin/searchSchema/stopwords/enendpoint. You can replace “en” with any other valid language code. The stopwords should be provided in a simple text (.txt) file of words delimited by newline.
Production Bug Fixes
| Service | Resolution |
|---|---|
| B2B | Email notifications were not being triggered after creating B2B accounts, despite being enabled in the site settings. This has been corrected so that these and other email notifications will be successfully sent when expected. |
| Catalog | The Product Variation Pricing Grid page of the Localization settings was not returning search results based on Product ID or Variation Product ID fields. This has been corrected so that you can successfully search by these IDs. |
| Catalog | Site Builder was not displaying images as expected due to the File Manager timing out. This has been fixed so that images will successfully load. |
| Commerce | A validation error was encountered while saving changes to payment types if any other active gateway also supported that card type. This has been fixed to better handle this scenario so that payment settings can be saved. |
| Commerce | After fixes to return labels in a previous release, some formatting errors were still being experienced. For example, dimensions were not being displayed for FedEx Ground labels. This has now been fixed so that these labels are properly formatted. |
| Commerce | When the “Authorize And Capture On Order Placement” and “Remorse” settings were both enabled, customers were not redirected to an order confirmation page after placing their order. Instead, the page would refresh and they would remain on the checkout page. This has been corrected so that the order confirmation is displayed as expected. |
| Commerce | When attempting to modify an imported order on an OMS-Only implementation, a 404 Error would be experienced if there was no fulfillmentLocationCode already set on an order item. This prevented changes like editing prices and order-level adjustments. This has been fixed so that these changes can successfully be made for orders with this scenario. |
| Fulfillment | Attempting to change the workflow of shipments in a KSA or Kuwait site via the Fulfiller UI resulted in a 412 Error. After changing the workflow via API, some shipment pages would enter an endless refresh loop at certain statuses (such as Print Packing Slip). This has been corrected so that workflows can be edited in these sites and shipments can complete fulfillment. |
| Import/Export | An error was sometimes experienced when attempting to export Marketing coupon data by coupon set name with the Import-Export tool. Attempting to run an export using the coupon set code instead resulted in all coupon sets being included, which was not intentional. This has been fixed so that exports can be successfully made for coupons with the expected data. |
| Subscriptions | After changing a subscription’s Next Order Date, it was still displayed as the previous date. This has been corrected so that the date displayed in the UI will update appropriately. |
Production Sandbox Features
Commerce
- Cybersource Fingerprint ID: The Cybersource integration now accepts a
deviceFingerprintIDfield as part of the fraud screen request object, which will then be passed through the authorization call and to Cybersource to provide fingerprint identification details.
Order Routing
- User Interface Update: The Order Routing UI has been enhanced. These changes went into effect in sandboxes on April 23 and will remain there until the 1.2416 production release on May 13. This includes removing the Reports and Routes pages from the navigation menu, the ability to create a new filter while viewing a group (now called a scenario), and other usability updates. “Groups” have been renamed to “scenarios” in all places where the term appears, but their functionality and the Order Routing APIs remain unchanged. See the updated Order Routing documentation for more details.
Transactional Logs
- Returns TLogs Update: The Returns transactional log now includes a new
returnItemTaxTotalfield to indicate how much tax credit is being returned for each line item.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | When adding values for the “Brand” product property on a product, typing the name of a brand into the text field did not result in automatic results. Instead, the user had to scroll down the dropdown menu in order to find the value they wanted to add. This has been corrected so that the UI will display suggestions of available values that match what the user is typing to make entry easier. |
| Catalog | In some cases, categories could not be assigned to products via the Quick Edit tool and resulted in an API failure despite returning a 200 OK response. This was due to product data not being retrieved if the catalog price was overridden for a standard product, but has now been corrected so that the Quick Edit tool can successfully update product categories. |
| Commerce | When creating a new shipment on an existing order, not all expected stores were displayed in the fulfillment location drop-down list. However, those locations did appear when creating a shipment for a new order. This has been fixed so that all available location records are displayed in the location options for existing orders. |
| Commerce | Subscription shipments that were being paid for with installment plans could not be successfully fulfilled after the first payment, when they are expected to be fulfillable even if the total amount has not yet been paid. This has been corrected so that shipments can be fulfilled while still pending future installment payments as intended. |
| Fulfillment | If a validation error was experienced when generating a Canada Post shipping label, fixing the invalid information and re-attempting to generate the label would still result in the previous error. This has been fixed to ensure that fixing incorrect information allows a new shipping label to be generated as expected. |