> 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/october/akinon-release-notes-10.26.2026.md).

# Akinon Release Notes 10.26.2026

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

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

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

**Remaining Amount Message for Vouchers Below the Threshold**

* When a shopper applies a voucher whose campaign threshold has not yet been met, the error message now shows the campaign’s remaining amount instead of a generic “invalid voucher” message. This helps shoppers understand how much more they need to add to their basket to use the voucher.

**Separate Display of Voucher and External Campaign Discounts**

* Discounts from external campaign services are no longer shown on the storefront as if they were applied by the voucher code in the basket. Commerce voucher discounts and external campaign discounts are now displayed separately. This ensures that shoppers see accurately which discount comes from which source.

**Product Attributes for All Items in B2B Baskets**

* B2B baskets now include product attributes for all items, including items that went out of stock or were unlisted after being added to the basket. This allows storefronts to group and filter basket items consistently.

***

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

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

**Accurate Stock Reservations When Orders Are Planned Together**

* When several orders are planned at the same time, such as the orders created when an order is split, they can no longer reserve the same last unit at a stock location. OMS now takes existing reservations into account before reserving stock and correctly deducts reserved quantities from the location’s available stock. Previously, a location with a single unit in stock could be assigned more than one package for that unit, and the extra packages then had to be re-planned as out of stock. This prevents packages from being assigned to stores that cannot fulfill them.

***

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

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

**Invoices from the Package Orders List**

* Staff can now open and print a package’s invoice directly from the Package Orders list, without opening Package Details. A “Show Invoice Document” icon appears in the “Actions” column for packages in the “Packed All Items”, “Ready for Customer Pickup”, “Shipped”, and “Delivered” statuses. The invoice opens in a window where it can be printed with “Print”. If the package has an e-archive invoice link, the invoice opens in a new tab instead. Printed rows are marked blue for invoices and green for shipping labels, so staff can print both from the same list and see at a glance what has already been printed. Multi-page invoices print page by page on desktop and tablet. This reduces the steps needed to print invoices and helps staff keep track of printed documents.

  <img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FA1U7gJjatWJG5FIWRXZM%2Funknown.png?alt=media&amp;token=98aa2857-20d4-4408-8d26-34a5f45d6383" alt="" height="520" width="624">

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FNYezDFZcCEE1OiPA3JDa%2Funknown.png?alt=media&amp;token=0061b388-32e5-4369-a3fe-9b02325b067f" alt="" height="520" width="624">

**Store Pickup Limited to Stores with Basket Stock**

* When "Get delivery from store" is selected during checkout, the city and store lists now include only stores that have stock for every item in the basket. This keeps orders from going to a store that can't fulfill them and prevents the customer from waiting while the order is re-planned. If the previously selected store has run out of stock, a warning asks staff to choose another store, and "Save and Continue" stays disabled until they do. If no store has stock, the screen says so and delivery to an address can be chosen instead. This feature is disabled by default; brands that want to use it can enable it.

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2Fb59GLDQP8UwCmETIwP0V%2Funknown.png?alt=media&amp;token=c4f7263d-8ffe-4e50-8d2e-71d314b59b4d" alt="" height="351" width="624">

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FZtGskaBhC1y8Wb3xHWMt%2Funknown.png?alt=media&amp;token=439cbf31-b217-40d0-bdc2-405e5bde90be" alt="" height="351" width="624">

**Option Sorting in Product List Filters**

* Options inside product list filters, opened with “Show Filters”, can now be sorted separately for each filter. Options can be sorted by product count with the largest first, or in a custom order the brand sets in content management, with options the brand chooses pinned to a fixed position. Selection and filtering work as before, and the sort order is kept after a filter is applied. This feature is disabled by default and can be enabled by brands that want to use it. This helps staff find the most common colors or brands faster and lets brands show filter options in the same order as on their website.

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FAEte9bvJWDVEX3GLYMtx%2Funknown.png?alt=media&amp;token=c09907f3-e1b3-46ef-9ddd-f01bd2790f81" alt="" height="816" width="580">

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2Fo4kWzNVn6GWrIMBurLkx%2Funknown.png?alt=media&amp;token=2700930b-58fe-4554-9511-f6505a6f2524" alt="" height="816" width="580">

***

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

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

**Trendyol – Cargo Provider Update and Selective Alternative Delivery**

