"Headless" means: Shopify stays catalog, cart and checkout, but everything your customers see comes from code of your own. No Liquid theme, but a frontend on Next.js that talks to Shopify through the Storefront API.
That isn't automatically better. For most stores, a well-built theme is the cheaper answer: it stays close to Shopify, the team keeps editing content in the theme editor, and updates stay predictable. If all your theme needs is a cleanup, you don't need headless. There's a separate article on that. This one shows when the other route pays off.
With a theme
- ShopifyCatalog, cart, checkout
- Liquid theme and appsEvery app brings its own scripts
- Visitors
What the store can do is decided by the theme and the app store.
Headless
- ShopifyCatalog, cart, checkout
- Your own frontend on Next.jsVia the Storefront API, your own code
- Visitors
Shopify remains the half that sells. What visitors see belongs to you.
When headless Shopify is the right choice
A frontend of your own pays off when the store is part of the product and a theme can no longer express that. Three signs:
- The brand needs features no theme offers. At whyraw, a maker of cameras that deliberately do less, that was the cam booth: visitors become the camera themselves in the browser, with live view, a shutter and the brand's look. Add to that a gallery of unedited shots and a countdown on products that aren't released yet, which unlocks itself at the right moment.
- Load time is part of the brand promise. Without third-party app scripts, the site stays fast. whyraw scores 100 out of 100 in the Ahrefs site audit.
- The frontend should belong to the company. Code, infrastructure and access sit with the client, not with a theme vendor.
The whyraw home page: the first button leads into the cam booth, not into the shop.
If none of the three signs sounds familiar, a lean theme is almost always the better route. How many third-party scripts your store loads today is shown by the Shopify-Check: enter your store address, first results in seconds.
What Shopify keeps doing
Everything that carries a store day to day stays with Shopify: catalog, cart, discounts, checkout, payment. The team keeps managing products and prices in the Shopify admin. The frontend queries that data through typed GraphQL and displays it. At whyraw, we added a two-step withdrawal without login, cookie settings through Shopify's own dialog and bot protection on the forms.
What a frontend of your own also needs
Headless shifts responsibility. Whatever the theme would otherwise bring along, the frontend has to handle itself:
| Task | With a theme | Headless, using whyraw as the example |
|---|---|---|
| Error cases | Handled by Shopify | The store tells "nothing in the cart" apart from "Shopify isn't answering right now". A test suite runs it against an unreachable Shopify address. |
| Findability | Shopify provides the sitemap and product data | Sitemap, structured data and a machine-readable product overview for search engines and AI assistants |
| Tracking parameters | Stay in the store | Click parameters from ads and price portals are passed through to checkout |
| Page content | In the theme editor | In code or in a connected CMS, decided up front |
| Operations | Hosted by Shopify | Hosting, monitoring and deployments are part of the handover, not an afterthought |
How long it takes
At whyraw: five days from the first storefront commit to go-live, including cart, checkout and legal texts.
- Storefront API connected for products and cart
- Out-of-cam gallery, FAQ and branding
- Cam booth, iOS PWA, legal pages
- Cart hardened, Playwright tests, live
From the project's Git history, summarized per working day.
Five days aren't a promise for every store. They show what's possible when the scope is clear and the person who decides is at the table. The full build is in the reference whyraw: a headless Shopify storefront that feels like the camera.
Frequently asked questions
What is headless Shopify?
Shopify keeps managing products, cart, checkout and payment. The pages visitors see don't come from a Liquid theme but from a frontend of your own, for example on Next.js, that talks to Shopify through the Storefront API.
Is headless worth it for every Shopify store?
No. For most stores, a lean theme is cheaper and easier to maintain. Headless pays off when the brand needs features no theme offers, or when the frontend is part of the product.
Can my team keep managing products in Shopify?
Yes. Products, prices, discounts and orders stay in the Shopify admin. What changes is page content outside the catalog: it lives in code or in a connected CMS. We settle that before the build.
How long does a headless Shopify store take?
That depends on the scope. whyraw was live five days after the first storefront commit, including cart, checkout and legal texts. That's evidence, not a promise for every store.
