commercetools Frontend: Three Routes to a Headless Storefront
AI generated
commercetools Frontend, your own frontend or an accelerator: the routes to a headless storefront and how to choose based on team, timeline and content workflow.
commercetools provides the commerce logic, but no ready-made frontend. That's by design: it's exactly where the freedom of headless commerce comes from. For your project, though, it means the storefront has to be in place before the first customer can buy anything.
That makes the commercetools frontend one of the most important decisions in the project. It determines time-to-market, cost and how independently your team can manage content later on.
At a glance:
What headless means with commercetools
Which routes lead to a storefront
What matters in the frontend
How to choose the right route
What headless means with commercetools
Headless means frontend and backend are separated. commercetools exposes products, prices, cart and orders via APIs. The frontend, meaning what customers see, is built independently and pulls its data through those APIs.
The upside: you can run your web shop, app and other channels on the same commerce logic and design the frontend freely. The downside: the frontend is built as part of the project and costs time and budget.
Three routes to a storefront
1. commercetools Frontend
commercetools offers its own solution with the Frontend add-on. According to commercetools, it includes Studio, a no-code interface where business teams manage page layouts and content, plus developer tooling and hosting. Developers build the components with React and Next.js. The add-on is paid, and commercetools provides pricing on request.
2. Your own frontend
You build the storefront entirely yourself, for example with Next.js, and connect it to commercetools, a headless CMS, search and payment. This gives you the most freedom, but it's also the most effort.
3. Accelerator
An accelerator is a pre-built foundation that already includes typical shop features and integrations. We built SHOPin for exactly this: an open-source accelerator built around commercetools that brings commerce, CMS, search and payment together in one monorepo. Find out more at shopin.dev.
In practice: an accelerator shortens the start because core features don't have to be built from scratch. Your frontend still stays fully customisable.
What matters in the frontend
Performance: fast load times are a core argument for headless. Server-side rendering and caching need to be planned in from the start.
Content management: business teams need a tool to manage pages and campaigns without developers, such as a headless CMS or Studio.
SEO: URLs, metadata and structured data must be implemented properly in the frontend, because the commerce platform doesn't deliver them automatically.
Operations: hosting, deployments and monitoring of the frontend are part of the project.
What this means for your team
A headless frontend needs frontend development, in-house or through a partner, including after go-live. Every new shop feature is also a frontend task.
In return, you get freedom in design and user journeys and can connect new channels via the same APIs.
Our recommendation: decide based on your team and timeline. If business teams should manage a lot themselves, the content tool matters most. If time-to-market matters most, an accelerator pays off.
How to choose the right route
Gather requirements. Which page types, channels and languages do you need?
Clarify the content workflow. Who manages content, and with which tool?
Check your team. Do you have frontend development in-house or through a partner?
Compare the routes. Assess commercetools Frontend, your own frontend and an accelerator by cost, time and flexibility.
Conclusion: your commercetools frontend shapes project success
The commercetools frontend isn't a side issue. It's the biggest lever for time-to-market and user experience. There are three routes: the commercetools add-on, your own frontend or an accelerator.
Which one fits depends on your team, timeline and content workflow.
As a commercetools agency, we build headless storefronts with our SHOPin accelerator, with commercetools Frontend or fully custom.
Frequently asked questions
Does commercetools have its own frontend?
commercetools offers a paid Frontend add-on with Studio for business teams, developer tooling and hosting. You can also build your own frontend, because all features are available via APIs.
What is a headless frontend?
A headless frontend is the customer-facing interface of a shop, developed separately from the backend and fed with data via APIs. This lets you design channels independently of the commerce logic.
What is SHOPin?
SHOPin is an open-source accelerator for commercetools by creativestyle. It brings commerce, CMS, search and payment together in one monorepo and shortens the start of headless projects.
Which framework works for a commercetools frontend?
React and Next.js are widely used. commercetools Frontend itself is built on React and Next.js components.