Announcements
Kount 360 update
Kount requires migration to their Kount 360 platform. KIBO has released a new Kount 360 compatible application to support this migration. Sandbox release: November 13, 2025 - The Kount 360 application was made available. Sandbox additional fixes: February 3, 2026 - KIBO recommends clients re-test their Kount integration in sandbox after this release. Please report any issues you have found to KIBO Support. New Production Completion date: February 26, 2026 - You must complete your changes and validation in production by this updated date.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
- FedEx One Rate: Clients can now utilize FedEx One Rate by enabling it on FedEx carrier account setup in KIBO. Clients can now leverage flat-rate pricing provided as a part of FedEx One Rate.
Fulfillment
- Multi-Consolidation for Delivery Shipments – Update: Multi-Consolidation for Delivery shipments has been enhanced to better handle short inventory scenarios. When transfer shipments have no or partial inventory within their configured transfer networks, the system now evaluates additional delivery locations to create new Delivery shipments and leverages their transfer networks to source the remaining inventory before applying after-actions.
- Rate Shopping in Fulfillment: You can now perform Rate Shopping during order fulfillment to compare shipping rates across multiple configured carriers and select the most cost-effective carrier-method combination for Ship to Home (STH) and Transfer shipments. Eligible options are highlighted alongside all available alternatives to help optimize shipping costs while maintaining service commitments.
Note: Above Rate Shopping in Fulfillment feature only supports Standard US Carriers for Ship to Home and transfer Shipments.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Commerce | Fixed an issue where failed login attempts accumulated and were not reset after a successful login. The system now correctly resets the failed login count upon successful authentication, preventing unintended account lockouts. |
| Commerce | Fixed an issue where reCAPTCHA validation was incorrectly triggered when adding payments in Admin, causing a 409 error. |
| Commerce | Fixed an issue where Kount Fraud Detection results were not populating in the Admin interface after upgrading to Kount 360. |
| Inventory | Fix the Inventory API to correctly respect the includeNegativeInventory parameter by excluding locations that have zero or negative available inventory(after safety stock adjustments) from the API response. |
Production Sandbox 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.
Sandbox 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. |