Skip to main content

Announcements

Migration of AWS US Sandbox Environment to Google Cloud Platform (GCP)

As part of KIBO’s ongoing commitment to providing a modernized cloud architecture that scales with your business, we are migrating our US sandbox environment from AWS to Google Cloud Platform (GCP). Timing
The migration is scheduled for March 25, 2026, starting at 6pm US Central time. A 6-hour downtime window will be required for this migration.
Impact
All AWS US sandbox tenants and services will be migrated to GCP.
During the migration window, the AWS US sandbox environment (https://t00000.sandbox.mozu.com/...) will be temporarily inaccessible. Sandbox services will be intermittently available during this time.
KIBO will automatically redirect all existing sandbox endpoints to the GCP infrastructure following the maintenance window.
Legacy Sandbox Orders Performance Optimization: Orders >60 days old will become non-progressible.
Client-side Actions Post-Migration
None; KIBO will automatically redirect traffic to the new infrastructure.
However, if your organization uses IP whitelisting, you must add the new GCP NAT gateway addresses found in our Knowledge Base prior to the migration date to avoid service interruption.
Find our more details about this migration in our Support Portal article: Action Required: AWS US Sandbox Migration to GCP (March 2026).
If you have questions, please contact KIBO Support.

Amazon Pay v2 update

To support Amazon’s update to Amazon Pay v2 (Checkout v2), all clients currently using Amazon Pay v1 are required to migrate to the new version. KIBO will support this transition with an updated Amazon Pay v2 integration, available in sandbox environments from January 22, 2026. You should test all relevant scenarios in your sandbox environment to make sure they work as expected. Once this update goes to production on March 02, 2026, you will have until March 20, 2026, to switch over to Amazon Checkout v2 in production. Amazon Pay v1 will no longer be supported after March 31, 2026 by Amazon. Please contact KIBO Support if you have any questions.

Production Tenant Features

Commerce

  • Independent JWT Expiration and Refresh Configuration: Introduced more granular configuration options for JWT token expiration and refresh periods. Tenants can now set independent session durations for different client applications, providing greater flexibility and control over JWT token expirations.
  • New Order Event for Pending Shipment Status: Introduced the order.pendingshipment event , which is triggered when an order transitions to the Pending Shipment status.

Fulfillment

  • Shipment On Hold – Update: CSR admins can now place a Ready shipment on Hold directly from the Admin UI via a new “Hold Shipment” button in the Update Shipment dropdown. When placing a shipment on hold, admins can optionally set a Hold Release Date and Time. On the Fulfillment UI , fulfillment users can now filter shipments by Hold status using the Advanced Filter dropdown . Additionally, when viewing a held shipment on the Fulfillment workflow page, the Shipment Release Date is displayed.

Production Bug Fixes

Production Sandbox Features

Fulfillment

  • Shipment on Hold - Updates: Fulfillment users can now place a shipment on hold or release it directly from the Actions dropdown on the Shipment Details page in the Fulfillment UI.

Order Routing

  • Order Routing UI redesign- Updates: Users can now export Filter Data Lists as a CSV file directly from the new Order Routing UI. A “Download as CSV” button has been added to the Filter Data List page, allowing users to export all values and descriptions for a selected site’s data list.

Commerce

  • Flexible Per-Customer Coupon Limits: Users can now configure coupon codes to have unlimited per-customer redemptions. Previously, the “Max redemptions per customer (Per Code)” field in the Coupon Set editor required a numeric value and displayed a confusing “Defaults to 1” placeholder. With this update, user can leave the field completely blank to indicate no per-customer limit. Important note: Leaving this field blank also allows guest shoppers to redeem the code, whereas entering any numeric value will automatically restrict the coupon to logged-in users.

Sandbox Bug Fixes