News Digest - 2 Jun 2022

Today’s Highlights Are:

  • Virto Commerce Storefront v6 & VC Storefront Theme v1 on .NET 6 Released
  • Virto Commerce ​Performance Tests​
  • Cross-Selling & Up-Selling & Product Relations Released
  • Support for Azure active directory multitenant mode Released
  • Authorize New Module Released
  • Improved JWT tokens certificate generation

Virto Commerce Storefront and Virto Commerce Storefront Theme

We are more than happy to announce that Virto Commerce Storefront fully migrated to ASP.NET Core 6.0.
Let`s look inside Virtos’s Storefront.

Virto Storefront adapts to your business needs and allows you to flexibly customize all processes.
Run several different stores (websites) on top of Virto Commerce. Create websites with different designs for different products, regions, types of customers.

Each store (website) might have its own theme with a specific layout still being based on the same catalog and customer data.

Key features

• Multi-Store support
• Multi-Language support
• Multi-Currency support
• Multi-Themes support
• Faceted search support
• SEO friendly routing
• Server-side rendering
• Client-side rendering
• Optimization for Desktop
• Optimization for Tables
• Optimization for Mobile

Need more details? Visit Virto Commerce Storefront Kit repo.

VC Storefront Team implements common business use-cases needed for a vast majority of projects we build.

Download and Apply VC Storefront Theme

We optimized our theme to the best possible experience on a number of devices from Desktops to Mobile phones, concentrated both on UI and UX.

Note: The old themes are no longer being maintained by Virto Commerce. Developers are encouraged to check out VC Storefront Theme.
You can continue to use these themes with Virto Commerce Platform 3.x and Storefront 5.x; however, these repos will not be kept up to date.

Virto Commerce Performance Tests

To ensure we meet companies’ performance and scalability needs of all sizes, everything we launch — whether a new feature or enhancement — is thoroughly tested.

The Virto Team has developed a load environment that controls Performance Metrics for every / stable release, checks scalability and helps with performance investigation in client solutions.

If performance is degraded by more than 10% in testing, we revert a release back.

We’ve done a lot of work, and now all verification settings are valid and correct. Testing has shown a significant performance improvement compared to Q4 2021.

Read the details about Virto Commerce Performance Tests

Virto Commerce Cross-Selling, Up-Selling and Product Relations

Drive your sales and reduce marketing spending with the upselling and cross-selling features. Easily define specific product relations to present customers with recommendations.

By grouping your products into sets you allow your customers to browse through shop-the-look collections.

Watch your sales soar by offering bundled products that can only be bought together.


You can easily establish product associations that let your customers see recommendations of products they might also like, to encourage cross-selling.

Learn more

In Back Office, you need to add product associations with the Related Items group.

View live demo


To up-sell items, you can build a set of suggestions to offer upscale product versions or additional fixtures to maximize the cart value.

For frontend developers, Rest API and GraphQL (XAPI module should be installed) are available.

Note: Dynamic Associations module should be installed.

In Back Office, you need to add dynamic product associations in Marketing Module.

For developers, Rest API is available.

POST /api/dynamicassociations/evaluate

Product Relations

Product Relations let you define a list of items that will be displayed as comparable or additional products. This is especially useful to cross and up-sell products to increase the average order value and maximize sales. You can choose to either use Virto Commerce condition rule builder to manually define relations or import the information from an external source.

Support for Azure active directory multitenant mode

Virto Team has developed Custom Multitenant Azure AD issuer validator. You will need it if you use the Azure AD authentication and want to allow users from any tenant to connect to your Virto Commerce application. In this case, you need to configure the Azure AD app as multi-tenant and use a wildcard tenant ID, such as organizations or common in the authority URL.

Also, you need to switch Validate Issuer from Default to MultitenantAzureAD mode.

"AzureAd": {
    "TenantId": "common",
    "ValidateIssuer" : "MultitenantAzureAD",

The updated configuration can look like this:

"AzureAd": {
    "Enabled": true,
    "AuthenticationType": "AzureAD",
    "AuthenticationCaption": "Azure Active Directory",
    "ApplicationId": "b6d8dc6a-6ddd-4497-ad55-d65f91ca7f50",
    "TenantId": "common",
    "ValidateIssuer" : "MultitenantAzureAD",
    "AzureAdInstance": "",
    "DefaultUserType": "Manager",
    "UsePreferredUsername": false,
    "Priority": 0

Note: If you’re using the newer Microsoft.Identity.Web library, you don’t have anything to do to handle this, as the library already holds it.
Apply this solution only if you are using a generic OpenID Connect provider.

Authorize .Net DPM payment gateway integration module

Authorize .Net is a United States-based payment gateway service provider, allowing more than 440,000 merchants to accept and manage credit card and electronic check transactions via websites, retail stores, mail order/telephone order (MOTO) call centers and mobile devices, providing a reliable platform, scalability, and numerous value-adding services.

Authorize .Net offers easy, safe, and affordable credit card and eCheck processing.

New Authorize.Net DPM payment gateway integration module allows you to keep the customer on your site for the checkout process, allowing you maximum control over checkout.

New implementation uses external JS file to communicate with authorize servers to tokenize a CC and latest API. Payment form is currently generated in backend, but will be changed in the future.

Improved JWT tokens certificate generation

The problem is that the tokens supplied with the platform (pre-bundled cert) are not replaced on time by users. Nobody pays attention to it.
Therefore, we offer an automatic solution. Self-signed cert is generated at the platform startup.

The self-signed certificate is automatically generated when the platform is launched and placed in the database. And then, the platform works with the newly created certificate.

Auto replaces expired self-signed cert is also implemented.
At the same time, the ability to use custom cert preserved is also left.

1 Like