> ## 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 15, 2026 - 1.2636 Service Update ## **Announcements** ### **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 since August 18, 2026. Please test all relevant scenarios in your sandbox environment to make sure they work as expected. Once this update goes to Production on September 28, 2026, you will need to complete your migration in Production by **March 2027**. Please contact [KIBO Support](https://help.kibocommerce.com/) if you have any questions. ## Production Tenant Features This production release is being postponed by one week, meaning that the updates listed here will be pushed to production tenants on Tuesday, Sept 22. ### **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. ### Dropship * **Vendor Portal User Management**: A new **User Management** page is available in the Vendor Portal sidebar, providing a paginated list of all vendor-scoped users with their name, email, role, and status (Active, Pending, Expired, or Declined). Vendor Admins can: * **Invite users:** Send invitations with a Vendor Admin or Vendor User role assignment. Invited users appear in the list with a Pending status. Inviting an email that already has a pending invitation resends that invitation instead of creating a duplicate. * **Resend invitations:** Re-send pending, expired, or declined invitations, extending the expiration by 5 days. * **Edit user roles:** Change a user's role between Vendor Admin and Vendor User. * **Delete users:** Permanently remove a user's vendor portal access. For users who have not yet accepted their invitation, the pending invitation is also canceled. * **Search users:** Filter the user list by name or email with case-insensitive matching. ### 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. ## Production 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 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. | ## Sandbox Bug Fixes | **Service** | **Resolution** | | :---------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Catalog | Resolved an issue where activating a search term redirect in the admin portal would produce an error, preventing the redirect from being changed from inactive to active. | | Commerce | Fixed an issue where product attribute data was missing from order routing requests made during inventory reservation when Configurable Shipment Release and Reserve Inventory at Pending Shipment were both enabled. | | Commerce | Optimized performance for B2B user management operations, significantly reducing API response times for users with many account associations. For GBA-enabled tenants, role management operations now also enforce geography-based access restrictions. | | Commerce | Fixed an issue where partial customer account updates could inadvertently clear existing contact types, causing single sign-on (SSO) login failures. | | Commerce | Fixed an issue where orders could become stuck in Validated status due to concurrent processing during shipment creation. | | Commerce | Fixed an issue where requesting shipping rates for orders with many line items or high item quantities resulted in slow response times when using EasyPost carrier integrations. | | Commerce | Fixed an issue where adding digital products to an order failed with an "Item not found" error. | | Commerce | Fixed an issue where payment reauthorization for the remaining balance was not triggered on mixed digital and physical orders when a digital shipment's capture was pending. | | Commerce | Fixed an issue where updating a cart after adding items to a specific fulfillment location could cause orders to submit successfully even when that location had no available stock. | | Commerce | Fixed an issue where a B2B account contact could incorrectly show as the primary contact after being explicitly set as non-primary. | | Commerce | Fixed an issue where Location Created, Location Updated, and Location Deleted events were missing from event subscriptions for certain applications. | | 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. | | Fulfillment | Transfer shipments created from a delivery-consolidated parent shipment were left in READY status without an active fulfillment workflow, making them invisible to pick/pack queues and permanently stuck. Transfer shipments now correctly initiate the fulfillment workflow at creation, regardless of the parent shipment's consolidation type. | | Fulfillment | Reassignment of future shipments could fail with an error and fall back to Customer Care status because the date in the order routing suggestion request was missing seconds precision. Future shipment reassignments now complete successfully and receive valid routing suggestions. | | Fulfillment | Shipment search and aggregation queries using RSQL filters with an AND condition nested inside an OR condition could silently return incorrect or zero results with no error. These queries now correctly translate and return the expected results for all filter combinations. | | Fulfillment | When substituting items on a shipment, the substitute item was always priced using the price list stored on the order, with no way to apply a location-specific or contractual price list. The purchase location is now passed through and respected during substitute item pricing, enabling location-based pricing for substituted items. |