> ## 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.

# October 27, 2026 - 1.2642 Service Update

## **Announcements**

### Code Freeze

Kibo is entering its “code freeze” for the peak holiday season. This production release of Version 1.2640 is the final major update being pushed to production tenants until January. Changes will continue to be added to sandbox environments per the below schedule and will be released to production on January 19, 2027:

* Version 1.2642: October 27
* Version 1.2644: November 10
* Version 1.2646: November 24
* Version 1.2648: December 8
* Version 1.2650: January 5
* Version 1.2652: January 5

### **Order Routing — "Group Rank and Quantity" Sort Now Honors Location Rankings**

Kibo has corrected behavior in [Order Routing](https://docs.kibocommerce.com/concept-guides/order-routing.md "https://docs.kibocommerce.com/concept-guides/order-routing"): when a strategy's [Candidate Sort Strategy](https://docs.kibocommerce.com/pages/routing-strategies.md "https://docs.kibocommerce.com/pages/routing-strategies") is set to **"Group Rank and Quantity"**, location rankings assigned within a scenario are now respected. Locations are prioritized by **scenario rank → location rank → available quantity**, with quantity used only as a tiebreaker between equally ranked locations. Previously, location rankings were ignored and orders were assigned to whichever eligible location held the most inventory. The Routing Debugger already reflected the correct behavior; live assignment now matches it. No API, integration, or data changes are required.

**Who is affected:** Clients whose routing strategies use the "Group Rank and Quantity" candidate sort in scenarios with more than one location. Note that every scenario built in the Order Routing UI carries rankings; the list order of locations is the ranking, even if you never set them explicitly. Strategies using Minimize Shipments, Quantity, or Distance are not affected, as are single-location scenarios and scenarios where all locations share the same rank. Review your location rankings and validate affected strategies in Sandbox before the Production release.

Available for validation in Sandbox from **October 27, 2026** (v1.2642), and takes effect in Production on **January 19, 2027** — the first Production release after Kibo's peak-season code freeze, giving approximately 12 weeks to test. To identify affected strategies, check the **Candidate Sort Strategy** field on the **List Strategies** page in the Order Routing UI. For a detailed before-and-after example, step-by-step testing instructions, and expected outcomes, see the Support Portal article [Action Required: Order Routing — "Group Rank and Quantity" Sort Now Honors Location Rankings](https://help.kibocommerce.com/s/article/Order-Routing--Group-Rank-and-Quantity-Sort-Now-Honors-Location-Rankings-Jan-2027 "https://help.kibocommerce.com/s/article/Order-Routing--Group-Rank-and-Quantity-Sort-Now-Honors-Location-Rankings-Jan-2027").

Please contact [Kibo Support](https://help.kibocommerce.com/ "https://help.kibocommerce.com/") if you have any questions.

## **Production Sandbox Features**

No new Production Sandbox features in this release.

## **Sandbox Bug Fixes**

<table>
  <colgroup>
    <col width="150" />

    <col width="679" />
  </colgroup>

  <thead>
    <tr>
      <th>**Service**</th>
      <th>**Resolution**</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Commerce</td>
      <td>Creating an End of Day manifest for Canada Post failed intermittently with a generic "ReverseProxy Unexpected Error" message, most commonly for batches of 15 or more shipments and required repeated retries before a manifest could be created. Manifests are now created successfully on the first attempt regardless of the number of shipments in the batch.</td>
    </tr>

    <tr>
      <td />

      <td />
    </tr>

    <tr>
      <td>Fulfillment</td>
      <td>Fixed an issue where a shipment search using a term that begins with a hyphen or minus sign (for example, -11605180) returned no results even when matching shipments existed, and caused those searches to respond slowly. These searches now return the correct results.</td>
    </tr>

    <tr>
      <td>Inventory</td>
      <td>Fixed an issue where a valid inventory import file submitted via automated fetch (SFTP or S3/GCS) was occasionally marked invalid and skipped when processed alongside another concurrent import. Imports now process reliably.</td>
    </tr>

    <tr>
      <td>Inventory</td>
      <td>Fixed an issue in Order Routing where the "Group Rank and Quantity" sort strategy ignored a location's configured rank, routing orders to the location with the most inventory instead of the preferred location. Orders now follow the configured rank order.</td>
    </tr>

    <tr>
      <td>Inventory</td>
      <td>Fixed an issue where updates to job, fulfillment, or inventory site settings could silently fail to take effect — typically when made shortly after a platform update — until another settings change was made. Settings updates now apply reliably.</td>
    </tr>

    <tr>
      <td>Catalog</td>
      <td>Fixed an issue where Search Terms uploaded in the Admin reported a successful update but the new terms never appeared in storefront search suggestions, leaving shoppers without the expected autocomplete results. Uploaded search terms now appear in storefront search suggestions as expected.</td>
    </tr>
  </tbody>
</table>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.