Production Tenant Features
Commerce
- Email Length Restriction: Validation has been added to ensure that email addresses on customers and orders do not exceed a maximum limit of 254 characters.
Inventory
- Inventory Tag Restrictions: A default maximum limit has now been placed on how many inventory tags and individual values can be allowed. This limit is 3 tags and 6 tag values (across all tags) per tenant.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Commerce | When orders were placed with valid addresses that didn’t include zip codes, such as for UAE locations, shipping methods would not be available. This has been corrected so that these addresses are still accepted and allow shipping methods to be selected for those orders. |
| Fulfillment | Customer Care shipments created from partial quantities of items were missing the fulfillment location code of the original shipment, causing undefined errors during reassignment. This has been fixed so that when some quantity is not available and gets sent to Customer Care, they can be successfully reassigned. |
| Fulfillment | Attempting to generate shipping manifests resulted in an error if any ineligible (such as voided) shipments were included in the manifest. This has been corrected so that manifests are no longer blocked from being generated in this case, allowing valid shipments to be fulfilled. |
| Fulfillment | For a certain implementation, the Create Manifest would appear to spin the loading icon endlessly despite actually creating the manifest in the backend (which was then accessible via the Reprint button). This has been fixed so that the icon stops spinning in the Fulfiller UI when the action is complete. |
| Fulfillment | UPS tracking numbers in the Admin and Fulfiller UIs did not match the actual tracking on shipping labels. This occurred when the fulfiller user mistakenly clicked the Print Shipping Label button more than once. The interface has now been updated to ensure that duplicate clicks will not create additional tracking numbers. |
Production Sandbox Features
Catalog
- Hidden Sales Ranks: The product properties for the Sales Rank boost/bury field were visible on storefronts alongside other properties, even though those values are not relevant to customers. These fields have now been updated to be hidden from shoppers.
Commerce
- 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. While API support will be released to production with the rest of 1.2412 changes, the full feature is being kept in sandboxes for additional time (including the site setting shown in the user guide) and will go to production in the following release. - Backorder Release Update: The backorder release process has been updated to consider future inventory while releasing shipments for fulfillment. Where previously the system only looked for available current inventory to satisfy the shipment, it will now release shipments if there is enough future inventory or a combination of current and future inventory available. Current inventory will always be prioritized for assignment.
Fulfillment
- Display Duty Total: If you use duty fees for internationally-traded products, those duty totals will now be displayed on shipment details in the FFUI as a separate line from the Tax total.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | When attempting to change the product type on specific products, a blanket change was instead performed across all products. This has been corrected so that product type changes made through the Quick Edit feature will not erroneously update other products. |
| Commerce | Some successfully-imported orders were not visible in the Admin UI if their data did not include all payment fields. This has been fixed so that if an imported order is missing required data, an error will be returned instead of a successful 200 OK response. |
| Commerce | An order experienced a SplitOrderIntoShipments error without a suggestion log, as a result of an internal server error. The logging process has been improved to ensure that orders include suggestion logs even during these scenarios. |
| Commerce | The SAR currency was incorrectly displayed as “SR” on the Catalogs UI. This has been corrected so that this currency uses the correct abbreviation. |
| Commerce | Customer accounts could not be successfully disabled due to validation errors if duplicate attributes had been added with the Add Account Attribute API. This API process has been updated to better handle this error situation and allow accounts to be disabled if needed. |