Hi Lindy,

By all means, yes. The site project and the Commerce Manager projects are two separate sites, both of which utilize the underlying Epi APIs. I haven't tried it myself, but I know that it has and can be done :)

Hi Joel!

Ah, that's great! Thank you very much for you answer 

I can confirm that you can have a perfectly working Commerce site without even deploying a corresponding commerce manager site. The tiny integration which gives you a Commerce Manager option under Commerce in the epi UI is also its own optional NuGet package (EPiServer.Commerce.UI.ManagerIntegration) so you can skip that if you don't run a Commerce Manager site.

For futuer visitors, the answers from Joel and Magnus are of course correct. I just want to add that the two sites are independent, and unless you want to use the management future, such as catalog (you should use Catalog UI anyway), or orders, or customers. If you don't want to use those features (which is reasonable because no editors or mechandisers should work off hours), you can turn CM site off, without any affects on end-user experience when they use the front-end site to browse catalog or place orders.

We have customers which do not use CM at all as they have some other integrated systems to handle those features provided by CM.