* Cargo provider changes on Trendyol orders can now be sent to Trendyol. When the “Update Cargo Provider” setting is enabled, changing an order’s shipping company in Omnitron also updates it on Trendyol. This applies only to cargo companies that have an agreement with Trendyol. The new “Exclude Alternative Delivery” setting excludes selected cargo companies from alternative delivery, so a channel can use both delivery types at once. For example, Sürat Kargo orders can use standard shipping while CargoX orders use alternative delivery. Errors during cargo provider changes can be tracked in the Marketplace Dashboard. Both settings are disabled by default and don’t affect channels that don’t use them. This gives merchants more flexibility in managing Trendyol shipping and keeps order information consistent across both platforms.

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

**Trendyol – Improved Order Cancellation Sync Performance**

* Order cancellations are now sent to Trendyol more reliably, even at high volumes. Brands with a large number of cancellations no longer experience timeouts, and each cancellation is sent to Trendyol only once. This ensures that cancellations reach Trendyol accurately and on time during busy periods.

**MPD – Automatic Token Refresh for Missing Order Retrieval**

* The daily task that retrieves missed orders now renews expired sessions automatically and continues without interruption. This ensures that missed orders are retrieved for every brand without manual intervention.

**Trendyol – Updated Return Rejection Reasons**

* Return rejection reasons for Trendyol now match Trendyol’s latest list. Three new reasons are available, retired reasons have been removed, and existing reason descriptions reflect Trendyol’s current wording. This ensures that every return rejection sent to Trendyol uses a valid, up-to-date reason.

**N11 – Faster Category and Attribute Transfer**

* Transferring N11 categories and attributes to Omnitron is now significantly faster, reducing the transfer time from about 7–8 days to a single day. Duplicate attribute values are also prevented during the transfer. This allows merchants to start working with up-to-date N11 category data much sooner.

***

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

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

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

**Marketplace-Defined Seller Document Fields**&#x20;

* Marketplace owners can now define the document fields that sellers see by using the `DATASOURCE_FILE_FIELDS` setting under **Settings > Dynamic Settings**. Previously, the seller document upload screen had five fixed fields, and adding a new document type required a code change.
  * For each field, operators can set a unique key, a label for each language, whether the field is required, and whether multiple files can be uploaded.
  * Fields added to the setting appear on the screen immediately. Removed fields are no longer displayed, but files already uploaded to them are kept.
  * **Finance > Seller Management > Seller Detail > Documents (and Finance > Account Management > Documents and Agreements for sellers)** now displays upload fields based on this setting, including multi-file fields. Previously uploaded files are kept and remain visible.
  * Each file can be up to 25 MB, and up to 15 files can be uploaded to a field at once.

