When Shopify Headless Makes Sense — And When It Doesn't

Shopify Headless: A Practical Guide to When It Delivers Real ROI — and When It’s Overkill

·Matija Žiberna·
When Shopify Headless Makes Sense — And When It Doesn't

The headless commerce movement has gained significant momentum, with developers and brands rushing to adopt "modern" architectures that promise better performance, design freedom, and future-proofing. Shopify, the e-commerce platform powering over 4 million stores, has embraced this trend with its Hydrogen framework and headless capabilities.

But here's the thing: the headless hype often overshadows the reality. While headless Shopify can deliver remarkable results for the right use cases, it's not universally superior — and the data proves it.

The Performance Reality Check

Shopify Liquid Outperforms Most Headless Implementations

Contrary to popular belief, Shopify's Liquid themes actually outperform most headless implementations when it comes to Core Web Vitals. According to Shopify's own performance analysis, 59.5% of Shopify Liquid sites pass all Core Web Vitals as of September 2023, a percentage that continues to climb.

Even more surprising: Liquid outperforms most Server-Side Rendering (SSR) frameworks that power headless setups. Of the common headless e-commerce frameworks, only Hydrogen — Shopify's own headless solution — comes close to matching Liquid's performance.

This gap became even more pronounced in 2024 when Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital. The performance differences are now more stark, with Liquid maintaining its lead over typical headless implementations.

Why This Matters

These aren't just vanity metrics. Core Web Vitals directly impact search rankings, conversion rates, and user experience. If you're considering headless primarily for performance gains, you might be solving the wrong problem.

When Shopify Headless Actually Makes Sense

Despite the performance reality, headless Shopify has clear advantages in specific scenarios:

1. Complex Frontend Requirements

Barefoot Dreams, a luxury bedding brand, achieved a 64% improvement in conversion rate after going headless with Nacelle. Their success came from implementing complex product quizzes, personalization engines, and multi-step product configurators — features that would be challenging to build in Liquid themes.

Similarly, ILIA Beauty improved their developer velocity and deployment speed using Shopify Plus with Nacelle and Vercel, enabling faster local development and git-based deployments that their team couldn't achieve with traditional themes.

2. Visual CMS Integration Needs

A leading luxury jewelry brand faced content management challenges with their existing Shopify setup. By implementing a headless architecture with Shopify Plus, Sanity CMS, and Next.js, they achieved:

  • Dramatic improvements in website load speed across all pages
  • Streamlined content management for their marketing team
  • 65% reduction in carbon footprint through optimized architecture
  • Enhanced accessibility meeting WCAG 2.2 standards

3. Multi-Brand or Multi-Regional Operations

Functional Nutrition used headless Shopify to support multiple currencies, languages, and payment methods when expanding from the UK to the Netherlands. The flexibility of a headless frontend made it possible to create region-specific experiences while maintaining a unified backend.

4. Advanced Interactive Features

Headless excels when you need:

  • Multi-step product configurators
  • Real-time inventory across multiple locations
  • Complex bundling and subscription logic
  • Embedded single-page applications for loyalty programs
  • Custom checkout flows beyond Shopify's standard options

When Headless Doesn't Make Sense

1. Simple Catalog Operations

If your primary needs are straightforward product display, basic filtering, and standard checkout flows, Liquid themes often provide better performance with significantly less complexity.

2. Limited Development Resources

Going headless means managing hosting, caching, CDNs, deployment pipelines, and potentially a separate CMS. This operational overhead requires dedicated development resources that many teams don't have.

3. Budget Constraints

Headless implementations typically cost $20,000-$100,000 depending on complexity, compared to $2,000-$10,000 for custom Liquid themes. The ongoing maintenance costs are also higher.

The API Rate Limit Reality

One common concern about Shopify is API rate limiting. Here's the current reality:

Current Limits (2024)

When Limits Matter

Admin API limits primarily affect backend integrations, bulk operations, and ERP synchronization. For customer-facing operations, the unlimited Storefront API means headless implementations can handle massive traffic spikes without throttling.

Brands with high-volume backend operations can work with Shopify's support team to create private apps with custom rate limits up to 200 requests per second.

Backend Limitations and Alternative Platforms

When Shopify's Backend Becomes the Bottleneck

