"Should we go headless?" comes up in a lot of our calls. Headless Shopify — using Shopify for products, cart and checkout while a separate frontend built in something like Hydrogen or Next.js handles the storefront — can be powerful. It can also be an expensive answer to a problem a good Liquid theme would solve.
What a Liquid theme gives you
- The theme editor. Your team can build pages, reorder sections and launch campaigns without a developer.
- App compatibility. Most Shopify apps are built to plug into themes through app blocks.
- Hosting included. Shopify serves the storefront on its global CDN at no extra cost.
- Lower running costs. One platform, one bill, fewer moving parts.
What headless gives you
- Complete frontend freedom. Any layout, any interaction, any framework.
- Multiple frontends. One Shopify backend feeding a website, a mobile app and in-store screens.
- Content from anywhere. Combine Shopify products with a separate CMS or your own data.
The costs that come with it
With headless, you're running a software product, not a theme. Many apps need custom integration or won't work at all. Marketing teams often lose the drag-and-drop editing they're used to unless a CMS is added. Hosting, monitoring and ongoing development become your responsibility, and every Shopify feature you want on the storefront has to be built rather than switched on.
A simple way to decide
Stay with Liquid if your main goals are a beautiful, fast, unique store that your team can manage — modern Online Store 2.0 themes handle that very well. Consider headless when you genuinely need multiple frontends, deep integration with a non-Shopify system on the storefront itself, or an experience the theme architecture can't support, and you have the budget for ongoing engineering.
Our honest take
For most brands we work with, a well-built custom Liquid theme delivers the speed and design they were hoping headless would bring, at a fraction of the long-term cost. When headless really is the right call, we'll say so and plan for it properly.
Comments 0
Loading comments…