Announcements
Cloudflare Migration for CDN and WAF
As part of our ongoing efforts to enhance platform performance and security, Kibo Commerce is migrating our Content Delivery Network (CDN) and Web Application Firewall (WAF) services to Cloudflare over the next several weeks. No action is required from you during this migration. However, please be aware that Kibo Support may reach out to you to coordinate the migration of certificates or address any specific needs related to your tenant. If you have any questions or concerns, please contact Kibo Support.Migration of Data Warehouse to GCP
Kibo Commerce is migrating its data warehouse behind the reporting infrastructure to Google Cloud Platform (GCP). This move is part of our commitment to leveraging advanced cloud technologies to improve data processing and reporting capabilities. The migration will take place over the coming weeks, ensuring minimal disruption to services. No action is required on your part. If you have any questions, please contact Kibo Support.EU Attribute Namespace Changes
On June 24, Kibo will be correcting attribute namespaces on EU sandbox tenants. Some product attributes that were expected to be in the tenant namespace were associated with the system namespace instead, which could be seen in the Admin UI under the System > Schema > Product Attributes details. This meant that updating these attributes was restricted. This change will move product attributes to the tenant namespace and allow updates on them going forward. If you have any questions or concerns, please contact Kibo Support. This will be reflected on the above Admin page and API access where namespaces are displayed, such as wherehttps://t<tenantId>.sb.euw1.kibocommerce.com/admin/s-<siteId>/attributes/edit/system~<attributeName> will now become https://t<tenantId>.sb.euw1.kibocommerce.com/admin/s-<siteId>/attributes/edit/tenant~<attributeName>
Production Tenant Features
Commerce
- External Discounts: An application is now available that allows you to apply order and item-level discounts from an external system to orders in Kibo. When this capability is enabled, Kibo will make an API request to the endpoint you provide to retrieve discount information. See the External Discounts documentation for more details about the API request and your expected response, external discount behavior, and installment instructions.
- Auto Capture Future Shipments: When configuring flexible auto capture, you can now select Future as a shipment state on which to capture the shipment amount. Future shipments are not included in forced auto capture by default, so if you want to capture future shipments then you must do so via flexible auto capture.
Fulfillment
- Signature Option Expansion: More signature options have been added to the UPS package signature integration, such as direct and indirect signatures. These options are now supported for FedEx as well, so packages being delivered by either carrier can make use of these delivery requirements.
Order Routing
- UI Enhancements: Following recent changes to the Order Routing UI, additional enhancements have been made to improve user experience. A link back to the routing strategy is now available when viewing the Scenarios page, making it easier to return to that page without re-navigating through the main routes page. The “Transfer to Store” fulfillment option has also been renamed to the more comprehensive “Transfer to Location.” Finally, some theme colors have been changed.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | Attributes could not be removed from the base product type because they were configured to be inherited from that product type. This is corrected so that attributes are not incorrectly marked as inherited and the base product type is not blocked from editing. |
| Catalog | Merchandizing rules did not allow more categories to be added after the initial set of categories was saved, as they would not be displayed in the UI. This has been fixed so that all categories added to a merchandizing rule are properly displayed. |
| Import/Export | Exports were timing out across all Import/Export categories. Performance improvements have now been implemented so that files can be successfully generated and downloaded. |
| Order Routing | When exporting custom data lists as a CSV file from the Order Routing UI, a Bad Request error was experienced that prevented download. This has been fixed so that the data is successfully converted to CSV and downloaded. |
| Order Routing | Setting up a distance-based filter was not working as expected, as fulfillment locations would be returned that were more than than the maximum distance from the shipping address. This has been corrected so that location distances are properly calculated and filtered out. |
Production Sandbox Features
Catalog
- File Manager Spinner: A loading spinner is now displayed in the file manager while retrieving data via the search function or changing to a new folder. Previously, there was no icon to indicate that files were loading which could result in users thinking there were no results returned. If a timeout does occur, an error message will clearly be displayed.
-
Multi-Locale Catalogs (US Sandbox Release): This feature allows you to configure catalogs that support multiple locales. You will be able to switch to any of the supported locales when viewing the product, product attribute, category, and discount configuration pages. Then you can change language-specific fields, such as product names and descriptions, to easily localize the content for that locale. For more general information, see the Multi-Locale Catalogs guide.
If you want to use this feature on an existing implementation, then you must contact Kibo Support to be upgraded to a new version of the Catalog Admin APIs and then rewrite your requests to provide a
localizedContentobject. The API documentation has been updated to reflect the new request models. If you upgrade and still need to manage product data that hasn’t been rewritten to the new model, you will be able to call the original version of the APIs without localization by including anx-api-versionheader set to “1” in your request. If you do not upgrade, then your current calls will not require any changes. This update was released to European sandboxes for stability testing on May 21. The testing period is now complete and it is being added to US sandboxes. It will progress to both EU and US production environments with the next release, where it will be available out-of-the-box for all new implementations and existing implementations will be able to upgrade if desired.
Fulfillment
- Configurable Shipping Label Orientation: You can now override the default orientations and styling of shipping labels through your Fulfiller UI theme. A new
shippingLabelOrientationsForCarriertenant setting is available as an array with configurations for each carrier where you can set the preferred orientation, CSS style, width, and/or height of that carrier’s labels. See the Fulfiller theme customization guide for more details.
Import/Export
- Search Term Redirect Status: Export files for search term redirects now include inactive redirects as long as they have not been deleted. A new “Status” column indicates whether that redirect is active or inactive. The export will not include any deleted redirects.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | Some attributes could not be deleted on the staging environment due to a query timing out. This has been corrected so that the query will not time out as easily and attributes can be successfully deleted in this environment. |
| Commerce | Qatar sites were displaying “QR” instead of “QAR” for the currency in both English and Arabic. This has been fixed so that the correct currency code is displayed. |
| Commerce | The SAR currency was being displayed as “SR” in the storefront page context and data layer tools. This has been corrected so that the correct currency code is displayed. |
| Commerce | When the general setting “Require login to view live site” was enabled, some email notifications were not sent because the email service was redirected to login. This has been fixed so that all emails will be successfully triggered when this setting is in use. |