Production Tenant Features
Order Management & eCommerce Functionality
- Flexible Auto Capture on Delivery: Shipments of the Delivery fulfillment type will now reference the existing flexible auto capture setting used for BOPIS orders in order to determine when payment is captured. See the Delivery and Auto Capture documentation for more information.
- Tax Recalculation on Refunds: Similar to the Tax Recalculation update released with Version 1.2128, tax is now recalculated when a return is initiated and the user issues a refund. This calculation is based on the item tax value and ensures that the automatically-generated refund is for the appropriate amount.
- Refunded Gift Card Number: When a refund is performed to a new gateway gift card, the full gift card number is now displayed in the Returns and Payments tabs when viewing an order in the Order Admin UI. This allows CSRs and Admins to reference the new gift card’s number if needed for the customer.
- Order Grid Update: A minor update has been made to right align the amount fields in the Orders grid of the Admin UI.
Order Management & Fulfiller Functionality
- HTML Pick Wave APIs: API support has now been added to retrieve the HTML data of pick lists and pick wave documents. This allows these documents to be printed via API rather than through the Fulfiller interface. These GET endpoints are:
/commerce/shipments/{shipmentNumber}/rendition/htmland/commerce/pickwaves/{pickWaveNumber}/rendition/html. The API documentation will be updated here with the release of this Kibo Composable Commerce Platform version. - Order Routing Filters API: A new Order Routing API endpoint (
…/group/add-filters) has been added to support adding multiple filters to a location group. The request payload only requires a list of filter codes and the identifier of the group that those filters should be added to, as shown below. Order Routing API documentation will be updated here with the release of this Kibo Composable Commerce Platform version.{ "selectedFilters" : [1,2], "groupID" : 1 } - Custom BPM Update: A particular implementation’s custom BPM, used to transmit shipments to SAP, now has associated updates in the Fulfiller UI to facilitate that process. These updates add buttons for Done, Skip, and Back to allow fulfillers to navigate between (though not every step has every button, such as Skip not being allowed when receiving a transfer). This does not affect other fulfillment flows, such as the standard STH and BOPIS, that already include UI buttons to continue on to the next step.
B2B Functionality
- B2B Account Hierarchy Update: When viewing the B2B account hierarchy on the storefront, the area where the hierarchy tree displays would be blank if the account was not part of a hierarchy. To reduce user confusion and assist them if they choose to add child accounts, a default root account node will now be shown with the current account name for those cases. See the B2B documentation here for more information about this hierarchy.
Search Functionality
- Typo Tolerance vs. Min Match: Note that this feature was added to sandbox in Version 1.2128 but has now been moved to 1.2130. The Typo Tolerance options in the site search configurations are now hidden when Min Match is in use. These features cannot both be active at the same time, so Typo Tolerance will not be displayed if Min Match is set to a percentage other than 0 percent. It will be available only when Min Match is set to 0 percent. For more information about these features, see the documentation.
Production Sandbox Features
eCommerce Functionality
- Quick Edits: The new Quick Edits feature allows you to make the same update to an attribute value across multiple products at once from the Products page. This update is performed at a master catalog level for Product attributes (i.e. pricing fields & properties), and saves you from having to perform the update one at a time for each product or using the import/export tool to perform a bulk update. For more information, see the updated Products guide.
- Customize Refund Reasons: New Arc.js before and after actions are now supported to customize payment refund reasons. These actions are http.refundReasons.before and http.refundReasons.after and relate to the Order API’s Get Refund Reasons operation. Calling these actions allows additional refund reason options to be added to the API and selected in the Admin UI when processing a refund on an order. See the Arc.js documentation for more information about these actions.
- Refund/Credit to Gift Cards: A new gift card payment type setting, called Refund/Credit Setting, now controls whether credits are made to an existing gateway gift card or to a new card. When this setting is toggled to credit new gift cards, then the system will perform a no-operation on the existing gift card while issuing the actual credit to a new one. If toggled to credit existing gift cards, then it will issue the credit directly on the known card. To support this, if viewing an order in the Order Admin UI then the Payments tab now displays a new section for Credits that includes the date, amount, original payment (original gift card number), and new payment (new gift card number) information.
Currently, initiating an automatic refund will always generate a new gift card regardless of the Refund/Credit Setting and will follow the payment rankings per existing functionality. This will be updated in a future release to support refunding to existing gift cards based on the new setting. See the Gift Card Processing and Appeasements documentation for more information. Other related guides have also been updated where appropriate to clarify the crediting/refunding behavior.
Order Management & Fulfiller Functionality
- Toggle Return Status: The Return Status column of the Fulfiller UI can now be hidden via theme customization if desired, such as if an implementation does not process returns in the Fulfiller UI and wants to toggle the displayed fields off. Though always displayed by default, the displayReturnsSection tenant setting is now available in the theme language files – a value of 1 will display the return column, while a value of 0 will hide it. For more information, see the documentation for Fulfiller Customization.
- NativeScript Printing: The NativeScript fulfillment application now supports Air Print/Android Print for creating and reprinting pick waves and shipping manifests, in addition to return receipts. The print options will be displayed when creating or viewing a pick wave, manifest, or return.
- Automatic BOPIS Transitioning: When a BOPIS shipment in the Waiting for Transfer state has no remaining Ready transfer shipments, it will now automatically move to Customer Pickup. Previously, BOPIS shipments could end up remaining in Waiting for Transfer even when it had no transfer shipments remaining to be fulfilled and thus required a manual transition. To support this, when an item is canceled or rejected from the Transfer shipment it is also rejected from the parent BOPIS shipment. This ensures that the BOPIS shipment reflects the correct quantity and price for that item when it reaches Customer Pickup.
- Expected Delivery Dates: Previously, an Expected Delivery Date could only be displayed for Delivery shipments. This has been extended to STH, BOPIS, Curbside, and Transfer shipments so that if provided via the Shipment API, the expected delivery or pickup date field will be displayed in the shipment details of the Fulfiller UI (as well as the Provide to Customer step for BOPIS and Curbside shipments). This field cannot currently be updated in the UI but can be changed via API as needed. It can also be hidden via site theme customization, but if no value is provided for the field then it will not be displayed by default. In the case of BOPIS or Curbside shipments, this date will be when the pickup is expected to be ready (such as the same day, or the following if the order was placed near closing hours). In the case of Transfer, this is the day that the shipment is expected to arrive at the fulfillment location. This field will also be added to the Admin UI in a future update.
B2B Functionality
- B2B Subscription Events: B2B event subscriptions have been added to the Dev Center, allowing you to receive notifications when B2B account statuses are changed. When an account is approved or denied, as well as when a previously-approved account is deactivated or reactivated, a notification will be sent containing the account ID and its old and new statuses. The Event Subscription documentation has not yet been updated but will be on Monday.
Search Functionality
- Typo Tolerance vs. Min Match: Note that this feature was added to sandbox in Version 1.2128 but has now been moved to 1.2130. The Typo Tolerance options in the site search configurations are now hidden when Min Match is in use. These features cannot both be active at the same time, so Typo Tolerance will not be displayed if Min Match is set to a percentage other than 0 percent. It will be available only when Min Match is set to 0 percent. For more information about these features, see the documentation.
Bug Fixes
The following list summarizes resolved issues for this release.
| Status | Resolution |
|---|---|
| Targeted for Production Tenants | Inventory refresh jobs were experiencing performance problems recently and taking more time than expected to process. Optimizations have now been made to improve the performance of the inventory refresh. |
| Targeted for Production Tenants | Available fulfillment locations were not displayed for a product during offline order creation if the product was not set to track inventory. This has been fixed so that the user will be able to select the default shipping location for these products when placing an order for direct ship or pickup. |
| Targeted for Production Tenants | Products configured with the Gift Included extra property were not being cancelled when their order was cancelled – the order’s shipment status would remain in Pending Fulfillment due to those items. This has been fixed so that cancelling an entire order will properly cancel those order items as well. |
| Targeted for Production Tenants | When a tenant had a large number of locations, the Location Group UI would time out and freeze while attempting to load the locations for configuration. These processes have been updated to retrieve locations more efficiently and handle large quantities without timing out. |
| Targeted for Production Tenants | The image groups displayed on the product details page did not include all of the expected image data, requiring additional API calls to get image paths. An “includeAllImages” parameter is now available for the …/catalog/storefront/productsearch/search GET API endpoint, allowing this data to be retrieved by a single API call and displayed on the storefront details page. |
| Targeted for Production Tenants | The Avalara application was not properly saving configurations and returned an error instead, even though the application had previously reported a successful connection with Avalara. This application process has been fixed so that configurations are able to be saved. |
| Targeted for Production Tenants | Inventory levels were occasionally not being affected by the purchase or fulfillment of items, where it would be expected for available inventory to decrease. This was occurring when the implementation had inventory tags enabled but no tag categories besides the default. The inventory logic has been updated to better handle this scenario and accurately update inventory levels for all items. |
| Targeted for Production Tenants | The single/multiple assignment radio buttons for configuring routes in Order Routing did not properly reflect the settings, as the buttons would always default to “single assignment preferred” on initial page load regardless of the actual flag in the backend. This has been fixed so that these buttons will save correct in the UI and continue to reflect the chosen setting after a new page load. |
| Targeted for Production Tenants | The inventory locator name field was not included in the translated APIs for upgraded clients, meaning that the field could not be populated in the Fulfiller UI and packing slips for these clients. This has been corrected so that the field is included in the API conversion and can be displayed. |
| Targeted for Production Tenants | The Avalara application had multiple installation and enablement issues - the address validator would not properly install when a tenant had multiple sites, some event subscriptions would not enable, and the country selection drop-down was poorly displayed. These issues have been fixed so that Avalara can be enabled more effectively. |
| Targeted for Production Tenants | Some categories could not be used in facets because their ID was not being appended into the URL. Logic has now been added to the system to safeguard against this problem and allow all categories to be properly faceted. |
| Targeted for Production Tenants | A particular configuration’s fulfillment partner application (such as for drop shippers) was experiencing problems in sandbox, as the Get Shipment API call would fail in that partner’s tenant instead of returning shipment data. This was due to a failure in the associated arc actions preventing the application from authenticating. That has been fixed so these applications will work as expected. |
| Targeted for Production Tenants | A fix previously reported in Version 1.2128, in which product codes were not staying filtered in Product Search after clicking a SKU, was not successfully deployed. It is now being properly deployed with Version 1.2130 so that the Search filter persists until it is manually cleared. |
| Targeted for Production Sandboxes | Customer lifetime values were not being updated from historical OMS import orders as they were expected to be. This has been fixed so that lifetime values will be properly updated as long as the order.submittedDate field is provided in the payload for the Create Order API call. |
| Targeted for Production Sandboxes | Only 25 locations would be listed when creating an order from the Admin UI, preventing other locations with available inventory from being selected as the designated fulfiller. A larger page size has now been implemented to enable displaying all inventory locations. |
| Targeted for Production Sandboxes | Adding a customer segment to discount conditions via the Add button would not display more than 25 segments at a time and also did not display a scroll bar, making it difficult to add more segments. This has been fixed so that the list of available segments is scrollable. |
| Targeted for Production Sandboxes | After closing a pick wave, some shipments would remain in the Accept Shipment state rather than proceeding to Prepare for Shipment. This has been corrected so that all shipments will properly move to the next fulfillment state when their pick wave is complete. |
| Targeted for Production Sandboxes | Shipment IDs were not displayed in the courier label. This has been updated so that these IDs will be listed on the label, enabling stores to easily identify the shipment. This will support another upcoming fix to correct an issue where shipping labels are not populating important reference fields on shipping labels. |
| Targeted for Production Sandboxes | In a particular implementation, clicking “Save” on the Carriers page of the Shipping Settings resulted in a validation failure error instead of saving the custom rate settings. This has been corrected so that custom rates can be successfully updated. |
| Targeted for Production Sandboxes | The Listing Preview endpoint was ignoring any supplied Category ID in the query as part of the search request, causing the response to be the same regardless of any specified category. This has been fixed so that the search results will vary based on the intended category being queried. |
| Targeted for Production Sandboxes | After the initial sandbox release, searching for an order/shipment in the Fulfiller UI or entering a fulfillment queue resulted in a blank page. A hotfix has been added to this release that will allow these pages to load and properly display shipment data. |
| Targeted for Production Sandboxes | Calling the Auto Refund API sometimes resulted in a validation conflict, with a message that a return had insufficient funds for automating refunds. This issue resulted in the Initiate Refund button for affected returns to be disabled and some data was not displaying in the return details of the Admin UI. This has been corrected so that refunds can be successfully initiated. |
| Targeted for Production Sandboxes | Orders with more than 10 shipments were able to be completed without the payment being fully collected, as one payment was captured and the status changed to Paid while there was still a remaining balance. This was due to miscalculating payments based on the default pageSize of shipment data in the Fulfillment APIs. This has been updated so that larger number of shipments can be accurately calculated for payment statuses. |