Once you have installed either the B2B Store Theme or the B2B New Store Theme (when using the B2B Suite solution), you can customize the theme according to your store’s business needs. To do so, follow the steps described below.

Do not proceed with these instructions if you haven't installed the B2B Store Theme or the B2B New Store Theme (if using the B2B Suite solution), or the customization will not work.

First of all, you must clone the theme's boilerplate repository to your local files by running one of the following commands:

Now you are ready to start working on storefront customizations using the code editor of your preference:

1. Open the repository folder in your local files.
2. In the manifest.json file, change:
   • The vendor field to the name of the account you are using.
   • The name field to one of your choosing.
3. Customize the files in your local repository by editing the theme’s blocks to create a storefront that matches your business needs and visual identity. Refer to our Configuring templates and Block templates guides for more information on how Store Framework blocks work.
4. Save all changed files locally.

Once you have finished customizing your local files, you need to link them with your development workspace so that it reflects your local changes. Check out our guide if you want to learn more about linking an app.

Before you link your local files with your current workspace, you should run the vtex whoami command to check if you are using the account and development workspace where you want to apply your customizations.

Follow the steps below to link your customized theme with your development workspace.

1. Using your terminal, access the customized theme repository folder in your local files.
2. Run the vtex link command to link your local files with the workspace you are logged into.
3. Run the vtex browse command to check out your customized storefront.

If you are comfortable with your new storefront and you want to make your changes public in your store’s production workspace, follow the steps described in our guide on Making your new app version publicly available.