> 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/september/akinon-release-notes-09.14.2026.md).
# Akinon Release Notes 09.14.2026
## ACC
#### **New Features**
**Build-Time Environment Variables Support**
* You can now define build-time environment variables for example, credentials for a private package repository directly within your application settings. These variables are automatically injected into each new build and made available inside build.sh. This gives merchants and administrators a secure, centralized way to manage sensitive build configuration without hardcoding values into scripts. Learn more on [How to Manage Build Variables](/tutorials/acc/how-to-manage-build-variables.md) tutorial.
***
## Omnitron
{% hint style="warning" %}
The following changes are available in **Omnitron FE versions later than** `v3.17.0` and **Omnitron BE versions later than** `v2.10.1`.
{% endhint %}
#### Resolved Issues
**Improved Performance for Collections and Catalogs Containing Grouped Products**
* Following Products and **Catalogs > Collection > Collection Detail** form for “Static” collections, queries containing grouped-type products have been optimized to prevent slow responses and timeouts.
#### New Features
**New Security Control: Account Lockout After Repeated Failed Login Attempts**
* Omnitron authentication now supports account lockout after repeated failed login attempts. Once the `ACCOUNT_LOCKOUT_MAX_FAILED_ATTEMPTS` Omnitron dynamic setting is configured with the maximum number of consecutive failed attempts, the account is automatically locked after reaching that limit, and further login attempts are rejected, even when the correct password is provided. The default limit is **5 attempts**, with a maximum configurable limit of **10 attempts**. A successful login before the limit is reached resets the failed attempt count.
* Failed attempts across these authentication methods contribute to the same lockout counter. When an account is locked, all existing sessions are terminated and the account's API token is rejected. Locked accounts can be identified under **Settings > Users**, where the **Account Locked** column displays **Yes**. Note that this is independent of the user's status: an account can remain **Active** and still be locked.
* Only a superuser can unlock an account. Opening the user record from the list navigates to the **Add/Edit Users** page, where a warning at the top of the **Edit User** form indicates that the account was locked due to repeated incorrect password entries. Clicking **Unlock Account** in this warning restores access; the account remains locked until this action is taken.
* The lockout mechanism is applied consistently across all authentication methods, including:
* Standard login
* Integration login
* Two-factor (OTP) verification
* LDAP authentication
#### Enhancements
**Apply Changes to Product Variants for AI-Generated Name and Description**
* Updated the AI-generated **Product Name & Description** save flow to allow approved changes to be applied to product variants as well. When a product has variants, users can choose whether to apply the generated **Product Name** and/or **Product Description** to the variants. Each field can be selected independently before saving. If the option is not selected, the changes are applied only to the current product.
**Sales Channels List Filters and Additional Columns**
* Added filtering capabilities to the **Settings > Sales Channels** page, allowing users to narrow down the sales channel list using key channel and date criteria. Added filters for *Channel Name, Channel ID, Channel Type, Catalog, Status, Has Orders, Creation Date,* and *Last Updated Date*. Added *Channel Type* and *Creation Date* columns to the *Sales Channels* table.
**Parent Product Image Preview Added to Offer Products**
* Updated the Offer Products to display the parent product image in applicable product list views.
**Variant Selection Algorithm**
* A Variant Selection Algorithm field has been added to the **Edit Collection Widgets** form on the **Recommendation System** page. The field is required and determines which variant of a product is displayed when the widget renders a collection item that has multiple variants.
**Multiple Category Assignment for Rule-Based Category Mapping**
* Rule based category mappings, defined on **Products and Catalogs > Catalogs > Category Mapping > Rules** tab, now assign products to all matching categories instead of only one. Previously, when a product met the conditions of multiple mapping rules within the same catalog category tree, only the most recently modified rule was applied and the other matching categories were skipped — for example, a unisex product matching both "Women" and "Men" rules was assigned to just one of them.
{% hint style="info" %}
This change applies only to a catalog's own category tree; mapping rules targeting a sales channel's category tree continue to assign a single category, since marketplace categories still allow only one category per product.
{% endhint %}
**Product Creation Now Sets Productization Date, Existing Records Backfilled**
* The *Productization Date* is now set when a product is created directly, not only when a Pending Product is converted into a *Product*. Previously, products added directly to the **Product Pool** were left with an empty *Productization Date*. Existing active products without a productization date have been backfilled using their creation date as an approximation; inactive products will receive the value automatically the next time they are updated (for example, when reactivated).
#### System Improvements
**Category Tree Rules Page Performance**
* The **Category Tree > Category Mapping > Rules** page (Auto Assign Rules) in Omnitron has been optimized for large catalogs. The page layout is now visible immediately on load, the page remains responsive while categories are matched against rules, and initial load is noticeably faster. No configuration change is required; the improvement applies automatically.
***
## Commerce
{% hint style="warning" %}
The following changes are available in **Commerce** **versions as of September 15, 2026**.
{% endhint %}
#### **Resolved Issues**
**Case-Insensitive Email Matching for Guest Order Tracking**
* Resolved an issue where guest order tracking could fail to find a valid order if the email address on the order and the email entered by the shopper differed only in letter casing. Guest order lookups now compare email addresses without regard to case. This ensures shoppers without an account can reliably track and manage their orders.
#### Enhancements
**Include All Active Campaigns in Marketing Feeds**
* Marketing data feeds previously included only the single highest-priority campaign for a product, even when multiple promotions were active. Feeds can now be configured to include all active campaigns for a product instead of just one, giving external marketing platforms a fuller picture of current promotions.
**Most-Recently-Added Item Sorting for B2B Shopping Carts**
* B2B shopping carts now sort line items so the most recently added product appears at the top of the list. Previously, cart item order was unpredictable, making it difficult for buyers working with large carts to locate items they had just added.
**Sellers Included in Search Autocomplete Results**
* Search autocomplete can now return matching sellers alongside the product and category suggestions it already provides. This helps shoppers on multi-seller marketplaces find a specific seller more quickly as they type.
**Country and Currency-Based Delivery Option Rules**
* Delivery options can now be restricted or enabled based on a shopper's country or currency, using a new rule type alongside the existing product-attribute, registered-user, and click-and-collect rules. This lets merchants operating across multiple countries manage which delivery methods are available in each market without relying on custom storefront logic.
***
## OMS
{% hint style="warning" %}
The following changes are available in **OMS versions later than** `v1.6.0`.
{% endhint %}
#### **Enhancements**
**Permission-Based Access Control Enabled for Omnitron Users**
* Direct access from Omnitron to Instore was previously limited, on a temporary basis, to superuser accounts only. Access is now determined by the user's permission definition in Omnitron. Omnitron users who aren't superusers, but do have the relevant permissions, can now perform Instore management operations within the scope of their own access. This gives administrators more precise control over who can access Instore management features.
***
## Instore
{% hint style="warning" %}
The following changes are available in **Instore FE versions later than** `v1.28.0` and **Instore BE versions later than** `v1.5.0`.
{% endhint %}
#### **New Features**
**Installment Options Modal Added to the Basket Screen**
* A new modal has been added to the Basket screen, showing installment options based on the bank cards a customer can use. Staff can now share the number of installments each bank offers, along with any applicable installment fee, directly from the basket before proceeding to payment. This allows staff to inform customers about payment options upfront, improving the overall checkout experience `v1.6.0`. See [Selling Through Instore](https://docs.akinon.com/tutorials/instore/instore-user-manual/selling-through-instore#customer-basket) tutorial for more details.
#### Enhancements
**Applicable Coupons Feature Can Now Be Enabled or Disabled Per Brand**
* The applicable coupon code modal introduced in the previous release is now controlled through a configurable setting, which is disabled by default. Brands that want to offer this functionality to customers can enable it as needed. This gives brands greater control over which features are visible to their customers.
**Search Suggestions (Autocomplete) Added to Product Search**
* The product search field in the header now displays live suggestions as staff type, and clicking a suggestion navigates directly to the relevant product page. This helps staff find products faster and reduces the time needed to complete a sale.
***
## Marketplace Dashboard
#### **New Features**
**N11 – E-Export (Micro Export) Order Support**
* Support has been added for N11's e-export (micro export) orders. These orders are now automatically recognized and processed through a dedicated flow, with buyer country information captured and export details — such as the HS code and export declaration (ETGB) number and date — stored with the order. Invoice submissions for these orders now also include the invoice date and number as N11 requires. This allows merchants to process N11 e-export orders accurately and in full compliance with N11's requirements.
#### **Enhancement**
**Single Order Retrieval While Order Flow is Off**
* You can now retrieve a single order manually using its order number or package number, even while automatic order retrieval is turned off. This lets you check or verify a specific order without enabling the full order flow. This gives merchants more flexibility to review individual orders without changing broader order settings.
**N11 – Readable Error Messages in Reports**
* N11 error reports now show the readable name of the related record such as an attribute, category, or product alongside its ID, along with guidance on how to resolve the issue. This makes it easier to understand and act on N11 error reports without needing to contact support, saving merchants time when resolving reporting issues.
#### **System Improvements**
**Trendyol – Product V2 Migration and Listing Product Matching (Deadline: September 15, 2026)**
* Trendyol product integrations now run on **Trendyol's V2** updated product service, improving how products are created, updated, and matched with your existing Trendyol listings. New products and pending updates are now submitted separately, and products still awaiting Trendyol's approval are clearly marked as "Waiting for Marketplace Approval" instead of being flagged as failed. Approved products stay automatically in sync with your catalog including descriptions, images, attributes, and delivery duration while pricing and stock updates continue to run separately as before. This results in more accurate and reliable product syncing with Trendyol.
**Trendyol – Order Services Migrated to V2 Endpoint (Deadline: October 15, 2026)**
* Trendyol V2 order-related processes including order retrieval, cancellations, and shipping have been updated to use Trendyol's newer service ahead of the retirement of the previous one on **October 15, 2026**. This ensures your Trendyol orders continue processing without interruption once Trendyol discontinues the older service.
**Trendyol – Batch Result Polling Until Item Counts Match**
* Trendyol returns bulk product results gradually rather than all at once. The batch verification step has been enhanced to wait until all expected results are received before evaluating the outcome, ensuring bulk product updates are processed accurately and reliably. This improves the consistency of your product syncing with Trendyol.
**Trendyol – Products with Empty Description Excluded from Batch**
* Previously, if a single product in a batch was missing a description, Trendyol rejected the entire batch, preventing all other products from being sent. Now, only the specific product missing a description is flagged with a clear error, while the rest of the batch is sent successfully. This prevents one incomplete product from blocking your other updates to Trendyol.
**Amazon – Refund Request for Invoiced Orders in Cancel Flow**
* In the Amazon `GetCancelOrders` flow, orders that already had an invoice could be cancelled by mistake. To bring Amazon in line with Trendyol behavior, the flow now checks whether a cancelled order has an invoice number. If there is no invoice, the order is cancelled as before. If an invoice exists, the order is not cancelled; instead an open refund request is created and an explanatory message is written to the log noting that the order was not cancelled but a refund request was opened. This prevents invoiced orders from being cancelled incorrectly.
***
## Seller Center
{% hint style="warning" %}
The following changes are available in **Seller Center FE versions later than** `v1.3.1` and **Seller Center BE versions later than** `v1.7.0`.
{% endhint %}
#### Resolved Issues
**Bulk Search and Bulk Actions by File Now Work Reliably**
* Bulk search and bulk actions by file on **Products > Product Pool** now work reliably. Previously, uploading a file of SKUs or base codes for bulk search appeared to succeed but the search itself always failed, the uploaded file's name sometimes displayed incorrectly next to the applied filter including on **Offer Actions**, and the **Download Template** button provided the wrong file. All three issues are now resolved: bulk search and bulk approve/reject by file complete successfully, file names display correctly everywhere they appear, and the **Download Template** button provides the correct template.
**Sales Reports No Longer Fail on High-Volume Sellers**
* Category-based sales reports no longer fail to generate for sellers with very high total sales or commission amounts. This ensures high-volume sellers can reliably generate their sales reports whenever they need them.
#### Enhancements
**Login Now Always Opens the Dashboard**
* Logging into Seller Center now always opens the Dashboard, regardless of which page the previous session had last been on. Previously, logging out and logging back in as a different user could reopen the prior session's last page instead of a neutral starting point. This prevents a new user on a shared device from momentarily seeing or interacting with a page left open by someone else, improving security and consistency across sessions.
***
## Project Zero
{% hint style="warning" %}
The following changes are available in **@akinon/next (Project Zero) version** `2.0.103` **and later**. **Theme Editor** updates are live on the current Akinon platform.
{% endhint %}
#### Resolved Issues
**Theme Editor – Empty Group Blocks No Longer Show Placeholder Text**
* Empty Group blocks no longer display the "Empty group block" placeholder text on the live storefront this text now appears only within the editor. This ensures shoppers always see a clean, polished storefront free of internal editor labels.
**Theme Editor – Theme Application Updated for Working Copies**
* Theme application now respects the active working copy. Applied themes remain in the current draft or preview until the user explicitly publishes the changes to the live site. Action needed: apply the theme, then publish explicitly.
**Theme Editor – Header States Apply Consistently When Overlays Are Open**
* Fixed an issue where header styles could apply inconsistently when multiple states such as docked and overlay-open were active at the same time. Header state precedence is now handled consistently, so the intended header appearance is always preserved, giving shoppers a reliably consistent header experience across the storefront.
**Theme Editor – All Available Blocks Now Render on the Storefront**
* Fixed an issue where certain blocks available in the Add Block picker did not display on the live storefront after being added. All available blocks now render correctly once published, so users can rely on every block in the picker working as expected on the live site.
#### New Features
**Theme Editor – Collapsible Content Block**
* A new collapsible content block has been added to Theme Editor, allowing long content to be shortened with a customizable “Read More / Read Less” interaction while keeping the full content available on the page for SEO.
**B2B – Basket Breakdown and Filtering**
* The basket screen now supports product attribute-based grouping and filtering, allowing users to review order quantities by categories such as season, collection, color, and hierarchy. When submitting a filtered basket, users are warned and can either proceed or clear the active filters.
#### Enhancements
**Theme Editor – Device-Specific Images**
* The Image Block now supports separate images for desktop, tablet, and mobile devices, so users can display the most suitable visual for each device from the moment the page loads. Existing single-image blocks continue to work without any changes. This lets users deliver a more tailored visual experience to shoppers on every device.
**Theme Editor – Improved Settings Search**
* Settings search now takes users directly to the matching control and shows only relevant results, making it faster and easier to find specific design settings across the editor.
**Theme Editor – Advanced Modal Styling**
* Modal surfaces can now be fully styled directly in Theme Editor, including backgrounds, borders, spacing, typography, shadows, close button states, and device-specific settings. Existing modals remain unchanged unless new styling options are applied.
#### System Improvements
**Theme Editor — Stable Slider Rendering**
* Sliders now arrive fully rendered with their slides in place instead of appearing as an empty strip, removing the layout jump shoppers previously saw when a page first loaded (on one home page, the layout shift score improved from 0.70 to 0.08). Behavior change: the Slider block now switches to its mobile item count at 1024 pixels instead of 768, so most tablets will show the mobile item count. Action needed: Users should check Slider blocks at tablet width after upgrading. This delivers a smoother, more stable browsing experience for shoppers from the very first page load.
**Build — Skip theme package** `2.0.101`
* `@akinon/pz-theme` version `2.0.101` fails type checking in some brand applications; this is resolved in version `2.0.102`. When upgrading, move `@akinon/next` and `@akinon/pz-`theme to the same version together, and skip `2.0.101`. This prevents build failures and keeps brand applications on a stable, verified package combination.
***
## App Maker
### Platform
#### Resolved Issues
**Corrected User Access Token Validation**
* User access tokens are no longer rejected because of the characters they contain. A token that included a hyphen or an underscore was previously turned away as malformed, even though the platform itself had issued it. Every token the platform generates is now accepted. This removes unnecessary authentication failures so you can rely on your access tokens working consistently. See the [User Access Tokens](https://docs.akinon.com/tutorials/app-maker/developer-tools-and-cli/user-access-tokens) tutorial for details.
**Resolved Organization Access Check for Plugins and Dependencies**
* Plugin and dependency endpoints that belong to an organization now consistently check that you have access to that organization before creating a dependency or a dependency package. This strengthens access control and helps keep your organization's plugins and dependencies secure. See the [Dependency Management ](/tutorials/app-maker/developer-tools-and-cli/dependency-management.md)tutorial for a full walkthrough.
#### New Features
* **Command Palette**\
Open a command palette from anywhere in App Maker with **Cmd+K** (Ctrl+K on Windows and Linux) and jump straight to where you're going, instead of clicking down through organization, project, and build.
* **Recents** — Open the palette without typing anything, and the three builds or code-pushes you started most recently are already there, across all your projects.
* **Projects** — Find a project by name, then go straight to its dashboard, settings, or deployments from the same row.
* **Navigation** — Every page you have access to, filtered to your own permissions.
* **Account** — Your own pages: profile, language, notifications, access tokens, and public keys.
* The palette is fully keyboard-driven: arrow keys move through results across all four sections, Enter opens the highlighted item, and Esc closes the palette. The footer always shows the correct shortcut for your keyboard. This lets you get to any build, project, or setting in seconds saving time on every task you do in App Maker. See the [Command Palette](/tutorials/app-maker/getting-started/command-palette.md) tutorial for a full walkthrough.
#### Enhancements
**Build Detail — Per-Artifact Size**
* Build Detail now shows each artifact's size on its own download button — AAB, APK, or IPA, whichever the build produced instead of a single generic "Artifact Size" field. An expanded **CodePush** release row now also shows its **Bundle Size**. Builds made before this change continue to show their previously recorded size. This gives you a clearer, more accurate picture of what you're downloading before you click. See the [Build Detail](/tutorials/app-maker/build-and-distribute/build-detail.md) tutorial for details.
### Mobile
{% hint style="warning" %}
The following changes are available in **App Maker Environment version** `env6.1.0`.
{% endhint %}
#### **Enhancements**
**Virtual Try-On (VTO) Text Rendering Improvements**
* The text handling behind the Virtual Try-On (VTO) feature has been refactored to use dedicated VTO text resources. This improves the accuracy and stability of text rendering within the virtual try-on flow.
**Action Required:** No action is needed for brands that do not use Virtual Try-On. Brands using VTO should confirm their text mapping configuration after upgrading to `env6.1.0` or above.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.akinon.com/release-notes/2026/september/akinon-release-notes-09.14.2026.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.