Do You Need a New Theme License for Every Expansion Store?
Relicensing the same premium theme is a $200 to $500 purchase per production store, one-time (illustrative), and that stays the right call at two or three storefronts. Theme licenses are required for each individual production store, and staging stores are exempt (verified Sep 2026). What repeats expensively is customization, at $10,000 to $30,000 per store (Deploi estimate, illustrative), which is where one shared codebase starts winning.
Your profile — see how the verdict shifts
- Confidence
- High — Shopify's expansion-stores page, read on 2026-09-05, states that theme licenses are required for each individual production store and adds that staging stores are exempt. The Plus plan page confirms support for adding up to 100 themes to your Shopify account and unlimited staging stores. No App Store product changes any of this: themes are sold through the Theme Store, not the App Store, as one-time purchases per store, and no listing manages, pools or reduces multi-store theme licensing. Dawn, Shopify's own free theme, is distributed through the Theme Store and GitHub and has no App Store listing at all. Premium theme prices below are illustrative bands, and the crossover framing is Deploi's cost reasoning rather than a Shopify recommendation.
- Reference scenario
- $20M–$100M GMV · Plus organization moving from two to five production stores · one premium licensed theme customized per store · agency dev bench · no in-house theme team
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Two production stores, one brand | BUY | One more license at $200 to $500 (illustrative) is cheaper than any alternative and carries vendor updates with it. Buy the second license and spend the saved budget on the customization that actually differs. |
| Three to five stores sharing one design language | DEPENDS | Licenses stay trivial at roughly $600 to $2,500 across the portfolio (illustrative), but each store's customization and QA repeats. Count the hours, not the licenses, then decide whether one codebase is worth commissioning. |
| Four or more stores, each heavily customized | BUILD | Custom sections, metafield-driven layouts and conversion work applied four times is the real bill. One codebase at $30,000 to $90,000 (Deploi estimate, illustrative) turns four maintenance streams into one. |
| Stores that must read as genuinely different brands | BUY | A shared codebase fights this requirement rather than serving it. License a different premium theme per brand, keep the teams independent, and accept the small per-store fee as the price of real design separation. |
What Per-Store Theme Licensing Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | A change made once and deployed everywhere replaces the same change made and tested on each storefront, which is where multi-store theme cost actually accumulates. |
| Revenue — indirect | Medium | Conversion work ships to every storefront in one release instead of queuing behind four separate theme merges, so wins compound across the portfolio rather than one store at a time. |
| Customer experience | Medium | Shoppers who cross between your storefronts meet the same navigation, product cards and checkout patterns, which a shared codebase enforces and five theme copies gradually lose. |
| Data & insight | Low | Structured data and analytics tagging implemented once stay identical across storefronts, so portfolio reporting compares like with like instead of five slightly different implementations. |
Spend ceiling: The license is never the decision. Cap theme licensing thinking at roughly $2,500 across a five-store portfolio (illustrative) and put the real budget where the repetition lives: per-store customization, vendor-update merges and QA. Commission a shared codebase only when that repetition is bigger than the build.
What buying enables (top apps)
- + A designed, tested storefront live within days on each new store, with no build phase
- + A vendor's update stream: new sections, platform compatibility and accessibility fixes for the price of the license
- + Support and documentation your agency already knows, which keeps onboarding cheap on store three
- + Genuine design separation between brands, since each storefront can license a different theme
What building additionally unlocks
- + One section library and one settings schema across every storefront, so a fix ships once rather than five times
- + No license line at all, and no vendor deciding when your architecture changes
- + Per-store configuration through theme settings and metafields, which keeps storefronts different without forking the code
- + A performance budget you control, carrying only the features your storefronts actually use
Find Your Verdict in 3 Questions
Should your storefronts read as one brand family?
Yes: Go to question 2.
No: Your verdict: BUY — license a different theme per brand; a shared codebase fights genuine design separation, and the per-store fee is trivial next to that.
Will four or more production stores run this design within two years?
Yes: Your verdict: BUILD — one codebase, configured per store, collapses four maintenance streams into one at $30,000 to $90,000 (Deploi estimate, illustrative).
No: Go to question 3.
Does each store get more than light theme customization?
Yes: Your verdict: DEPENDS — count the per-store customization hours over three years before buying a third license; that number, not the license, decides this.
No: Your verdict: BUY — relicense the premium theme at $200 to $500 per store (illustrative) and keep the vendor's update stream.
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 | A licensed theme is live the day you buy it; a custom theme runs 8 to 16 weeks before the first store launches on it. | ||
| Recurring fees | Theme licenses are one-time per production store rather than a subscription, and a shared codebase carries no license line at all. | ||
| Maintenance & upgrades | Vendor updates arrive free but must be applied per store, and heavy customization makes each update a merge; one codebase turns five merges into one. | ||
| Switching & exit | Swapping a licensed theme means buying another and redoing customization per store; a custom theme is yours to keep, port or hand to another agency. | ||
| Risk | |||
| Vendor risk | A theme vendor can stop updating a theme, and the license you bought per store does not oblige anyone to keep it current. | ||
| Security & compliance surface | Theme code runs in the storefront either way; the difference is who reviews third-party scripts and accessibility fixes, and how many copies need the fix. | ||
| Platform-deprecation exposure | Online Store 2.0 sections, blocks and metafields are stable primitives, but a custom theme puts every future platform change on your maintenance plan. | ||
| Value | |||
| Fit to requirement | A licensed theme fits the average store well and your merchandising exactly never; a shared codebase encodes your own patterns once. | ||
| Time to market | Store four can launch this month on a licensed theme, or next quarter on a codebase you commissioned. | ||
| Performance & scale | Premium themes ship features every store pays for in page weight; a purpose-built theme carries only what your storefronts use. | ||
| Data ownership & AI-readiness | Structured data, analytics tagging and metafield-driven content get implemented once in a shared codebase instead of drifting across five theme copies. | ||
| Focus & opportunity cost | Theme engineering is not where a five-store portfolio wins, and a licensed theme buys back the quarter a custom build would consume. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify's free themes (Dawn and the free Theme Store range) | Native — Shopify's own themes carry no license fee on any store. Dawn is a theme rather than an app: it ships through the Theme Store and on GitHub, and has no App Store listing, so nothing about it is billed per store. | Free on every store, with no per-store license (verified Sep 2026) | Portfolios that customize heavily anyway and treat the base theme as a starting point |
| Premium Theme Store theme, relicensed per store | Category — Sold on the Theme Store rather than the App Store, as a one-time purchase per store. No App Store listing manages, pools or discounts multi-store theme licensing, so the only lever is which theme you standardize on. Theme licenses are required for each individual production store; staging stores are exempt. | $200–$500 per production store, one-time (illustrative — confirm the current Theme Store listing) | Two or three storefronts that can live inside one design language |
| Staging stores | Native — Staging stores are exempt from the theme-license requirement, and Plus supports unlimited staging stores, so a theme can be built, reviewed and QA'd across as many environments as you want. The license falls due when a storefront goes to production. | Included with Shopify Plus; no theme license required (verified Sep 2026) | Building and reviewing a theme before any license is due |
| One shared theme codebase (custom) | Build lane — One repository, per-store configuration through theme settings and metafields, deployed to each production store from the same source. Removes the license line entirely and collapses four maintenance streams into one, at the cost of owning every future platform change yourself. | $30,000–$90,000 one-time plus $3,000–$8,000 per store to roll out (Deploi estimate, illustrative) | Four or more storefronts that each need real customization |
The Build Path
- Standardize on one licensed theme, then customize per store: The cheapest path to store three. Buy the license again, apply your section library, and accept that vendor updates get merged per store. Works while customization stays light and the storefronts want to look related.
- Fork a free Shopify theme into a shared codebase: Dawn and the free range cost nothing on any store, which removes the license question and starts you from source you can read. The work is the same section, metafield and settings architecture a custom theme needs, without a vendor's opinions to unpick first.
- Commission one theme, configure it per store: Design tokens, sections and blocks live in one repository; each storefront's colors, typography, merchandising modules and copy live in theme settings and metafields. Storefronts differ by configuration rather than by code, so a conversion fix ships once. Deploy from the Shopify CLI, using an environment per store.
- Effort band
- $30,000–$90,000 for one shared theme codebase, plus $3,000–$8,000 per store to roll out — Deploi estimate (illustrative); lands in the $75K+ contact-form band across a five-store portfolio
- Typical timeline
- 8–16 weeks to the first store, then 1–3 weeks per additional storefront (Deploi estimate, illustrative)
- Maintenance, honestly
- Roughly 15–20% of build cost a year, about $5,000–$18,000/yr (Deploi estimate, illustrative), against theme-vendor updates that are free but must be merged into every store separately.
- What you own — and what you take on
- You own: the codebase, the section library, the settings schema and the deploy pipeline across every storefront. You take on: platform changes, accessibility and performance work that a theme vendor would otherwise ship for the price of the license.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $26,000–$77,500 (licenses plus per-store customization) | $45,000–$130,000 |
| Years 1–3 (recurring) | $45,000–$120,000 (per-store updates and changes) | $15,000–$54,000 (maintenance) |
| 3-year total | ≈$71,000–$197,500 | ≈$60,000–$184,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: a premium licensed theme purchased for each of five production stores, plus customization and vendor-update merges carried per store.
- † Build column: one shared codebase built once, rolled out to five storefronts, with annual upkeep; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Theme licenses are required for each individual production store (verified Sep 2026), so the purchase repeats with every storefront you launch
- — Vendor updates are free but land per store, and heavy customization turns each update into a merge someone has to test
- — Customization is the repeated cost, not the license: $10,000 to $30,000 per storefront in year one is typical (Deploi estimate, illustrative)
- — Five copies drift, so a conversion fix or an accessibility remediation has to be shipped and QA'd five times
On the build path
- — $30,000 to $90,000 before the first storefront launches, plus $3,000 to $8,000 per store to roll out (Deploi estimate, illustrative)
- — No vendor ships you platform updates, accessibility fixes or new section types; that work becomes your maintenance plan
- — A shared codebase forks anyway unless per-store differences are forced into theme settings and metafields from day one
- — Roughly 15–20% of build cost a year in upkeep, about $5,000–$18,000/yr (Deploi estimate, illustrative)
What Merchants Say
The common surprise at store two is not the theme price but the checkout at all: merchants expect a portfolio license and find that each production storefront needs its own.
The pain that follows is drift. Five copies of one theme diverge within a year, and a bug fix or a conversion change has to be applied and tested five separate times.
If You Change Your Mind Later
If you bought and outgrow it
Leaving a licensed theme means buying another one and redoing customization on every store that ran it, because the license does not travel and neither does the section work. Budget the exit per storefront, not per portfolio, and keep customizations in sections and metafields so the next theme inherits the content.
If you built and want out
A custom theme is yours: the repository ports to another agency, another store, or back onto a licensed base if priorities change. What you cannot recover is the vendor update stream you stopped paying for, so plan for accessibility and platform work to stay on your side permanently.
When This Answer Changes
We're watching for:
- ▸ A theme vendor introducing portfolio or multi-store licensing, which would remove the repeat purchase from the math
- ▸ Shopify extending the staging-store exemption or adding an organization-level theme allowance
- ▸ Your storefront count passing four with real customization on each, which is where one codebase overtakes five licensed copies
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Do you need a separate theme license for each Shopify store?
Yes. Shopify states that theme licenses are required for each individual production store, and adds that staging stores are exempt (verified Sep 2026). A Plus organization can run ten stores, one main and nine expansion, so a portfolio that standardizes on one premium theme buys it up to ten times. Plus also supports adding up to 100 themes to your Shopify account.
How much does relicensing a premium theme across five stores cost?
Roughly $1,000 to $2,500 in total, at $200 to $500 per production store, one-time (illustrative). That figure is the smallest line in any multi-store budget. The cost that matters is customization and vendor-update merges repeated per store, which run $10,000 to $30,000 per storefront in the first year (Deploi estimate, illustrative).
Is a custom theme cheaper than buying a theme for every store?
Not on license fees. A shared codebase costs $30,000 to $90,000 to build (Deploi estimate, illustrative) against roughly $1,000 to $2,500 of licenses across five stores (illustrative). A custom theme wins on maintenance instead: one section library, one settings schema and one fix per change, which overtakes five licensed copies at around four heavily customized storefronts.
Your Next Steps
If you're going with BUY
- Confirm the theme's current Theme Store price before budgeting store three, since listings change
- Build and review on a staging store first, which is exempt from the license requirement
- Keep every customization in sections, blocks and metafields so the next theme inherits the content
- Log which vendor updates were applied to which store, so drift stays visible
- Re-run this decision when the fourth production store enters planning
If you're going with BUILD
- Inventory the customizations already made on each store and mark which are genuinely store-specific
- Design the settings and metafield schema first, so storefronts differ by configuration rather than code
- Fork a free Shopify theme rather than a licensed one, to avoid carrying a vendor's architecture
- Roll out store by store, keeping the licensed theme live until each storefront is verified
- Budget upkeep at roughly 15–20% of build cost a year and name an owner for the section library
Official Docs & Sources
- Expansion stores — Shopify Help Center
- Shopify Plus plan features — Shopify Help Center
- Theme architecture — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Build or Buy Observability for Checkout Functions on Shopify?
Shopify documents 12 function error types and stores each run in the Dev Dashboard, but no default alert tells you a checkout function has started failing.
Do Customer Accounts Follow Shoppers Across Plus Stores?
Each Plus store keeps its own customer records, so accounts don't follow shoppers between stores. Multipass rides legacy accounts Shopify deprecated.
Should You Build or Buy Cross-Store Staff Access on Plus?
Custom organization-level roles give one staff login reach across a Plus organization. No app grants staff access across stores; below Plus, every store is separate.
Customer Account API vs. a Custom Login System on Headless?
Shopify's Customer Account API authenticates buyers on headless. A custom login build costs six figures, and legacy accounts are deprecated since February 2026.
Build or Buy Performance Monitoring & App Audits on Shopify?
Measurement is free on Shopify; storefront speed comes from an audit-and-remediation program, not a speed app.
Ready to stop maintaining five copies of one theme?
We price the honest version of this: what the licenses actually cost, what the per-store customization costs, and whether one shared codebase is worth commissioning at your store count.
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.