Production Tenant Features
Commerce
- Storefront 2FA and OTP: You can now integrate Two-Factor Authentication and One-Time Password features for customers signing into their account on your storefront. When either one is triggered (either because you've configured your login process to always require it, or because the user's device fingerprint or region changed), the customer will have three minutes to input a code sent to them via email. If the time expires or they enter an incorrect code three times, they must request a new one. This feature will be kept in sandboxes for additional time before being released to production tenants on August 18.
Fulfillment
- Multiple Consolidation for Delivery: You can now enable multiple consolidation under your Delivery Consolidation site settings if you want to route items through multiple consolidation locations when there no single consolidation location is appropriate for an order. This dedicated toggle allows you to configure your fulfillment preferences separately for Delivery and Ship to Home fulfillment types.
- Pick Wave Rules: Pick waves can now be created based on defined business rules. This allows you to improve fulfillment efficiency and accuracy by configuring reusable rules based on products, customers, and shipments (such as for specific product codes, product attributes, B2B accounts, shipping methods, carriers and many other criteria) to customize the criteria for pick waves. The ability to create a pick wave by selecting a fulfillment type (such as BOPIS) will still be available in the rule criteria. When this feature is enabled, the Advanced options previously available while creating pick waves will be within rules. Only shipments matching the selected rule's criteria will be included in the wave.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Commerce | After editing and saving an order attribute of the List type, its values were being replaced by their labels which resulted in orders not passing validation. This has been fixed so that attributes properly retain their values after saving and orders with those attributes can be placed successfully. |
| Commerce | After reauthorization, some orders imported with a fraud status were returned to Pending Review when they should have had their payment captured instead. This was due to an issue with validation data not being updated on the order data, which has been corrected so that these cases can progress as expected. |
| Commerce | Bundles were unable to be changed (downgraded, upgraded, or switched between) in some Canadian subscriptions when a standard product with extras was only enabled for Direct Ship / STH and then added to a subscription. This has been fixed so that bundles can be successfully updated. |
| Commerce | Order Routing API Extensions were not being invoked for configurable shipment release, in which orders were in the Pending Shipment status. This has been corrected so that API Extensions are correctly called for these cases. |
| Import/Export | Dynamic categories were not updated as expected from import files if expressions were not provided. The expression column has now been added to these file templates as a default and validation has been added to ensure that imported data contains a valid expression.
Note that if you import files with minimal columns to make small changes (such as disabling a category or changing its parents), then you should contact Kibo Support to enable backwards compatibility for your previous behavior. Otherwise, the expression will be required going forwards. |
| User Management | Some menu links were still displayed for user roles, like Catalog Manager, even if the users couldn't actually access them due to the role not having appropriate permissions. The Admin UI navigation has been updated to hide these menus where applicable to reduce confusion. |
Internal Production Details
Find more information about the client-facing updates at these Jira tickets:
- 2FA and OTP: COM-9420
- Multiple Consolidation for Delivery: CHAR-6231 and COM-9560
- Pick Wave Rules: FFMT-4754
The following enhancements are internal-only and not exposed to clients:
- CAT-6657 and CAT-6717: As part of work being done to Solr authentication, the auth header has been added to all Catalog Solr HTTP calls and a safety catch has been implemented for config keys.
- COM-9616 and COM-9693: Locking has been added to returns processes to prevent race conditions.
- FFMT-3614: Validation has been added to ensure that shipments cannot be created or reassigned when their order is in the Errored state.
- COM-9705: Scoped service factory is now supported for order handling, allowing for better tenant context isolation and correlation tracking.
- CAT-6616: Cleanup has been done to reduce some API log noise.
- CHAR-6269: Work has been done for code compatibility in the Inventory service and to remove sensitive credentials from fetch and export logs.
Find more information about the client-facing bug fixes at these Jira tickets:
- Saving Order Attributes: COM-9604 (reported by Ssense)
- Orders in Pending Review: COM-9732 (reported by Fleet Farm)
- Change Subscription Bundles: COM-9708 (reported by Proactiv)
- Order Routing API Extensions: COM-9707 (reported by Office Depot)
- Expressions in Category Import: CAT-6647 and CAT-6603
- Display Menu Permissions: COM-9035
The following bug fixes are internal-only and not exposed to clients:
Production Sandbox Features
Commerce
- Returns API Extensions: New HTTP API Extensions are now available to perform custom functions before and after the Create Return, Restock Return Items, and Dispose Return Items processes.
- Return Pickup Date: You can now provide a
pickupDatein the Create and Update Return endpoints, as well as use it to filter the Get Returns API. This allows you to specify the scheduled or requested date when a returned item should be picked up from the customer, and is a date/time in UTC format. The linked API documentation will be updated soon to include that field in the request and response models. - Customer Rules Update: A warning message is now displayed while editing a customer rule that is referred to by another return rule or purchase limit rule. This message informs the user that edits will apply to all other return or purchase limit rules that the customer rule has been added to.
Inventory
- Update Available Inventory: You can now choose to directly modify Available inventory levels with the
quantityfield when calling the Refresh/Adjust APIs or importing a file, where previously this field was used for the On Hand amount and the system then calculated the appropriate Available count. Likewise, you can enable the ability to modify the Available field in the Inventory UI where previously only the On Hand field would be editable. Contact Kibo Support if you want to switch to this new behavior; otherwise your existing inventory processes will not be affected.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | Some product variations were unable to be updated on a particular implementation due to a "Product Variation Product Code Already Exists" error where the code had previously been orphaned. Cleanup has been done to remove these old codes so that they may be reused.
|
| Catalog | Products were not being updated with the correct sales rank numbers as expected in cases with multiple master catalogs. This has been correct so that these values are updated appropriately when updates are imported. |
| Catalog | Some extras were erroneously removed from their product configurations after updating products via the Import/Export tool. This has been fixed so that product files can be imported without losing the configured extras. |
| Commerce | Digital shipments were intermittently not auto-fulfilling on some production environments. This has been updated so that all digital shipments are automatically fulfilled as expected. |
| Commerce | Extensible product attributes were not being sent to Order Routing on some orders from OMS-Only implementations. This has been fixed so that these attributes are passed as expected. |
| Commerce | API Extensions were not being invoked when making Order Routing calls for suggestions with estimated delivery dates. This has been corrected so that API Extensions are correctly called for these cases.
|
| Commerce | A 403 Forbidden error was returned when some Admin users tried to view Pending Shipment orders, even though the users had the appropriate permissions. This has been fixed so that Pending Shipment orders can be successfully accessed. |
Internal Sandbox Details
Find more information about the client-facing updates at these Jira tickets:
- Returns API Extensions: COM-9670
- Return Pickup Date: COM-9711
- Customer Rules Update: COM-9695
- Update Available Inventory: CHAR-6234
The following enhancements are internal-only and not exposed to clients:
- ICKY-1851 and ICKY-1802: Hardcoded shipment rule fields have been removed and API integration has been improved.
- COM-9348 and COM-9721: Caching improvements have been made to the Get Transit Times process.
- CAT-6689: A new endpoint, GET
.../commerce/catalog/storefront/discount_redemption/{orderNumber}/redemptionshas been added that returns a list of discounts already redeemed for an order. - COM-9677: As part of work being done to Solr authentication, the auth header has been added to all Commerce Solr HTTP calls.
- COM-9651: The auto capture job will no longer retry bad transactions after 20 failures, in order to avoid continuously generating bad data.
- CHAR-9684: More work has been done for code compatibility in Dev Center, Inventory, provisioning, and other services.
Find more information about the client-facing bug fixes at these Jira tickets:
- Orphan Product Variations: CAT-6700 (reported by Sun & Ski)
- Updating Sales Ranks: CAT-4933 (reported by Calendars)
- Product Extras Removed: CAT-6715 (reported by French Toast)
- Digital Shipment Fulfillment: COM-9703 (reported by Sound United)
- Order Routing Attributes: COM-9606
- EDD API Extensions: COM-9689 (reported by Sound United)
- Pending Shipment Orders: COM-9743 (reported by Honey Birdette)
The following bug fixes are internal-only and not exposed to clients:
- CHAR-6264: Fixed an issue where the backFillMissingProducts method was crashing when the input included duplicate product codes.
- CHAR-6025: Fixed an issue where Order Routing was not running all tests in Jenkins.
- CAT-6721: Fixed an issue where shipment rules could not be saved in a dev environment.
- COM-9562: Fixed an issue where reservations did not pass the appropriate shipping address information to Order Routing suggestion calls.