Note: These topics explain how to install Epi Commerce in a local environment. To learn about installing it in the cloud, see
* Install an Episerver Commerce site to run on Azure Web Sites
* Install an Episerver Commerce site to run on Amazon Web Services (AWS)
For better control and understanding, it is recommended to start developing in an empty project. However, you can install a sample site to explore and use for inspiration. The Episerver Visual Studio extension configured with NuGet packages provides a pre-configured website with CMS, and a Visual Studio project for development, to which you add the Commerce components through NuGet.
Note: If you install a project outside the default location Documents\Visual Studio\Projects, ensure that the current user has write permission to the parent directory to which you are installing. SQL LocalDB does not respect the Administrators group.
Episerver Commerce is based on two sites: a front-end (CMS) site and a back-end (Commerce Manager) site. In this example, we create an MVC-based project, but the procedure is similar for Web Forms.
The installed folder structure is similar to a "plain" CMS site, except there are two sites, back-end and front-end, and an Infrastructure folder containing InitializationModule.
The initialization module ensures that the catalog structure is added under the site's root level.
See Installing Episerver updates to add the latest updates to a Commerce site.
Go to Creating a start page. This will be the starting point for displaying product content on your e-commerce website.
Last updated: Aug 21, 2013