Stock Shopify themes are right for most brands — they ship fast (3–6 weeks) and cost less (typically 125–375 hrs at $30–$50/hour), and cover the majority of DTC needs. Headless Shopify is right when storefront speed, SEO, or editorial flexibility is differentiating — it costs more (600–1,500 hrs), takes longer (8–14 weeks), but delivers Core Web Vitals and SEO control stock themes cannot. The decision is not technical — it is a business one about whether storefront performance is part of the brand’s competitive advantage.
The framework: it is a business decision, not a technical one
The headless-versus-stock-theme question is usually presented as a technical one — APIs, rendering strategies, frameworks. It is not. It is a business question about whether storefront performance is part of your brand’s competitive advantage.
If organic traffic is a primary growth channel, if Core Web Vitals materially move conversion, or if your brand’s content strategy depends on editorial flexibility — headless pays back. If paid media drives most traffic and the catalog is straightforward — stock themes are not just adequate, they are correct.
“Going headless when you don’t need to is the most expensive mistake in modern Shopify. Staying on a stock theme when you do need headless is the second-most expensive.”
Side-by-side comparison
| Dimension | Stock theme | Custom theme | Headless Shopify |
|---|---|---|---|
| Build cost (at $40/hr) | $5k – $15k | $8k – $25k | $25k – $60k |
| Build timeline | 3–6 weeks | 6–10 weeks | 8–14 weeks |
| Core Web Vitals ceiling | 50–75 typical | 70–85 with effort | 90+ achievable |
| SEO metadata control | Theme-template constrained | Better but Liquid-bound | Per-page granular |
| Editorial flexibility | Theme-blog level | Better, still in Liquid | Full — same routing as products |
| Image optimization | Shopify CDN, theme-controlled | Same as stock | Framework-level (Next.js Image, etc.) |
| Shopify app compatibility | Full | Mostly full | Limited — many require adaptation |
| Ongoing maintenance | Low | Medium | Higher |
| Engineering team requirement | Optional | Optional | Required (or partner with one) |
| Replatform risk later | Low — straightforward to upgrade | Low–medium | Low — Shopify backend stays |
When to choose stock theme
- Launching fast — under 6 weeks to market
- Catalog under ~500 SKUs, standard variants
- Paid media is the primary traffic source
- Editorial / content needs are basic (theme blog is enough)
- Team prefers operational simplicity over storefront flexibility
- Budget under $15k for the build
When to choose custom theme (Shopify 2.0)
- Brand needs more design flexibility than stock themes provide
- Performance matters but not at the level that requires headless
- You want section-level merchandising flexibility
- Budget allows $8k–$25k
- You want to stay fully on Liquid and Shopify’s rendering pipeline
When to choose headless
- Organic search is a primary growth channel
- Heavy content alongside commerce — lookbooks, editorial, brand storytelling
- Core Web Vitals are differentiating (e.g. competing on quality scores in paid)
- Need rendering control beyond Liquid (SSR, ISR, edge rendering)
- Image-heavy storefront where stock theme image pipeline is a bottleneck
- Multi-region content with locale-specific routing
- Budget allows $25k–$60k
Real example: see our headless Shopify case study for a garments brand — Next.js frontend, Shopify backend, 90+ Core Web Vitals, full pixel continuity through cutover.
The hidden cost of going headless: app compatibility
Some Shopify apps that ship as theme components do not work on a custom frontend without adaptation. Common culprits:
- Review apps that inject UI via theme code
- Subscription apps with theme-injected widgets
- Currency / geolocation apps that override theme rendering
- Older A/B testing tools relying on theme-side logic
Modern Shopify apps offer Storefront API support and headless-compatible SDKs. The pre-migration check: take your current app inventory, contact each vendor (or check their docs), and confirm headless support. If a critical app has no headless story, factor in replacement cost or stay on a theme.
What headless does not change
- Checkout still runs on Shopify. PCI-DSS compliance and payment security stay with Shopify.
- Catalog, inventory, and orders still live in Shopify admin. Operations teams use the same admin they use today.
- Shopify Functions, Flow, and most Plus features still apply.
- Tax, shipping, and fulfillment configuration is unchanged.
Hydrogen vs Next.js for headless Shopify
| Framework | Strengths | Tradeoffs |
|---|---|---|
| Shopify Hydrogen | Built specifically for Shopify; deep Storefront API integration; Oxygen hosting | Smaller ecosystem than Next.js; Shopify-specific lock-in; less flexible for non-commerce content |
| Next.js | Largest React ecosystem; flexible rendering strategies; strong content/CMS story | More integration plumbing; need to build Shopify primitives or use third-party SDKs |
Both work. Hydrogen wins for commerce-only, Shopify-native projects. Next.js wins when the project has significant content alongside commerce, or when the team already works in Next.js.
The decision in one sentence
If your brand’s next three years of growth depend on organic traffic, content, or storefront performance, go headless. If they depend on paid media to a simple catalog, stay on a stock or custom theme.
Trying to decide between headless and a theme?
Tell us about your brand’s traffic mix, content strategy, and growth ambitions. 30 minutes. We’ll give you an honest read on whether headless pays back for your specific case.