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
- Customer Email and Password Update Notifications: You can now configure automated email notifications to trigger whenever a customer updates their email address or password. This feature introduces distinct templates (
customer-email-updatedandcustomer-password-updated) to ensure customers are immediately informed of critical account changes. For added security, email address update notifications are sent to both the new and previous email addresses. - Fulfillment Automated Return Label Notifications: The platform now publishes a
ReturnLabelAddedevent whenever a return label is successfully generated. This update triggers a new automated email notification (product-return-label-added) to share label details and tracking numbers with customers immediately.
Fulfillment
- Shipment On Hold – Update: The
ReleaseHoldShipmentjob has been enhanced to support automatic release of shipments in Hold status based on both Hold Release Date and Time.
Previously, automatic release considered only the date component, causing shipments to be released on the set date while ignoring the configured time. With this update, the system now evaluates the full date and time value, ensuring shipments are released at the scheduled time.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Commerce | Fixed an issue where processing multiple return refunds simultaneously on the same order caused discrepancies in refund totals and received quantities. The system now ensures that concurrent return operations are synchronized correctly, maintaining accurate payment and status updates at both the return and order levels. |
| Commerce | Fixed an issue where the totalCollected field incorrectly returned a value of zero when calling the Get Order API with mode=synthesized. |
| Commerce | Fixed an issue where adding pickup items to orders in Pending Shipment status caused shipments to be incorrectly assigned despite inventory being available at the fulfillment location. |
| Commerce | Fixed an issue where customer Import/Export operations and GetAccounts API calls returned inconsistent results—including missing or duplicate accounts. The API now returns complete and accurate data when retrieving customer accounts. |
| Commerce | Fixed an issue where printing Canada Post labels through EasyPost would fail if the shipment contained items with a zero-dollar value. The system now ensures a minimum required customs value is applied to items, allowing fulfillment to proceed for orders with zero-dollar item prices. |
| Commerce | Updated inventory validation to ensure the total quantity of a product is validated across all line items during checkout and order submission. This ensures that orders do not exceed available stock even when products are split across multiple lines due to different product extras. |
| Inventory | Fixed an issue where the inventory quantity field was incorrectly included in API payloads when only non-quantity fields (Safety Stock, Floor, LTD) were modified. The system now only sends the quantity field when the actual On Hand or Available quantity values change, preventing unintended inventory updates and ensuring proper restoration of quantities when safety stock is removed. |
Production Sandbox 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.
Sandbox 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. |