Ecommerce

Shopify vs Custom Headless Ecommerce: When to Stay and When to Switch

Your Shopify store is growing, the app bills keep rising, and an agency has just told you it's time to go headless.

They might be right. But rebuild for the wrong reason and you pay twice: once for the build, then every month for the developers who keep it running, while the original problem is often still there.

The real choice isn't Shopify or custom. There are three options, and each one fixes a different problem. Here's how to tell which one yours actually needs.

What's the Difference Between Shopify, Headless and Fully Custom?

The difference is how much of your store you own and maintain yourself. Standard Shopify runs everything. Headless keeps Shopify's engine and checkout but replaces the storefront. Fully custom means leaving Shopify and owning every part of the stack.

Standard ShopifyHeadless ShopifyFully custom
StorefrontShopify theme (Liquid)Custom build (Hydrogen, Next.js)Custom build
Products, cart, checkoutShopifyShopifyYou
Payments, PCI compliance, fraud, taxShopifyShopifyYou
Hosting and uptimeShopifyYou (or Shopify's Oxygen)You
Typical launch timeWeeksMonthsMany months
Who maintains itYour team plus appsA developer team, permanentlyA developer team, permanently

Hydrogen is Shopify's own framework for building headless storefronts, and Oxygen is Shopify's hosting for them. Both are available on every paid Shopify plan, so headless doesn't automatically mean Shopify Plus.

The key point: headless and fully custom are not the same decision. Headless changes what customers see. Fully custom changes what runs the business. Mixing the two up is how brands end up paying for a full rebuild when they only needed a better storefront.

Why Should Most Brands Stay on Shopify?

Most brands should stay because Shopify handles the expensive, risky parts of ecommerce for them: payments, PCI compliance, fraud checks, tax, hosting, peak-traffic uptime and security updates. If you sell products with variants through a normal checkout, that's hard to beat on cost or reliability.

Several common objections are also out of date:

"Shopify limits my variants." Shopify now supports up to 2,048 variants per product, up from the old limit of 100.

"I can't get the design I want." A well-built custom theme can look and behave very differently from a template.

"I don't own my store." You can export your products, customers and orders. What you can't take with you is Shopify's infrastructure, and a custom build doesn't remove dependency, it just spreads it across more suppliers.

In our experience, many "Shopify is holding us back" complaints turn out to be build-quality problems, not platform problems. Check these first:

The complaintThe usual real causeThe cheaper fix
"The site is slow"Heavy theme, too many apps, large imagesTheme clean-up, app audit, image optimisation
"It looks generic"An off-the-shelf templateA custom theme design
"Content is hard to update"Poor use of sections and metafieldsRebuild the content model in the theme
"Search is poor"Default search on a big catalogueA dedicated search and filtering app
"App costs keep rising"Apps doing overlapping jobsConsolidate apps or build key features into the theme

If one of these fixes your problem, you've saved the cost of a rebuild. A specialist ecommerce development team can usually tell you which category you're in after a short audit.

What Are Shopify's Real Limits in 2026?

Shopify's real limits are in checkout control, fees, app sprawl and unusual product or pricing models, not in design or speed. These are the constraints that genuinely push brands to look elsewhere:

  • Checkout control has tightened. Shopify has retired checkout.liquid, so checkout changes now go through Checkout Extensibility. The deepest customisation of the information, shipping and payment steps is limited to Shopify Plus, and some checkout logic can't be built at all.
  • Transaction fees. If you use a payment provider other than Shopify Payments, Shopify adds a fee on every sale, up to 2% on the Basic plan.
  • App sprawl and the workaround tax. Each missing feature becomes another monthly app, and each app adds weight, cost and another thing that can break. Staff time spent working around the platform is a real cost, even if it never shows up on an invoice.
  • Complex products and pricing. Configurable products with formula-based pricing, customer-specific contract pricing and quote-and-approve buying don't fit neatly into products, variants and metafields.
  • Content and commerce friction. Brands that run heavy editorial content or fast-changing campaigns can find the theme editor slows their marketing team down.

If none of these describe your business, you probably haven't outgrown Shopify. If one or two do, read on, because the right fix depends on which one.

When Is Headless Shopify the Right Move?

Headless is the right move when your storefront is the bottleneck but Shopify's engine and checkout still work well for you. It's a fix for experience problems, not commerce problems. Strong triggers include:

  • You need interactive experiences a theme can't handle smoothly, such as 3D product configurators or app-like product builders.
  • Your brand is content-led, and editorial pages, campaigns and products need to live together in one experience.
  • You run several storefronts, brands or regions from one Shopify backend.
  • You have the engineering team to tune performance at a scale where small speed gains are worth real money.

What you take on is just as important: front-end hosting, deployments, ongoing developer time, keeping up with Shopify's API version changes and, often overlooked, losing many front-end apps. Reviews widgets, upsell tools and page builders built for themes often don't work on a headless storefront, so those features must be rebuilt or replaced.

Use this test before you commit: name the specific thing your theme cannot do. If you can't, headless is an expensive answer to a problem you don't have.

When Does a Fully Custom Build Make Sense?

A fully custom build makes sense only when your business model itself can't be expressed cleanly on Shopify, even with Plus, apps and a headless front end. These cases are rare but real:

  • You're not really a storefront. Multi-seller marketplaces, rental platforms and complex booking or operations systems often fight Shopify's structure.
  • Your checkout can't be built on Plus. Regulated sales flows, multi-step quoting and approvals, or unusual payment logic.
  • Your data doesn't fit products and variants. Formula-based pricing or deeply configurable products where every order is different.
  • The store is the system of record. Complex business logic needs to live in the commerce platform itself, not in apps bolted around it.

What you take on is permanent. Leaving Shopify makes you responsible for PCI compliance, fraud prevention, tax calculation, uptime, security patches and every feature your apps used to provide, including the admin tools your team uses daily.

Before choosing this route, ask one question: who will maintain this system in 18 months? If there's no clear answer, a custom platform becomes a liability as soon as the original developers move on.

How Much Does Each Option Really Cost?

Standard Shopify is by far the cheapest to run. Headless and fully custom builds cost more upfront and, more importantly, add permanent monthly costs that most business cases underestimate. As a rough guide (quotes vary widely with scope and integrations):

UpfrontOngoing
Standard ShopifyLow thousands to tens of thousands for a custom themePlan, apps, transaction fees
Shopify PlusSame as above, plus migration if upgradingFrom $2,300 a month on a 3-year term ($2,500 on 1 year)
Headless ShopifyTypically tens of thousands to six figuresShopify plan, front-end hosting, developer retainer
Fully customTypically six figuresHosting, security, compliance, a permanent development team

At enterprise level the numbers get much larger. In a WP Engine survey of organisations with 1,000+ employees, companies spent an average of $2.6 million implementing headless architecture.

A Worked Example: What Does Headless Need to Earn?

Take a store turning over £3 million a year at a 40% gross margin. It's quoted £80,000 for a headless build, plus £3,000 a month for hosting and a developer retainer.

  • Three-year cost: £80,000 + (£36,000 × 3) = £188,000
  • Revenue needed to cover it at 40% margin: £188,000 ÷ 0.4 = £470,000
  • That's about £157,000 a year, or a 5.2% sustained revenue lift, just to break even

That's achievable for some brands, but only if headless solves a real conversion problem. If the store is already fast and the theme already converts well, the lift may never come.

The Hidden Costs on Both Sides

  • If you switch: rebuilding app features, admin tools for your merchandisers, API upgrades, monitoring and on-call support.
  • If you stay: stacked app subscriptions, staff hours spent on workarounds, and features you can't launch.

Before deciding, log every hour your team spends working around the platform for one month, then multiply by twelve. That number, not an agency's pitch, is your real cost of staying.

Does Going Headless Hurt SEO?

Going headless only hurts SEO when it's built badly, but it's easy to build badly. The common problem is pages that render in the browser with JavaScript, so Google sees a thin or empty page before the content loads, along with missing metadata and structured data.

If you go headless, make these non-negotiable in your developer's brief:

  • Server-side rendering, so every page arrives with its content, title, meta description and schema already in the HTML
  • Structured data for products, reviews, breadcrumbs and your organisation
  • Core Web Vitals targets agreed before launch and tested on real mobile devices
  • A complete URL map with 301 redirects if any URLs change, plus an updated XML sitemap

Done properly, headless can match or beat a theme on speed. Done carelessly, it can cost you rankings you spent years earning.

Should You Stay, Go Headless or Go Custom?

You should match the option to where the problem actually sits: in the build, in the storefront, or in the commerce engine. Answer these six questions honestly:

  • Is the core problem the storefront experience, or the commerce engine itself?
  • Does your product and pricing model fit Shopify's structure, even with metafields?
  • Can your checkout requirements be met on Shopify Plus with Checkout Extensibility?
  • Do you have ongoing engineering capacity, and will you still have it in two years?
  • Have you already tried the cheaper fixes: theme, apps, search and content model?
  • What will your platform need to support in two to three years?

Then use this matrix:

If the pain is...Choose
Build quality: speed, design, apps, searchStay on Shopify and fix the theme
The storefront, content or UX, while the commerce engine works fineHeadless Shopify
The business model itself: pricing, checkout, data structureFully custom

That's why speed alone rarely justifies a rebuild: a well-optimised theme can often deliver those gains for a fraction of the cost.

Why Upgrade in Stages Instead of All at Once?

Upgrading in stages means you only pay for the level of change your problem actually needs. Each step is cheaper and less risky than the one after it:

  • Optimise the theme: speed, design and content model
  • Audit and consolidate apps
  • Upgrade to Shopify Plus for checkout extensibility, Shopify Functions and B2B features
  • Go headless for part of the site, such as content or campaign pages
  • Go fully headless
  • Go fully custom

Most brands find their answer in the first three steps. Stop as soon as the constraint that's costing you money is gone.

What Does Switching Actually Involve?

Switching involves far more than a new design: your products, customers, orders and SEO all have to move without breaking. The main stages are:

  • Protect SEO: map every URL, set up 301 redirects, and carry over metadata and structured data
  • Migrate data: products, customers and order history. Subscriptions are the hardest part, because live billing agreements can't be allowed to fail
  • Choose a launch approach: run both sites in parallel, or plan a hard cutover in a low-traffic window
  • Rebuild what apps did: reviews, loyalty, upsells and email triggers
  • Plan post-launch support: someone must own fixes, monitoring and updates from day one

For the full process, see our guide on how to migrate your store without losing SEO rankings, customer accounts or sales.

FAQs

Headless means separating what customers see from the engine that runs the store. Shopify still handles products, stock and checkout, while developers build a custom front end that pulls data through APIs.

Final Thoughts

Most brands should stay on Shopify longer than they think. Headless is a powerful middle path when the storefront is the bottleneck. A fully custom build is justified only when the business model itself can't fit.

So don't ask which platform is better. Ask which specific constraints are costing you money right now, and what the cheapest reliable way to remove them is.

If you're not sure whether your problem is the platform, the theme or the process, our ecommerce development team can review your store and tell you honestly whether to fix, upgrade or rebuild. Get in touch with Cyber Ghost Solutions for a platform fit review.

Sources

Shopify Performance: Liquid vs headless, a look at real user web performance

web.dev: Milliseconds Make Millions (Deloitte and 55 for Google)

WP Engine: The State of Headless 2021

Shopify Plus pricing

Shopify.dev: Hydrogen and Oxygen fundamentals

Turn the reading into results

Tell us where you are and we will show you the shortest path to more leads — free, in writing, within 48 hours.