Per-Store App Fees or a Shared Hydrogen Front End on Plus?
Absorbing per-store app and theme licenses beats a shared Hydrogen front end for most Plus organizations; headless never pays for itself on license savings. Apps are billed per store (verified Sep 2026), and those that work on orders, customers and inventory keep billing per store under any front end. A $150,000 to $400,000 rebuild (Deploi estimate, illustrative) chases 15 to 30% of stack spend. Build headless for its own reasons, never for the bill.
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's expansion-stores page on 2026-09-05 for the per-store app billing and per-production-store theme license rules, and the Hydrogen fundamentals page for Oxygen at no extra charge on paid plans. Searched the App Store for a headless commerce or theme-licensing consolidation category; none exists in Shopify's taxonomy, and direct listing guesses for headless front-end vendors such as Builder.io found no App Store listing. Hydrogen is Shopify's own free framework, not a purchase, so no app substitutes here. The split between storefront-only apps and apps bound to store data is a Deploi estimate from mid-market stack audits, not a Shopify figure.
- Reference scenario
- $20M–$100M GMV · Plus organization at production store three · 15–25 paid apps per store · one licensed theme per store · agency dev bench, no in-house React team
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| One expansion store (two production stores) | BUY | Absorb the second stack and audit it. One extra store's app fees, an illustrative $24,000–$60,000/yr, cannot fund a rebuild that starts at $150,000 (Deploi estimate, illustrative). |
| Three to five stores, same brand family | BUY | Absorb, negotiate organization pricing with each vendor, and deploy one theme codebase to every store through Shopify CLI environments. Most of the duplicated work disappears without headless. |
| Five or more stores with a front-end team that can own React | CUSTOMIZE | A shared Hydrogen front end for the storefront layer, with backend apps kept per store. License savings become an offset against upkeep, not the case for the project. |
| Headless already justified on performance, design system or content | BUILD | Build the shared Hydrogen front end for those reasons. The theme licenses and storefront-only widgets you drop are a footnote in the business case, and honest accounting keeps them there. |
What Expansion Store Licensing Costs Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | Every paid app installs, configures and bills again per store (verified Sep 2026), so store two doubles admin work; a shared theme codebase through CLI environments removes most front-end duplication without a rebuild. |
| Revenue — indirect | Medium | A shared design system ships storefront changes once, so a conversion improvement reaches every store the same week rather than store by store over a quarter. |
| Customer experience | Medium | Owned components replace widget apps that each inject scripts, which is where the app-bloat page-speed tax comes from; the gain is speed on every storefront, not license savings. |
| Data & insight | Low | A shared front end changes where the UI lives, not where the data lives: each store still holds its own products, orders and customers (verified Sep 2026). |
| Revenue — direct | Low | License savings never reach the P&L in a size a CFO notices; the storefront-only apps you could drop are typically 15–30% of stack spend (Deploi estimate, illustrative). |
Spend ceiling: Spend on a stack audit and a shared theme codebase first; together they remove most duplicated work for a fraction of a headless build. Cap what you spend chasing license savings at the savings themselves, which are 15–30% of stack spend at best (Deploi estimate, illustrative).
What buying enables (top apps)
- + Store two live in weeks on a licensed theme, with vendor-maintained apps that update themselves
- + Theme app extensions built for Online Store 2.0 themes, which reviews, loyalty and upsell vendors ship and no Hydrogen storefront gets for free (verified Sep 2026)
- + Organization or multi-store pricing from vendors who negotiate, which cuts the per-store bill without changing architecture
- + Staging stores exempt from theme licenses (verified Sep 2026), so a shared theme pipeline costs nothing extra to test
What building additionally unlocks
- + One React codebase serving up to 25 Hydrogen storefronts on Plus (verified Sep 2026), with a design system shared across brands
- + Storefront-only widget apps replaced by owned components, ending their per-store subscriptions and their injected scripts
- + Oxygen hosting at no extra charge on paid plans (verified Sep 2026), with checkout still on Shopify's hosted checkout subdomain
- + Composable content and custom UX that a theme cannot express, which is the real reason to go headless
Find Your Verdict in 3 Questions
Are you going headless for reasons that stand on their own: performance targets, a shared design system across brands, composable content or custom UX?
Yes: Your verdict: BUILD — a shared Hydrogen front end on those merits; count the theme licenses and storefront-only app subscriptions you drop as a small offset, never as the business case.
No: Go to question 2.
Is the per-store cost that hurts mostly storefront-only widgets (page builders, banners, upsell widgets, size charts) rather than apps that work on orders, customers or inventory?
Yes: Go to question 3.
No: Your verdict: BUY — apps bound to store data install and bill per store under any front end (verified Sep 2026); a headless rebuild saves nothing on them, so negotiate organization pricing and prune.
Do you run five or more production stores with a front-end team that can own a React codebase?
Yes: Your verdict: CUSTOMIZE — a shared Hydrogen front end for the storefront layer, backend apps kept per store, and license savings treated as an offset against upkeep.
No: Your verdict: BUY — absorb the per-store licenses, replace the worst widgets with theme sections in a shared theme codebase, and revisit at five stores.
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 | Store two installs a licensed theme and the app stack in weeks; a shared Hydrogen front end for two to five storefronts is an estimated $150,000–$400,000 (Deploi estimate, illustrative). | ||
| Recurring fees | Apps are billed on a per-store basis (verified Sep 2026) in both lanes; headless drops only storefront-only widgets, an illustrative 15–30% of stack spend, while Oxygen hosting adds nothing. | ||
| Maintenance & upgrades | Vendors maintain the apps and theme updates run per store; a React codebase plus every storefront app integration you rebuilt is yours, at ~15–20% of build cost per year (Deploi estimate). | ||
| Switching & exit | Per-store apps uninstall and stop billing the same month; retreating from headless means re-theming every storefront and re-installing theme app extensions. | ||
| Risk | |||
| Vendor risk | Three stores means three copies of every vendor dependency; a shared front end removes the storefront-widget vendors and keeps the data-bound ones. | ||
| Security & compliance surface | Themes run on Shopify's hosting with checkout untouched; Hydrogen code is yours to secure on Oxygen, though checkout still routes to a Shopify-hosted checkout subdomain (verified Sep 2026). | ||
| Platform-deprecation exposure | Online Store 2.0 themes and theme app extensions are first-class and vendor-maintained; a Hydrogen front end tracks framework and Storefront API versions on your calendar. | ||
| Value | |||
| Fit to requirement | Licensed themes and widget apps ship generic UX configured three times over; one design system across brands is exactly what a shared front end is for. | ||
| Time to market | A new expansion store is live in weeks on the licensed-theme lane; a shared Hydrogen migration across storefronts runs 6–12 months (Deploi estimate, illustrative). | ||
| Performance & scale | Widget apps each inject scripts and the app-bloat page-speed tax is a documented recurring pattern; owned components remove it, which is a real gain and not a license saving. | ||
| Data ownership & AI-readiness | A shared front end changes where the UI lives, not where the data lives: each store still holds its own products, orders and customers (verified Sep 2026). | ||
| Focus & opportunity cost | A stack audit and a shared theme codebase take weeks of a dev bench; a headless program consumes a front-end team for a year and everything else waits. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Per-store app and theme licensing (expansion stores) | Native — First-party Shopify, Plus only. A Plus organization can have up to ten stores at no additional cost, one main and nine expansion. Apps are billed on a per-store basis rather than for the entire organization; theme licenses are required for each individual production store, staging stores exempt; each store operates completely independently with its own data, settings and configurations (verified Sep 2026). | Store included (up to nine expansion stores); apps re-bill per store and a theme license is required per production store, staging exempt (verified Sep 2026) | Every organization at store two or three: absorb, audit, negotiate |
| Hydrogen and Oxygen (shared front end) | Native — First-party Shopify. Build up to 25 custom React-based storefronts with Hydrogen on Plus; Oxygen hosting is available at no extra charge on paid plans (verified Sep 2026). Checkout stays on a Shopify-hosted checkout subdomain. Theme app extensions integrate with Online Store 2.0 themes, so every storefront-facing app needs re-integration on Hydrogen. | Framework and Oxygen hosting included; the build and its upkeep are the cost, an estimated $150,000–$400,000 to build (Deploi estimate, illustrative) | Organizations that want headless on its merits and can own a React codebase |
| Headless CMS and front-end platforms | Category — Off-platform SaaS such as Builder.io and Contentful, sold on enterprise or seat terms with no per-store App Store listing (verified Sep 2026). They solve content composition, not per-store relicensing, and they add a subscription rather than removing one. | Quote-based or seat-based on the vendor's site; pricing not listed on the App Store | Content teams composing pages across brands, once a headless front end already exists |
| Shared theme codebase (custom) | Build lane — The small build that captures most of the duplication savings: one theme codebase deployed to development, staging and production instances across stores with Shopify CLI theme environments (verified Sep 2026), with the worst widget apps replaced by theme sections. Theme licenses still apply per production store. | $15,000–$40,000 one-time plus upkeep (Deploi estimate, illustrative) | Two to five stores of the same brand family that duplicate front-end work |
The Build Path
- One Hydrogen codebase, many storefronts: Plus supports up to 25 custom React-based storefronts with Hydrogen (verified Sep 2026), so one codebase with per-storefront configuration serves every brand and region. Oxygen hosts it at no extra charge on paid plans. The design system, not the hosting bill, is what you are buying with the build.
- Re-integrate storefront apps by API: Theme app extensions integrate with Online Store 2.0 themes (verified Sep 2026); a Hydrogen storefront gets none of them. Each storefront-facing app either ships a headless SDK you wire in or gets rebuilt as a component. Apps bound to orders, customers, inventory and reviews stay installed, and billed, on each store.
- Migration mechanics, repeated per store: Shared carts need the same products published to both the Online Store channel and the Hydrogen storefront; checkout gets its own subdomain such as checkout.example.com; customized routes need redirects; feed rules and notification URLs move to the new domain (verified Sep 2026). Every one of those steps runs once per store.
- The smaller build that beats the big one: A single theme codebase pushed through Shopify CLI theme environments to development, staging and production instances across stores (verified Sep 2026) removes most duplicated front-end work. Replace the heaviest widget apps with theme sections, and the license savings arrive without a rebuild.
- Effort band
- $150,000–$400,000 for a shared Hydrogen front end serving two to five storefronts, including app re-integration — Deploi estimate (illustrative); lands in the $75K+ contact-form band. The shared theme codebase alternative runs $15,000–$40,000 (Deploi estimate, illustrative).
- Typical timeline
- 6–12 months to migrate two to five storefronts to a shared Hydrogen front end; 4–8 weeks for a shared theme codebase across stores (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $22,000–$80,000/yr (Deploi estimate, illustrative) for framework upgrades, Storefront API versions and every storefront app integration you now own, on top of the data-bound apps that still bill per store.
- What you own — and what you take on
- You own: the storefront code, the design system and every storefront app integration. You take on: a React codebase run as a product, API version cadence, and stores that still hold separate data, settings and app installs underneath the shared front end.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $15,000–$41,000 (shared theme codebase plus two theme licenses) | $150,000–$400,000 |
| Years 1–3 (recurring) | $144,000–$360,000 (two extra stores' app stacks) | $167,000–$546,000 (remaining per-store apps plus upkeep) |
| 3-year total | ≈$159,000–$401,000 | ≈$317,000–$946,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column = absorbing per-store licensing for two expansion stores beyond the main store: a theme license per production store at an illustrative $150–$500 one-time, an app stack at an illustrative $2,000–$5,000/month per store, and a shared theme codebase build; three-year horizon.
- † Build column = a shared Hydrogen front end for the same three storefronts, with storefront-only apps (an illustrative 15–30% of stack spend) dropped, data-bound apps still billed per store, and Oxygen hosting at no extra charge (verified Sep 2026).
What the Sticker Price Hides
On the buy path
- — Apps are billed on a per-store basis rather than for the entire organization (verified Sep 2026): a $3,000/month stack is $9,000/month across three stores (illustrative)
- — Theme licenses are required for each individual production store (verified Sep 2026); the one-time fee is small, the per-store configuration time is not
- — Each store operates completely independently (verified Sep 2026), so app settings, discounts and theme customizations are re-entered by hand unless a pipeline carries them
- — Widget apps each inject scripts, and the app-bloat page-speed tax compounds on every store you copy the stack to
On the build path
- — Theme app extensions integrate with Online Store 2.0 themes (verified Sep 2026); every storefront-facing app on Hydrogen needs a headless SDK or a rebuild you pay for
- — Apps bound to orders, customers, inventory and reviews still install and bill per store, because the data they work on lives per store (verified Sep 2026)
- — Shared carts need the same products published to both the Online Store channel and the Hydrogen storefront, plus a checkout subdomain, redirects and feed rules per store (verified Sep 2026)
- — ~$22,000–$80,000/yr upkeep (Deploi estimate, illustrative) exceeds the license savings for most three-to-five-store organizations
What Merchants Say
Finance leads describe the moment store three goes live: the app line on the Shopify bill triples, and the first question is whether a shared front end would make it stop.
Teams that went headless to cut costs report the opposite shape: the front end got faster and the subscriptions stayed, because the apps they paid for were about orders and customers, not pages.
If You Change Your Mind Later
If you bought and outgrow it
Uninstall is the exit: per-store apps stop billing the month you remove them, and a licensed theme is a sunk cost of a few hundred dollars (illustrative). Absorbing per-store licenses locks you out of nothing; the stack audit you run now is the first step of any later headless migration.
If you built and want out
A headless front end is a one-way door in practice: retreating means re-theming every storefront, re-installing theme app extensions and re-learning the theme editor. Keep the Online Store channel published in parallel during migration, as Shopify's shared-cart guidance requires anyway, and the retreat path stays open longer.
When This Answer Changes
We're watching for:
- ▸ Shopify moving app billing from per-store to organization-level, which would remove the cost this page is about
- ▸ Major storefront apps shipping first-class Hydrogen components licensed once per organization rather than per store
- ▸ Shopify adding native cross-store sync of settings, products or theme configuration between expansion stores
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Does a Shopify expansion store re-bill your apps and theme?
Yes, a Shopify expansion store re-bills your apps and theme. Shopify's expansion-stores page states apps are billed on a per-store basis rather than for the entire organization, and theme licenses are required for each individual production store, with staging stores exempt (verified Sep 2026). The store itself is included, up to nine expansion stores on Plus; the stack you install on it is not.
Does a headless Hydrogen front end remove per-store app fees?
A headless Hydrogen front end removes only the storefront-only app fees, not the rest. Apps that operate on orders, customers, inventory or reviews install and bill per store under any front end, because each store operates completely independently with its own data (verified Sep 2026). Storefront-only widgets you replace with owned components are typically 15 to 30% of stack spend (Deploi estimate, illustrative).
What does a shared Hydrogen front end cost across expansion stores?
A shared Hydrogen front end costs $150,000 to $400,000 to build for two to five storefronts, including app re-integration, plus 15 to 20% of that per year in upkeep (Deploi estimate, illustrative). Oxygen hosting comes at no extra charge on paid Shopify plans, and Plus supports up to 25 Hydrogen storefronts (verified Sep 2026). A shared theme codebase captures most duplication savings for $15,000 to $40,000 (Deploi estimate, illustrative).
Your Next Steps
If you're going with BUY(matches your selected profile)
- Export the app charges from each store's bill and tag every app as storefront-only or data-bound
- Ask each vendor for organization or multi-store pricing before renewing at list price
- Set up Shopify CLI theme environments so one theme codebase deploys to every production store
- Replace the heaviest storefront widgets with theme sections in that shared codebase
- Re-run the numbers at five stores, or when a headless case appears on its own merits
If you're going with BUILD
- Write the headless business case without license savings, then add them back as an offset
- Inventory every storefront-facing app and confirm a headless SDK exists, or budget the rebuild
- Migrate one storefront first: shared products, checkout subdomain, redirects, feed rules
- Keep data-bound apps installed per store and budget their subscriptions unchanged
- Fund upkeep at 15–20% of build cost per year (Deploi estimate) before the first line of code
Official Docs & Sources
- Expansion stores — Shopify Help Center
- Hydrogen and Oxygen fundamentals — shopify.dev
- Migrating to Hydrogen — 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.
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 Plan Around Plus's 25-Hydrogen-Storefront Cap?
Plus documents up to 25 Hydrogen storefronts, and no app can lift that entitlement. The ceiling that arrives first is the number of codebases you can maintain.
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 cut the per-store bill without a rebuild?
We audit the stack across your stores, negotiate what can be negotiated, and ship one theme codebase to every storefront. When headless is the right call on its own merits, we build that too, with honest numbers.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. 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.