Skip to content

Comparison

Shopify vs headless commerce

A Liquid theme is the storefront Shopify renders for you. A headless storefront is one you build and host yourself on top of Shopify's APIs, with Shopify still running the catalog, checkout and orders. The theme gives you sections, apps and an editor with nothing to maintain; headless gives you any front end you can build and everything that comes with owning it.

By CartKernel · Last reviewed 2026-09-07

Ask us which fits your storeAll comparisons

Option A

Shopify (Liquid theme)

Shopify's hosted storefront, built in Liquid with Online Store 2.0 sections, JSON templates, metafields and theme app extensions, edited in the theme editor and rendered by Shopify.

Best for

  • Stores whose front end needs are met by a well-built theme and a short list of apps
  • Teams without in-house engineers who want to change pages without a deployment
  • Brands launching or relaunching quickly, with SEO plumbing generated by the platform
  • Stores that depend on apps that deliver their features through the theme

Option B

Headless storefront

A custom front end built with a framework such as Hydrogen, Next.js or Astro, fetching products, collections and carts through the Storefront API, hosted on Oxygen or infrastructure you choose, and handing off to Shopify checkout.

Best for

  • Brands with an engineering team and a front end design a theme cannot express
  • Content-rich sites that combine a headless CMS and commerce in one experience
  • Businesses serving several brands or regions from one Shopify backend with distinct sites
  • Stores with specific performance, personalization or architecture requirements

Side by side

Shopify (Liquid theme) and Headless storefront, criterion by criterion

CriterionShopify (Liquid theme)Headless storefront
Who renders the pageShopify, from the themeYour framework, on Oxygen or your own hosting
Editing contentTheme editor, sections, metafields and metaobjectsA CMS you connect, plus Shopify data through the API
CheckoutShopify checkout, integratedShopify checkout, reached from your cart through the API
AppsTheme app extensions and app blocks work directlyOnly apps with APIs or SDKs; the rest are rebuilt or dropped
SEO plumbingSitemap, canonicals, robots and Markets hreflang generatedMetadata, sitemaps, redirects and rendering built and maintained by you
PerformanceGood by default; theme and app weight decide the restCan be excellent; depends entirely on the build
Time to launchTypically weeks with a themeTypically months, with engineering afterward
Ongoing maintenanceTheme updates and app hygieneDependencies, hosting, API versions and framework upgrades

What the theme gives you that headless makes you build

A Shopify theme arrives with a great deal already done. The sitemap, canonical tags, robots rules, hreflang for Markets, image resizing, the cart, customer accounts, search and the connection to every app that uses theme app extensions all exist the day the store opens. Merchants change layouts in the editor, and a developer changes templates without touching infrastructure.

Headless starts from an empty repository. Each of those pieces becomes a decision and then a task: how pages render, how metadata is generated, where redirects live, how the cart persists, how search works, and which apps can stay because they expose an API. Hydrogen and Oxygen shorten the path for a React team by handling hosting and the API connection, but the storefront is still software the business owns.

When a theme stops being enough

The reasons are concrete. A design that needs interactions a theme cannot express well. A content operation that lives in a headless CMS and needs product data woven through it. Several brands or regions that share a Shopify backend but need visibly different sites. A performance budget a theme with the required apps cannot meet. A team that already builds and deploys web applications and wants the storefront in that workflow.

If none of those apply, the theme is the better tool. Most stores that outgrow their theme are really outgrowing a heavy theme and a long app list, which a rebuilt theme fixes for a fraction of the effort. Headless suits a store that has hit a real ceiling and has the people to own the result.

Headless and SEO: the parts that are easy to miss

A headless storefront is only as visible as its rendering. Pages must be server-rendered or pre-rendered so crawlers and AI systems receive full HTML with product data, prices and structured markup, not an empty shell waiting for JavaScript. Hydrogen renders on the server by default; other frameworks need that set up and kept.

