Not every digital project needs a commerce platform, and not every commerce project needs a separate CMS. The right answer depends on where the value sits: in transactions, in content, or in how the two work together.

When commerce should be the centre

If the requirement is primarily transactional - pricing, accounts, catalogues, checkout and orders - the commerce platform should remain the architectural centre. Its own content features are often enough for product pages and supporting information.

When a CMS should be the centre

Content-led websites, portals, directories and multisite platforms are a different problem. Editors need freedom without breaking the design, structured information such as locations, products and partners needs to be governed at scale, and forms, CRM and other services need to connect to the content model.

That is where a CMS such as Umbraco earns its place. Our work with Big Day Cakes, for example, delivers self-theming licensed brand pages, store search with live opening status, structured store data and reusable content blocks on Umbraco 17.

When you need both

Content-led commerce, campaign-heavy journeys and multiple frontends often need both: Umbraco managing content, campaigns and editorial workflow, and commerce services handling catalogue, pricing, basket, checkout and accounts. Headless or composable architecture can connect them where the business case justifies the additional complexity - and it should be avoided where it does not. More on Umbraco CMS development.

Commerce-led, content-led, or both

Commerce-led

Transactions are the point. The commerce platform leads and carries enough content to support buying.

Content-led

Content, structured data and editorial freedom are the point. A CMS leads, with integrations where needed.

Both

Content and transactions carry equal weight. A CMS and commerce services work together in a deliberately designed architecture.

Questions that decide it

  • Where does most of the value for customers sit - in buying, or in finding and understanding?

  • How often do editors need to change pages, campaigns and structured content?

  • Which systems already own products, pricing and customer data?

  • Is there a genuine need for more than one frontend?