--- title: "Headless Shopify with Next.js: When It's Worth It" description: "Headless Shopify with Next.js: when a custom storefront pays off, when a theme is enough, and how whyraw went live in five days. With build log." canonical_url: "https://preview.kevinludwig.com/en/blog/headless-shopify-nextjs-when-worth-it" last_updated: "2026-10-13" --- [Blog](https://preview.kevinludwig.com/en/blog) # Headless Shopify with Next.js: When It's Worth It and When It Isn't A frontend of your own in front of Shopify sounds like more work than a theme. For most stores, it is. At whyraw it was the right call: live after five days, without third-party app scripts, with features no theme offers. How to tell which route fits your store. [Kevin Ludwig](https://preview.kevinludwig.com/en/team/kevin-ludwig) 13 Oct 2026 , 4 min read [Auf Deutsch lesen](https://preview.kevinludwig.com/de/blog/headless-shopify-nextjs-wann-lohnt-es-sich) Contents 1. When headless Shopify is the right choice 2. What Shopify keeps doing 3. What a frontend of your own also needs 4. How long it takes 5. Frequently asked questions "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](https://preview.kevinludwig.com/en/blog/replace-shopify-apps-theme) on that. This one shows when the other route pays off. What changes and what stays With a theme 1. Shopify Catalog, cart, checkout 2. Liquid theme and apps Every app brings its own scripts 3. Visitors What the store can do is decided by the theme and the app store. Headless 1. Shopify Catalog, cart, checkout 2. Your own frontend on Next.js Via the Storefront API, your own code 3. 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. ![Home page of whyraw.de: handwritten logo on a dark background, below it the buttons to try the cam and to go to the shop](https://preview.kevinludwig.com/images/work/whyraw.webp) 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](https://preview.kevinludwig.com/en/leistungen/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. whyraw build log: from first commit to live 1. 14 May 2026 Storefront API connected for products and cart 2. 15 May 2026 Out-of-cam gallery, FAQ and branding 3. 18 May 2026 Cam booth, iOS PWA, legal pages 4. 19 May 2026 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](https://preview.kevinludwig.com/en/referenzen/whyraw-headless-shopify-storefront). ## 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. ## How we go about it We look at your store, apps and data and tell you which route is cheaper, theme or headless. If the question is still open, a [10-day pilot](https://preview.kevinludwig.com/en/leistungen/pilot) answers it with a first version on your real data. If the whole stack is unclear, an [audit](https://preview.kevinludwig.com/en/leistungen/audit). [Book a first call](https://preview.kevinludwig.com/en/kontakt#termin) A first conversation takes 30 minutes. [More on Shopify development](https://preview.kevinludwig.com/en/leistungen/shopify-development) Tags: [Shopify](https://preview.kevinludwig.com/en/blog?tag=Shopify) , [Headless](https://preview.kevinludwig.com/en/blog?tag=Headless) , [Next.js](https://preview.kevinludwig.com/en/blog?tag=Next.js) , [Storefront](https://preview.kevinludwig.com/en/blog?tag=Storefront) , [E-Commerce](https://preview.kevinludwig.com/en/blog?tag=E-Commerce) , [D2C](https://preview.kevinludwig.com/en/blog?tag=D2C) Written by [Kevin Ludwig](https://preview.kevinludwig.com/en/team/kevin-ludwig) Engineering & Product Ships systems that people use every day: web apps, internal systems, AI pipelines, own products. Along the way: Porsche projects at MHP, research at Mercedes-Benz, technical lead of software development at Advanced UniByte. [View profile](https://preview.kevinludwig.com/en/team/kevin-ludwig) [LinkedIn](https://www.linkedin.com/in/kev-ludwig/) ## Related - Reference ### [whyraw: a headless Shopify storefront that feels like the camera](https://preview.kevinludwig.com/en/referenzen/whyraw-headless-shopify-storefront) 5 days from start of build to live - Service: Shopify ### [Shopify stores that load fast and don't depend on a pile of apps.](https://preview.kevinludwig.com/en/leistungen/shopify-development) [All articles](https://preview.kevinludwig.com/en/blog) ## What are you working on? 30 minutes on video with Kevin Ludwig, free of charge. You describe what you have in mind; afterwards you know whether it fits and which entry point is right. > “You can simply rely on him.” Judith Hickel, Gloria Kollektiv e.V. 5.0 from 8 Google reviews As of October 6, 2026. We don't verify whether reviews come from clients. [Book a first call](https://preview.kevinludwig.com/en/kontakt#termin) [Or write to us, one sentence is enough.](https://preview.kevinludwig.com/en/kontakt#anliegen) On working days we usually reply within 24 hours.