# Virto’s Release Notes | October 2026 **URL:** \ **Category:** news digest\ **Created:** [September 28, 2026, 1:59pm UTC](https://www.virtocommerce.org/t/virto-s-release-notes-october-2026/864 "2026-09-28T13:59:09Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Maria-Volkova-Tula](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/maria-volkova-tula/32/1326_2.png) [@Maria-Volkova-Tula](https://www.virtocommerce.org/u/Maria-Volkova-Tula)\ **Post date:** [September 28, 2026, 1:59pm UTC](https://www.virtocommerce.org/t/virto-s-release-notes-october-2026/864/1 "2026-09-28T13:59:09Z")
Welcome to the October 2026 release notes! Autumn is settling in and the days are getting shorter, but our journey continues at full speed with new features, improvements, and plenty of exciting updates along the way! ![october2026](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/8/8f56daf89e260a69ea5d828a05ace331af786eb0.png) **Highlights** : - Missions and challenges now available in the Loyalty module. - Sales reps can now manage their tasks on the Frontend. - Sign-in logs have been added to the Security module. - Shared components can now be created in Page Builder. ## [Loyalty missions and challenges. Loyalty 3.1006.0](https://github.com/VirtoCommerce/vc-module-loyalty/releases/tag/3.1006.0) + [Frontend 2.57.0](https://github.com/VirtoCommerce/vc-frontend/releases/tag/2.57.0) A shopper can now view their open loyalty missions from their account, open any mission to see its goal and current progress: ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/f/f802b626e20d80a06b5b157a29a3bdf8917a9716.jpeg) ➡ [Missions and сhallenges](https://docs.virtocommerce.org/storefront/user-guide/latest/account/missions) The missions are configured by managers in the Platform. Managers can set a mission goal based on order value, order count, or the purchase of specific SKUs, scope it to one store with a start and end date, offer it only to selected customer groups, and award a fixed number of points on completion: ![new-loyalty-mission](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/0/0d4ff5b193b7aadb6db0427941426c90e976591b.png) ➡ [Managing loyalty missions](https://docs.virtocommerce.org/platform/user-guide/latest/loyalty/managing-loyalty-missions) ## [Earning and redeeming loyalty points at the organizational level. Loyalty 3.1008.0](https://github.com/VirtoCommerce/vc-module-loyalty/releases/tag/3.1008.0) Loyalty missions can now be completed by organizations, not just by individual customers: ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/2/2b5ad461a395a8dd29f8e28c3e711e65f36de5fb.png) Multiple managers can purchase on behalf of the same outlet and earn loyalty points collectively. Any manager can redeem the loyalty points earned by the outlet. ![organization-mission-reward](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/b/b859862dd77f05fd5480ec87b4d5d005e05d1ae0.png) ## [Sign-in log. Platform 3.1071.0](https://github.com/VirtoCommerce/vc-platform/releases/tag/3.1071.0) The Platform now keeps a durable record of every successful and failed sign-in attempt including sessions started through **Login on behalf**. ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/5/50aaeb834b44fec306aaba2509ab281cf1af65d6.png) Each widget is clickable and opens a detailed log. Each record carries the date, the user name as it was typed, the outcome, the failure reason if any, the sign-in type, the operator for on-behalf rows, IP address, host, user agent, store and member: ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/3/36d675cfa37d102f215c82b666b660eb794cb2b2.png) ➡ [Sign-in log](https://docs.virtocommerce.org/platform/user-guide/latest/security/sign-in-log) ## [Page-wide anchor linking. Page Builder 3.1022.0](https://github.com/VirtoCommerce/vc-module-pagebuilder/releases/tag/3.1022.0) Users can add links to selected text within a **Subscribe form** block making tables of contents, jump links, “back to top” and section navigation possible against anchors rendered by other components on the page: ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/7/70d632afc1bc379aec7fe2a2ef185487b21b7284.png) ➡ [Adding links to text](https://docs.virtocommerce.org/platform/user-guide/latest/page-builder/configure-content-block/#add-links-to-text) ## [Shared components. Page Builder 3.1026.0](https://github.com/VirtoCommerce/vc-module-pagebuilder/releases/tag/3.1026.0) Users can create, add, and delete shared components to be used across multiple pages, with the option to synchronize changes across all instances or edit each copy independently: ![create-shared-component](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/b/b9f7a59751217f79450ff04f5322bbf6d579b103.png) As soon as the component appears in the list of shared components in the **Page Builder Office** , you can view the pages where it is used: ![shared-components-used](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/e/e6ac40a92d13f122d5aa83beb9f0bdb69ade6c39.png) ➡ [Creating and adding shared components](https://docs.virtocommerce.org/platform/user-guide/latest/page-builder/configure-content-block/#create-and-add-shared-components) ## [Uploading over an asset improved. Page Builder 3.1025.0](https://github.com/VirtoCommerce/vc-module-pagebuilder/releases/tag/3.1025.0) If a user is trying to upload a file with the same full name (name + extension) as an existing file in the target folder, a confirmation prompt is displayed before anything is written ![file-name-conflict](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/c/cd338d6f90f603fd43e136bbb5b0a5e352882355.png) ➡ [Managing assets](https://docs.virtocommerce.org/platform/user-guide/latest/page-builder/manage-pages-via-office/#manage-assets) ## [Shared document library for sales reps. Sales Rep 3.1006.0](https://github.com/VirtoCommerce/vc-module-sales-rep/releases/tag/3.1006.0) + [Frontend 2.57.0](https://github.com/VirtoCommerce/vc-frontend/releases/tag/2.57.0) A Sales Rep can now access a centralized document library and quickly find and share approved sales materials, product images, brochures and price sheets, with customers. Uploaded files are organized into categories and shown on the Frontend dashboard. ![image|](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/f/f84fcab6113172f662dfd7cac290fc65dc04199b.png) ➡ [Document library](https://docs.virtocommerce.org/platform/user-guide/latest/sales-rep/document-library) ➡ [Sales rep hub](https://docs.virtocommerce.org/storefront/user-guide/latest/account/sales-rep-hub) ## [Sales rep task management. Sales Rep 3.1009.0](https://github.com/VirtoCommerce/vc-module-sales-rep/releases/tag/3.1009.0) Sales rep can now create a task with a title, description, due date and priority, view and complete active tasks grouped as Upcoming, Overdue and Completed, and see task indicators on a calendar: ![calendar](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/e/e1b660c39b4a3b2aa6256c89ac2ff9fb86046a6e.png) ➡ [Sales rep task management](https://docs.virtocommerce.org/storefront/user-guide/latest/account/sales-rep-hub/#calendar) ## [Product comparison. Frontend 2.57.0](https://github.com/VirtoCommerce/vc-frontend/releases/tag/2.57.0) Products comparison is now easier to navigate and review. Product attributes are grouped into **category tabs** instead of being displayed in a single mixed list. The **All/Differences** toggle lets users hide attributes that are identical across products, while any characteristic can be **pinned** for quick access. ![products-comparison](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/e/e87f1a5de29877f8f0c10f52647bdf195809a276.png) ➡ [Comparing products](https://docs.virtocommerce.org/storefront/user-guide/latest/shopping/compare-products/#compare-products) ## [Order price protection as a service. Orders 3.1015.0](https://github.com/VirtoCommerce/vc-module-order/releases/tag/3.1015.0) An administrator can give a user full access to orders while making it impossible for them to see the money on those orders. Order price visibility is now decided by one service rather than as a side effect of authorization, so the rule reaches every path that reads or writes an order: search, get by ID, save, patch, export and import. The default rule is unchanged, the global **order:read\_prices** permission, but it is now a single overridable method, so a solution can restrict prices by store, store type or organization instead of all-or-nothing. ➡ [Order prices visibility restriction](https://docs.virtocommerce.org/platform/user-guide/latest/order-management/order-price-restriction) ➡ [Order price visibility](https://docs.virtocommerce.org/platform/developer-guide/latest/Fundamentals/Security/authorization/order-price-visibility) ## [SSO support added for login on behalf. Frontend 2.57.0](https://github.com/VirtoCommerce/vc-frontend/releases/tag/2.57.0) The **Login on behalf** session page previously supported only a username and password. It now also supports SSO sign-in, where that option is enabled for the store. ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/9/9cf83fae18fd7971f3354fb9290570211e985dbe.png) ➡ [Logging in on behalf of company members](https://docs.virtocommerce.org/storefront/user-guide/latest/account/company-members/#log-in-on-behalf-of-company-member) ## [Locked organizations can no longer be switched into. Frontend 2.58.0](https://github.com/VirtoCommerce/vc-frontend/releases/tag/2.58.0) The organization switcher now reflects membership state: a locked organization is marked and disabled in the switcher instead of silently missing, so a multi-organization user can no longer switch into an organization they’re locked out of: ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/8/8704871558d941af1513f03682bf9c31589612f9.png) ➡ [Blocking, unblocking, deleting company members](https://docs.virtocommerce.org/storefront/user-guide/latest/account/company-members/#block-unblock-delete-company-members) ## [Configurable customer company roles on the Frontend. Customer 3.1023.0](https://github.com/VirtoCommerce/vc-module-customer/releases/tag/3.1023.0) An ecommerce administrator can now configure the customer company role per store in the backend: ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/6/6aa8c192a6581a25b0145f2ea6be2fb61748fcc5.png) On the Frontend, the roles appear in the roles list: ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/d/db56400a205a95096004056e939a7058c54fa277.png) ➡ [Membership roles whitelist](https://docs.virtocommerce.org/platform/user-guide/latest/contacts/managing-organization-roles/#membership-roles-whitelist) ## [Facet priority sorting now runs the way it reads. Catalog 3.1044.0](https://github.com/VirtoCommerce/vc-module-catalog/releases/tag/3.1044.0) Facets sorting now offers Priority ascending and Priority descending, set per property alongside Name, Numeric and Score sorting, so an administrator chooses the direction instead of guessing it. ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/9/9eadb1ff2e647eb8f5c308a631dc9a1f5597fe17.png) ➡ [Define product’s sorting order](https://docs.virtocommerce.org/platform/user-guide/latest/catalog/managing-properties/#define-products-sorting-order) ## [Users belonging to user groups visible right away. Core 3.1008.0](https://github.com/VirtoCommerce/vc-module-core/releases/tag/3.1008.0) A **Show customers** link is now available for every user group condition in **Promotions** , **Loyalty missions** , and **Pricelist assignment**. Clicking the link opens a blade with the contacts from the selected user groups, allowing managers to see which customers the rule applies to without performing a separate search. ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/0/0edc8a43461b2514e2009a6a2c16d825c6241f70.png) ## [UI Kit improvements. Frontend 2.58.0](https://github.com/VirtoCommerce/vc-frontend/releases/tag/2.58.0) A handful of shared UI Kit components were refined: - **VcButton** icon sizing and label casing now follow the design spec. - **Focus indicators** gained clearer accessibility styling across the framework. - **VcDateRangePicker** , a new component, ships for the first time. ## QA The team reworked its internal test flow, `/qa-test`, so a feature reaches release with less delay and less risk of a known-broken change slipping through. A five-minute environment check now runs first, so a dead test stand is caught immediately instead of forty minutes in. Testing starts as soon as a checklist and test data are ready, instead of waiting on a fixed step order, with test-writing happening in parallel. The slow full regression run at the end is gone, replaced by a check that re-runs only the tests actually written or changed for that piece of work. ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/1/19c15c9382ccf471374a9866d249dd37eb096f85.png) ## Marketplace Vendors picked up an improved custom-properties experience: setting a custom property on a product no longer requires master catalog taxonomy to define it first, and the workflow for doing so was refined for usability. The team also closed out a set of offer-management bugs, including a keyword search that missed matches, a special price that couldn’t be deleted, and an offer rename that silently reverted, and started work on self-serve returns management for vendors. ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/0/06490b919fbec043a8b562b8b0fe313c29a6a4b3.png) For more information, [request a demo](https://virtocommerce.com/request-demo) ## VC-Shell - **Accessibility, focus and honest hints** : Repairing focus after sign-out and after expanding a blade from the keyboard, fixing a maximized blade’s covering state not reaching sibling panels, announcing a self-disabling button’s state through `aria-disabled`, and correcting a stale dashboard-widget label. - **One owner for the URL.** A rule for keeping the blade stack and the browser URL in sync had been hand-written in eleven places, and one of them was missed. The blade stack now owns the URL directly and syncs it after any navigation action that actually changed something, fixing five related defects in the legacy adapter along the way. - **Loading and stale results.** A skeleton-loading indicator stopped rendering because its watcher ran before loading began, so nothing appeared at all on some blades; a stale search response was found overwriting a fresher one under load. Both are fixed, and a new `useLatestRequest` composable now guards eight list searches in the vendor portal. - **Custom properties in one window.** Adding a custom property to a product or offer used to mean leaving for a separate screen. It now opens in a small window next to the field, three duplicated implementations collapsed into one shared component, and the Create button now shows its own loading state while a name is validated. [Explore the new features and capabilities](https://vc-shell-storybook.govirto.com/) ## Documentation ➡ [Configuring Microsoft Entra-only authentication for Azure SQL](https://docs.virtocommerce.org/platform/developer-guide/latest/Fundamentals/Persistence/DB-Agnostic/azure-sql-entra-only-authentication/) ## Knowledge hub - [Integration Decision Guide: Choosing the Right Path for Commerce](https://virtocommerce.com/assets/integration-decision-guide) This 23-page guide covers the nine ways a commerce platform can connect to the systems around it, such as ERP, procurement platforms, suppliers and AI agents. The paths are grouped as buyer-facing, internal or supplier-facing. For each path it explains who owns the data, how sync works, what identity is required, and what happens when a connected system fails. It ends with an integration readiness self-assessment worksheet. Examples come from HEINEKEN and De Klok Dranken. - [The Virto Commerce Platform Brief for Pre-RFI Evaluation](https://virtocommerce.com/assets/virtos-commerce-innovation-platform) This 30-page brief answers the architecture, security and pricing questions that usually take up the first round of an evaluation. It covers: - [The Virto Marketplace Brief for Pre-RFI Evaluation](https://virtocommerce.com/assets/virto-marketplace) This is the 40-page marketplace version of the platform brief. It covers: ## Virto talks **Virto Commerce at Shoptalk Fall - Nashville, September 29 - October 1** Benjamin Black, VP of Growth, will show how AI changes B2B purchasing. Instead of making buyers navigate an entire catalog, the experience starts from what they want to get done. Coming to the event? Book a 20-minute meeting to see how this could work for your business. [Virto Commerce at Shoptalk Fall 2026 | Discovery Stage](https://virtocommerce.com/blog/shoptalk-fall-2026?utm_source=linkedin&utm_medium=social&utm_campaign=post-sep-25) ---
**Author:** ![OlegoO](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/olegoo/32/27_2.png) [@OlegoO](https://www.virtocommerce.org/u/OlegoO)\ **Post date:** [October 2, 2026, 10:17am UTC](https://www.virtocommerce.org/t/virto-s-release-notes-october-2026/864/2 "2026-10-02T10:17:04Z")
[Virto Commerce – Release Notes | October 2026](https://virtocommerce.github.io/vc-release-notes/2026-10/) in Business Format