Headless Shopify development

Headless Shopify keeps what Shopify does well (products, stock, checkout, payments) and replaces the theme with a storefront built from scratch, usually in Next.js with Sanity for content. I build and maintain headless Shopify stores for brands whose catalogue or content no longer fits a theme.

What usually goes wrong

The theme sets the limits. Lookbooks, bundles, configurable products or trade pricing turn into a pile of apps and workarounds layered on top of Liquid.

Content and commerce in separate places. Editorial content lives in a blog that isn't connected to the catalogue, so stories can't sell and products can't tell their story.

Performance that depends on apps. Each app adds scripts to every page. The store gets slower with every feature, and nobody can say which one is to blame.

Headless for the wrong reasons. Going headless adds a second system to maintain. For a small catalogue with a good theme it is often not worth it, and it is better to say so before starting.

The approach

Storefront. A Next.js storefront on the Shopify Storefront API: catalogue, search, cart and customer account, with Shopify's own checkout so payments stay where they are safest.

Content. Sanity for editorial content (collections, lookbooks, campaigns) linked to Shopify products, so editors build pages around products without touching code.

Performance. Pages rendered on the server and cached, optimised images, and no app scripts on the storefront.

Maintenance. API versions, dependencies and integrations kept up to date after launch, with monitoring so problems are caught before customers notice.

Work

Process

First conversationWhat the site has to do, who will edit it, and what has to keep working for years.
ProposalA written scope with phases, dates and the revision rounds agreed before we start.
BuildInterface and development in short iterations, with real content from the start.
LaunchAn audit before going live: performance, SEO, accessibility and code quality.
After launchMaintenance, offered by default, and a direct line to the person who built it.

Questions

When does headless Shopify make sense? When the catalogue, the content or the way you sell no longer fit a theme: complex products, trade pricing, editorial content tied to products, or several markets. If a theme covers what you need, I will tell you.

Does checkout still run on Shopify? Yes. Checkout, payments and orders stay in Shopify; the storefront hands the cart to Shopify's checkout.

Can we keep our current store and apps? Products, customers and orders stay where they are. Apps that work in the admin keep working; apps that inject code into the theme need an alternative, reviewed one by one in the proposal.

Hydrogen or Next.js? Both are valid. I work with Next.js because it lets one project combine Shopify, Sanity and other services, and it doesn't tie you to a single host.

What does maintenance include? Updates to Shopify API versions and dependencies, monitoring, performance checks and small changes, offered by default after launch.

Do I need headless, or is a theme enough? Most shops are well served by a custom native theme, which is simpler to run. Headless is worth it when content and commerce are mixed, or the shop needs things a theme can't do. See Native Shopify.

Get in touch