When headless Shopify is worth it - and when Liquid still wins

Choose Shopify Hydrogen / headless commerce when you need storefront experiences Liquid cannot express cleanly — complex configurators, shared React design systems across app and web, heavy CMS-driven editorial at scale, or multi-surface commerce where the same components must ship everywhere. Stay on Online Store 2.0 when speed-to-market, theme-editor autonomy, App Store compatibility, and maintainability matter more than React control. Propeller recommends headless only with a clear performance or UX case — not because the pitch deck said “composable.”

This is a decision tree, not a fashion brief. Pair it with Shopify Plus vs Shopify when plan and architecture get conflated, and with the CRO checklist when the real problem is conversion debt on an existing theme.

Decision tree: Liquid vs Hydrogen

• If Core Web Vitals are the only complaint → fix theme debt and third-party scripts first; do not go headless to escape a heavy app stack you will reinstall.
• If marketing needs daily theme-editor control and no CMS budget → Liquid / OS 2.0 wins.
• If UX requires configurators, multi-step builders, or app-shared React components Liquid fights weekly → score headless higher.
• If you lack senior React owners (or retainer budget for them) → Liquid, or fund the team before you fund Hydrogen.
• If multi-brand or multi-surface frontends must share one design system → headless can pay.
• If checkout customization is the real need → that is often Plus + Extensions, not headless; see Shopify Plus.
• If “composable” is the only rationale → stop; write the UX requirement that Liquid cannot meet.

The three-axis score

Score brand sophistication (does the UX exceed themes?), team capability (do you have senior React owners or budget to retain them?), and surface requirements (mobile app, multi-brand frontends, CMS architecture Liquid fights). Three out of three and Hydrogen can pay. One out of three and you are funding fashion.

• Sophistication high + team low → redesign Liquid with discipline; hire before Hydrogen.
• Sophistication low + team high → do not invent complexity to entertain engineers.
• Surfaces many + CMS ready → headless shortlist with honest TCO.
• Surfaces one + App Store dependency heavy → Liquid; headless will fight apps you love.

What you inherit with headless

You own rendering, caching, content ops (usually a headless CMS), and a permanently higher build and maintenance cost — often several times a comparable theme. Checkout still lives on Shopify. Marketing loses the theme editor unless you invest in content infrastructure. Preview workflows, localization, and merchandising tooling must be designed — they are not free gifts of “modern stack.”

A Los Angeles headless Shopify agency should talk you out of Hydrogen as often as into it. Propeller defaults to Liquid excellence first, then Hydrogen / Oxygen with cost and ownership written in the proposal — not buried in a footnote.

When Liquid still wins in 2026

• Most mid-market DTC catalogs with strong merchandising and a CRO backlog.
• Teams that ship weekly via theme editor and metafields.
• Brands that need App Store coverage more than custom React trees.
• Migrations where day-one revenue risk is already high — add headless later, not into the same cutover; see migration without chaos.

Total cost of ownership you should put in the deck

Headless proposals that only show build week estimates are incomplete. Add year-two maintenance, CMS licenses, preview tooling, localization workflows, monitoring, and the senior React retainers required to keep the storefront current with Shopify API changes. Compare that stack to a well-built Online Store 2.0 theme with metafields and a CRO backlog. Many brands discover Hydrogen’s sticker price was the down payment.

• Build: design system, storefront, CMS models, CI/CD, Oxygen or equivalent hosting.
• Operate: content training, incident response, dependency upgrades, A/B tooling parity.
• Opportunity cost: months not spent shipping Liquid CRO while the React app is still greenfield.
• Vendor risk: agency lock-in if only two people understand the repo — demand documentation and pairing.

Hybrid paths that are honest

Not every surface must go headless on day one. Some brands keep OS 2.0 for core commerce and use Hydrogen (or a React app) for a configurator, retail locator, or editorial magazine that Liquid fights. That hybrid only works with clear ownership boundaries and shared design tokens. Without those, you get two half-brands and double the meetings.

If your brief is really “we need Plus checkout extensibility,” stop and read the Plus guide. If your brief is “our theme is slow,” profile scripts before you rewrite the world. Propeller’s headless commerce practice exists to make that call with receipts — then build whichever path you actually need.

Performance myths vs real bottlenecks

Teams reach for Hydrogen because a Lighthouse screenshot hurt feelings. Often the fix is removing dead apps, deferring tags, compressing heroes, and killing a chat widget that blocks input. Sometimes the fix is Plus-grade hosting patterns and a cleaner Liquid architecture. Headless can be fast — it can also be a slow React tree with a CMS waterfall if you build carelessly. Benchmark the current store with third parties disabled before you approve a rewrite.

• Profile: which scripts cost interaction delay on mobile PDP?
• Theme: section sprawl and unoptimized media vs framework choice.
• Apps: paid rent that injects storefront JS you no longer use.
• Fonts and third-party pixels: often cheaper to discipline than to re-platform.
• Only then: does the UX still require React-level control?

Need an honest architecture call? Talk headless commerce or start a project. Bring the UX that Liquid cannot express — if you cannot name it, we will help you stay on Online Store 2.0 with a sharper build.