> ## 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. # September 01, 2026 - 1.2634 Service Update ## **Announcements** ### **Admin Left Navigation Update** KIBO will release an updated Admin left navigation, available in Production Sandbox from September 1, 2026 and in Production from September 14, 2026. See this [walkthrough video and guide](https://app.guidde.com/playbooks/rjQAfxfLzaagQMHJLZZZ3Y?origin=tu4WuEdc43eEtvi5z8W7zxZ0le92\&mode=videoAndDoc) for a breakdown of the changes. Please contact [KIBO Support](https://help.kibocommerce.com/) if you have any questions. ### **CyberSource Message-Level Encryption (MLE) Update** CyberSource is requiring merchants to migrate to their new JWT/MLE authentication method. KIBO has released 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 14 Sept 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 * **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. ## Production 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. | ## Production Sandbox Features ### **B2B Wholesale OMS** KIBO now supports contractual wholesale purchasing in the OMS. B2B merchants can capture long-term purchase agreements, draw down quantities against them, and release call off orders into fulfillment-ready sales orders. * **Blanket Orders:** [Blanket Orders](https://docs.kibocommerce.com/pages/blanket-order) capture a customer's contractual commitment to buy specified quantities over a defined period. A Blanket Order is the single source of truth for committed and consumed quantities, giving teams a forward view of demand for procurement planning. * **Call Off Orders:** [Call Off Orders](https://docs.kibocommerce.com/pages/call-off-orders) draw down quantities against a Blanket Order, or create a Call Off Order on its own. Each line can carry its own quantity, requested ship date, and delivery location. * **Call Off Release Rules:** [Call Off Release Rules](https://docs.kibocommerce.com/pages/call-off-release-rules) control when a Call Off Order line becomes eligible to convert into a Sales Order. A configurable rules engine determines which lines release and when, based on criteria you define. * **Shipment Release Rules:** Control when Sales Orders in Hold Shipment status are released for shipment fulfillment. A configurable[ Shipment Release rules](https://docs.kibocommerce.com/pages/shipment-release-rule) engine determines which shipment release and in what priority order, based on customer, product, shipment, and location criteria you define. * **Reservations & Reservation Rules:** Soft-allocate inventory against Call Off Orders so committed stock is protected from other order types without locking it into a shipment prematurely.[ Call Off Reservation Rules](https://docs.kibocommerce.com/pages/call-off-reservation-rules) determine which Call Off Orders are eligible for[ reservation](https://docs.kibocommerce.com/pages/reservations) and in what priority order, with a configurable time fence around the requested ship date. * **Allocation Rebalancer:** Detect supply and demand changes — PO delays, short shipments, order cancellations — and automatically reprioritize future shipments and backorder queues in response. Runs on a configurable schedule or on demand. * **Future Shipment Rules:** Prioritize future shipments during reallocation by the[ Allocation Rebalancer](https://docs.kibocommerce.com/pages/allocation-rebalancer). * **Backorder Shipment Rules:** Re-rank the full backorder queue against the revised inventory position on every rebalancer run, determining which backorder shipments release into fulfillment and in what order. * **Reservation Rebalancer:** Re-secure soft inventory reservations on Call Off Orders when a supply disruption affects already-promised inventory. Draws from free available supply first; if still short, may take supply from lower-priority, later-shipping Call Off Orders under configurable rules and a hard ship-date buffer. * **Steal-For Rules:** Define which still-short Call Off Orders are eligible to attempt taking reserved supply from later-shipping, lower-priority Call Off Orders during[ Reservation Rebalancer](https://docs.kibocommerce.com/pages/reservation-rebalancer) * **Steal-From Rules:** [Steal-From Rule](https://docs.kibocommerce.com/pages/steal-from-rules) defines which Call Off Orders may give up reserved supply to higher-priority, earlier-shipping Call Off Orders. * **Blanket Network Reservations:** Reserve committed Blanket Order quantities at the network level so the entitled buyer's stock is protected from the moment of contract signing — before any Call-Off Orders are placed. The ring-fenced inventory draws down as Call-Off Orders consume the commitment. ### Catalog * **Price List Entries Export Filtering:** The Price List Entries bulk export now supports filtering by price list code, currency, active status, date range, customer segment, enabled state, exclusive-only flag, and site assignment. This allows you to export smaller subsets of price list entries — for example, only the entries for a specific channel or currency — instead of requiring a full export every time. Existing export requests without filters continue to export all entries as before. ### Fulfillment * **Configurable On-Complete Email Notifications for Workflow Steps** Building on the [configurable pop-up and dashboard redirect behaviors](https://docs.kibocommerce.com/pages/fulfiller-theme-customization#workflow-step-on-complete-behaviors) introduced in the 1.2632 service update, tenants can now configure an outbound email notification to be triggered when any BPM workflow step completes in the Fulfillment application. For each workflow step, tenants can specify whether to trigger an email, which Hypr email template to use, and which recipient audience to send to — Shopper, Fulfiller, Recipient, or AlternateContact. ## Sandbox Bug Fixes | **Service** | **Resolution** | | :---------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Commerce | Fixed an issue where order submission failed with an authorization error when return rules were enabled. | | Commerce | Fixed an issue where orders using external discount or pricing adapters failed to include line item tax in the total order amount. | | Commerce | Fixed an issue where the Decline Payment action was unavailable for asynchronous credit card payments in Authorize Pending or Capture Pending status. | | Commerce | Fixed an issue where the auto capture job repeatedly retried payments that were still awaiting confirmation from the payment gateway, which could result in duplicate capture or credit requests. | | Commerce | Fixed an issue where an order could transition to Errored status during shipment creation when the billing address had an empty or invalid address type. | | Commerce | Fixed an issue where receiving a return for an order containing non-taxable items or items shipped to a non-taxable state failed when using the Avalara tax integration. | | Commerce | Fixed an issue where saving shipping configuration for a Location Group failed with a validation error when a disabled shipping carrier had leftover default values from a previous version. | | Commerce | Fixed an issue where performing an admin cart takeover for a registered customer could merge items from previous customer sessions into the active cart. | | Commerce | Fixed an issue where pending orders were not automatically transitioning to abandoned status after the configured threshold period. | | Fulfillment | The Get Shipments API returned a 500 error when an after-action extension hook was enabled, even though the underlying shipment query completed successfully. This has been fixed so that shipment queries return results correctly regardless of whether after-action extension hooks are configured. |