Headless vs traditional e-commerce — a comparison

The traditional platform you know from tens of thousands of other stores, or headless, which has been quietly becoming the standard in bigger brands for the last few years. The choice sounds simple until you start poking around in the details. Both sides make loud promises, so let's drop the marketing and get to specifics. Architecture, performance, SEO, costs, flexibility, security, lock-in. One by one, with numbers and honest caveats.

If the word "headless" still sounds abstract, start with our complete guide to headless e-commerce. Here we assume you already know the basics.

Architecture — monolith or two separate worlds

A traditional store is a monolith. On WooCommerce, PrestaShop, Shopify's hosted tier, and Magento, the frontend (what the customer sees) and the backend (products, orders, payments) sit in the same codebase, on the same server. Changing the cart layout means digging through templates, overrides, and plugins. Every deeper modification touches the whole system and carries the risk of regressions somewhere further down the line.

Headless separates these two layers. The frontend is a standalone application, most often in Next.js. The backend is an e-commerce engine (Medusa, Saleor, Shopify Storefront API, commercetools). They talk to each other through an API, usually GraphQL or REST. Every part can be developed, replaced, and scaled independently.

This isn't an academic difference. In a monolith, the design team waits for the backend team to finish engine changes before testing a new layout. In headless, they work in parallel. In business terms: headless lets you react to the market faster, and that speed eventually shows up in sales.

Performance and SEO — where headless wins hardest

This is the axis that translates most directly into money. Google has been using page speed as a ranking factor for years, and every extra second of load time eats into conversion.

Core Web Vitals

Google measures three things: LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift). WooCommerce with 15–20 plugins, a page builder, and a heavy theme almost always struggles with them. Headless on Next.js with a CDN starts with a ready-made advantage: SSR/SSG, image optimization through next/image, lazy loading and edge caching are in the box. You don't fight the platform, you just build. A full breakdown of the LCP/INP/CLS metrics with case studies and improvement techniques is in our piece on Core Web Vitals in e-commerce.

Load time and conversion

Three numbers worth keeping in mind:

• A headless store typically loads in under 1 second. A traditional platform needs 4–8 seconds.
• Google reports that 53% of mobile users abandon a page that takes longer than 3 seconds to load.
• Pages loading in 1 second have 3× the conversion rate of pages loading in 5 seconds (Google/Deloitte data).

Put in money: with 10,000 monthly visits and a 1.5% conversion rate, going from 5 to 1 second isn't a "nice improvement." It's several times more orders on the same marketing budget.

Full control over technical SEO

In headless, meta tags, Open Graph, JSON-LD, canonical, hreflang, and sitemaps are defined programmatically. No fighting template limits. On traditional platforms, you depend on plugins like Yoast, Rank Math, or a built-in SEO module. They work, but you hit their ceiling the moment you start doing SEO seriously.

How these differences translate into actual sales, we break down in a separate piece on how SEO impacts e-commerce sales.

An honest caveat

Traditional platforms give you SEO out of the box. Sitemaps, meta tags, breadcrumbs are there by default. In headless, it's a deliberate piece of work at rollout, but one-time work, not an ongoing overhead. At Outfox it goes into the rollout package as standard, so for the client it's invisible.

Costs — TCO, not the number on a landing page

This is where most misunderstandings happen, so let's lay it out honestly. The price on the platform's landing page is only a fraction of what you actually pay. Total Cost of Ownership over 3 years is what tells you the real number.

What really goes into the cost of a traditional platform

Hosted SaaS (Shopify, Shoper, BigCommerce). Subscription starting at a few dozen dollars a month, and on many plans you also pay transaction fees, paid modules (advanced promotions, wholesaler integrations, reviews, loyalty), a premium theme, and marketplace integrations. An active store easily runs into several hundred dollars a month, and it scales with turnover.

WooCommerce. The core is free, but in practice you still need decent hosting, a paid theme, and commercial plugins: Yoast Premium, WP Rocket, ACF Pro, something for payments, something for SEO, something for backups. With ten plugins, licenses easily eat up $500–1,000 a year, before you even add technical care.

PrestaShop. Free core plus paid modules, which vary wildly in quality and generate costs at every bigger change.

