> 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.22.2026.md). # Akinon Release Notes 06.22.2026 ## Omnitron {% hint style="warning" %} The following changes are available in **Omnitron FE** versions **later than** `v3.11.0` **and Omnitron BE** versions **later than** `v1.6.1`. {% endhint %} #### Resolved Issues **Whippy Ware - Stock List Rule Name Display** * The **Stock List Rule** field in the Whippy Ware Stock List form now displays rule names rather than rule IDs, improving readability and usability during stock list configuration. ![](/files/bPVjgpX3OLb73BSfE5Ka) #### Enhancements **Main Category Assignment for Products** * A new capability has been added to define a main category for products assigned to multiple categories. In **Products & Catalogs > Catalogs > Category Tree**, the categories assigned to a product are now listed in the Category column of the Products table. Users can designate a main category by clicking the category tag icon next to the desired category. {% embed url="" %} **Sorting Category Tree Scroll Improvement** * Scrolling has been enabled for the category tree in the **Sorting** section when the content exceeds the container height. This ensures all categories are accessible and aligns the behavior with other category trees in the application. ![](/files/WEvO5LO8Njg3sf1lwXW0) **Sales Channels List – Channel ID Column Added** * A new **Channel ID** column has been added to the **Sales Channels list** page, allowing users to easily identify and reference channel ID. ![](/files/EekjRRBB7If9bG5iOdhU) **Increase Minimum Password Length to 10 Characters for User Accounts** * In addition to the existing password policy rules — uppercase letter, lowercase letter, digit, special character, and no reuse of the last 3 passwords — the minimum password length for standard user accounts in Omnitron has been increased from 8 to 10 characters. This applies to both password creation and password change flows. **Add Audit Event Logging for Marketplace Attribute Schema Write Operations** * Write operations (`POST`, `PUT`, `PATCH`, `DELETE`) on the `api/v1/marketplace_attribute_schemas/` endpoint are now covered by the existing `django_audit_events` infrastructure, which was already in use across other modules such as payment, product, customer, and OAuth. Going forward, every write action on this endpoint will generate an audit event, making it possible to track who changed what and when on the marketplace attribute mapping screen. *** ## Commerce {% hint style="warning" %} The following changes are available in **Commerce** versions as of **June 22, 2026.** {% endhint %} #### **Resolved Issues** **Subscription Gateway Configuration Resilience** * Modified the subscription gateway initialization to safely handle environments where the campaign forms map is not explicitly configured. This prevents repetitive background task failures and ensures stable execution for unconfigured campaign types without generating false error alerts. **CRM Synchronization Task Stability** * Resolved a variable binding error in the CRM synchronization background task caused by missing gateway configurations. The service now implements safe defaults and graceful exits, preventing unhandled exceptions from masking root causes and spamming system logs. **URL Slug Generation Type Safety** * Fixed a type error during pretty URL generation triggered when localized product names are purely numeric. The URL slug utility now safely converts integer values to strings, ensuring product updates and listable status calculations process successfully without crashing. **CRM User Payload Validation** * Resolved missing key errors during user profile updates in the CRM synchronization service. The system now utilizes safe fallbacks for missing user identifier attributes, preventing synchronization flow failures for users with incomplete profile data. **User Permission Sync Stability** * Fixed a dictionary parsing error in the third-party permission synchronization service caused by unexpected API response formats. Improved data extraction logic ensures that a single invalid or empty user record no longer blocks the entire batch of bulk permission updates. **Event Message Definition Duplication Prevention** * Implemented strict validation at the service level to prevent the creation or modification of event messages with duplicate event names. This ensures structural integrity and prevents duplicate webhook deliveries and potential downstream data replication. **Product Category Main Flag Management** * Updated the product category API endpoints to properly process the primary category boolean flag. The system now safely evaluates null or omitted values as false, ensuring stable, error-free primary category assignments during product updates. **Search Engine Bot Verification Resilience** * Updated the external IP range validation URL for search engine bots to match the provider's latest endpoint. The system reliably fetches and parses the updated format to maintain accurate and uninterrupted bot traffic validation. #### New Features **Multi-Region Subscription Gateway Routing** * Implemented dynamic routing support for subscription gateways. The platform can now seamlessly direct user registrations, newsletter subscriptions, and order data to different regional third-party accounts based on specific user attributes (such as country code) within a single commerce instance. **Advanced Payment Option Rules** * Introduced frequency and limit-based rules for payment methods. Merchants can now configure rules to restrict specific payment options based on a customer's maximum order count or total maximum order amount within a configurable timeframe. **Platform-Specific Product Visibility** * Added support for filtering product visibility by shopping platform using dynamic exclusion parameters. Merchants can now configure specific items or collections to be exclusively available on mobile applications by dynamically hiding them from web storefronts, which enables app-only assortments and channel-specific merchandising. **AI-Powered Search Codebase Optimization** * Conducted a comprehensive structural optimization of the AI-powered search service. Introduced a standardized API router and improved module separation to enhance long-term maintainability, testability, and performance without altering existing search logic or end-user functionality. #### Enhancement **Gift Card & Promotion Calculation Integration** * Enhanced the gift card and loyalty payment flow to fully support basket-level discounts. The platform now accurately calculates and transmits the post-discount product amounts to external card services, ensuring correct balance deductions and discount applications across the cart. *** ## OMS #### **New Features** **Substitute Payment Pending Flow Added** * When a package is being finalized and the order is awaiting a substitute product with pending payment, the system now automatically monitors the payment status and finalizes the package once payment is confirmed. Previously this required manual intervention. Brands that wish to enable this can do so. #### **Enhancements** **Store-Specific Replan Can Now Be Disabled** * For orders assigned to a specific store (retail store delivery), it is now possible to disable automatic replanning when stock runs out via Application Settings; previously the system could reassign the order to a different store, which conflicted with the customer's original store selection, so disabling it keeps the order aligned with what the customer actually chose. **Product Replacement Error Messages Now Include Rejection Reason** * When a store associate uses the Replace Product action on a package and the request is rejected (for example, because the replacement item's price exceeds the allowed limit), the error message now shows the exact reason returned by the system instead of a generic failure notice. This allows the associate to understand immediately why the replacement was not allowed and take the appropriate next step — without needing to escalate for investigation. **Blacklist Products Can Now Be Added by SKU** * Products can now be added to the blacklist using their SKU in addition to their internal ID, making the process easier for operations teams who work with SKU-based data. Brands that wish to enable this can do so. **Cargo Label Query Number Source Is Now Configurable** * The identifier used when querying cargo labels can now be configured per cargo company. This allows different carriers to use the appropriate reference number without requiring code changes. Brands that wish to enable this can do so. **Inventory Discrepancy List Now Returns Full Details in a Single Request** * The inventory discrepancy listing page previously required multiple additional API calls to load related details for each row. All relevant information is now returned in a single request, significantly improving page load performance. **Omnitron Sync Behavior on Shipment Is Now Configurable** * The `sync_omnitron_status` setting can now be configured at the command level for the shipment flow, giving more granular control over when Omnitron is updated during package shipping. Brands that wish to enable this can do so. **Quota Change Logging Improved** * Quota increases and carry-over updates on stock locations are now fully logged with structured details (who, when, how much, and why). This makes it significantly easier to trace inventory discrepancies and investigate incidents. **Webhook Event Actions Now Audit Logged** * Manual publish and resend actions on webhook events are now recorded in the audit log, including who triggered them, when, and for which event. This improves operational traceability. *** ## Instore #### Resolved Issues **Cross-Border Minimum Amount Check Corrected** * When a cart contained both local and international items, the minimum order amount check was incorrectly calculated against the full cart total; it now considers only the total of international items, which prevents customers from being wrongly blocked at checkout and removes a barrier to completing cross-border orders. The warning message has also been updated to clearly tell the customer how much more they need to add in cross-border items. Brands that wish to enable this can do so. #### New Features **Cargo Company Name Not Displaying Correctly** * The cargo company name is now displayed consistently across all shipping providers, including extension-based ones. The display logic has been updated to always show the correct carrier name. Additionally, the form's package data fetching has been optimized for better performance.
![](/files/aMU0Bhn75PzSdqiQSWkY) **Phone Number Update Flow With OTP Verification** * Customers can now update their phone number from the profile page through a more secure flow. Clicking the update button opens a consent and SMS verification (OTP) step. The verification code is not sent until the customer confirms the required agreements, which protects against account takeover by requiring explicit consent and verification before such a sensitive change. Brands that wish to enable this flow can do so.
#### **Enhancements** **Customer login — Consent Step Before OTP** * On brands with SMS verification enabled, customers are now shown an informational prompt before a login OTP is sent. The customer must confirm before the code is dispatched and the login flow continues, increasing transparency while reducing unwanted OTPs and unnecessary SMS costs. Brands that wish to enable this can do so. **Staff Names Hidden on Personnel Selection** * The staff selection screen at the start of a sale can now be configured to show only the seller code (e.g. \[1024]) instead of the full name, supporting staff privacy and data minimization on shared, public-facing screens. **Order List Sales Channel Filter** * The sales channel list on the order list page can now be configured dynamically through UI Settings, letting brands show only the channels relevant to their operations and tailor the order list to their own needs without a code change. If no channels are configured, all channels are shown as before. Brands that wish to enable this can do so. ![](/files/A1KjCbfgVcd5AThpdSuu) **Order List Shipping Company Filter** * The shipping company filter on the Package Order List page can now be configured dynamically through UI Settings, allowing brands to show only the carriers they actively use. If no carriers are configured, all carriers continue to be shown as before. Brands that wish to enable this can do so. *** ## Seller Center {% hint style="warning" %} The following changes are available in **Seller Center FE versions later than** `v.8.136f0` **and Seller Center BE versions later than** `v1.1.182`. {% endhint %} #### Resolved Issues **Package List Page Error** * Fixed an issue on the **Orders > Packages > Package List** page where a previously selected status filter was rendered as an empty box with only an X icon upon page load, instead of displaying the selected value. Attempting to add a new status filter in this broken state caused a "Cannot read properties of null (reading 'value')" error and made the page inaccessible. The status filter now retains and displays its selected value correctly on page load. **Product Revision Modal Issue** * Fixed an issue where the Product Revision modal failed to open for non-variant and single-variant products in **Marketplace Catalog > Search Bulk Product.** Clicking **Select Action > Product Revision > Apply** resulted in a "Cannot read properties of null (reading 'classList')" error, preventing the modal from opening. The issue affected only non-variant and single-variant products; multi-variant products were not impacted. The modal now opens correctly for all product types. #### New Features **Datasource-Based Field Locking Page** * The Locked Fields feature under **Settings > Locked Fields** can now be applied and customized on a per-seller basis. Marketplace Owners can define field-locking rules tied to a specific sellers, enabling more granular control over which fields each seller can edit within their product and order workflows. ([How to manage locked fields — tutorial](/tutorials/seller-center/how-to-manage-locked-fields-in-seller-center.md)) **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. #### Enhancements **Contract Upload Size Limit Increased** * The maximum file size allowed for contract document uploads via **Finance > Agreements > Agreement Detail** has been increased to 20 MB. This accommodates larger contract files and reduces friction during seller onboarding and agreement management processes. **New Fields Added to Billing Address Section cvb5** * The Package Detail page (**Orders > Packages > Package List > Package Detail**) now shows three additional fields in the existing invoice address display. The new fields provide tax-related information, helping sellers particularly those without ERP integration capture the full billing details needed for invoicing. The invoice address section now shows the following fields (new fields marked): * Full Name * Phone * Identity Number / `identity_number` **(new)** * Tax Number / `tax_no` **(new)** * Tax Office / `tax_office` **(new)** * Full Address {% hint style="info" %} Empty fields are left blank and not displayed. {% endhint %} **Shipping Company List — Priority Ordering & Manual-Entry Labelling** Two improvements to the **Change Cargo Company** dropdown under **Actions** in **Orders > Packages > Package List**: * For packages in **Preparing** status, shipping options are now listed in ascending order by **Priority**, so sellers see options in the configured order and make fewer selection errors. * Options configured with **Allow Manual Entry = Yes** (**Settings > Delivery Settings > Delivery Setting Detail**) are now labelled as *Shipping Company Name + (Manual Entry)*, making them clearly distinguishable from standard options and preventing sellers who are expected to use manual entry from accidentally selecting a non-manual option. ![](/files/zdtvzKu9mZAn8kQxVz8o) *** ## App Maker ### Mobile #### New Features **Native Assets** {% hint style="warning" %} The following changes are available in **Environment version** `env6.8.0`**.** {% endhint %} * A new nativeAssets field has been added to akinon.json. The images, vector icons (SVG/XML), and media files listed here are automatically copied into each platform's own native resource system during the build (iOS Asset Catalog, Android res/drawable and res/raw). As a result, SVG icons and media files that previously could not easily be referenced from the native side are now resolved to the correct platform resource on iOS and Android through a single name (for example, native bottom tab bar icons); this removes the need for per-platform manual native configuration and the errors that came with it. **Plugins Can Contribute Every package.json Field** {% hint style="warning" %} The following changes are available in **Environment version** `env6.9.0`. {% endhint %} * Plugins can now contribute every documented package.json field to the project during installation, not just dependencies (scripts, engines, resolutions, overrides, and so on); each field is merged according to its own type. This lets plugin developers configure the project end to end at install time, reducing the steps where a developer would otherwise have to edit package.json manually and the errors that come with them. #### Enhancements **Axios Upgrade (0.19 → 1.13.6)** {% hint style="warning" %} The following changes are available in **Environment version** `env6.9.0`. {% endhint %} * `axios` has been upgraded from `0.19` to `1.13.6`; this is a major version jump. A dependency that had remained outdated for years was moved to a current, secure, and modern API, closing known security vulnerabilities and bringing the framework's network layer in line with up-to-date infrastructure. For compatibility, `axios-mock-adapter` has also been updated from `1.x` to `2.x`. * The framework's request() function (**mobile-framework-ui/shop/\_api/request.js**) has been updated internally to use the axios 1.x APIs. **No action is required for projects that only use `request()`**. * For projects that use axios directly via \`\`\_dependencies (or that have moved the request layer under `src`), breaking changes apply; the upgrade steps should be followed via the changelog. {% hint style="warning" %} The following changes are available in **Environment version** `env7.1.0`**.** {% endhint %} **React Native 0.83 & Expo SDK 55 Upgrade** * React Native has been upgraded to `0.83.9`, React to `19.2.1`, and Expo SDK to `55;` all Expo modules and the Android toolchain (compileSdk 36, Gradle 9, Kotlin 2.1.20) have been updated to compatible versions. Applications are moved to the latest supported, New Architecture compatible version, gaining performance, new features, and security updates, while avoiding the compatibility and support issues of staying on older versions. With this upgrade, the minimum Node.js version is now `20.19.4` and the minimum Xcode version is now `26.2`. Builds will fail on older versions. **New DevTools** * DevTools now run in a standalone desktop application without requiring a browser, and include a Network Inspector that shows all network requests with their timings, headers, and response previews. Developers can inspect network traffic and the origin of requests from a single place, completing debugging faster. For all technical details, code examples, dependency tables, and the step-by-step migration guide, see [ABP](https://abp.akinon.net/). --- # 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.22.2026.md?ask=&goal= ``` `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.