The generated pieces need rebuilding too: XML sitemaps that update with the catalog, canonical tags on variant and filtered URLs, redirects from every old theme URL, hreflang across markets, and 404 handling that returns a real 404. Product feeds keep working from the Shopify catalog, but the landing URLs must match the new storefront. Done without this list, a headless build loses rankings the theme had earned.

The honest bottom line

Stay with a Liquid theme unless there is a specific, named requirement it cannot meet, because it delivers the storefront, the SEO plumbing and the app ecosystem with the least to maintain. Choose headless when the business has an engineering team, a front end vision or content architecture the theme cannot express, or several sites on one backend, and is ready to own rendering, SEO infrastructure and integrations for as long as the site exists.

Get a Growth Analysis

We will tell you which fits, with your numbers.

Questions

Asked when choosing

By CartKernel · Last reviewed

Does going headless mean leaving Shopify checkout?

No. A headless storefront builds the cart through the Storefront API and sends the shopper to Shopify's hosted checkout, so payments, Shop Pay, discounts, shipping rules and order management stay where they are. The custom front end covers browsing and the cart; Shopify covers the transaction.

Is a headless storefront automatically faster than a theme?

No. Headless can be very fast because the team controls every byte, and it can be slow if the build loads heavy client-side JavaScript or renders in the browser. A lean theme with few apps often outperforms a careless headless build, so performance should be a stated goal of the project rather than an assumed outcome.

Can a store go headless for only part of the site?

Yes. A common pattern keeps the product catalog on the theme and runs an editorial or campaign site on a separate framework that links into it, or the reverse. Shopify's storefront components and the Storefront API also let a store embed products and carts in pages served elsewhere, a smaller step than rebuilding the whole storefront.

What happens to apps when a store goes headless?

Apps that work through theme app extensions or Liquid stop rendering, because there is no theme. Apps with an API or SDK, such as many review, search, subscription and analytics tools, can be integrated into the new front end. Before committing, list every installed app and mark which have a headless path, which need replacing and which the store can drop.

Services involved

Build the storeShopify DevelopmentThemes, apps, Plus features and Hydrogen buildsExploreBuild the storeEcommerce DevelopmentStorefront engineering built for speed and conversionExploreGet foundEcommerce SEOCategory and product pages that rank for buying queriesExplore

More comparisons, answers and tools

All comparisons
ComparisonShopify vs Shopify PlusShopify vs Shopify Plus: what Plus adds in checkout, B2B, automation and multi-store operations, and which stores need it versus a strong standard plan.OpenComparisonShopify vs WooCommerce for SEOShopify vs WooCommerce for SEO: URL control, speed and hosting, content tooling, and which platform fits which catalog, team and growth plan.OpenComparisonShopify vs BigCommerce for SEOShopify vs BigCommerce for SEO: URL flexibility, built-in tooling versus apps, multi-storefront options, and which hosted platform fits which catalog.OpenAnswerHow long does a headless commerce build take?A headless commerce build usually runs three to nine months. What drives the range, the work a theme build does not have, and the ongoing cost after launch.OpenAnswerDo you need a developer for a Shopify store?You do not need a developer to launch a Shopify store. What you can do with theme settings and apps, and the work that genuinely requires code.OpenAnswerDoes site speed affect ecommerce rankings?Site speed is a small ranking factor and a large conversion factor. What Google measures, where store templates lose time, and how to prioritise fixes.OpenAnswerHow many apps are too many on a Shopify store?There is no app limit on Shopify. The real cost is scripts, cost and conflicts. How to audit what you have and decide what earns its place.OpenHeadless ShopifyHydrogenHydrogen for ecommerce stores: a headless Shopify storefront on the Storefront API, with editable content, tracking rebuilt and an honest case for going custom.OpenStorefront frameworkAstroAstro for ecommerce stores: content and programmatic pages that ship almost no JavaScript, built as data and templates and served on one domain with the store.OpenEdge and performanceCloudflareCloudflare for ecommerce stores: DNS and redirects handled properly, content and headless builds hosted at the edge, forms and crawlers managed on purpose.Open

Find the leak.

A free Growth Analysis ranks what your store should fix first, by revenue at stake.

Get a Growth Analysis