Fully hosted regional SaaS. Subscription plus transaction fees, no ability to touch the code yourself.

What headless actually costs

Medusa and Saleor are open source. Zero licenses. You only pay for hosting. A backend on Railway or a similar provider runs in the tens of dollars a month. The frontend on Vercel or Netlify usually starts on the free tier, and with larger traffic you move to plans around $20–30/month. And no sales commissions.

Honestly: headless has a higher rollout cost than clicking a store together from a ready-made template. If you're building an MVP with a dozen or so products, "let's see if it catches on," a traditional platform wins on starting budget. Nothing wrong with that.

When the balance flips

Typically somewhere between month 18 and 24 after launch. The one-time headless rollout investment becomes cheaper than the sum of subscriptions, commissions, paid plugins, and licenses. The gap keeps widening every year. Over a 3–5 year horizon you're looking at tens of thousands of dollars of difference, not a handful.

Flexibility and growth

Design

A traditional platform gives you a theme or a page builder. Sure, you can reshape it, but every bigger modification means a deeper fight with the system. Especially with page builders like Elementor, which layer their own DOM on top, generate extra bloat, and butcher your Core Web Vitals. In headless, you write the frontend from scratch, so every pixel is where it should be. The difference shows at a glance: stores on WooCommerce and hosted SaaS often look similar because they share the same pool of themes. A headless store looks like a premium product, because it isn't a template.

Omnichannel

In a traditional store, every channel (web, mobile app, kiosk, B2B portal) needs a separate implementation, and sometimes a completely separate system. In headless, one backend powers every frontend at once. Launching in Germany with a dedicated German-language storefront? You plug in another "head," the backend stays the same. That is a real advantage for companies thinking beyond "one website."

Integrations

Headless connects to ERP, PIM, CRM, OMS, and marketing tools through APIs. On traditional platforms, you depend on what plugins offer, and those can be half-finished, unmaintained, or sold on subscription. Got a warehouse system that works and you don't want to touch it? In headless you wire it into the store through an API and move on.

Pace of new feature rollouts

A new feature on a traditional store typically takes 8–12 weeks. In headless, it fits in 2–4 weeks, mainly because frontend and backend teams can work in parallel instead of one waiting on the other. If your business has to test market hypotheses fast, that difference in pace becomes hard to catch up with.

Security and updates

WordPress (and with it WooCommerce) is the most frequent target of CMS attacks on the internet. The reason is mundane: it's also the most popular CMS in the world. Every plugin is a potential hole, and a core update can break a theme or plugins that haven't had a patch in years. PrestaShop isn't any better: the ecosystem is aging, and modules are often poorly maintained.

In headless, you update frontend and backend independently. The backend gets a new version and the frontend doesn't even know. The frontend gets a redesign and the backend doesn't need to be touched. Fewer points of contact means fewer places where something can break on the side. The attack surface itself is smaller, because the admin panel isn't publicly exposed on the same domain as the store.

Vendor lock-in — renting or owning

This is the argument that's easy to ignore at launch and hurts the most 2–3 years in.

