Headless Shopify and Hydrogen: when it is justified
Headless commerce means running your own storefront against Shopify's APIs instead of using a Liquid theme. Hydrogen is Shopify's framework for doing that.
The technology works. The question is whether the store you are building needs it, because the cost is not the build — it is the decade of maintenance that follows.
What you gain and what you take on#
| Liquid theme | Headless | |
|---|---|---|
| Storefront control | Within theme structure | Total |
| Hosting | Shopify | Yours to run |
| Time to launch | Weeks | Months |
| Platform updates | Mostly automatic | Your dependency upgrades |
| Theme editor for merchants | Full | Whatever you build |
| Team needed | Shopify developer | Front-end team, ongoing |
Good reasons to go headless#
- The storefront must integrate deeply with a non-Shopify experience — a configurator, a booking system, an existing app.
- Content and commerce are equally important and live in a separate system already.
- You have a front-end team who will still be here in three years.
- Performance requirements the theme layer genuinely cannot meet, measured rather than assumed.
Bad reasons#
"Themes are limiting" usually means the theme was chosen badly or customised into a corner. "Headless is faster" is true only if you build it well; a poorly built headless storefront is slower than a good theme, and there is nobody but you to fix it.
Measure the current theme before concluding the theme is the problem. In most audits the problem is apps and images, and both survive a headless rebuild.
The part people forget#
You lose the theme editor. Merchants who could reorder a page now file a ticket. Rebuilding a merchant editing experience is real work, and skipping it moves the cost from your team to theirs, permanently.
Frequently asked questions
Is Hydrogen required for headless?
No, but it is the best-supported path and removes a lot of undifferentiated work if you are going headless anyway.
Does headless improve SEO?
Only through speed and structure you would have to build correctly. It also introduces ways to get rendering wrong that a theme cannot.
Can we go headless later?
Yes. Keeping product data clean and content in metaobjects makes that migration much cheaper.
headless shopifyshopify hydrogenheadless commerceshopify storefront apihydrogen vs liquid
