Virto Commerce Stable 16: Agent-Assisted Upgrades, Stable UCP, and a New Job Engine

Most releases add features. Stable 16 also changes how you upgrade to them.

This is the first Stable bundle built for agent-assisted upgrades. An AI coding agent can read its upgrade material, assess the impact on your custom modules, and help you upgrade them. The bundle holds 59 modules, five of them new to the stable line: UCP, BackgroundJobs, OpenTelemetry, WhiteLabeling and XPickup.

Here is what Stable 16 contains.

Stable 16 publishes its upgrade material as plain files an agent can read: a breaking-changes inventory, an update path and a dependency-ordered module tree. An agent uses them as context to analyze what the release changes for your custom modules, then helps upgrade them one module per branch. The result is run against a live stack with the new BackgroundJobs module installed, and it goes through a normal pull request review.

Why it matters: Custom modules are where upgrades get expensive. The agent prepares the change for each module, and your developers keep the review.

Every Stable bundle passes full regression, end-to-end and load testing. These five modules are now part of it for the first time.

The UCP adapter implements the Universal Commerce Protocol, an open standard for agentic commerce. A compatible AI agent can sign the buyer in, search the catalog and build a cart under the buyer’s identity, then hand checkout back to your storefront. B2B buyers see their own contract prices, and your store stays the merchant of record.

Why it matters: UCP now sits on the line you run in production, so you can open your store to AI shopping agents without building a separate integration for each one.

BackgroundJobs takes over indexing, export and recurring jobs from the platform’s built-in Hangfire integration. Hangfire remains the default engine inside the module, and RabbitMQ or an in-memory engine can be used instead. See Platform Operations for how jobs are monitored and controlled.

Why it matters: Job processing becomes a module you version and choose. It also makes Stable 16 a breaking release. Without the module installed, no background or recurring job runs.

The OpenTelemetry module exports platform traces and metrics to external monitoring systems, as part of Platform Operations.

Why it matters: Operations teams can follow a slow request through the platform from the monitoring tool they already use.

The WhiteLabeling module gives each organization its own logo, colors, favicon and footer on a shared storefront. The White Label page shows how it fits partner portals and franchise networks.

Why it matters: Partners and customer organizations see their own brand while you run one store, now on a production-validated module.

XPickup adds a GraphQL API for finding pickup locations and choosing one at checkout, the API side of buy online, pick up in store.

Why it matters: Click and collect can be built into your own storefront through a stable module.

Two bigger changes arrive in this release. Neither replaces what you run today.

Admin Shell is a Vue-based admin UI. It is in preview, intended for testing and demos, and not yet a replacement for the existing Backoffice. The part that ships today is already useful. The AngularJS admin is now a separate module, and the Platform package shrank from 58 MB to 37 MB.

Frontend Next is a new Vue theme with a redesigned UI, built alongside the current theme. There is no forced migration, and the current theme stays supported. It is still evolving, so talk to our team before you adopt it.

Sign-in also gets new options: passkeys, email one-time codes and an email second factor. And buyers can now request returns in the storefront.

Stable 16 is a breaking release. Background processing moved into the BackgroundJobs module, and expired obsolete members were removed. Review the release notes before you start.

Questions?

Talk to our team.