Marketplace owners can now request new seller documents without waiting for development work. See [Account Management](https://docs.akinon.com/tutorials/seller-center/seller/finance/account-management.md) and [Seller Management](https://docs.akinon.com/tutorials/seller-center/marketplace-owner/finance/seller-management.md) tutorials for details.

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FdWJj0lyLuhw3LErZuhqs%2Funknown.png?alt=media&amp;token=fb5b6e0e-87b7-4684-a6a5-b48b49873c85" alt="" height="403" width="624">

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FVVMhxGEtFcn4o6JvgAIh%2Funknown.png?alt=media&amp;token=adbd4a46-3a76-463b-a537-669ab8f39a0a" alt="" height="404" width="624">

**Sellers Can Edit Their Own Campaigns**

* Sellers can now edit their own campaigns using the new **Edit Campaign** button under **Marketing > Campaigns > Campaign Detail**. The campaign form opens with the current values already filled in.
  * The following fields can be updated: name, collections, condition type, minimum amount/quantity, discount amount/percentage, Max. Basket Retry Count, Stock Limit, Campaign Working Limit, start/end dates, and active/passive status.
  * The campaign type cannot be changed. Creating a different type requires a new campaign.
  * Show on Product List and Seller Campaign Share (%) can be edited only if the marketplace operator marks them as updatable in the `DATASOURCE_BASKET_OFFER_FIELDS` setting. Otherwise, these fields are displayed but cannot be changed.
  * Campaigns that have already been used cannot be edited. In this case, the **Edit Campaign** button is disabled and shows “Used campaigns cannot be updated.” on hover.
  * A passive campaign can be activated only if its end date is in the future. Passive campaigns can still be saved with a past end date.
  * Marketplace campaigns cannot be edited. The existing Join/Leave flow remains unchanged.

Sellers can now adjust their campaigns without recreating them, which saves time and reduces manual work. See the [Seller Generated Campaigns](https://docs.akinon.com/tutorials/seller-center/seller-generated-campaigns.md) tutorial for details.

{% hint style="info" %}
Changes made by the MPO to a seller-created campaign in **Omnitron > Sales Channels > Marketing > Campaigns** are not reflected in Seller Center.
{% endhint %}

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FSME6q8cBfDPzMJ7nTEUf%2Funknown.png?alt=media&amp;token=da024b57-14c7-46fe-b952-93a1580c7dc5" alt="" height="296" width="624">

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FKTop0bcEd3B6j2mEqLBk%2Funknown.png?alt=media&amp;token=e4be49b4-8038-4f83-8498-6165dd99a755" alt="" height="320" width="624">

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

**Error Files Can Be Downloaded for Imports**

* Under **File Management > Imports**, a download button is now shown whenever an import has an error file, regardless of its status. If an import has both an error file and an error message, only the download button is shown. Failed imports without an error file continue to show their error message as before. Sellers can now see which rows failed and why without opening a support request. See [How to Use Bulk Actions in Seller Center](https://docs.akinon.com/tutorials/seller-center/seller/products/how-to-use-bulk-actions-in-seller-center.md) tutorial for details.&#x20;

  <img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FtMmCXO4iscfSKpNgw5CH%2Funknown.png?alt=media&amp;token=d15b5dbf-6943-46c3-b133-76f30d9c0b62" alt="" height="240" width="624">

**Revision Requests Flag Attribute Keys Outside the Attribute Set**&#x20;

* Revision requests could contain attribute keys that are not part of the product's attribute set, and nothing on the screen indicated this. The revision request detail under **Products > Revision Requests** now shows an information box listing the attribute keys that do not match the product's attribute set. The warning is informational only: the revision request is not blocked and is processed as before. Sellers and operators can spot incorrect attribute keys and correct them. See [How to Create Revision Requests](https://docs.akinon.com/tutorials/seller-center/seller/products/how-to-create-revison-requests.md) tutorial for detail. &#x20;

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FydkPA5crm4pXDdaFW1Eh%2Funknown.png?alt=media&amp;token=8213b84d-b61a-4682-be2b-9c44e15283ac" alt="" height="337" width="624">

**Revision Requests List Can Be Exported**

* The Revision Requests list could not be downloaded, so checking in bulk which products had revision requests meant going through the records one by one. An "Export Revision List" option has been added to **Products > Revision Requests**. The export follows the active filters (including a bulk search file), lets users choose the fields to include (Product Name, SKU, Seller, Status, Creation Date and, for marketplace operators, Rejection Reason) and produces an XLSX file. Exports are generated in the background and tracked like other exports, so large lists can be exported without timing out.

  <img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FGRJgega3oqwdL08iwb3T%2Funknown.png?alt=media&amp;token=900c2be3-2427-4271-a5c8-bd3f8c96ee53" alt="" height="223" width="624">

***

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

{% hint style="warning" %}
The following changes are available in **@akinon/next (Project Zero) version** `2.0.158` **and** **later. Template Studio updates** are available on the current Akinon platform.
{% endhint %}

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

**Template Studio – Visibility Conditions**

* Blocks, columns, and sections in Template Studio can now be displayed based on configurable conditions, without writing Jinja. Multiple conditions can be combined using “all” or “any” logic, and alternative content can be defined with an “otherwise” option. Conditions can be previewed with test data before publishing. This makes it possible to tailor email content to different scenarios without coding.

**Template Studio – Convert HTML Emails into Editable Templates with AI**

* Users can now convert existing HTML emails into editable Template Studio templates using AI. They can paste HTML or upload an .html file, preview the converted blocks, and apply the result. Variables, links, and images are preserved during conversion. This makes it faster to bring existing email designs into Template Studio without rebuilding them manually.

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

**Template Studio – Complete Template Variables and Status Selection**

* Template Studio now provides the full set of commerce data available for each mail type, including order status, payment, shipping, tracking, and address information. When creating conditions, order and item statuses can be selected from predefined values. This gives users access to all relevant order details in their templates and reduces errors when setting up conditions.

**Template Studio – Draft Protection**

* When a draft already exists and the published version is opened for editing, Template Studio now asks whether to continue with the draft or edit the published version. Existing draft changes remain protected until the user makes a selection.

**Template Studio – Safer Publishing**

* Template Studio now checks emails, subject lines, and shared headers and footers for Jinja errors before publishing. If an error is found, publishing is blocked and the affected block and line are shown so the issue can be corrected. This prevents broken templates from reaching shoppers.

***

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

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

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

**Builds Use the Updated Keystore or Certificate**

* After a keystore or certificate is updated, builds now use the new file. Previously, a build could continue using the old keystore after an update and fail during signing. When the file type changes (for example, from .keystore to .jks), the new file is saved and the old one is removed. If the upload fails, no changes are saved, so the screen no longer shows values that builds do not use. This ensures that builds are signed with the credentials users uploaded and prevents unexpected signing failures. See the[ Credentials](https://docs.akinon.com/tutorials/app-maker/projects/settings/credentials) tutorial for details.&#x20;

**iOS Builds with App Extensions Start Correctly**

* iOS builds that include an app extension no longer fail before starting when the extension’s profile was uploaded under a different file name. Profiles for newly added extensions are now saved under their standard name. This allows iOS apps with extensions to build reliably, regardless of the profile’s original file name. See the[ Credentials](https://docs.akinon.com/tutorials/app-maker/projects/settings/credentials) tutorial for details.

**User Column on Dashboard Cards**

* On the Project Dashboard, the Latest Builds, Latest Code Push, and Latest Distributions cards now include a User column that shows who started each entry. Long names are shortened, and users can hover over a name to see the full name and email address. This makes it easier to see who started each build, code push, or distribution. See the[ Project Details](https://docs.akinon.com/tutorials/app-maker/projects/project-details.md) tutorial for details.

  <img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2FRK59tS6huJs8S2jjesYi%2Funknown.png?alt=media&amp;token=7bea72c9-2799-49b8-8799-ab2701343399" alt="" height="324" width="269">

**Simplified Detail Windows on Dashboard Cards**

* The detail windows of the Latest Builds, Latest Code Push, and Latest Distributions cards on the **Project Dashboard** now show who started each entry and how long it took, with columns in a fixed order. A single Started at column replaces the separate created and completed date columns, and users can hover over it to see both times. The release notes column and other additional detail columns have been removed from the table. This provides a cleaner and more consistent view of recent activity.

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2Ft8TU24AE17pJUCfp3aQ8%2Funknown.png?alt=media&amp;token=627fe456-6c0e-4d9b-9afc-e0a486dee701" alt="" height="257" width="624">

**Reworked Builds List**

* The Builds list now has seven columns instead of nine. A single Build column shows the full tag with a copy icon, the build number and target, and a Live badge on the live build. The Store column shows the store version with a status label such as Pending, Live, Approved, or Rejected. A single Created column shows the build date, with the build duration below it. This makes key build information easier to scan at a glance. See the [Build List](https://docs.akinon.com/tutorials/app-maker/build-and-distribute/build-list.md) tutorial for details.

**Artifact Details on Build Hover Cards**

* The build hover card now shows the store version and its status, along with the type and size of each artifact (for example, APK 94.58 MB · AAB 61.39 MB) and a Download link for each AAB, APK, or IPA file. If an artifact has expired, the card explains why it cannot be downloaded. Empty fields are hidden, and a missing version code or bundle number is shown as a dash. The build hover card on the Project Dashboard also shows artifact sizes by type. This gives users quick access to key build and artifact information.

<img src="https://1066499406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpVRheUHzJXXkDHR0KGf%2Fuploads%2F2CReXxgwjHQuODHVYzRB%2Funknown.png?alt=media&amp;token=ad2da54e-04e6-4c73-9996-b8c35e576c72" alt="" height="259" width="557">

**Keystore Validation Before Android and Huawei Builds**

* Android and Huawei builds now check the keystore password, key alias, and key password before the full build process starts. If any of these values is incorrect, the build timeline shows the error on the keystore step within seconds, instead of the build failing much later during signing. This helps users find and fix credential errors quickly without waiting for a long build to fail.


---

# 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/october/akinon-release-notes-10.26.2026.md?ask=<question>&goal=<user_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.
