Headless Shopify · developer

Headless Shopify, built on Next.js or Hydrogen.

Independent headless Shopify developer building on Next.js (App Router), Hydrogen on Oxygen, or Remix. Most stores don't need headless — when yours actually does, this is the build that gets it right.

Book a 20-min scope call → See selected work

◆ Storefront API · Hydrogen · Next.js App Router · ISR + edge caching · Oxygen · Vercel

Why most "headless" projects fail

What goes wrong with headless Shopify.

Five reasons headless Shopify projects burn budget without shipping a faster store. The honest answer is usually "you didn't need to go headless in the first place."

01 ◆

You went headless to fix a speed problem that was actually an app problem. The native theme would have hit 1.8s LCP if you'd removed six apps. The $80K headless build got you to 2.1s and added a new operational surface.

02 ◆

Cart, checkout, customer accounts, and discount logic all moved to "the app" but Shopify's checkout still has to be reached — and routing the customer between your headless storefront and Shopify's checkout is the hardest part of the build.

03 ◆

Content editing got worse, not better. Your team can no longer use the Shopify theme editor; they have to learn Sanity, Storyblok, or Contentful. Marketing missed deadlines for two quarters.

04 ◆

You picked Hydrogen on Oxygen and now have a deployment surface only Shopify can support, with all the constraints that implies. Or you picked Next.js and have to wire up image optimization, ISR, and Storefront API caching from scratch.

05 ◆

Apps that worked on the storefront theme don't work on the headless front-end. Klaviyo onsite forms, ReCharge subscriptions, judge.me reviews, Yotpo loyalty — all need re-integration via APIs.

When I do recommend headless

When headless is the right call.

I do not push headless on stores that don't need it. The cases where it earns its keep are narrow but real.

◆ You're running a global storefront with multiple regions, languages, and currencies, and Shopify Markets isn't flexible enough.
◆ Your CMS-heavy content (editorial commerce, deep storytelling, magazine-style commerce) needs Sanity / Storyblok / Contentful as the editorial layer.
◆ You have a custom configurator (jewelry, made-to-order furniture, bespoke fashion) that needs visual feedback on every interaction — true SPA performance, not OS 2.0 sections.
◆ You need React Server Components, Suspense streaming, or partial prerendering for a level of UX polish that Liquid genuinely can't match.
◆ You want to ship native mobile apps (React Native) that share the same Storefront API + commerce logic as the web storefront.
◆ When NONE of the above apply — I'll tell you on the scope call and recommend OS 2.0 + speed work instead. Saves you $50-100K.

Packages

Two headless tracks.

Hydrogen / Oxygen

From $18,000

Delivery 8-12 weeks

Hydrogen storefront on Oxygen (Shopify-managed deploy)
Storefront API integration with proper caching
Customer accounts via the new B2B/customer account API
Klaviyo / GA4 / Meta CAPI integration
CMS integration (Sanity or Contentful) if needed
Performance: LCP under 1.5s, INP under 100ms

Get a quote →

Next.js + Vercel Most chosen

From $24,000

Delivery 10-14 weeks

Next.js App Router on Vercel
Storefront API + Admin API where needed
ISR + edge caching strategy for product/collection pages
CMS integration (Sanity / Storyblok / Contentful)
Custom configurator UX with real-time stock validation
Multi-region routing + currency switcher
Optional React Native mobile app sharing same API layer

Get a quote →

Process

How a typical project ships.

Honest scoping call

I ask hard questions about why you're considering headless. If the answer is "speed" or "branding" alone, I recommend OS 2.0 + speed work and save you a lot of money.

Architecture spec

Written architecture doc — framework choice, deployment target, CMS choice, caching strategy, customer-account flow, checkout routing, integration surface. You sign off before any code.

Build with content path live

CMS and Storefront API wired in week 1 so your content team can populate while engineering builds. Weekly demo on staging URL.

Cutover + 30-day support

Planned DNS cutover with rollback. 30 days of post-launch monitoring + iteration to land speed and tracking targets.

FAQ

Headless Shopify FAQs.

No fluff — the specifics buyers want before booking a call. If yours isn't here, ask on the call.

When is headless Shopify actually worth it?

Five clear cases: global multi-region commerce beyond what Shopify Markets handles; CMS-heavy editorial commerce that needs Sanity/Contentful as the editorial layer; complex custom configurators (jewelry, made-to-order); React-Native mobile apps sharing the same API layer; or you have a UX bar that genuinely exceeds Liquid's ceiling. The "When headless is worth it" post on the blog walks through the test.

Hydrogen on Oxygen, or Next.js on Vercel?

Hydrogen is the simpler operational story — Shopify-managed hosting (Oxygen), tight Storefront API integration, a smaller surface area to maintain. Next.js is more flexible — better for content-heavy commerce, multi-region, or stores that want to use Vercel's broader ecosystem. I recommend per-case; not a one-size answer.

Do I lose Shopify's checkout?

No — Shopify's checkout is non-negotiable. The headless storefront routes the customer to Shopify's checkout for the actual transaction, then back to a thank-you page on your headless front-end. On Plus you can extend the checkout via Checkout Extensibility; on standard you use the default. Either way, the conversion-critical step stays on Shopify's infrastructure.

Will Klaviyo / GA4 / Meta still work?

Yes, but the integration is different. Klaviyo onsite forms move to API-driven JSON; GA4 events are fired via gtag from the React layer; Meta moves to server-side CAPI. We rebuild every conversion path during the headless build and verify before cutover.

How does the Shopify theme editor still work?

It doesn't — that's the trade-off of headless. Content editing moves to your CMS (Sanity, Storyblok, Contentful) or to a custom admin we build. Your team needs training on the new tool. This is the single biggest "don't go headless" reason for most stores.

How much faster will the headless storefront actually be?

Best case (Next.js + ISR + edge caching, optimized images, lean React tree) hits sub-1.0s LCP on real devices. A native OS 2.0 theme done right hits 1.5-1.8s. So the realistic delta is 0.5-1.0s. If your current store is at 4.5s, you'll see a much bigger jump — but most of that gain comes from removing apps and refactoring code, both of which I'd do on OS 2.0 too.

Can I migrate from a headless mistake back to OS 2.0?

Yes — it happens. We rebuild the storefront on OS 2.0, decommission the headless front-end, and route all traffic back to shopify-managed Liquid. Cost depends on how much custom CMS content has to be re-modeled, but it's usually 60-70% of the original headless build cost.

Keep reading