If you run an online store on Shopify, you may have heard the term "headless" from a developer or another store owner. It describes a different way of building the shop your customers see, while keeping Shopify behind it. For the right store it can mean a faster, more distinctive storefront. For many others, a well-built Shopify theme is the better choice.

We build both, so this guide is meant to help you tell which one fits your store.

What "headless Shopify" actually means

A standard Shopify store uses a theme. Shopify stores your products, runs checkout and also generates every page your customers see from that theme.

A headless store splits those jobs. Shopify keeps doing what it does well: products, inventory, orders, customers, payments and checkout. The storefront, meaning the pages customers browse, is built separately, in our case with Next.js. The storefront reads products and collections from Shopify through its Storefront API, and when a customer is ready to pay, they are sent to Shopify's checkout.

For your team, very little changes day to day. Products, prices, stock and orders are still managed in the Shopify admin you already know.

What stays with Shopify

It is worth being clear about this, because it is where most of the risk is handled:

  • Checkout and payments stay on Shopify's hosted checkout, so card handling and payment security remain Shopify's responsibility.
  • Orders, fulfilment and customer accounts stay in Shopify.
  • Your Shopify plan continues as before. Headless is not a way to stop paying for Shopify.

Why stores go headless

The common reasons are:

  • Speed. A Next.js storefront only loads the code each page needs, renders pages ahead of time where it can, and optimizes images automatically. Themes with many apps installed often load scripts on every page whether they are used or not.
  • Design freedom. The storefront is not limited by a theme's structure, which matters for brands whose story and presentation are part of what they sell.
  • Content alongside products. Guides, lookbooks, recipes and editorial content can come from a content management system and sit naturally next to products, instead of being squeezed into a blog template.
  • Several storefronts, one back end. Different sites for different brands, regions or wholesale customers can all draw on the same Shopify catalogue.
  • Connecting other systems. Product data, reviews, loyalty or your own APIs can be combined in the storefront in ways a theme makes awkward.

The trade-offs

Headless is not free of costs, and it is worth knowing them before you decide:

  • A higher build cost. A custom storefront is more work than configuring a theme.
  • Some apps will not work as they are. Many Shopify apps add features by inserting code into the theme. On a headless storefront those features have to be connected through an API or rebuilt, and some apps do not offer a headless option at all.
  • More to maintain. You now have a storefront application as well as a Shopify store, and both need looking after.
  • SEO details become your responsibility. Product page structure, structured data, sitemaps and redirects are built into the storefront rather than handled by the theme. Done well, that gives you more control. Done carelessly, it can cost you search traffic.
  • Theme editing goes away. Your team will not rearrange pages in Shopify's theme editor. Content changes go through the CMS instead, and new layouts go through a developer.

When a theme is the better choice

A well-built, well-optimized Shopify theme is the right answer for many stores, especially when:

  • The catalogue is small or medium and a theme presents it well
  • The store relies on several apps that depend on the theme
  • Your team likes changing layouts themselves in the theme editor
  • Budget is better spent on products, photography or marketing right now

A slow theme can often be made much faster without going headless, by removing unused apps, compressing images and cleaning up scripts. That is usually the first thing we look at.

When headless is worth considering

It tends to make sense when:

  • Speed problems persist after the theme has been optimized
  • Your brand needs a storefront a theme cannot deliver
  • Content is a large part of how you sell
  • You run, or plan to run, more than one storefront
  • The store needs to work closely with other systems or your own APIs

Hydrogen or Next.js?

Shopify also offers its own framework for headless storefronts, called Hydrogen, with its own hosting. It is a reasonable option, especially for stores that want to stay entirely within Shopify's ecosystem. We build headless storefronts on Next.js, which is the same framework we use for every website we build, and which works well when the storefront also needs to bring in content or data from outside Shopify.

Moving an existing store

If you already have a Shopify store with traffic, a move to headless needs the same care as any migration: keep product and collection URLs where you can, map and redirect anything that changes, carry over titles, descriptions and structured data, and test checkout end to end before launch.

Where we come in

Velora builds Shopify stores on themes and headless storefronts on Next.js, and works on existing stores to fix speed and checkout problems. If you are wondering whether headless makes sense for your store, tell us what you sell, how you sell it and what is frustrating you about the current site. We will tell you honestly whether a theme, an optimized theme or a headless build is the better fit.