Headless e-commerce: what it means and when it pays off

In short: the head and the body apart

In a traditional online store one program does everything: products, cart, orders and how the pages look. In a headless setup the "head" – the store your customers see (frontend) – is detached from the "body": products, prices, stock and orders (backend). They exchange data through an API.

In practice the same body can serve many heads at once: the web store, the in-store POS, measurement calculators, a mobile app or a reseller's system.

Traditional or headless?

What does headless give you?

• Speed and search. The store is rendered on the server, so Google and your customer get finished HTML straight away. Speed affects both rankings (Core Web Vitals) and conversion.
• Full control of SEO. URLs, language versions, hreflang, structured data and redirects are yours, not dictated by a theme or plugin.
• Many channels, one truth. The web store, POS, B2B orders and calculators share the same products, prices and stock.
• Room to grow. A new country, domain, sales channel or ERP integration is added on top of the API without changing platforms.
• Design without compromise. The store looks like your brand, not like a theme template.

What does headless take?

Honestly: a headless store is technically more demanding than a ready-made theme store. There are more moving parts, and someone has to look after servers, updates, backups and security. That is why building one yourself is a heavy project for most merchants.

KIDE solves this by being a managed headless platform: you get the benefits of the architecture, while servers, updates and monitoring are handled for you for a monthly price.

When does headless pay off?

• You sell in several countries or languages, ideally on country domains.
• You have business customers: customer prices, quotes, invoice and 0 % VAT on EU sales.
• You run a shop and a web store that must share stock.
• You sell made-to-measure products or use calculators that add products to the cart.
• You publish a lot of content – blog, galleries, guides – and want search traffic from it.
• The store must connect to other systems such as accounting, ERP or shipping.

When is it not worth it? If the store is small, has few products and a standard theme is enough, an affordable SaaS platform is often the better choice. KIDE is sized for stores that have outgrown plans under €500 a month.

How KIDE does headless

• Medusa v2 – open-source commerce engine (MIT licence): products, prices, stock, orders, B2B.
• Next.js – server-rendered, cached storefront with its own URLs for every language.
• REST APIs – Store API for the storefront and Admin API for management. The POS, calculators and integrations use the same APIs.
• Your own server in the EU – a PostgreSQL database and all data on the customer's own server, not on a shared platform.

An example: LedStore sells on KIDE in eight country stores on their own domains. One admin runs over 1,600 products, 2,365 articles in eight languages and a gallery, and measurement calculators add products sold by the centimetre straight to the cart through the API.

What does a headless store cost?

Built yourself, a headless store costs development, hosting and ongoing maintenance. On KIDE all of this is in the monthly price: €500–2,000 a month including hosting, maintenance and backups, onboarding from €3,900 (excl. VAT). No transaction fees. See also the comparison with Shopify.