Announcements
Migration of the AWS EU 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 EU Production environment from AWS to Google Cloud Platform (GCP). This migration follows the successful completion of our lower-environment migrations. TimingThe migration of EUW1 Tenant Pod 1 (EUW1-TP1) is scheduled for July 14, 2026, from 1:00 PM – 3:00 PM US Central time. A 2-hour maintenance window is required for this migration. This is a phased migration; additional US tenant pod migrations are scheduled separately in July and August. Impact
All EU Production tenants hosted on EUW1-TP1 will be migrated to GCP EU infrastructure. During the maintenance window, the EU Production environment (
https://….euw1.kibocommerce.com/… & https://t100000.tp1.euw1.kibocommerce.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
Ensure your teams and any connected systems are aware of the July 14 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 & FAQ 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.
Production Tenant Features
Inventory
- Future Inventory Fields in Delta and Full Inventory Exports: The delta and full inventory export jobs now include future inventory data alongside current inventory records. Exported records include future on-hand, available, and allocated quantities along with the expected future inventory date.
Dropship
- Vendor Profile — Fulfillment Location Mapping: Operators can now view and manage fulfillment locations directly from a vendor’s profile in the Admin Portal, eliminating the need to navigate to the Location Management module. A new Mapped Locations section has been added to the Vendor Profile Overview tab, providing visibility into all locations associated with the vendor. Operators can add one or more existing locations through a searchable modal that supports multi-select, bulk selection, and real-time filtering by name and code. Locations that are already mapped to the vendor are clearly identified and cannot be selected again. Operators can also remove mapped locations directly from the profile. Locations created by vendors in the Vendor Portal are automatically reflected in the operator’s Mapped Locations view, while locations assigned by operators become immediately available in the Vendor Portal without requiring any additional configuration. When no locations are associated with a vendor, an empty state is displayed while still allowing operators to add locations as needed.
- Vendor Shipping Mode — Operator-Managed Carrier Configuration: A new Vendor setting allows operators to define how vendors manage shipping across the organization. By default, vendors operate in Vendor-Managed Shipping mode, where they use their own shipping arrangements and manually enter tracking numbers for fulfillment. Alternatively, operators can enable Operator-Managed Shipping, allowing vendors to generate shipping labels directly from the Vendor Portal using carrier accounts configured by the operator. When labels are generated, the system automatically determines the appropriate carrier accounts and box types based on the configuration associated with the vendor’s fulfillment location. Manual tracking number entry remains available regardless of the selected shipping mode. This setting applies to the entire tenant rather than individual vendors or locations, ensuring a consistent shipping experience across all vendors. Changes take effect immediately without service interruption, and only Operator Admins have permission to modify the setting.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | Fixed an issue where merchants were unable to save changes to a product’s variant attributes. Attempting to update any variant attribute, including adding a value of a single character such as “1”, returned a validation error stating the attribute value was too many characters. Merchants can now save variant attribute updates without encountering this error. |
| Commerce | Fixed an issue where orders paid via Apple Pay or Google Pay would fail to capture the remaining balance when the order was split across multiple shipments with one or more on backorder. |
| Commerce | Fixed an issue where customer service representatives using cart takeover would encounter an error when attempting to add items to a shopper’s cart. |
| Commerce | Fixed an issue where subscription details, including subscription IDs and creation event logs, were intermittently missing from order data. |
Production Sandbox 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 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, which now also includes shipment attributes alongside order and subscription attributes. A new Extensible Item Attributes 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 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, alongside order and subscription attributes. Shipment line item attributes are managed under Extensible Item Attributes, 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.
Sandbox 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. |

