> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/release-notes/2026/june/akinon-release-notes-06.08.2026.md).

# Akinon Release Notes 06.08.2026

## <mark style="color:$primary;">Commerce Cloud</mark>

#### <mark style="color:red;">New Features</mark>&#x20;

**Multi-Account Access Without Plus-Addressing**

Previously, accessing multiple accounts on ACC required creating separate users with “+” addressed emails (e.g. <yourname+accountname@domain.com>). You can now be added to any account using your existing email address (e.g. <yourname@domain.com>).

If no user exists with that email, one is created automatically. If a user already exists, you are added directly to the account and notified by email. The existing user creation flow remains unchanged. Once added to multiple accounts, you can switch between them from the top-right corner after logging in.

**Merging Existing Plus-Addressed Accounts**

Migration of existing plus-addressed accounts is in progress. Affected users will be notified individually as their accounts are merged.

**CLI Support**

Upgrade to **akinoncli** `v1.0.25` or later to access multi-account features, including account switching, account listing, and the ability to initiate a login session for a specific account directly.

<img src="/files/VtRLiy1H6RkH3bCn3jzn" alt="" height="337" width="624">

{% hint style="info" %}
For CLI details:[ https://pypi.org/project/akinoncli/](https://pypi.org/project/akinoncli/) For detailed CLI installation and usage instructions, refer to the[ How to Manage Users and Roles in ACC? ](/tutorials/acc/how-to-manage-users-and-roles-in-acc.md)tutorial.
{% endhint %}

## <mark style="color:$primary;">Omnitron</mark>

{% hint style="warning" %}
The following changes are available in **Omnitron FE** versions later than `v3.10.0` and **Omnitron BE** versions later than `v1.5.0`.
{% endhint %}

#### <mark style="color:red;">Resolved Issues</mark>

**Double Loyalty Credit on Refund After Partial Cancellation**

* When an order paid with loyalty money underwent a capture\_refund (partial cancellation) followed by a refund, the loyalty amount returned on the second operation was incorrectly calculated it included the amount already refunded by the prior capture\_refund, resulting in duplicate loyalty credits being issued to the customer. This has been resolved; each operation now refunds only its own corresponding loyalty amount.

**Stock Reset to Zero When Adding Simple Products to a Catalog**

* When a simple product with no offer children was added to a catalog, its existing ProductStock rows covering both the main stock list and all extra stock lists were being overwritten with `stock=0` and `sold_quantity_unreported=0`. The stock would remain at zero until a full ERP feed was triggered manually, since the ERP delta service detected no change on its end and would not re-push the data automatically. This issue has been resolved, so simple products added to a catalog no longer have their existing stock values overwritten.

#### <mark style="color:red;">Enhancements</mark>

**Transaction List XLS Export**

* An XLS export functionality has been added to the **Orders > Transactions** page. Users can now export transaction records in XLS format for easier reporting, analysis, and offline processing.

  <img src="/files/oKl4Tv4xDjNrXQndY3pf" alt="" height="293" width="618">

**Language Filter for Search Results**

* A new Language filter has been added to the AI Powered **Search > Search Results** page. Users can now filter search result keywords based on the language of the storefront where the search was performed, enabling more accurate analysis and management of multilingual search data.

  <img src="/files/crdUrUByEGtUprKyvMK9" alt="" height="288" width="605">

**New Store Pickup Email Templates**

* Two new email templates have been added to **Sales Channel > Content Management > Mailing Templates**:
  * Order Is Ready For Store Pickup
  * Order Is Ready For Store Pickup Subject Title
* These templates enable merchants to customize both the email content and subject line used to notify customers when their orders are ready for collection from the selected store, helping provide a more consistent and branded pickup experience.

  <img src="/files/a8DYAbjdDVuy9ci4G260" alt="" height="296" width="624">

**B2B Quotation Export Enhancements with Order and Metadata Details**

* CSV and XLS export functionalities have been added to the **B2B > Quotations** page. Users can now export quotations along with their associated orders, order statuses, and metadata fields, making it easier to perform detailed analysis, reporting, and offline processing of quotation data.

  <img src="/files/dMDqqehVZS5Zz9TLzP8V" alt="" height="297" width="624">

<img src="/files/EvEYB3LDQPw4uByLioIQ" alt="" height="200" width="624">

**Configurable Column Names for External Sorting File Uploads**

* Previously, CSV and Excel files uploaded for external (Stream-type) sorting were required to have columns named exactly sku and number. Any deviation from these fixed names would cause the file to be rejected with a validation error, forcing users to manually rename their columns before every upload.
* Column name mapping for external sorting file uploads is now configurable. Users can define which columns in their file correspond to the product code and sort order fields, allowing them to upload files in their existing format without modification.

***

## <mark style="color:$primary;">Commerce</mark>

{% hint style="warning" %}
The following changes are available in **Commerce** versions as of **June 08, 2026**.
{% endhint %}

#### <mark style="color:red;">**Resolved Issues**</mark>

**Database Migration for URL Redirections**&#x20;

* Resolved an issue where database records for URL redirections failed when product URLs exceeded 200 characters. A custom database migration was developed to widen the old and new path columns to 512 characters, ensuring long URLs are redirected smoothly without causing system errors.

**Facet Sorting Type Error Fix**

* Fixed a type error that caused product category pages to crash when certain filter options lacked a sorting order. The sorting logic was updated to safely handle missing values by placing them at the end of the list, ensuring product filters load reliably.

**Webhook Duplication Control**&#x20;

* Resolved a problem where external webhooks (such as user registration notifications) were firing multiple times for a single event, causing duplicate records in external systems like ERPs. A caching mechanism was added to lock the webhook trigger for 5 seconds after the first event, preventing repetitive calls.

**Graceful Shutdown Serialization Fix**&#x20;

* Fixed an issue where background workers would crash during graceful shutdown due to uncopyable object types in the task cache. The system code was updated to use standard and safe input/output protocols, ensuring background operations can shut down cleanly without errors.

**reCAPTCHA Replay Attack Prevention**&#x20;

* Strengthened security on user registration endpoints to prevent SMS spam and replay attacks. reCAPTCHA tokens are now strictly validated as single-use and assigned a time-to-live (TTL) limit. If a token is reused or expired, the backend explicitly rejects the request and prompts the frontend to generate a fresh verification code.

***

## <mark style="color:$primary;">OMS</mark>

{% hint style="warning" %}
The following changes are available in **OMS versions later than** **`oms726`**.
{% endhint %}

#### <mark style="color:red;">**Enhancements**</mark>

**Performance Improvement in Package Processing**

* OMS Celery workers have been separated into two dedicated pools: one for critical fulfillment and high-priority webhook tasks, and another for background processes such as tracking and informational events. Previously, all task types shared a single worker pool, causing high webhook traffic during peak hours to block fulfillment processing and significantly delay package creation. With this architectural change, fulfillment tasks are now isolated from background load, ensuring consistent package processing times regardless of webhook volume.

**Stock Location Quota Management — New Model & Race-Safe Increment**

* The stock location quota management system has been rebuilt with a dedicated model and an atomic, race-safe increment mechanism. Previously, concurrent order processing could cause quota limits to be exceeded due to simultaneous in-memory checks without database-level locking. Quota increments are now applied via a conditional database update, making it impossible to exceed the defined maximum under concurrent load. Predefined and manual assignment methods are excluded from quota enforcement, ensuring that manually assigned orders are never blocked by quota limits.

**Blacklist Product — Soft Delete**

* Removing a product from the blacklist no longer permanently deletes the record from the database. The entry is now marked as inactive (is\_active=false) instead, preserving the full history of blacklisted products. If the same product is blacklisted again in the future, the existing record is reactivated rather than creating a duplicate. This change ensures auditability and makes it possible to track whether a product has been previously blacklisted.

**Inventory Discrepancy Filtering**

* The inventory discrepancy list now supports filtering by stock location, status, reason, product, and date range. Previously, no filter options were available on this endpoint, making it difficult to narrow down discrepancy records during investigations. Operations teams can now quickly isolate relevant records without having to scroll through unfiltered results.

***

## <mark style="color:$primary;">Instore</mark>

{% hint style="warning" %}
The following changes are available in Instore FE  versions later than `acc-842` and Instore BE versions later than `s157`.
{% endhint %}

#### <mark style="color:red;">New Features</mark>

**Cargo Delivery / Reconciliation Form**

* A new form page, accessible from the packaging orders list, has been added to document the cargo handover process. Filterable by date-time range, the form includes sequence number, sender/recipient store information, package code, and cargo tracking number. The form is available in a printable/downloadable format.

  <img src="/files/88h3NQum9OOpfMj4B0G4" alt="" height="312" width="624">

<img src="/files/viLASmZzf10tSoAU4qXb" alt="" height="324.6163000981909" width="624">

**Store Filtering by Product Attribute in Instore Checkout C\&C**

* In some retail operations, not every store is equipped to fulfill every type of product. For example, a store that does not carry a specific product line should not appear as a Click & Collect option when that product is in the basket. With this update, stores are automatically filtered at checkout based on the attributes of the products in the basket only the stores that are eligible to fulfill those specific products are shown, reducing the risk of incorrect store selection. To enable this feature, navigate to **Sales Channels > Content Management > Widget Management** in Omnitron, add or edit the instore-cc-control widget, and define filtering rules using the `attribute_key`, `attribute_value`, and `store_name` fields. In Instore, go to **Settings > Configuration** and enable the "**Filter CC stores in checkout screen according to widget (instore-cc-control)**" setting.

{% hint style="info" %}
Store filtering by product attribute during C\&C checkout is a separate behavior controlled by the "Controls the CC attribute behavior during checkout" setting, also available under Instore Configuration. For detailed C\&C usage instructions, refer to the [C\&C Widget Configuration Guide](/technical-guides/instore/c-and-c-widget-configuration.md).
{% endhint %}

<figure><img src="/files/DzdgtiYBrYvASvINtif1" alt=""><figcaption></figcaption></figure>

<img src="/files/NumHElSgOUyS1rGxWS8t" alt="" height="385" width="624">

#### <mark style="color:red;">Enhancements</mark>

* **Customer Registration — SMS Verification & Password Security**

  When an incorrect code is entered during the SMS verification step, a descriptive error message is now displayed directly on the verification modal, making it clearer for staff to guide customers through the process. Additionally, passwords automatically generated by the system during customer registration now meet stronger security requirements, including uppercase and lowercase letters, numbers, and special characters.&#x20;

***

## <mark style="color:$primary;">Marketplace Dashboard</mark>

#### <mark style="color:red;">Enhancement</mark>&#x20;

* **Amazon – Address Resolution via Postal Code in GetOrders Flow**

  An improvement has been made to the Amazon GetOrders flow to handle cases where address data is missing or invalid. When an address error is encountered during order retrieval, the system now attempts to populate address fields such as city and country using the postal code associated with the order. The order is then created using these derived address values, ensuring the flow continues without interruption even when address information is incomplete.<br>

***

## <mark style="color:$primary;">Seller Center</mark>

{% hint style="warning" %}
The following changes are available in **Seller Center FE versions later than `v.08.135`** and **Seller Center BE versions later than** **`v1.1.180`**.
{% endhint %}

#### <mark style="color:red;">Resolved Issues</mark>

**Bulk Price Update Template — Missing currency\_type Field**

* Fixed an issue in the Bulk Price Information Update flow via **Products > Inventory Management > Price List > Price Detail** where the downloaded template did not include the `currency_type` field. When sellers uploaded the template back, the system returned an error because it expected this field. The `currency_type` field has now been added to the export fields parameter, and the template downloads correctly. Sellers can now successfully perform bulk price updates without manual template modifications or upload failures.

  <img src="/files/YM0glWitdBLSsPMWiisI" alt="" height="263" width="624">

<img src="/files/uBx1fkAg67xws4cTbaJZ" alt="" height="111" width="559">

**Revision Requests — Sorting Not Functioning**

* Resolved an issue where column sorting on the Revision Requests via **Products > Revision Requests** was not operational. Clicking on any column header had no effect on the list order. Sorting is now fully functional for all fields on the Revision Requests table across all environments. Improves usability and efficiency when reviewing and managing large numbers of revision requests.

#### <mark style="color:red;">New Features</mark>

**Refund Button for Delivery Failed Packages**&#x20;

* A new "Refund" action button has been added to the Package Detail via **Orders > Packages > Package List > Package Detail** for packages in "Delivery Failed" status. This leverages the new delivery-failed-return endpoint on the backend, allowing sellers to trigger the return process directly from the package detail screen without manual intervention. Reduces operational workload, speeds up refund processing, and improves the seller experience when handling failed deliveries.

  <img src="/files/XZqsRmHQKzJr6w37Msbq" alt="" height="317" width="624">

<img src="/files/4lBNo3Fe5LH95wxRJEWp" alt="" height="229" width="624">

**New Locked Fields Page**&#x20;

**For Marketplace Owners:**

A new Locked Fields management page has been added under **Settings > Locked Fields**, allowing Marketplace Owners to control which product fields and seller attributes are prevented from modifying through revisions.

<img src="/files/c3veffqyxX1cazfTE6V0" alt="" height="315" width="624">

* Two types of locks are supported: Product Field Lock, which globally locks product-level fields such as name and image via **Settings > Dynamic Settings > LOCKED\_PRODUCT\_FIELDS**, and Attribute Lock, which locks specific attributes within an attribute set (e.g., locking "color" under the "Shoe Attributes" set).

  <img src="/files/b7mfWmNHAfOVDHIFOHiK" alt="" height="307" width="624">
* Lock behavior is controlled via **Settings > Dynamic Settings > LOCK\_FAIL\_SILENTLY**. In **Silent Mode** (default), locked fields are quietly stripped from the revision and the operation continues; sellers receive no error, but locked fields are not updated. In Strict Mode, the entire revision is blocked and the seller receives an error.

  <img src="/files/3PVfIRTYB0i8eUKszHCb" alt="" height="295" width="624">

{% hint style="info" %}
In Silent Mode, sellers are not notified that their changes were partially ignored. Consider communicating active locks to avoid confusion.
{% endhint %}

* All lock drop actions are recorded in the audit log. Marketplace Owners bypass all lock restrictions.

**For Sellers:**

* Some product fields and attributes may be restricted by the Marketplace Owner. If a restricted field is included in your revision, one of two things may happen: your revision is processed but the locked fields are silently ignored, or your revision is blocked entirely with an error message. If your changes are not reflected after a successful revision, the affected fields may be locked, contact your marketplace administrator for details.
* If your revision contains variant attribute values that differ from the existing product, it will be automatically rejected with an explanation on the revision screen.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akinon.com/release-notes/2026/june/akinon-release-notes-06.08.2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.