By Mehdi HassanShould you move a headless Shopify store back to a theme?
You should move a headless Shopify store back to a theme when the custom storefront no longer earns its upkeep: the team that built it has moved on, app features keep breaking, and every marketing change waits on a developer. If your pages are mostly products, collections and a few content pages, a modern Liquid theme will likely serve you better.
That's a contrarian view in a market that often treats headless as the grown-up choice. We think headless is the right answer for some stores and an expensive mistake for many others. Our hub on when headless Shopify is worth it sets out the thresholds. This piece is for the brands on the other side of that line, who built headless and are now paying for it.
Why do brands regret going headless?
Brands regret going headless when the build was justified by a launch moment rather than by ongoing needs. A redesign, a new funding round or an agency pitch makes headless look like progress. Two years later, the storefront needs constant care and the reasons for it have faded.
- Maintenance outran the budget. Framework updates, hosting issues and dependency changes became a permanent line item nobody planned for.
- Apps became projects. Every new review, loyalty or bundle app means custom integration work instead of a toggle in the theme editor.
- Marketing lost control. Without a well-designed CMS, launching a campaign page takes a ticket, a sprint and a deploy.
- The original team left. The developers who understood the codebase moved on, and new ones are slower and more cautious with it.
- The benefits were never measured. Nobody can show what headless earned compared with a well-built theme.
What are the signs you should go from headless Shopify to Liquid?
The clearest sign is that your headless storefront delivers nothing a modern theme couldn't, while costing developer time every month. Use this table to score your store honestly.
Question | Points to a theme | Points to staying headless |
|---|---|---|
Who maintains the front end? | Nobody full-time, or a contractor on call | An in-house or retained team that ships monthly |
How do marketers launch a page? | They file a ticket and wait | They build it in a CMS with preview |
What's on most pages? | Products, collections, standard content | Heavy editorial, configurators, mixed data |
How many storefronts? | One | Several brands, regions or channels from one codebase |
How do apps get added? | Slowly, with custom code each time | Rarely needed, or built in-house by design |
Could you list what headless earns? | Not really | Yes, with features a theme can't match |
If most of your answers land in the middle column, a theme is probably the better home. If they land on the right, the problem may be your process or CMS rather than headless itself.
What do you gain and lose by moving back to a theme?
You gain app compatibility, a visual editor for marketing and a much smaller maintenance burden; you lose full design freedom and some performance control. For most DTC stores, that's a good trade.
Pros
- Most Shopify apps work out of the box again, with theme app blocks
- Marketers edit sections, templates and campaigns in the theme editor
- Shopify handles hosting, sitemaps, canonicals and much of the SEO plumbing
- Far less ongoing developer time, and an easier hiring pool
- Shopify's own theme features arrive without integration work
Cons
- Design is bounded by sections and what Liquid makes practical
- Mixing heavy content and commerce is harder than with a headless CMS
- Less control over every script and request on the page
- Some custom features need rebuilding as theme sections or apps
- Part of the original headless investment is written off
Shopify themes have also improved a lot. Sections on every page, metaobjects for structured content and theme app extensions cover many of the needs that pushed brands to headless a few years ago. Check what a current theme can do before assuming it can't match your storefront.
How do you move from headless Shopify back to Liquid safely?
You move back by rebuilding the storefront as a theme, keeping every URL identical, and switching the domain back to Shopify once the theme passes the same checks you'd run on any migration. Because products, orders and checkout never left Shopify, the work is mostly front end and SEO.
List what the headless front end does
Inventory every template, custom feature, integration and tracking event. Decide which become theme sections, which become apps and which you drop.
Choose or build the theme
Start from a well-built theme with custom sections, or a custom theme if your brand needs it. Design for the pages that drive revenue.
Move content into Shopify
Bring editorial content from your headless CMS into Shopify pages, blogs and metaobjects, or keep a separate content site if it's large.
Keep URLs identical
If the headless store used Shopify-style paths, you're in luck. Anything custom gets a one-to-one 301 in Shopify's URL redirects.
Test, then switch the domain
Compare titles, canonicals, schema and tracking on top pages, run test orders, then point the domain back at the theme.
Hypothetical example: keeping the good parts
For example, suppose a brand built a headless storefront mainly for a rich journal and a custom product quiz. On review, the quiz is still valuable but the journal could live elsewhere. The brand moves back to a theme, rebuilds the quiz as an app embed, and moves the journal to a visual builder on its own path, linking into the store.
The result keeps the two features that mattered and drops the custom storefront that nobody had time to maintain. That hybrid is often a better landing spot than either extreme.
That hybrid model, with the store on a theme and brand or campaign pages on Framer or Webflow, is covered in our guide to Shopify marketing pages in Framer or Webflow.
When should you stay headless?
Stay headless when your storefront does something a theme genuinely can't and a team is in place to keep it healthy. Undoing headless just to cut a bill is a mistake if the custom front end is driving revenue you'd lose.
Good reasons to stay include several storefronts on one codebase, heavy editorial content tied to products, complex integrations shown live on product pages and app-like experiences. If those apply but upkeep is the issue, fix the operating model first: a clearer CMS, fewer custom dependencies, a retained team. Our headless Shopify cost guide shows what that ongoing budget looks like, and our DTC website cost guide compares it with themes.
