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). TimingThe 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.pendingshipmentevent , 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
| Service | Resolution |
|---|---|
| Catalog | The dynamic category preview tool in the Admin UI was failing to render results for secondary locales (e.g., a Chinese site sharing a catalog with an English site), often displaying zero products despite valid matches. This has been corrected so that the preview now accurately applies the selected site’s locale and currency context, allowing merchandisers to validate dynamic rules across all regions reliably. |
| Catalog | Users assigned to specific customer segments were occasionally experiencing inconsistent pricing when returning to the storefront after closing their browser. In these instances, the segment-specific price list failed to load, causing the system to revert to default pricing. This has been corrected so that user segment data is accurately persisted and refreshed across sessions, ensuring the correct pricing is always applied for logged-in users. |
| Catalog | An issue was identified where the ‘Category’ search facet would display an incomplete list of filters (e.g., showing only “Women” when valid products for “Men” or “Kids” were also present in the results). This was caused by an error in how category hierarchy parameters were bound in the search URL. This has been corrected so that all relevant category filters now populate correctly based on the search results, ensuring users can refine their searches across all available product categories. |
| Catalog | Category facets were missing or functioning incorrectly on storefront pages due to a conflict where the system prioritized categoryCode over the template-defined categoryId. This caused issues with hierarchical refinement and SiteBuilder compatibility. This has been corrected so that the API now automatically prioritizes categoryId, ensuring facets appear correctly and navigation works as expected. Additionally, a case-sensitivity issue with category codes has been resolved. |
| Commerce | Fixed an issue where carts containing items with multiple unique purchaseLocation values failed to convert to an order due to pricing validation errors. The system now correctly handles and validates item-level pricing from different purchase locations during the order creation flow. |
| Inventory | Resolved slow response times on the Get Inventory GraphQL API that were correlated with concurrent Smart Refresh (/inventory/smart-refresh) calls, resulting in 499 timeouts and downstream service errors. |
| Inventory | Resolved intermittent socket timeout errors occurring when Order Routing called the Real-time Inventory service, which caused inventory lookup failures and degraded order routing performance. |
| Fulfillment | Resolved an issue where the “Exclude Blocked Location” checkbox was appearing in the Fulfiller UI (FFUI) during the Validate Stock step, even when the theme configuration explicitly disabled it using isAllowExcludeLocation: 0 in the theme’s en.json file. |
Production Sandbox Features
Reporting
- Operational Dashboard: An integrated section within the KIBO Admin Console for real-time and historical monitoring of operational health — combining business and technical metrics in a single experience.
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
| Service | Resolution |
|---|---|
| Catalog | Fixed an issue where importing a product attribute file containing localized attributes incorrectly created those attributes as options rather than properties. The import now classifies these localized attributes as properties, eliminating related API validation errors and maintaining a correct product catalog structure. |
| Commerce | Fixed an issue where externally set override prices were removed when a checkout was subsequently updated from the storefront, such as when adding shipping or payment details. The system now correctly preserves prices set via external price mode throughout the checkout lifecycle. |
| Commerce | Fixed an issue where a coupon code applied to an order became unavailable for reuse after the order was cancelled within the remorse period. Customers can now successfully apply the same coupon code to a new order following a remorse period cancellation |
| Inventory | Resolved the export coordinator’s inability to handle large-volume inventory exports, ensuring the CSV aggregation process completes successfully even when export file sizes are significantly larger than typical |
| Inventory | Added proper input validation handling for InventoryRequestValidationException in the OR suggestion API, so that requests with missing or null product identifiers/quantities are gracefully handled rather than causing uncontrolled errors. |
| Inventory | Fixed intermittent inventory import failures caused by S3 download timeouts by implementing a retry strategy across S3, GCS, and SFTP file streamers. Additionally, imports that fail due to a missing GCS file now correctly report a FILE_NOT_FOUND status instead of the generic SERVER_CONN_ERROR. |
| Fulfillment | Enhanced the event publishing logic to ensure all necessary status change events are reliably fired for digital shipments, allowing orders to complete their fulfillment workflow consistently. |