# Configuring Multiple Stores on Virto Commerce (Virto Cloud)

**URL:** <https://www.virtocommerce.org/t/configuring-multiple-stores-on-virto-commerce-virto-cloud/794>\
**Category:** howto\
**Tags:** storefront, multistore\
**Created:** [May 29, 2025, 3:41pm UTC](https://www.virtocommerce.org/t/configuring-multiple-stores-on-virto-commerce-virto-cloud/794 "2025-05-29T15:41:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**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:** [May 29, 2025, 3:41pm UTC](https://www.virtocommerce.org/t/configuring-multiple-stores-on-virto-commerce-virto-cloud/794/1 "2025-05-29T15:41:56Z")

</div>

Virto Commerce lets you run **multiple websites(stores)** on a single platform instance, each with its domain, theme, and configurations while sharing the same catalogs and customer data. In practice, you create separate stores in the Virto Commerce Manager, assign catalogs/pricing, and upload individual themes. The new Virto Commerce frontend is fully headless and composable, so you can flexibly add any number of front-end sites.

Below is a step-by-step guide to set up multiple stores on Virto Cloud.

## Prerequisites

Before you begin, ensure your Virto Commerce platform is deployed and running in Virto Cloud (see the [Deployment on Virto Cloud](https://docs.virtocommerce.org/platform/deployment-on-cloud/)).

Review [Virto Commerce Frontend Architecture](https://docs.virtocommerce.org/storefront/developer-guide/architecture/).

## Step 1: Create and Configure Store #1, Store #2, etc

Follow the following steps to configure a [New Store](https://docs.virtocommerce.org/platform/deployment-on-cloud/store-configuration/)

## Step 2. Create a New Virto Commerce Frontend Application

You can either create a new Virto Commerce Frontend Application or use ready ready-created artefact from [VirtoCommerce/vc-frontend Releases](https://github.com/VirtoCommerce/vc-frontend/releases)

## Step 3. Add Frontend Application

To integrate a frontend application (ex: `B2B-loyalty` ) into your Virto Commerce deployment, follow these steps.

> You can find all changes in [this commit](https://github.com/VirtoCommerce/vc-deploy-dev/commit/b6b672abbec6236fca5f704ec2d12998143296a0).

1. **Locate the `environments.yml` File:**  
Navigate to the `infra` directory of your deployment repository and open the `environments.yml` file.

2. **Add the `B2B-loyalty` Theme:**  
Within the `themes` section, add an entry for `B2B-loyalty` pointing to the appropriate theme package. For example:

3. **Define the `B2B-loyalty` Frontend Application:**  
Under the `frontend` section, add a new entry for `B2B-loyalty` with `prerender` set to `true`. For example:

4. **Configure Domain and Routing in Ingress** :

> 3rd-level domain for [govirto.com](http://govirto.com) will be enabled automatically. If you will need additional steps for custom domain assignment. Please follow Virto Cloud documentation for it.

```yaml
   - host: virtostart-loyalty-store.govirto.com
     root: B2B-loyalty
     paths:
     - path: /xapi
       route: platform
     - path: /files
       route: platform
     - path: /connect/token
       route: platform
     - path: /graphql
       route: platform
     - path: /revoke/token
       route: platform
     - path: /api/files
       route: platform
     - path: /externalsignin
       route: platform
     - path: /signin-oidc
       route: platform
     - path: /signin-google
       route: platform

```

1. **Deploy the Changes:**  
After updating the `environments.yml` file, apply the changes to your deployment environment using your standard deployment process.

By following these steps, you will successfully add the `B2B-loyalty` frontend application to your Virto Commerce deployment configuration. Here the some results after small branding.

 ![image](https://canada1.discourse-cdn.com/flex032/uploads/virtocommerce/original/2X/c/c9fde08f22ce086ff71fb98004846fba1f8fc42d.jpeg)