> 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/july/akinon-release-notes-07.06.2026.md). # Akinon Release Notes 07.06.2026 ## Omnitron {% hint style="warning" %} The following changes are available in **Omnitron FE versions later than** `v3.12.0` and **Omnitron BE versions later than** `v1.7.0`. {% endhint %} #### Resolved Issues **Marketplace-Funded Campaign Reconciliation Fix for Zero Seller Share** * Previously, when a campaign's Seller Campaign Share (`data_source_discount_share`) was set to 0.00 — meaning the marketplace fully covers the campaign cost Omnitron failed to correctly recognize this as a marketplace-funded campaign, resulting in incorrect (or missing) reconciliation adjustments. With this release, campaigns with a zero Seller Campaign Share are now properly identified as marketplace-funded, and the correct reconciliation adjustment is generated accordingly. **Dashboard - Consistent Refund Handling Between Total Revenue and Total Discount Metrics** * Previously, the “Total Revenue” and “Total Discount” metrics on the **Sales Channels > Dashboard** screen used inconsistent calculation logic regarding refunds. Total Revenue subtracted refund amounts from order totals, so a fully refunded order contributed zero to revenue. Total Discount, however, only summed order-level discount amounts without deducting the discount portion of refunded orders meaning a fully refunded order's discount still counted toward the total, even though the order itself no longer contributed to revenue. With this release, discount amounts from refunded orders are now also deducted from the Total Discount calculation, so both metrics are consistently based on the same set of orders. **Attribute Deletion Now Blocked When Products Are Associated** * Attribute deletion now checks for associated products before allowing removal. Previously, an attribute could be deleted even if products still referenced it, while its individual dropdown values (e.g., "Red", "Blue") were already protected from deletion in the same scenario an inconsistency that also meant deleting the parent attribute silently removed all of its values, bypassing that protection. This fix aligns the two behaviors: an attribute can no longer be deleted while it remains associated with any product. #### Enhancements **Campaign Management – Make Seller Campaign Share Mandatory** * The seller discount contribution field in the campaign detail form has been renamed to Seller Campaign Share (%) for improved clarity. The field is now mandatory, preventing campaigns from being saved without specifying a value. Additionally, an informational tooltip has been added to explain how the percentage determines the discount cost distribution between the marketplace and the seller (0–100%). This enhancement applies to campaign creation and editing for channels with **Seller Cente**r integration enabled. **B2B – Display Total Quantity in the Quote Totals** * A new **Total Quantity** row has been added to the **Quote Totals** table on the **Quotation Detail** page. Positioned above the **Total Price** row, it displays the aggregated quantity of all quotation items by retrieving and summing the `quantity` values across all paginated quotation item records. **B2B – Add Price Modified Date Column** * The **Price List Detail** page has been enhanced with a new **Price Modified Date** column, displaying the last update timestamp of each price record. To improve clarity, the existing **Creation Date** and **Date Updated** columns have been renamed to **Product Created Date** and **Product Modified Date**, respectively. Corresponding filter labels have also been updated, making it easier to distinguish product lifecycle dates from price update information. **Campaign Management – Add Basket Email Extension as a Secondary Campaign Condition** * A new **Basket Email Extension** secondary condition has been added to the **Campaign Conditions** tab, allowing campaigns to target baskets based on one or more email domains. This enhancement simplifies configuration for campaigns targeting multiple email domains while leveraging the new backend support for list-based email extension matching. **Automatic Retry for Bulk Operations on System-Induced Failures** * Previously, when a chunk within a bulk operation (covering sorting algorithms, collections, products, catalogs, and orders) failed due to a system-level issue — such as a Celery worker error, timeout, or lost connection the entire operation was immediately marked as `failed` with no retry attempt, requiring manual intervention to restart. With this release, bulk operations now automatically retry up to 3 times following a system-induced chunk failure. The operation is only marked as `failed` after all 3 retry attempts are exhausted, reducing the need for manual restarts. *** ## Commerce {% hint style="warning" %} The following changes are available in **Commerce versions as of July 06, 2026**. {% endhint %} #### **Resolved Issues** **Merchant Feed Availability Ratio Calculation** * Fixed an error that occurred during Google merchant feed generation, which was causing background feed upload failures. Feed generation now runs reliably, ensuring product availability data is calculated and uploaded correctly. **Multi-Brand Discount Code Email Extension Support** * Fixed an issue where campaigns failed to apply when multiple email extensions were configured simultaneously. The validation logic has been updated to correctly evaluate list-based email domains alongside direct email addresses, ensuring smooth promotional executions. **Registration Endpoint Multi-Language Translation Updates** * Addressed missing localized response messages for the registration endpoint (`/users/registration/`). Missing translations for specific custom validation and error messages have been successfully added for Polish, Ukrainian, Russian, Czech, Hungarian, Slovak, Kazakh, and Azerbaijani languages. **Basket Amount Shipping Rule Optimization** * Optimized the `BasketAmountQueryRule` within Commerce Bridge to calculate shipping thresholds using the final net amount after campaign discounts are applied, rather than the initial gross amount. This aligns the shipping charge execution directly with the true customer paid balance. **Promotion Offer Stock Limit Comparison Safety** * Fixed a critical error that occurred during basket operations when a promotion's maximum stock limit was missing or empty in the database. Stock limits with no value are now safely treated as zero, preventing the error and ensuring basket operations complete successfully. **Basket Offer Query Performance Optimization** * Fixed a database performance bottleneck that caused high CPU usage on database servers during periods of heavy traffic, specifically when checking basket offers and bulk voucher codes together. This change makes those checks run faster and puts less strain on the database during high load. **Merchant Feed Query Rule Initialization Safety** * Fixed a runtime `TypeError` in the merchant feed generation task caused by improperly formatted JSON structures within the attribute mapper's rule set. Added defensive exception handling during rule instantiation to log errors cleanly without disrupting the entire background catalog export process. **Broken Page Links (Pretty URLs)** * Fixed a server error caused by duplicate internal page links for the same page, language, and content combination. Users are now automatically redirected to a valid page instead of encountering an error. **Promotional Image Updates** * Fixed a long-standing error that prevented promotional product images from being updated correctly. Promotional images can now be edited reliably, without unexpected failures. **Autocomplete Product Extractions with Seller ID** * Resolved a front-end inventory display synchronization issue where products occasionally showed inaccurate supplier data during next-turn rendering. Updated the autocomplete extraction strategy setting to natively include the accurate `seller_id` directly within the backend response envelope. **User Collections API Price and Tax Integration** * Enhanced user and public collection listing endpoints to incorporate full pricing, retail pricing, currency mapping, price types, and specific tax rates within the inner product payload. This fix updates serializer inheritance patterns to correctly account for segment-based price tiers and dynamic discount variations. **Navigation Breadcrumb Hierarchy Synchronization** * Fixed an issue where the breadcrumb path on the storefront sometimes showed the wrong category path instead of the page's actual location in the catalog. **Concurrent Product URL Generation Conflict** * Fixed an error that could occur when multiple product images were uploaded or listing statuses were updated at the same time, causing URL conflicts and page failures for some products. Product pages now stay stable and accessible even during periods of heavy, simultaneous updates. #### New Features **Automated InStore Order Email Notifications** * Enhanced the order placement workflow to trigger automated email notifications to specific retail store locations using designated store email profiles managed via the Order Management System (OMS) and Omnitron layout settings. **Asynchronous Audit Log XLS Export for Marketing Actions** * Added a new asynchronous data-warehouse reporting capability allowing business teams to chunk and export historical audit event logs into downloadable Excel formatting directly from the Omnitron marketing panels. *** ## OMS {% hint style="warning" %} The following changes are available in **OMS versions later than** `v1.0.1`. {% endhint %} #### Resolved Issues **Cargo Label Not Regenerated When Shipping Company Changes** * Fixed an issue where, if the shipping carrier assigned to a package changed, the system continued using the outdated shipping label sometimes causing the carrier to reject the package. The correct, up-to-date label is now always fetched when the shipping company changes. **Stock Over-Reservation Under Concurrent Fulfillment** * Fixed a rare issue where, during periods of high order volume, a single low-stock item could occasionally be allocated to two different orders at the same time. Stock availability is now calculated more accurately, preventing this kind of overselling. **Silent Shipment Creation Failure for Misconfigured Cargo Conditions** * Previously, if a shipping rule was misconfigured in a way that routed a package to an incompatible shipping method, the system would fail with an unclear technical error and no explanation. The system now shows a clear message explaining what went wrong and which setting needs to be reviewed. **`shipper_info` Saved as String Instead of JSON Object** * Fixed an issue where certain nested shipping configuration values were being saved in the wrong format, silently preventing some settings from working as expected. These values are now saved and applied correctly. **Meaningful Error Response When External Stock Service Fails** * Previously, when the external stock system experienced a temporary issue, our system would show a generic server error making it look like our platform itself had failed. Stock-related queries now return a clear, meaningful error message instead, so it's easy to tell the difference between a temporary external issue and an actual system problem. **Blacklist Retention Task No Longer Reprocesses Inactive Records** * Fixed an issue where already-removed (inactive) blacklist entries were being unnecessarily reprocessed every hour, creating redundant log entries and updates. Inactive entries are now correctly left untouched, and reactivated items are handled properly going forward. **Cargo Label Query Key Determined per Shipment** * Fixed an issue where certain shipments specifically those registered through an external process rather than through our system could run into tracking problems because the wrong lookup method was being used. The system now automatically determines the correct way to look up each shipment's label, resolving tracking issues for the affected shipment types without impacting standard shipments. **Turkish Character Protection Extended to Staff Email Updates** * Fixed an issue where staff email addresses containing Turkish characters (such as ı, ş, ğ) could cause errors when updating staff information. This protection previously applied only when creating new staff accounts now also applies when updating existing ones. Existing affected email addresses have also been automatically corrected. #### Enhancements **Cargo Label Retrieved from Omnitron Only for 4P Orders** * For brands that use both their own fulfillment and a third-party (4P) fulfillment partner, a new setting now allows the third-party partner's shipping label to be used only for the orders they fulfill while all other orders continue using the standard label as before. This setting is off by default, so existing behavior is unchanged unless a brand chooses to enable it. **Package Detail API Now Includes `client_type`** * Package details now show where an order originated for example, website, mobile app, in-store, or B2B making it easier for store staff to see at a glance whether an order was placed online or in person. **Cancellation Plan Tagging to Prevent Reprocessing** * Cancellation requests are now marked as completed immediately after processing, preventing the same cancellation from being processed more than once. This reduces unnecessary system load, and in the rare case this marking step fails, the cancellation itself still completes successfully. *** ## Instore {% hint style="warning" %} The following changes are available in **Instore FE versions later than** `v1.0.4` and **Instore BE versions later than** `v1.0.0`. {% endhint %} #### New Features **Cross-Border Delivery Indicator on Package Order Detail** * The Package Order Detail screen now displays a delivery type indicator (Local / International) based on the `is_local` attribute of each order item, giving store staff immediate visibility into whether a package is intended for local or cross-border delivery. Visibility of this indicator is controlled by the same UI Setting used for the basket-screen indicator, ensuring consistent behavior across screens. Brands that wish to enable this can do so. **Order Source Displayed on Package Detail** * The Package Detail screen now displays the order source (Web / Mobile Browser, inStore App, Android App, iOS App) based on the order's `client_type` field, which is now included in the OMS package detail API response. Because web and Instore orders have different structures, this allows store staff to immediately identify the channel a package originated from and process it accordingly. Brands that wish to enable this can do so. *** ## Marketplace Dashboard #### Resolved Issues **Trendyol – Neighborhood-Based Address Creation Fix for Micro Orders** * Fixed an issue in Trendyol micro order flows where address creation failed when the use\_neighborhood setting was enabled on the channel configuration. Address creation for brands with this setting active now completes without errors. #### New Features **All Marketplaces – Send Products With Stock Only Setting** * A new configurable setting, *Send Products With Stock Only*, has been added across all marketplace integrations. When enabled on the sales channel configuration, only products with a stock quantity greater than zero are submitted to the marketplace, preventing unnecessary processing of out-of-stock items. When disabled, existing behavior is preserved and all products continue to be included in the product submission flow. **Trendyol – Cross-Border Order Invoice and Shipping Label Integration** * Support for Trendyol's cross-border (4P) order flow has been integrated. For these orders, invoices must be issued to DSM Grup Danışmanlık as an e-invoice, and shipping labels cannot be retrieved until the invoice is approved by Trendyol a process that typically completes within 30 minutes. Invoice validation errors are logged in detail under the marketplace's AB Labels operations screen. * Shipping labels for these orders are now fetched automatically once approved, and are delivered as a PDF containing the shipping label followed by product labels. Labels can be retrieved via the order shipping info endpoint, filterable by order number. {% hint style="warning" %} Sellers must sign a new agreement with Trendyol and complete the transition through the seller panel before their orders can be processed under this new cross-border flow. Enabling label retrieval also requires configuration changes on the integration side — please coordinate with your technical/integration team before enabling this flow. {% endhint %} **Hepsiburada – maximumPurchasableQuantity Sent via Stock Update Flow** * The `maximumPurchasableQuantity` field, configurable under Product Shipping Info Extra Data in the sales channel settings, is now sent through the stock update flow. Previously this value was not included in stock updates; it will now be transmitted alongside stock information whenever the stock flow runs. **Trendyol – Origin Field Migration for Product Create and Update Flows** * Country of origin information in Trendyol product create and update flows has been migrated to the dedicated origin field, in line with Trendyol's updated API requirements. {% hint style="warning" %} This field is mandatory as of **June 30, 2026**. Going forward, origin data will be submitted exclusively through the origin field in all product send and update flows — please ensure your product data includes this field ahead of the deadline. {% endhint %} #### Enhancements **Trendyol – Category Attributes Flow Performance Improvement** * The Trendyol Category Attributes flow has been optimized to support bulk writing of category nodes and attributes. This significantly reduces the time required to complete category and attribute transfers from approximately 7–8 days down to a single day. *** ## Seller Center {% hint style="warning" %} The following changes are available in **Seller Center FE versions later than** `v0.8.138` and **Seller Center BE versions later than** `v1.2.0`. {% endhint %} #### Resolved Issues **Orders Not Being Created for Products with Stock-Inactive Status** * Fixed an issue where orders were not being created when the basket contained products with a stock-inactive (passive) status. The order creation pipeline was incorrectly blocking order placement based on the stock activity status at checkout time, even when the product was legitimately purchasable. Orders are now created correctly regardless of the stock activity status of the products at the time of order placement. Customers can complete purchases and sellers receive orders correctly for products that are available but flagged as stock-inactive in the system. **Incorrect Discount Sharing Rate Value Displayed on Campaign Edit Screen** * On the campaign edit screen via **Marketing > Campaigns > Edit Campaign**, the **Discount Sharing Rate** field was displaying '–' instead of its actual numeric value. The field now correctly displays the configured rate, giving campaign managers accurate visibility into campaign configuration without needing to cross-reference other screens. **Unsynced Collections Shown as Disabled in Campaign Creation** * On the campaign creation screen via **Marketing > Campaigns > Add New Campaign** the collection dropdown now only shows collections synced to Commerce. Collections that have not been synced are shown as disabled in the dropdown, preventing campaign creation with unsynced collections. After campaign creation, collection information is now correctly sent to Omnitron. #### New Features **Failed Records Management Interface for Marketplace Owners** * A new **Failed Records** management page has been introduced for Marketplace Owners (MPO) under **Settings > Failed Records**. The page provides a list view showing operation date, operation type, seller name, number of failed records, and status. MPO can be filtered by dropdown, operation type, or date range (including time component). Clicking a row opens a detail modal showing which record failed, the row number, field name, and error message. An **XLSX** export button is available for reporting. **Shipment Auto-Creation Setting per Seller** * A new boolean configuration option, **Create Shipment for Preparing Packages**, has been added to the seller general info page under **Finance > Seller Management > General Info**. This setting is configurable by Marketplace Owners on a per-seller basis. When enabled, a shipment is automatically created for packages in the Preparing status, allowing different shipment creation behaviours to be defined independently across sellers. #### Enhancements **Duplicate Bulk Action Prevention per Datasource** * Users can no longer trigger a new bulk action with the same filters while an identical action is already running under the same datasource. Before starting a new bulk action, the system checks for any active bulk action with the same filters under the same datasource and blocks the duplicate request. Previously, users could launch multiple identical actions simultaneously, causing unnecessary system load and inefficient parallel processing. System stability improves as redundant queue entries are prevented, reducing processing overhead and avoiding conflicting bulk operations. **New Filters and Copy Buttons Added to Revision Requests** * The Revision Requests page (**Products > Revision Requests**) now supports filtering by UUID and Created Date, with copy-to-clipboard buttons added alongside UUID values. New default filters are shown on page load for newly added filter fields, ensuring users see the full filter set immediately. Previously, reviewers had no direct way to look up a specific revision by UUID or filter by creation date, requiring manual scrolling through large lists. * Users can now locate specific revision requests in seconds using UUID or date-based filters, significantly reducing lookup time for high-volume revision queues. *** ## Project Zero {% hint style="warning" %} The following changes are available in **@akinon/next (Project Zero) version** `2.0.33` and later. Theme Editor updates are live on the current Akinon platform. {% endhint %} #### Resolved Issues **Theme Editor — Security: Hardened Theme Styles** * Custom style values are now safely escaped so they cannot inject or run unintended markup on a visitor's page. This protects storefronts and visitors from potential security exploits hidden in custom styling. **Theme Editor — Icon Blocks Respect Mobile Settings** * Icon value, size and color now apply on mobile instead of falling back to desktop values. Ensures icons look and behave as intended on mobile, where most shoppers browse. **Theme Editor — Group Blocks Use the Right Element Per Screen Size** * Group blocks now use the correct element for the active screen size (previously always the desktop setting). Prevents layout and accessibility inconsistencies between desktop and mobile views. **Theme Editor — Coupon Banner Corner Radius Fixed** * A plain numeric corner radius (for example 12) is no longer reset to zero. Coupon banners now render with the intended design instead of losing custom styling. **Theme Editor — Video Blocks Handle Invalid URLs** * Video blocks show a placeholder for invalid URLs instead of breaking the page. This prevents a single bad video link from breaking the entire page for visitors. **Theme Editor — Cleaner Live Pages** * The "unknown block type" developer hint now appears only in the editor, never on live pages. This keeps the live storefront looking polished and free of internal debug messages. #### New Features **Checkout — Settings-Driven Checkout Variants** * Choose your checkout layout from a single setting. Alongside the default multi-step checkout, two new layouts are available: a one-page checkout and a combined basket-and-checkout page. Switching is a configuration change — your current checkout stays the default until you opt in. (See the [checkout variant system configuration](/technical-guides/project-zero/next.js/checkout-variant-system-configuration.md) guide for values and flow differences.) **Checkout — Better Support For In-Store Checkout Links** * Checkout links generated for in-store use now carry their session context and the originating cart's cookies through to checkout, so in-store-initiated orders continue smoothly. This ensures in-store-initiated purchases complete reliably, without losing cart or session information. #### Enhancements **Theme Editor — Faster Image Handling** * Uploaded images are now stored as CDN links instead of being embedded in the page data, so pages and the editor load faster. This improves loading speed for both the storefront and the editing experience. **Theme Editor — Clearer Warnings While Building Themes (Development Only)** * The theme editor now points out common mistakes — unknown blocks, misconfigured sections, missing data sources — that used to fail silently, with live pages unaffected. This helps developers catch and fix configuration mistakes earlier, before they reach the live storefront. #### System Improvements **Theme Editor — More Resilient Storefront Rendering** * If a single custom section fails, it is now skipped instead of breaking the whole page, and the platform also handles unexpected or unusual data more gracefully during rendering. This means a single faulty section or unexpected data no longer risks taking down an entire storefront page. --- # 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/july/akinon-release-notes-07.06.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.