Should You Plan Around Plus's 25-Hydrogen-Storefront Cap?
Plus's 25-Hydrogen-storefront cap is a BUILD signal, not a planning constraint: one storefront serving several brands by route beats one storefront per sub-brand. Shopify's Plus plan page documents building up to 25 custom React-based storefronts with Hydrogen (verified Sep 2026). Oxygen hosting is included on every paid plan from Starter upward, so going headless is not a Plus decision. No app raises, monitors or works around the cap.
Your profile — see how the verdict shifts
- Confidence
- Medium — Shopify's Plus plan page states you can build up to 25 custom React-based storefronts with Hydrogen, alongside 100 themes, 1 TB of file storage per store, 200 locations and unlimited staging stores (verified Sep 2026). Confidence is medium on that number for one reason worth stating: the 25-storefront figure was found on the Plus plan page and not on a second Shopify page, and the page does not say whether the allowance is per store or per organization, so confirm the scope with your account team before architecting around it. The surrounding facts are firmer. Oxygen is available at no extra charge on paid Shopify plans, named as Starter, Basic, Grow, Advanced, Plus and Pause and build, so headless is not a Plus-gated move. A Plus organization can have a maximum of ten stores on its contract at no additional cost, one main store and nine expansion stores, and store settings, products, collections and inventory aren't synced between stores. On the market side, the App Store's storefronts category was browsed on 2026-09-05 and returned 24 listings, including Shopify's own Headless connector at 5.0★ on 5 reviews, which creates Storefront API access tokens for a custom storefront. Nothing in that category raises, monitors or works around a storefront-count entitlement, because the cap is enforced by Shopify rather than by anything installable. A merchant who reaches it consolidates storefronts or negotiates with Shopify.
- Reference scenario
- $30M–$200M GMV · Shopify Plus · five sub-brands or market storefronts planned · one main store plus expansion stores · React front-end team or agency · Oxygen hosting
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| One brand, one or two markets, Online Store theme today | WAIT | The storefront count should play no part in your decision at this size, because you are 23 storefronts away from any ceiling. Go headless for rendering control, content architecture or performance, and stay on a theme if none of those is the reason. |
| Plus · three to eight sub-brands or market storefronts planned | BUILD | The fork this page exists for. One storefront that resolves brand and market by route and locale, with per-brand content in metaobjects, costs $60,000–$180,000 (Deploi estimate, illustrative) against roughly three times that for five separate codebases, and it collapses five dependency baselines into one. |
| Plus · storefronts must sit in separate stores for legal, tax or catalog reasons | BUILD | Accept a storefront per store and share one codebase across them. A Plus contract covers ten stores at no additional cost, so 25 Hydrogen storefronts is generous against a ten-store ceiling. Deploy the same repository per store rather than forking it, or the maintenance cost arrives anyway. |
| Not on Shopify Plus | BUILD | Oxygen is available at no extra charge on paid plans from Starter upward, so Hydrogen is open to you (verified Sep 2026). The documented 25-storefront allowance sits on the Plus plan page and no equivalent figure for lower plans was found, which is a question for your account team rather than a reason to avoid headless. |
What Hydrogen Storefront Ceiling Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | One quarterly Shopify API upgrade applied to one codebase replaces the same upgrade repeated per storefront, which is the cost that grows fastest as a portfolio adds brands. |
| Revenue — indirect | Medium | A conversion or performance improvement measured on one brand ships to every brand in the next deploy instead of waiting for each storefront's own roadmap. |
| Customer experience | Medium | Shoppers crossing between brands in the same portfolio meet the same cart, account and checkout behavior, provided the shared-cart product publishing rule is respected. |
| Data & insight | Medium | Brand and market variation held as routes and metaobjects is queryable Shopify data, so merchandising can compare brands without reconciling five separate front-end implementations. |
Spend ceiling: Size the spend against codebases, not storefront slots. Five separate Hydrogen storefronts run $200,000–$500,000 to build and $90,000–$300,000 to keep over three years (Deploi estimate, illustrative), against $60,000–$180,000 for one consolidated storefront. Spend nothing on the entitlement itself, because nothing you can buy changes it.
What buying enables (top apps)
- + A genuinely separate brand can be launched, changed or shut down without touching any other storefront
- + Each brand team owns its own release cadence, stack choices and roadmap
- + Oxygen hosting at no extra charge for every storefront on any paid plan (verified Sep 2026)
- + Shopify's own Headless connector issues Storefront API tokens for each storefront without custom tooling
What building additionally unlocks
- + One quarterly upgrade, one dependency baseline and one deploy pipeline across the whole portfolio
- + Brand six as a configuration and content exercise rather than another repository
- + A shared component library where a fix or a conversion win reaches every brand in the next release
- + Brand and market variation as queryable Shopify data in routes and metaobjects, not assumptions baked into five codebases
Find Your Verdict in 3 Questions
Are three or more brand or market storefronts in your plan for the next two years?
Yes: Go to question 2.
No: Your verdict: WAIT. The storefront count should play no part in the decision at one or two storefronts; choose headless on rendering and content grounds instead.
Do those brands share a component library, a cart model and a release cadence?
Yes: Your verdict: BUILD. One consolidated storefront resolving brand and market by route costs $60,000–$180,000 (Deploi estimate, illustrative) against roughly three times that for five separate codebases.
No: Go to question 3.
Must the storefronts sit in separate stores for legal, tax or catalog reasons?
Yes: Your verdict: BUILD. Keep a storefront per store but deploy one shared repository to each, because 25 storefronts is generous against a ten-store Plus contract and forking the code is what actually costs you.
No: Your verdict: BUILD. Consolidate anyway and express brand differences as configuration, since no app raises, monitors or works around the storefront-count entitlement.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | Five storefronts is five discovery phases, five design systems and five launches, while one consolidated storefront is a single project with brand configuration behind it. | ||
| Recurring fees | Oxygen hosting is at no extra charge on paid plans either way (verified Sep 2026), so the recurring cost is engineering time, and that scales with the number of codebases rather than storefronts served. | ||
| Maintenance & upgrades | The decisive line: Shopify ships quarterly API versions, and five storefronts turn one upgrade into five upgrades, five regression passes and five deploys every quarter. | ||
| Switching & exit | Retiring one of five storefronts means untangling its routes, redirects and feed rules alone, while a consolidated storefront retires a brand by removing a route and its content entries. | ||
| Risk | |||
| Vendor risk | Neither lane depends on a vendor, since no App Store app addresses storefront counts; the dependency in both directions is Shopify's own entitlement and your front-end team. | ||
| Security & compliance surface | Five codebases means five sets of dependencies to patch and five Storefront API token sets to rotate, against one of each on a consolidated storefront. | ||
| Platform-deprecation exposure | Hydrogen's documented baseline still names Node.js v16.20+ and npm v8.19+, so your own runtime policy is the real floor, and holding one policy across one repository beats holding five. | ||
| Value | |||
| Fit to requirement | A dedicated storefront fits a genuinely distinct brand best, while a consolidated storefront fits a portfolio that shares a cart, a component library and a release cadence. | ||
| Time to market | The first storefront takes the same time either way, and every brand after it launches in weeks on a consolidated codebase against months on a new one. | ||
| Performance & scale | Both run on Oxygen with the same edge behavior, though a shared codebase means a performance fix measured on one brand ships to all of them in the next deploy. | ||
| Data ownership & AI-readiness | Brand and market variation modeled as metaobjects and routes is structured Shopify data you can query across the portfolio, rather than assumptions baked separately into five repositories. | ||
| Focus & opportunity cost | Five front-end codebases consume a team that should be shipping merchandising work, which is the cost nobody puts in the storefront-count business case. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Hydrogen and Oxygen | Native — First-party. Oxygen is available at no extra charge on paid Shopify plans: Starter, Basic, Grow, Advanced, Plus and Pause and build, so headless hosting is not a Plus entitlement. Shopify's Plus plan page separately documents building up to 25 custom React-based storefronts with Hydrogen. Hydrogen's own documentation still names Node.js v16.20+ and npm v8.19+, with deployment through the Hydrogen channel (verified Sep 2026). | Framework and Oxygen hosting included on paid plans; the build and its upkeep are the cost (verified Sep 2026) | React storefronts that need rendering control a theme can't give, on any paid plan |
| Store design: storefronts (App Store category) | Category — 24 listings were checked in this category on 2026-09-05, including Shopify's own Headless connector at 5.0★ on 5 reviews, which creates and manages Storefront API access tokens for a custom storefront. Nothing in the category raises, monitors or works around a storefront-count entitlement, because Shopify enforces the cap itself. There is no storefront-ceiling manager app to buy. | Free or low monthly tiers by listing; none addresses the storefront-count entitlement (illustrative) | Issuing Storefront API tokens and starter scaffolding, which is a different job from managing storefront counts |
| One Hydrogen storefront per sub-brand | Build lane — The path most portfolios drift into: a dedicated repository, design system and deploy pipeline per brand. It consumes the entitlement fastest and, more importantly, multiplies quarterly Shopify API upgrades, dependency patching and regression testing by the number of storefronts live. | $40,000–$100,000 per storefront plus roughly 15–20% of build cost per year, each (Deploi estimate, illustrative) | A genuinely separate brand with its own team, cadence and commercial model |
| One consolidated multi-brand storefront (custom) | Build lane — One Hydrogen application resolving brand and market from the route and locale, with a shared component library, per-brand theming tokens, and brand content in metaobjects. Each storefront still needs its own checkout subdomain, and shared carts require the same products published to both the Online Store channel and the Hydrogen storefront. | $60,000–$180,000 one-time plus roughly 15–20% of build cost per year in upkeep (Deploi estimate, illustrative) | Portfolios of three or more brands or markets that share a cart, a component library and a release cadence |
| Online Store themes on expansion stores | Native — The lane that consumes no Hydrogen entitlement at all. A Plus contract covers ten stores at no additional cost, one main store and nine expansion stores, with a theme license required per production store and staging stores exempt. Store settings, products, collections and inventory aren't synced between stores under any front end (verified Sep 2026). | Stores included up to nine expansion stores; a theme license per production store (verified Sep 2026) | Sub-brands that don't need React rendering, where a shared theme codebase is the cheaper architecture |
The Build Path
- Resolve brand and market from the request, not from the repository: One Hydrogen application reads the incoming domain, path prefix or locale and loads the brand's theming tokens, navigation and content from metaobjects. Adding brand six becomes a content and configuration exercise. The rule that keeps this honest: a brand may configure anything and fork nothing, and any exception gets implemented as a component variant in the shared library.
- Plan the checkout subdomain per storefront from day one: Shopify's migration guidance is explicit: if your Hydrogen store is example.com, assign checkout.example.com to checkout. Every brand domain needs that pairing, and every customized route needs a redirect so backlinks keep working. Product feeds need feed rules pointing at the Hydrogen storefront's domain, which is the step teams discover after paid search breaks.
- Decide the shared-cart boundary before you write routes: Shared carts require the same products published to both the Online Store channel and your Hydrogen storefront. Decide which brands share a cart and which do not, because that choice determines whether a phased rollout is possible and whether a shopper moving between two of your brands keeps a basket or starts over.
- Hold one runtime policy across the fleet: Hydrogen's documentation still names Node.js v16.20+ and npm v8.19+ as its floor, which means your own runtime policy is the one that matters. Pin one Node version, one package manager version and one Shopify API version across the whole application, and upgrade on one schedule. Five storefronts with five baselines is how a quarterly upgrade becomes a quarter of work.
- Effort band
- $60,000–$180,000 for one consolidated multi-brand Hydrogen storefront with brand and market routing, shared component library, metaobject content model and per-brand checkout domains — Deploi estimate (illustrative); lands in the $75K+ contact-form band
- Typical timeline
- 5–9 months for the first two brands, then 3–6 weeks per additional brand on the shared codebase (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $9,000–$36,000/yr (Deploi estimate, illustrative) for quarterly Shopify API versions, dependency patching, Oxygen deployment upkeep and new brand variants, all on one schedule instead of one per storefront.
- What you own — and what you take on
- You own: the rendering layer, the routing model, the component library, the brand content model and the release cadence across every brand. You take on: a front-end platform to maintain, a runtime policy for the whole fleet, redirect and feed rules per domain, and the discipline to keep brand differences in configuration rather than in forks.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $200,000–$500,000 (five separate Hydrogen storefronts) | $60,000–$180,000 (one consolidated storefront with brand routing) |
| Years 1–3 (recurring) | $90,000–$300,000 (upkeep across five codebases) | $27,000–$108,000 (upkeep on one codebase) |
| 3-year total | ≈$290,000–$800,000 | ≈$87,000–$288,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column on this page is the storefront-per-sub-brand path: five separate Hydrogen storefronts, each with its own codebase and upkeep.
- † Build column is one consolidated storefront serving all five brands by route and locale; Oxygen hosting is at no extra charge in both; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Quarterly Shopify API versions multiply by the number of storefronts, so five codebases is five upgrade projects a year
- — Each storefront needs its own checkout subdomain, redirect set and product feed rules, and those are the steps discovered after paid search breaks
- — Component drift between storefronts is silent for a year and expensive forever, because no two brands end up sharing the cart code they started from
- — The entitlement is not the constraint most portfolios hit; the front-end team's capacity is, and it arrives far earlier than 25 storefronts
On the build path
- — A consolidated storefront needs a hard rule that brands configure and never fork, or the repository quietly becomes five applications in one
- — Shared carts require the same products published to both the Online Store channel and the Hydrogen storefront, which constrains a phased rollout
- — The 25-storefront figure appears on the Plus plan page alone, with no stated per-store or per-organization scope, so confirm it before architecting around it
- — ~$9,000–$36,000/yr in upkeep (Deploi estimate, illustrative)
What Merchants Say
Teams describe the wall as release cadence rather than entitlement: with four Hydrogen storefronts live, one quarterly Shopify API upgrade becomes four upgrades, four regression passes and four deploys.
The second pattern is drift: storefront three forks a component just for this brand, and eighteen months later no two storefronts share the cart code they all started from.
If You Change Your Mind Later
If you bought and outgrow it
Retiring one of several storefronts is self-contained but rarely cheap: its routes, redirects, feed rules and checkout subdomain all need unwinding, and any component the other storefronts borrowed from it has to be rehomed. The upside is that a single brand can be shut down without touching the others, which is the one real advantage of the per-storefront path.
If you built and want out
Nothing strands, because the storefront is your code on Shopify's APIs and the brand content sits in metaobjects you own. Retiring a brand means removing a route and its content entries. Splitting a brand back out into its own storefront is a fork of a repository you already control, which is the cheapest reversal available here.
When This Answer Changes
We're watching for:
- ▸ Shopify restating the 25-storefront figure on a second page, or clarifying whether the allowance is per store or per organization, since it currently appears only on the Plus plan page (verified Sep 2026)
- ▸ Hydrogen's documented baseline moving off Node.js v16.20+ and npm v8.19+, which sets the runtime floor for every storefront in the fleet
- ▸ A sixth or seventh brand joining the portfolio, which is where per-storefront maintenance passes the cost of consolidating
Verdict change log:
No changes since first publication (September 2026).
Common Questions
How many Hydrogen storefronts can a Shopify Plus store have?
Shopify's Plus plan page states you can build up to 25 custom React-based storefronts with Hydrogen (verified Sep 2026). The figure appears on the Plus plan page and was not found on a second Shopify page, so confirm the per-store versus per-organization scope with your account team. A Plus contract also covers ten stores: one main store and nine expansion stores.
Is going headless with Hydrogen a Shopify Plus feature?
Hydrogen and Oxygen are not Plus-exclusive. Shopify's documentation states that Oxygen is available at no extra charge on paid Shopify plans: Starter, Basic, Grow, Advanced, Plus and Pause and build. What the Plus plan adds is the documented allowance of up to 25 Hydrogen storefronts, plus unlimited staging stores and up to ten stores on one contract at no additional cost.
What does consolidating sub-brands onto one Hydrogen storefront cost?
Consolidating sub-brands onto one Hydrogen storefront costs $60,000–$180,000 one-time plus roughly 15–20% of build cost per year (Deploi estimate, illustrative). Scope covers brand and market routing, a shared component library, per-brand content in metaobjects, and the checkout subdomain each storefront needs. Shared carts require the same products published to both the Online Store channel and the Hydrogen storefront.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Count what you would maintain: codebases, deploy pipelines, dependency baselines and quarterly API upgrades, not storefront slots
- Confirm with your account team whether the 25-storefront allowance is per store or per organization
- Design the routing model first: how brand and market resolve from domain, path prefix and locale
- Model brand differences as theming tokens and metaobject content, and write the no-forking rule into the codebase's contributing guide
- Map every brand domain to its checkout subdomain, redirect set and product feed rules before launch
If you're going with WAIT
- Decide headless on rendering, content and performance grounds, never on the storefront count
- Confirm that Oxygen at no extra charge covers your hosting expectation on your current plan
- Prototype one brand on Hydrogen against a staging store, which Plus provides without limit
- Diary a re-decision when the third brand or market storefront enters the roadmap
Official Docs & Sources
- Shopify Plus plan features (25 Hydrogen storefronts) — Shopify Help Center
- Hydrogen — shopify.dev
- Hydrogen fundamentals and Oxygen plan availability — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Bulk Channel Publishing on Plus?
No app bulk publishes products to your own channels and markets. On Plus, a small custom app on two exclusive GraphQL mutations does the job.
Checkout Extension Translations: Build or Buy the Localization?
Shopify states merchants can't override or add translations for a checkout UI extension, so whoever ships the extension owns every language it renders.
Per-Store App Fees or a Shared Hydrogen Front End on Plus?
Apps bill per store and theme licenses repeat per store on Plus. A shared Hydrogen front end removes the theme fee and little else. Go headless for other reasons.
Expansion Store vs. Shopify Markets: Which Fits a New Region?
Markets keeps a new region on the store you have. An expansion store fits a new brand or entity; nine are free on Plus, but apps and themes bill again per store.
Should You Build or Buy Multi-Currency & Market Pricing on Shopify?
Multi-currency is native on Shopify. The real decision is the market-pricing layer on top.
Ready to size your storefront architecture against the real ceiling?
We start by counting what you would actually maintain: codebases, deploy pipelines, dependency baselines and quarterly API upgrades, not storefront slots. Then we scope a routing model that resolves brand and market from the request, a shared component library, and per-brand content in metaobjects, so brand six is a configuration exercise rather than another repository.
Contact us todayVerdict scored for the reference scenario above. On this page the buy column is the storefront-per-sub-brand path and the build column is one consolidated storefront, because no App Store app addresses storefront counts. Estimates are not quotes and get re-verified quarterly. Plan allowances quoted from Shopify's help documentation as of September 2026, with the 25-storefront figure sourced from the Plus plan page alone. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.