Production Tenant Features
Commerce
- Reserve Future Inventory: Future inventory is now supported alongside reservations in the cart to allocate from upcoming inventory if there isn't enough quantity currently available at a fulfillment location. For more details about the behavior of inventory in different cases, refer to the future inventory and reservation guides.
- PayPal Multiparty Application: A new application is now available that enables you to add PayPal's ability to accept multiple payment methods to your eCommerce payment options. If you are already using PayPal Express and want to use this new functionality, you will need to fully swap over to this new application. This also requires installation and configuration assistance from Kibo. For more details, see the PayPal Multiparty Application guide.
- Default Return Carriers: You can now specify a default return carrier at the location group configuration level. This is useful in scenarios such as when you want to use FedEx Ground as the return carrier for shipments fulfilled by FedEx SmartPost, which you would not otherwise be able to select since these are set up as separate carriers.
- UPS Updates: To support changes to UPS' OAuth 2.0 security model, Kibo is updating UPS carrier configurations. This requires action from any implementations using UPS or UPS SurePost.
- Go to the UPS configurations in your sandbox and click the new Authorize button, then follow the instructions on the next window to authorize with UPS. Upon closing that window and refreshing your carrier configuration page, you should see a a successful authorization status. Next, contact Kibo Support with the time window to switch you to the new implementation. Then test UPS to ensure that it works as expected. You must do this on the production environment even if you already did so in sandbox.
- Going forward, UPS carrier configurations will require the account number to be set in both environments. If you use both UPS and UPS SurePost, then they must be configured as separate carrier accounts within Kibo.
Fulfillment
- Default Sort Options: You can now configure the Fulfiller UI's default sorting order of search results so that users can view either the most relevant, most recent, or other preferred shipments first. Previously, results were always sorted by oldest first which caused some partial matches to appear at the top instead of exact matches. While customizing your Fulfiller theme, change to
searchShipmentSortBytenant setting to orderFirst, orderLast, newest, oldest, highestCost, or lowestCost.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | After recent optimizations to the response time, searching for image files in the File Manager did not return files older than 5 years. This has been fixed so that older files can still be returned as search results. |
| Commerce | The total count of orders with discounts displayed in Reporting did not match up with the transaction metrics for that specific discount. This was due to an issue with redeeming discounts for coupon codes that were added to orders even if they weren't applied to any items. This process has been updated so that codes are redeemed appropriately and the metrics are more accurate. |
| Fulfiller | Tracking numbers were unable to be manually entered for "Other" carriers as expected, since the system was expecting a carrier name to be specified first. This has been corrected so that tracking numbers can be successfully entered for that carrier type. |
| Subscriptions | After adding both a one-time purchase and a subscription for the same product to the cart, the product price was being overwritten so that both line items reflected the subscription price. This has been fixed so that the cart more accurately updates different line items for the same product and reflects the correct one-time versus subscription pricing. |
Internal Production Details
Find more information about the client-facing updates at these Jira tickets:
- Reserve Future Inventory: COM-8138
- PayPal Multiparty Application: COM-8461
- Default Return Carriers: COM-8863 and FFMT-4491
- UPS Updates: COM-8555
- FFUI Default Sort Options: FFMT-4397
The following enhancements are internal-only and not exposed to clients:
- CHAR-5534 and CHAR-5535: The legacy Get Order Item Information API has been copied to the KCCP Inventory APIs with full functionality, as well as the Get Order Item Log endpoint.
- CAT-5340: The locale code has been added to the search indexer message context in order to improve logging and troubleshoot indexing errors.
- FFMT-4438 and FFMT-4439: The carrier name is now passed on to the package class from the shipment data and the Fulfiller UI
The following bug fixes are internal-only and not exposed to clients:
- CHAR-5660: Fixed an issue where Order Routing was taking 10 minutes to reconnect to redis after rolling restart.
- COM-8621: Updated some application keys that were still hitting PHP Get Inventory instead of RIS.
- CHAR-5571: Some work has been done to fix serialization errors on the includeZeroInventory field in Inventory APIs. This is part of a REEDS Jewelers bug report about creating pick waves for locations with zero inventory, but that functionality is not currently supported because this field is not passed by the Fulfillment UI. Thus, this use case will not work until it is evaluated for a future enhancement.
Find more information about the client-facing bug fixes at these Jira tickets:
Production Sandbox Features
Commerce
- Unique External Order IDs: The system can now optionally enforce unique External Order IDs. When an order is imported, it will validate that the
externalIDfield is unique compared to existing orders. If it does match another order'sexternalId, an error will be returned. Kibo can enable this in your tenant attributes if you want to utilize this behavior. - Partial Pickup Ready Event: A new event notification (shipment.partialpickupready) has been created that is triggered when at least one shipment item is ready to pickup, even if other items in the same shipment are in another state such as Waiting for Transfer. This allows your applications to subscribe to this event and then alert the customer that they can pick up their item(s).
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Commerce | The BOPIS pickup reminder email was not being triggered at the expected frequency while shipments were awaiting customer pickup. This was due to incorrect Catalog IDs being used in the publishing context of the notification, which has been fixed so that emails are triggered as expected. |
Internal Sandbox Details
Find more information about the client-facing updates at these Jira tickets:
The following enhancements are internal-only and not exposed to clients:
- COM-8769: TTL has been added to the cache for the product/group site available queries.
- CHAR-5563: TLog support has been migrated to BigQuery, and the output is identical to what was received from Redshift for each log type. See the ticket for more details if needed.
Find more information about the client-facing bug fixes at these Jira tickets:
- Pickup Reminder Email: CHAR-5647 (reported by Al Futtaim)