Hosted SaaS (Shopify's hosted tier, Shoper, IdoSell). You're renting the platform. Product data, look, and functionality are in its format, so leaving usually means rebuilding the store from scratch. A client who wants to switch providers effectively starts the project over.

WooCommerce. Technically you own the code, practically you're dependent on the WordPress ecosystem, paid plugins, and the theme. Migrating to another solution is still a sizable project, but at least you're not starting from zero.

Headless on open source (Medusa, Saleor). The code is yours. Want to change service providers later? You can. Swap the frontend and keep the backend? Go for it. Swap the backend and keep the frontend? Harder, but doable, because the APIs are well documented.

When a traditional store is actually the better choice

Headless isn't the answer to every question. It's a tool, not an ideology. A traditional platform is the healthier choice if:

• You're launching "yesterday" on a tight budget and need to start selling right now
• You have a small catalog (a dozen or so products) and no plans for multi-channel
• The store is an experiment, a pilot, a "let's see if it catches on"
• You don't care about a unique design and it's fine if the store looks like many others
• You have no tech partner and want to click the store together yourself

When headless is an obvious call

On the other side, headless is the pick when:

• The store is a long-term project, not "let's see if it catches on"
• You care about performance and want Core Web Vitals to be your advantage instead of a problem
• The brand has its own visual language and a template isn't enough
• You're planning several channels (web + app, web + B2B, web + other markets)
• You want to ship and test new things often
• You don't want growing turnover to automatically pump up your platform fees

Debunking the five most common myths

"Headless is too expensive for a small store"

If you only compare the rollout price, yes, headless is more expensive. If you compare TCO over 3 years, including subscriptions, commissions, paid modules, and plugin licenses, it usually comes out cheaper. This isn't marketing, it's math.

"It's too complicated for a client without a technical background"

Running a headless store from the admin looks exactly like running a Shopify or Shoper store: you log into the admin, add products, set up promotions, handle orders. Medusa and Saleor have solid dashboards. The client doesn't see code day to day, just like they don't see Shopify's code.

"Headless only makes sense for big players"

That was a real argument in 2019–2022, when headless required expensive platforms like commercetools. Today, Medusa and Saleor paired with Next.js put the same level of technology within reach of a small store's budget. The same way WordPress democratized blogs fifteen years ago, Medusa and Saleor are democratizing headless today.

"WooCommerce is proven and everywhere"

Proven, yes, but in a different era. WordPress started as a blogging platform in 2003. WooCommerce is a plugin stapled onto a blog, not an architecture native to e-commerce. It works, but everything you do in e-commerce on WP, you do against its original purpose. For a small store, fine. For a business looking to scale, the limitation shows up sooner and sooner.

"You can't migrate, I'm stuck on my current platform"

You can. Migration is a project, not a miracle. Products, categories, customers, historical orders, we pull all of it and move it. Bad news for believers in this myth: the longer you wait, the more data there is to move, and the more expensive the migration.

Frequently asked questions

Can I migrate from Shopify, Shoper, or WooCommerce to headless without losing data?

Yes. Products, categories, historical orders, customer data, we move all of it. On SaaS platforms, access to data goes through APIs; in WooCommerce, directly from the database. Rare exceptions are specific attributes that the new backend doesn't support 1:1, and those we map manually. For a larger store, migration usually takes 2–4 weeks of work, depending on the number of integrations.

How much does headless actually cost vs a traditional platform over 3 years?

It depends on turnover. For a small store (up to around $100k in yearly sales), a traditional platform like Shopify runs roughly $5–8k over 3 years, with subscriptions, commissions, and add-ons. Headless is a one-time rollout investment (in the $3–7k range for a small store) plus a few hundred dollars a year for hosting. The balance typically flips around month 18–24.

Should small stores (up to 50 products) go headless?

Depends on the horizon. If the store is going to be a multi-year project and you care about standing out through unique design and strong performance, then yes. If it's a 3-month pilot on a $500 budget, then no. Grab Shopify or WooCommerce, launch, and see what happens.

What happens to my headless store in 5 years if the framework changes?

The frontend gets updated. Next.js has shipped 15+ major versions since 2016, and each one has either been backward compatible or had a clean migration path. Headless backends (Medusa, Saleor) evolve similarly. The big advantage of headless here is that you update frontend and backend independently, so there's no "big leap" every few years. Standard technical care with us includes stack upgrades.

Does headless need expensive developers for day-to-day care?

Day to day, no. The client runs the store from the admin panel: products, categories, promotions, orders. Developers are needed for bigger changes: new sections, integrations, redesigns. Same as with WooCommerce, except instead of fighting plugins you're doing it cleanly and on purpose.

Wrapping up

If you're just starting out, have a dozen or so products, and want to launch as fast, cheap, and low-friction as possible, grab Shopify or WooCommerce and go. Seriously, nothing wrong with that.

If the store is meant to be a long-term project, if you care about performance, SEO, unique design, and don't want growing revenue to automatically grow your platform fees, headless is the healthier call. Not the cheapest at launch, but healthier over 2–3 years and beyond.

The worst decision is the one made without thinking it through. Migrating from headless to a monolith is painful and expensive, and going the other way isn't any nicer. If you're not sure where your store fits, instead of guessing, let's start with a concrete conversation about your business, not about the technology.