Google once paid Deloitte to measure something most store owners only guess at: what a tiny bit of extra speed is worth. The answer was surprisingly concrete. On retail sites, a 0.1-second gain in mobile load speed came with an 8.4% jump in conversions. That stat is a big part of why headless Shopify gets pitched so often, sometimes to stores that don’t need it.
Speed alone doesn’t decide this, though. A lean Shopify theme can be very fast. A headless build done in a hurry can crawl, and it can run months past its deadline, too. What tips the scale is less exciting. It’s how much content a brand makes, who’ll look after the code, and what the storefront itself has to do.
Below is a plain look at both setups, the costs people tend to forget, and five questions worth asking before anyone writes a brief.
Same Engine, Different Body: What Actually Changes?
Both options sit on top of the same Shopify admin. Orders, products, stock, payments, and checkout don’t move. What changes is the storefront, the part a shopper actually scrolls through.
Traditional Shopify: The Theme Does the Talking
Here the storefront is a theme written in Liquid, Shopify’s template language. A lot of stores begin on Dawn, the free default, and later move to a paid theme from the Theme Store. Online Store 2.0 gave themes a lot more room to move. Sections now work on every page, and apps can drop blocks right into the editor, so a marketer can add a reviews strip or reorder the homepage on a Tuesday morning without filing a ticket.
The limits show up at the edges. Odd layouts, deep custom logic, or a page that acts more like an app can get awkward inside a theme. Devs can work around a lot. Just not everything.
Headless Shopify: The Front End Moves Out
Going headless means the storefront is built as its own app. It talks to Shopify through the Storefront API and draws pages any way the team likes. Hydrogen, Shopify’s own React toolkit, is the usual pick now. Some agencies still like Next.js on Vercel. Content often ends up in a headless CMS like Sanity, Contentful, or Storyblok.
Headless Shopify development lets a brand build features a theme can’t handle, such as interactive product pages or one catalog that feeds both a website and a mobile app. Hosting is simpler than it used to be, too. Shopify’s Oxygen platform runs Hydrogen storefronts, and it’s included at no extra charge on paid plans.
Where Traditional Shopify Still Shines
Themes get a bad rap in some agency pitches. It isn’t really deserved.
A tidy Liquid store with compressed images, a short app list and lazy-loaded video can pass Core Web Vitals comfortably. Plenty do. The usual reason a theme store feels slow is app bloat, not Liquid.
Launch time is the other obvious plus. A theme store can go from kickoff to live in a few weeks, and once it’s up, most changes are editor work. Swapping a homepage banner for a weekend promo takes minutes, and nobody has to deploy anything.
Apps plug in fast, too. Klaviyo, Judge.me, and Recharge all have theme app add-ons, so setup is mostly a screen or two of clicks. Shopify handles hosting, SSL, uptime, and checkout updates. That means one good freelancer can often keep a mid-sized store running.
Theme setups usually make the most sense for stores with:
- standard product and collection pages, even across a few thousand SKUs
- no full-time front-end developer on staff
- no plans for a native app or other custom-built front ends
The Case for Going Headless (and the Bill That Comes With It)
Headless isn’t hype. It does solve real problems, just not cheap ones.
What Brands Gain
Mostly, it’s freedom on the front end. Story pages, product builders, quizzes, 3D viewers: none of it has to squeeze into a theme’s sections. Lady Gaga’s team used Hydrogen to fold a separate content site and its US store into a single site. Good American, the denim and fashion label, also runs its storefront on Hydrogen.
Custom touchpoints are another reason. The same product data can power the website, an iOS app, a kiosk in a flagship store. Speed may improve as well, since Hydrogen renders at the edge and can split code per page. May. A poorly built headless store can easily load slower than a well-kept theme, and that happens more often than vendors admit.
What It Really Costs
Hydrogen costs nothing to download. Building with it is another story.
Agency quotes for headless builds often run several times higher than a theme job. And the spend keeps going after launch. Shopify puts out a new Storefront API version every quarter, named by date (2025-01, 2025-04 and so on). Old ones lose support in time. So someone has to keep the code up to date. Apps are a sore spot. Many that take one click on a theme need custom work on headless. A few just don’t support it. Marketers can also lose the visual editor unless the CMS is set up carefully from the start.
And then there’s staffing. A headless store with no React developer around tends to age badly: small bugs pile up, API upgrades slip, and six months in, the team is nervous about touching anything.
Side by Side: A Quick Comparison
For a quick scan, here’s how the two compare on the points that matter most.
| Factor | Traditional Shopify | Headless Shopify |
| Time to launch | Weeks | Several months |
| Upfront cost | Lower | Much higher |
| Upkeep | Mostly handled by Shopify | Needs steady developer time |
| Design freedom | Shaped by the theme | Nearly unlimited |
| App support | Wide, often one click | Partial, often custom work |
| Content editing | Built-in visual editor | Depends on the CMS |
| Sales channels | Web first | Built for many channels |
| Custom front ends (apps, kiosks) | Limited to the theme storefront | Built for it |
| Marketplace selling | Supported via integrations | Supported via integrations |
Five Questions That Settle the Decision
Vendor demos make both options look great. These questions are more useful, because they’re about the store rather than the tech.
1. Is the Theme Really the Problem?
Run PageSpeed Insights or Lighthouse first. In a lot of slow stores, the report points at third-party scripts, an autoplaying hero video, or apps that were removed but left code behind. Fixing those is cheap. If the store still hits real limits after a cleanup, then a rebuild talk makes sense.
2. How Much Content Does the Brand Publish?
A beauty brand that posts weekly how-to videos and ingredient guides has different needs from a parts shop with 4,000 SKUs and two-line blurbs. The first may well outgrow Shopify’s blog templates. The second probably never will.
3. Who Will Look After It?
Ask who fixes a broken cart at 9 p.m. on Black Friday. If nobody can answer with a name, headless is risky. It works best with an in-house front-end dev or an agency on a long retainer.
It’s not only about emergencies, either. Someone also has to ship small changes each week, test new app versions, and keep an eye on load times. On a theme, a lot of that is light work. On headless, it’s a real job.
4. How Many Channels Are on the Roadmap?
Marketplaces aren’t a reason to go headless on their own, since Amazon, eBay, Walmart, and TikTok Shop connect to either setup through integration tools. The real question is about touchpoints the brand designs and builds itself. One website? A split setup is overkill. A native app, an in-store kiosk or a custom B2B portal planned for the next couple of years changes the math, since one API layer can feed all of them.
5. What Does Year Two Look Like?
Most budgets focus on launch. Year two is where headless projects quietly go over. Add up CMS fees, a search tool such as Algolia, monitoring, and monthly dev hours, then set that against a realistic revenue estimate (not the rosy one from the pitch deck). If it only works in the best case, that’s a no.
Is Headless Shopify Required to Sell on Many Marketplaces?
No. You can sell on Amazon, eBay, Walmart, and TikTok Shop without changing your Shopify store.
Using either traditional or headless Shopify, you connect to various marketplaces using integration tools to run your business in one place.
For instance, M2E Multichannel Connect gives you an integration tool that connects your Shopify store to over 600 marketplaces and automates daily tasks like product and inventory management, order management, and product updates.
Headless Shopify performs different functions. This option allows you to fully enjoy the design and shopping experience of your site. It also means headless Shopify doesn’t have to serve marketing purposes.
Is There a Middle Ground?
There is, and it gets skipped a lot.
Some brands keep their Liquid theme for products and collections. Then they build one or two custom pages headless, like a campaign hub or a product builder. Others stay fully on a theme and use metaobjects for richer content. Shopify has been closing the gap from its side as well; Checkout Extensibility, metaobjects and Shopify Markets now cover much of what used to justify a full rebuild.
A partial approach also lets devs get used to Hydrogen on something small before they bet the whole store on it. If the custom page lifts sales, great, there’s a case for more. If it doesn’t, the team has lost a few weeks, not a year.
Summing It Up
Headless pays off when a brand produces a lot of content, needs custom front ends such as a native app, and has developers who’ll stick around. Marketplace selling works with either setup, so it shouldn’t drive the choice. Neither one is better in general.
A sensible order: audit the current store, write down which limits actually cost sales, and then see whether a theme fix, a hybrid build or a full headless move solves them. It’s cheaper that way, and the decision tends to be clearer by the end.
