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 ATP — Cancel Future Inventory PO and Reassign Allocated Shipments: When a future inventory purchase order (PO) is cancelled, the system automatically reassigns any Ship-to-Home and Delivery shipments that were allocated to that PO. These shipments re-enter the standard fulfillment assignment process — checking for available inventory across eligible locations — so orders continue moving forward without any manual intervention. If the cancelled PO had no shipments allocated to it, the record is simply removed with no further impact.
Order Routing
- Location Code and Express Flag Support in Order Routing Filters: Order Routing filters now support
Location Codeas a first-class attribute in the Location filter group. Merchants can build routing rules based on a location’s specific code without needing extensible attributes as a workaround. TheCan Fulfill Express Ordersflag has also been added as a first-class filter attribute in the same location dropdown, enabling more precise routing control for express fulfillment scenarios.
Reporting
- Fulfillment SLA Dashboard: A new Fulfillment SLA Dashboard is now available under Kibo Standard Reports > Shipment > Fulfillment SLA Dashboard. This dashboard provides historical analysis of SLA performance across locations, fulfillment types, and time periods. It also provides a breakdown of each SLA across Compliant, At-Risk, and Non-Compliant thresholds, along with the average time in hours each SLA takes to complete. Users can further drill down into individual shipment workflow steps within an SLA to view average time spent at each step.
Production Bug Fixes
Production Sandbox 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.