> ## Documentation Index > Fetch the complete documentation index at: https://docs.kibocommerce.com/llms.txt > Use this file to discover all available pages before exploring further. # July 21, 2026 - 1.2628 Service Update ## Announcements ### Migration of the AWS TP2 Production 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 Production Tenant Pod 2 (TP2) environment from AWS to Google Cloud Platform (GCP). This migration follows the successful completion of our previous environment migrations. **Timing**
The migration of **Tenant Pod 2 (TP2)** is scheduled for **Tuesday, July 28, 2026, from 10:00 PM to Wednesday, July 29, 1:00 AM US Central Time**. A maintenance window of **up to 3 hours** is required for this migration. This is a phased migration; additional US tenant pod migrations are scheduled separately in July and August. **Impact**
All Production tenants hosted on TP2 will be migrated to GCP infrastructure. During the maintenance window, the **Production TP2 environment** ( `https://….mozu.com/…` & `https://t100000.tp2.mozu.com/…`) will be **unavailable**. The maintenance window should be treated as a **full service blackout** for all affected tenants. While some login pages or services may appear intermittently accessible, **no production activity should take place** during this time. Specifically: * All KIBO-hosted storefronts, APIs, and platform services for affected tenants will be unavailable * Orders, payments, shipments, and fulfillment processes will not be processed * Third-party integrations and any headless or API-connected systems will be unable to reach KIBO services KIBO will automatically redirect all existing environment endpoints to the new GCP infrastructure following the maintenance window. No DNS or endpoint changes are required on your side. **Required Client-Side Actions Before the Migration** **Plan for Downtime**
Ensure your teams and any connected systems are aware of the July 28 maintenance window. Plan to suspend all KIBO platform activity – including commerce, storefront operations, order management workflows, and integration traffic – for the full duration of the window. Review our [guide](https://help.kibocommerce.com/s/article/Summer-2026-AWS-Production-Tenant-Pod-Migrations-EUTP-TP2-TP6-to-GCP) & [FAQ](https://help.kibocommerce.com/s/article/2026-FAQ-AWS-Migration-to-GCP) articles in the KIBO Support Portal to get ready and prepare for this migration. If you have questions, please contact your KIBO Technical Account Manager or [KIBO Support](https://help.kibocommerce.com/). ### New Inventory UI The New Inventory UI (Supply/Demand UI) will be released to Production sandbox on July 21, 2026 as an **opt-in.** Your tenant will remain on the legacy Inventory UI by default. [Contact Kibo Support](https://help.kibocommerce.com/) to enable it for your sandbox tenant. ## Production Tenant Features ### Catalog * **Admin UI - German Locale Quality Improvements :** Merchants operating the Kibo Admin in German will see a broad set of translation improvements across the Admin interfaces. The updates address inaccurate or inconsistent German terminology throughout the platform — including standardizing the German term for "coupon code" (*Aktionscode*), normalizing return-related labels (*Retoure*), and correcting a variety of labeling issues across the Products, Categories, Price List, Discounts, and Publishing pages. These improvements bring the German locale experience significantly closer to DACH commerce industry standards. ### Dropship * **Vendor Portal — Forgot Password:** Vendors can now reset their Vendor Portal password directly from the Login screen. Vendors enter their registered email address to receive a password-reset link, then follow a guided flow to set a new password that meets the configured policy requirements. The reset link is single-use and expires after use. ### Commerce * **Geography-Based User Access (GBA):** The existing [GBA](https://docs.kibocommerce.com/pages/geography-based-user-access) capability has been enhanced to support state-level restrictions, in addition to the existing country-level controls. This allows you to limit what users can see and manage based on their assigned regional jurisdiction. * **Extensible Attribute and Extensible Line Item Attribute**: Order and subscription attribute configuration is now available under [Extensible Attributes](https://docs.kibocommerce.com/pages/schema-extensible-attribute), which now also includes shipment attributes alongside order and subscription attributes. A new [Extensible Item Attributes](https://docs.kibocommerce.com/pages/schema-extensible-item-attribute) capability has been introduced, enabling merchants to capture custom attributes at the individual line item level for orders and subscriptions. Merchants can define a single attribute that applies to one or more entities — Order, Subscription, or Shipment ### Fulfillment * **Pick Wave Rules — Custom Attribute & Custom Item Attribute Criteria in Shipment Rules:** Admins can now use Custom Attribute and Custom Item Attribute as criteria when building Shipment Rules. These options allow [pick wave](/pages/pick-wave-rules) routing logic to be driven by extensible attribute values at the shipment header and shipment item level, respectively. * **Extensible Attributes — Shipment and Shipment Line Item Attributes:** Shipment attributes are now managed under [**Extensible Attributes**](/pages/schema-extensible-attribute), alongside order and subscription attributes. Shipment line item attributes are managed under [**Extensible Item Attributes**](/pages/schema-extensible-item-attribute), alongside order and subscription line item attributes. For attributes that apply to both orders and shipments, the new **Attribute Value Sync** setting lets merchants either keep shipment attribute values continuously synchronized with the order or copy the order value at shipment creation, after which the shipment value can be updated independently. ## Production Bug Fixes | **Service** | **Resolution** | | :---------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Commerce | Fixed an issue where handling fee discounts were not distributed correctly across shipment items when the same discount applied to multiple fulfillment groups on an order, causing the item-level discount total to exceed the actual order handling discount amount. | | Commerce | Fixed an issue where some orders could be omitted from a generated GDPR data report, which prevented the associated customer information in those orders from being redacted. | | Commerce | Fixed an issue where duplicate customer accounts could be created with the same username, which could cause login failures | | Commerce | Fixed an issue where coupons applied to an abandoned order remained marked as used, preventing shoppers from reusing them on future checkouts. | | Fulfillment | Fixed an issue where the Locations dropdown in the Fulfiller UI appeared empty due to a routing conflict with the shipment aggregation endpoint. Locations are now populated correctly in the dropdown. | | Inventory | Fixed an issue where the estimated delivery date (EDD) was calculated too far into the future when a remorse period was applied and the fulfillment location was closed over the weekend. The remorse period now advances the EDD by only the configured amount, regardless of weekend store closures. | | Inventory | Fixed an issue on legacy tenants where inventory adjustment requests were routed to the wrong internal endpoint, causing external callers to receive failed responses. Adjustment requests now route correctly, eliminating the failures. | ## Production Sandbox Features ### Commerce **Fulfillment Location as Return Location:** When [creating a return](https://docs.kibocommerce.com/pages/initiate-a-return), the system now supports defaulting the return location to the shipment's fulfillment location. This behavior is configurable via a new site setting, "Use fulfillment location as return location," available under Return Settings. ### Inventory & Fulfillment **Inventory UI Upgrade (Supply/Demand UI):** The Inventory experience has been redesigned with an updated look and feel, along with new functionality.
Inventory management is now organized across dedicated pages — Inventory, Future Inventory, Shipments, and Settings — replacing the single, dense table view.
New capabilities amongst others include: * A **Supply & Demand view** for consolidated visibility into supply versus demand across multiple UPCs and locations * A streamlined way to view and manage individual inventory records * **New filter capabilities** by Product and Inventory attributes * A **calendar view** for future inventory See the [Inventory documentation](https://docs.kibocommerce.com/concept-guides/inventory) for more details ## Sandbox Bug Fixes | Service | Resolution | | :------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Commerce | Fixed an issue where orders for products configured with infinite inventory were incorrectly cancelled or moved to Customer Care status instead of being created in a Ready state. | | Commerce | Fixed an issue where subscriptions with a declined payment during continuity order creation remained in Active status instead of transitioning to Errored. | | Commerce | Fixed an issue where logging in via a One Time Code (OTP) failed to merge a shopper's guest cart with their authenticated account cart, causing the guest items to be lost. | | Catalog | Fixed an issue where saving or updating product attributes with values at or near the character length limit could result in unexpected server errors (HTTP 500) instead of a clear validation message. Merchants now receive an informative error response (HTTP 400) when an attribute value exceeds the allowed length. Additionally, existing product variant attribute values that were already stored in the database and exceeded the character limit are now preserved correctly during updates, rather than causing failures. |