Wild Fork Foods, a direct-to-consumer meat retailer, migrated from Shopify to CommerceTools due to fundamental limitations in handling variable weight products. Shopify's pricing structure couldn't accommodate their need for dynamic pricing based on actual product weight at checkout.

Current Shopify limitations include:

  • B2B operations: Limited to 500 items per order, 25 company locations
  • Multi-currency complexity: Struggles with complex multi-regional tax and pricing logic
  • Customization constraints: Liquid scripting makes deep backend customization difficult
  • Vendor lock-in: Proprietary language makes migration challenging

The Reverse Migration Story

However, migration stories go both directions. PAIGE, the American fashion brand, moved from CommerceTools to Shopify Plus due to complexity issues. They found CommerceTools' flexibility came with significant technical challenges, high maintenance costs, and poor international customer experience.

Universal Music and Coeur de Lion also migrated from CommerceTools to Shopify, citing the reality that building with CommerceTools was more time-consuming and costly than anticipated.

Visual CMS Integration: The Sweet Spot

This is where headless Shopify often shines. Leading brands successfully combine Shopify's e-commerce backend with powerful content management systems:

Top Visual CMS Options

Sanity CMS: Shopify has invested in Sanity and developed tight integration through "Sanity Connect." Changes to your Shopify product catalog instantly reflect in Sanity Studio, where you can enrich products with additional content. Starting at $99/month, it's ideal for content that changes frequently.

Storyblok: The only headless CMS with a visual editor that's native to Hydrogen. Starting at $12/month, it's designed for non-technical users who need real-time content previews. Bols Spirits uses Storyblok with Shopify to let their marketing team create and ship content-rich campaigns without developer involvement.

Builder.io: Perfect for teams where non-technical members need to create landing pages and promotional content quickly. The drag-and-drop interface removes developer bottlenecks for marketing campaigns.

Contentful: The reliable choice for proven stability and well-documented integrations. It handles product stories, blog content, and landing pages while connecting seamlessly to Shopify.

Making the Decision

Here's a practical framework for choosing your approach:

Use CaseStay LiquidGo Headless ShopifyConsider Alternatives
Simple product catalog
Standard B2C operations
Complex UX requirements
Heavy content marketing
Advanced B2B workflows
Multi-tier marketplaces
Variable/complex pricing

Questions to Ask Yourself

  1. Do you need features that Liquid themes can't provide? If not, stick with Liquid for better performance and lower complexity.

  2. Do you have the development resources? Headless requires ongoing maintenance of frontend infrastructure, deployment pipelines, and potentially a separate CMS.

  3. Are Shopify's backend limitations blocking your business model? If you need complex B2B workflows, marketplace functionality, or highly custom pricing logic, consider CommerceTools, Saleor, or other composable platforms.

  4. What's your budget for ongoing maintenance? Headless isn't just more expensive to build — it's more expensive to maintain.

The Bottom Line

Shopify headless isn't a default upgrade path. It's a strategic choice that makes sense when:

  • Your frontend requirements exceed what Liquid themes can deliver
  • You need tight integration with a visual CMS for content marketing
  • Your team has the resources to maintain custom frontend infrastructure
  • The benefits justify the increased complexity and cost

The data shows that for many use cases, well-optimized Liquid themes deliver better performance with significantly lower complexity. But for brands with specific requirements around design flexibility, content management, or advanced user experiences, headless Shopify provides a compelling path forward.

The key is being honest about your actual needs versus the theoretical benefits of "modern" architecture. Sometimes the best solution is the one that works reliably with minimal overhead.


Need Help Deciding?

If you're evaluating headless Shopify for your brand, I can help you make the right decision based on your specific requirements and constraints. I specialize in helping brands navigate the headless transition — whether that means moving forward with a headless implementation or optimizing your existing Liquid setup.

Contact me at matija@buildwithmatija.com to discuss your project and get expert guidance on the best path forward for your business.

3

Frequently Asked Questions

Enjoyed this article?
Subscribe to my newsletter for more insights and tutorials.
Matija Žiberna
Matija Žiberna
Full-stack developer, co-founder

I'm Matija Žiberna, a self-taught full-stack developer and co-founder passionate about building products, writing clean code, and figuring out how to turn ideas into businesses. I write about web development with Next.js, lessons from entrepreneurship, and the journey of learning by doing. My goal is to provide value through code—whether it's through tools, content, or real-world software.

You might be interested in