Who is involved in Ucommerce projects?
In order to get to an ideal situation you will have a couple of parties involved who do what they are best at. A typical Ucommerce solution usually has multiple parties involved.
Ucommerce provides the commerce building blocks and their default configuration. This saves valuable development time for the client, as it is more about configuration than developing from scratch. Out-of-the-box there is no frontend store, its custom implemented by the Partner. Ucommerce does provide an Accelerator frontend store, that serves as a sample and a quick start for the Partner.
The CMS provides powerful content creation features and the shell of the system. If you already have a favourite CMS, you won't have Your choices are currently Umbraco, Sitecore or Kentico.
The Partner implements a frontend store that is uniquely tailored for the Client, using the CMS content feature and the Ucommerce APIs. Moreover the partner molds the default configuration of the Ucommerce building blocks, to fit the needs of the client. Every commerce project is different and each client has a unique business model. Ucommerce can be changed to fit the clients business model, and not the other way around. Thanks to Ucommerce, the partner saves time and has a higher level of quality, and can focus on the clients complicated commerce features.
The back-office user its a seamless UI where they work with content and commerce experience. Everything from sign-in to a single system, to working with content or commerce, is all a click away. When the clients business grows or new commerce ideas, Ucommerce has the potential to be easily changed by the partner to fit the new business model. Ideally, the client will not be able to tell the difference between the CMS and Ucommerce.