Where it gets stuck.
he default pitch for Shopify Hydrogen — Shopify's React framework for headless storefronts — is performance. Faster pages, better Core Web Vitals, sub-2-second LCP. That pitch is true but incomplete. A well-built Shopify theme on Dawn or Symmetry can also hit sub-2s LCP for a small catalog. The performance gap only becomes structural at catalog scale and at custom-surface scale — and that is where the Hydrogen decision actually gets made, not in a generic 'speed matters' argument.
Why it happens.
Three questions decide whether Hydrogen pays off over a theme. First: how many variants does your largest product have? Above 500 variants per product, themes stall on hydration because all variant data ships to the client upfront. Second: how many custom surfaces does the storefront need to do work themes cannot model — sample tracking, quote-to-cart, slab-level inventory, freight calculation, trade portals? Above three, themes start to crack under the weight of bolt-on apps. Third: how performance-sensitive is your funnel — is page speed the bottleneck of your conversion rate, or is it sample-to-purchase rate? Hydrogen unlocks the first two; it amplifies the third only if it is already a real constraint.
The size of it.
Brands selling 50 products with one variant axis and a standard checkout do not need Hydrogen. A good Shopify theme is faster to ship, cheaper to maintain, and indistinguishable in performance for that catalog shape. Hydrogen pays off when your product page does more than show variants and add to cart — when it has to render a 36-hour slab hold, a sq-ft calculator, a freight estimate, an FTL bracket, a pattern visualizer, a tear-sheet builder. At that point the theme becomes the bottleneck, and Hydrogen stops being an upgrade and starts being the only viable architecture.
Filed from inside a working engagement. Edited only for client privacy — the numbers and the mechanisms are exact.