> ## 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. # August 18, 2026 - 1.2632 Service Update ## **Announcements** CyberSource is requiring merchants to migrate to their new JWT/MLE authentication method. KIBO will release an updated CyberSource integration to support this migration, available in Production Sandbox from **18 August 2026**. Please be prepared to test all relevant scenarios in your sandbox environment once this is available, to make sure they work as expected. Once this update goes to production on **31 August 2026**, you will need to complete your migration in production **by CyberSource's deadline of September 2026**. Please contact [KIBO Support](https://help.kibocommerce.com/) if you have any questions. ## Production Tenant Features ### Catalog * **Configurable Variant Property Limit per Product Type:** Merchants can now configure the maximum number of variant properties allowed on a product type beyond the previous hard limit of 30. A new tenant attribute, `catalog.productType.maximumVariantProperties`, controls this limit on a per-tenant basis, with a default of 30. The Product Type admin page, Product Edit page, and Active Properties modal all function correctly when the configured limit exceeds 30, and the related API endpoints return all variant attribute values without truncation. Import and Export operations are also subject to the same limit enforcement. * **"Block Discounts That Cancel Their Own Minimum" Setting in Discount Condition Settings:** A new toggle — "Block discounts that cancel their own minimum" — is now available under System → Discount Settings → Condition Settings. When enabled, this setting `(rejectSelfDefeatingDiscounts) `prevents a discount from applying if applying it causes the order to fall below the discount's own configured minimum. The toggle is off by default and includes a tooltip explaining its behavior. The setting is localized across all supported Admin UI locales (English, German, Spanish, French, Japanese, Korean). The existing "Include discounts for order min/max condition evaluation" toggle is unaffected. * **Dynamic Price List Hierarchy Exposed as Product Property:** The Product Runtime service now captures the dynamic price list hierarchy produced by the `GetPriceListHierarchy` Arc action and exposes it as a product property `(system~DPLH)` on the price object. When the Arc action modifies the hierarchy relative to the default, the `system~DPLH` property is populated in `GetProduct` and `ValidateProduct` API responses, listing the price list codes from most-specific to least-specific. The property is hidden from shoppers and is omitted entirely when the hierarchy is unchanged or no Arc action is configured. This is an additive change to the API contract; existing integrations are not affected. ### Commerce * **Payments - Support for Externally Tokenized Payment Instruments:** Processing payments using tokens issued by an external payment token provider is now supported, allowing card and other instrument data to remain securely outside the platform (entirely skipping the KIBO vault) while payments are still authorized, captured, voided, and credited as usual. This gives businesses added flexibility in how they manage payment credentials, while preserving all existing payment behavior for those who continue using standard tokenization. ### Inventory * **Send Negative Inventory in Export files:** Merchants whose inventory positions can fall below zero can now receive those accurate negative quantities in scheduled [inventory export files](https://docs.kibocommerce.com/pages/inventory-export-file). A new export setting, `sendNegativeInventory`, allows export configurations to pass through real negative available quantities rather than clamping them to zero. When this setting is disabled (the default), export behavior remains unchanged — negative quantities continue to appear as 0 in the file, preserving existing behavior for all other merchants. ## Production Bug Fixes | Service | Resolution | | :---------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Catalog | Fixed an issue where updating a product that belongs to a Collection product type would fail with a mapping error. Merchants can now successfully update Collection-type products via the Product Admin API without encountering an error. | | Catalog | Fixed an issue where Japanese Admin UI labels were systematically incorrect across the Order listing, Order detail, Shipments, Returns, and Payments screens. Merchants using the Admin UI in Japanese will now see accurate, contextually correct translations across these screens. | | Commerce | Fixed an issue where Buy Online, Pickup In Store (BOPIS) orders containing duplicate bundle components within a single bundle product failed during shipment creation, leaving the order stuck in Validated status with an error. | | Commerce | Fixed an issue where a Vendor SKU could be mapped to multiple retailer UPCs without warning or validation, potentially resulting in incorrect inventory mapping. | | Commerce | Fixed an issue where item custom data was missing from Order Routing suggestion logs when Configurable Shipment Release and "Reserve inventory when order status is Pending Shipment" were both enabled. | | Fulfillment | Fixed an issue where canceling an item from a BOPIS shipment that has associated transfer child shipments resulted in a generic "Error while canceling shipment item" error and an HTTP 500 response. Canceling a shipment item now succeeds correctly, even when the item being canceled does not exist in one or more of the associated child transfer shipments. | | Fulfillment | Fixed an issue where submitting an assembly order whose parent and child items were routed into separate shipments caused Commerce Runtime to retry the order acceptance indefinitely — generating multiple errors over multiple days for a single order. The Fulfillment API now returns a clear validation error for this constraint, causing the order to terminate cleanly rather than entering a retry loop. | | Fulfillment | Fixed an issue where GET /commerce/shipments queries filtering by multiple order IDs were timing out and returning client disconnect errors in production. The internal query builder now lifts all order ID filters into a single top-level IN comparison rather than generating a branching \$or shape, resolving the excessive planning overhead that caused the timeouts under load. | ## Production Sandbox Features ### Catalog * **Variant Product Code Search in Catalog Admin**
Merchants can now search for products in the Catalog Admin using variant (child SKU) product codes. A new dedicated **Variant Product Code** field is available in the Advanced Filter panel on the product list page, allowing users to locate a configurable product's variant directly by its code. Previously, the product list search only matched on base product codes and product names, meaning users who knew only the variant code received no results and had to look up the corresponding base product code separately. The new field can also be used via the quick-filter textbox. ### Fulfillment * **Multi-Package Receiving for Transfer Shipments** Store associates and fulfillment operators can now receive transfer shipments on a package-by-package basis. Previously, a transfer shipment could only be received as a single, all-or-nothing action. With [multi-package receiving](/pages/transfer-shipments#multi-package-receiving), each individual package within a shipment can be scanned or manually acknowledged as it arrives — by tracking number or through item-level validation — independently of the others. The shipment transitions to a Partially Received state as packages arrive and automatically completes to Received/Fulfilled once all packages have been accounted for. * **Configurable On-Complete Pop-ups and Dashboard Redirect for Workflow Steps** Tenants can now [configure step-specific behaviors](/pages/fulfiller-theme-customization#workflow-step-on-complete-behaviors) — an instructions pop-up and/or an automatic redirect to the shipments dashboard — for any BPM workflow step in the Fulfillment application, including both out-of-the-box and custom steps. These behaviors are triggered only when the associate clicks **Continue**; Skip and Back are unaffected. ## Sandbox Bug Fixes | **Service** | **Resolution** | | :---------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Commerce | Fixed an issue where updating a vendor without specifying a Vendor Type would incorrectly reset it to '0' instead of retaining the existing value, preventing vendor activation. | | Commerce | Fixed an issue where saving a customer contact with a phone or fax number longer than 20 characters resulted in an unexpected error instead of a clear validation message. | | Commerce | Fixed an issue in the Vendor Portal where submitting a "Forgot Password" request triggered two password reset emails instead of one. | | Commerce | Added logging for the One Time Code (OTP) validation flow to provide greater diagnostic visibility and assist with troubleshooting during user authentication. | | Fulfillment | Fixed an issue where BOPIS shipments were incorrectly transitioned to **Customer Care** status before their configured pickup deadline had elapsed. This occurred when a location was shared across multiple sites with different pickup policies — the wrong site's policy was applied during the late-pickup background job, causing shipments to be escalated prematurely. | | Fulfillment | Fixed an issue where the Location Shipment Count API (`GET /locationShipmentCount`) could time out and return client disconnect errors when queried with a large list of location codes. Merchants and order routing operations that rely on real-time location capacity data will no longer encounter these timeouts. |