Plus's 100 Themes vs. a Multi-Tenant CMS for Sub-Brands?
Plus's 100-theme allowance is not the constraint, so sub-brand storefronts are a BUILD: one shared theme with settings-driven brand variants. Shopify documents up to 100 themes per account and requires a theme license for each production store (verified Sep 2026). Page builders at $24–$499/month fix page sprawl inside one store, and only Shogun's top tier names cross-store content syncing (verified Sep 2026). Divergent theme code is what costs you, not the theme count.
Your profile — see how the verdict shifts
- Confidence
- High — Shopify's Plus plan page states that the plan supports adding up to 100 themes to your Shopify account, alongside 1 TB of file storage per store, up to 200 locations, up to 25 Hydrogen storefronts and unlimited staging stores (verified Sep 2026). The expansion-stores documentation states that a Plus organization can have a maximum of ten stores on its contract at no additional cost, one main store and nine expansion stores, that theme licenses are required for each individual production store with staging stores exempt, that apps are billed per store rather than per organization, and that store settings, products, collections and inventory aren't synced between stores. The page-builder market is genuinely healthy and well reviewed: PageFly at 4.9★ on 5,892 reviews, GemPages at 4.9★ on 4,205 reviews and Shogun at 4.8★ on 1,972 reviews, all Built for Shopify. Reading all three price cards on 2026-09-05 established the distinction this decision turns on: GemPages and PageFly publish pages within the store they are installed on, and only Shogun's $499/month Advanced tier names content syncing between stores. No listing manages themes across a portfolio, because a theme is store-scoped by design.
- Reference scenario
- $20M–$150M GMV · Shopify Plus · one main store plus four expansion stores for sub-brands · 4–8 seasonal or campaign theme variants a year · shared design language · agency or in-house front-end bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| One store, two or three seasonal looks a year | BUY | A page builder at $24–$59/month handles a seasonal campaign as pages rather than as a duplicated theme (verified Sep 2026). Duplicating a theme for a six-week campaign creates a fork somebody has to reconcile in January. |
| One store, five or more live theme variants for sub-brands or tests | BUILD | Five duplicated themes means five copies of every bug fix and every Online Store 2.0 upgrade. One theme with brand variants in theme settings and metaobjects keeps the divergence in data instead of in code, and the 100-theme allowance stops being relevant. |
| Plus organization, three to nine expansion stores, one sub-brand per store | BUILD | Themes don't cross stores and neither does content: store settings, products, collections and inventory aren't synced between stores, and a theme license is required per production store. One repository deployed to each store with the CLI's environments is the only way a fix ships once. |
| Marketing publishes identical content to several stores without developer time | CUSTOMIZE | Shogun's $499/month Advanced tier is the only plan among the three leading builders that names content syncing between stores (verified Sep 2026), and apps bill per store. Pair it with the shared theme: the theme holds the brand system, the builder holds the campaign content. |
What Plus Theme Allowance for Sub-Brands Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | A design change made once in a shared theme reaches every sub-brand storefront on the next deploy, instead of being reapplied and retested per store. |
| Customer experience | Medium | Shoppers moving between sub-brands in the same portfolio meet the same cart, account and checkout patterns, which removes the small frictions that forked themes introduce quietly. |
| Revenue — indirect | Medium | A conversion improvement proven on one storefront rolls out to the whole portfolio in one release rather than being re-implemented per brand months later. |
| Data & insight | Medium | Brand variation stored in metaobjects and theme settings is structured data you can query across storefronts, so merchandising can report on what each sub-brand actually publishes. |
Spend ceiling: Size the spend against divergence, not against the theme count. The 100-theme allowance costs nothing to sit inside, so the money is only justified when the same change is being made three or more times. A $25,000–$70,000 shared theme (Deploi estimate, illustrative) earns out on maintenance and consistency, never on avoided subscriptions.
What buying enables (top apps)
- + Campaign and landing pages published by marketing in an hour, with A/B testing on paid tiers
- + A category with real evidence behind it: 1,972 to 5,892 reviews across the three leading builders, all Built for Shopify
- + Cross-store content syncing on Shogun's $499/month Advanced tier, the only listed plan naming it (verified Sep 2026)
- + Zero front-end engineering to keep a seasonal look on schedule
What building additionally unlocks
- + One fix, one deploy, every storefront, instead of the same change applied per store
- + A brand system encoded as tokens and components that new sub-brands inherit on day one
- + Sub-brand variation held as queryable Shopify data in metaobjects rather than in forked Liquid
- + Storefront rendering with no vendor layer in the critical path across the portfolio
Find Your Verdict in 3 Questions
Do your sub-brands live in separate stores in a Plus organization?
Yes: Go to question 2.
No: Go to question 3.
Does the same design change currently have to be applied store by store?
Yes: Your verdict: BUILD. One shared theme repository deployed per store with the CLI's environments costs $25,000–$70,000 (Deploi estimate, illustrative) and turns five fixes into one.
No: Your verdict: CUSTOMIZE. Keep the stores independent and use Shogun's $499/month cross-store content syncing for the content marketing genuinely shares (verified Sep 2026).
Are five or more theme variants live in one store for sub-brands, seasons or tests?
Yes: Your verdict: BUILD. Move the variation into theme settings and metaobjects so the 100-theme allowance stops being the thing you manage.
No: Your verdict: BUY. A page builder at $24–$59/month covers seasonal campaigns without duplicating a theme at all (verified Sep 2026).
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 page builder is live the afternoon it installs, while a shared theme with brand variants and a deployment pipeline is an estimated 8–14 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Page builders run $24–$499/month and bill per store in a Plus organization (verified Sep 2026), so five stores means five subscriptions; a shared theme carries upkeep and no per-store licence beyond Shopify's own. | ||
| Maintenance & upgrades | The decisive line: a fix applied to five divergent themes is five fixes and five regression passes, while the same fix in one repository ships to every store from a single commit. | ||
| Switching & exit | Page-builder pages are stored in the vendor's structure and often revert to unstyled blocks on uninstall; a shared theme's sections and metaobject content stay in Shopify whatever you do next. | ||
| Risk | |||
| Vendor risk | The three leading builders carry 1,972 to 5,892 reviews each and are Built for Shopify, so vendor risk here is low by category standards; a theme you own has none. | ||
| Security & compliance surface | A builder injects its own rendering layer into storefront pages under its App Store permissions, while a theme runs inside Shopify's own rendering with nothing extra installed. | ||
| Platform-deprecation exposure | Builder output has to keep pace with Online Store 2.0 and theme app extensions on the vendor's schedule; a theme you maintain moves on yours, and Shopify's theme architecture is a first-class primitive. | ||
| Value | |||
| Fit to requirement | A builder produces pages that look like the brand you configured it for, while a shared theme encodes the brand system itself: tokens, components and layout rules each sub-brand inherits. | ||
| Time to market | A campaign page ships in an hour with a builder and a new sub-brand storefront takes weeks with a theme, which is why most portfolios end up running both. | ||
| Performance & scale | Builder-rendered pages add a vendor layer to the critical path on every store, while a native theme renders through Shopify's own pipeline with the same code across the portfolio. | ||
| Data ownership & AI-readiness | Brand variants held in metaobjects and theme settings are structured Shopify data you can query and reuse across storefronts and feeds; builder page content lives in the vendor's own model. | ||
| Focus & opportunity cost | Front-end platform work competes with merchandising, though a portfolio that adds a sub-brand every year spends the investment once instead of every launch. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shogun — Landing Page Builder | Live — 4.8★ on 1,972 reviews; Built for Shopify. The only builder among the three whose price card names content syncing between stores, and that sits on the top tier alone. For a sub-brand portfolio that is the feature that matters, because store settings, products and collections aren't synced between stores natively (verified Sep 2026). | Draft Mode free (create drafts, no publishing); Build $39/month or $372/year (25 published pages); Grow $199/month or $1,908/year (unlimited published pages); Advanced $499/month or $4,788/year (content syncing between stores); 10-day trial (verified Sep 2026) | Marketing teams publishing the same campaign content into several stores in a Plus organization |
| PageFly ✦ AI Page Builder | Live — 4.9★ on 5,892 reviews; Built for Shopify. The most-reviewed builder in the category, and a single-store tool: pages publish in the store where the app is installed. It reduces the reason to duplicate a theme for a campaign, and does nothing about a theme portfolio spread across expansion stores (verified Sep 2026). | Free (10 AI credits, 320+ templates); Builder $24/month (5 published slots, 80 AI credits, A/B testing); Accelerate $99/month (unlimited published pages, 320 AI credits, heatmaps and analytics); Enterprise $299/month (1,600 monthly credits, priority support) (verified Sep 2026) | Campaign and landing pages inside one store, with A/B testing on the paid tiers |
| GemPages Landing Page Builder | Live — 4.9★ on 4,205 reviews; Built for Shopify. Single-store like PageFly, with unlimited published pages from the entry paid tier upward. Useful for keeping seasonal work out of theme duplication; not a multi-store content system, and apps bill per store in a Plus organization (verified Sep 2026). | Free to install (1 published page); Build $29/month (unlimited published pages, CRO templates, 300 AI sections); Optimize $59/month (sales funnels, post-purchase upsells, unlimited AI features); Enterprise $199/month (priority video call support) (verified Sep 2026) | High-volume campaign pages in a single store on a low monthly fee |
| Shared theme with brand variants (custom) | Build lane — One Online Store 2.0 theme in a repository, with each sub-brand's logo, palette, typography, navigation and homepage composition held in theme settings and metaobjects rather than in a forked copy of the code. Deployed to each production store with the Shopify CLI's environments in a shopify.theme.toml file, so a fix ships once and lands everywhere. | $25,000–$70,000 one-time plus roughly 15–20% of build cost per year in upkeep (Deploi estimate, illustrative) | Portfolios where the same design system has to hold across several sub-brands and keep holding |
The Build Path
- Separate the brand system from the brand: Write down what every sub-brand shares (grid, components, cart behavior, PDP structure) and what each one owns (logo, palette, type, tone, navigation, homepage composition). The shared half becomes theme code. The owned half becomes theme settings and metaobject entries a merchandiser edits. Getting that line wrong is the single reason shared-theme projects fail.
- One repository, environments per store: Configure a shopify.theme.toml file with an environment per store, then deploy with the CLI by passing the environment name. Development, staging and production instances are the documented use case, and a Plus organization gets unlimited staging stores to rehearse against. Theme licenses are required per production store, and staging stores are exempt.
- Push what varies into metaobjects, not into forks: Metaobjects hold sub-brand content that would otherwise justify a code fork: brand stories, size guides, care instructions, campaign modules. Sections read them by handle, which means adding a sub-brand becomes a data exercise. Anything that needs a genuinely different layout gets a section variant in the shared theme, never a duplicated theme.
- Keep a page builder for campaigns, deliberately: The shared theme should not become the bottleneck for a Black Friday landing page. Leave a builder installed on the stores marketing actually campaigns in, at $24–$99/month per store (verified Sep 2026), and set the rule explicitly: builder pages for time-boxed campaigns, theme sections for anything that outlives one season.
- Effort band
- $25,000–$70,000 for the shared theme, sub-brand variant system, metaobject content model and per-store deployment pipeline — Deploi estimate (illustrative); lands in the $25–75K contact-form band
- Typical timeline
- 8–14 weeks for the first two storefronts, then 1–3 weeks per additional sub-brand (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $3,750–$14,000/yr (Deploi estimate, illustrative) covering Online Store 2.0 upgrades, new section variants as sub-brands ask for them, and keeping the deployment pipeline current across every production store.
- What you own — and what you take on
- You own: the theme repository, the design tokens, the section library, the metaobject content model and the deployment pipeline. You take on: front-end release discipline across several live stores, a review process for section variants so the shared theme doesn't quietly fork again, and a theme license per production store.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $4,000–$15,000 (a premium theme licensed and customized per production store) | $25,000–$70,000 (shared theme repository and variant system) |
| Years 1–3 (recurring) | $21,600–$46,600 in builder subscriptions plus $30,000–$90,000 maintaining five divergent themes | $11,250–$42,000 upkeep plus $2,600–$7,200 for one builder on the main store |
| 3-year total | ≈$55,600–$151,600 | ≈$38,850–$119,200 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Reference scenario: one main store plus four expansion stores, one sub-brand each, with a page builder installed on every store.
- † Buy column keeps five separately maintained themes plus per-store builder subscriptions; build column is one shared theme plus a builder retained on the main store; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Apps are billed per store rather than per organization, so a $199/month builder across five stores is $995/month (verified Sep 2026)
- — Only the top Shogun tier names content syncing between stores, so the cross-store requirement lands on the $499/month plan and nowhere cheaper (verified Sep 2026)
- — Builder pages often degrade to unstyled content when the app is uninstalled, which makes a builder a long-term dependency for anything permanent
- — A page builder does nothing about theme divergence, so the maintenance problem stays exactly where it was
On the build path
- — The shared theme becomes a release bottleneck if marketing has no fast lane, which is why a builder stays installed for campaigns
- — Drawing the shared-versus-owned line badly recreates the fork inside one repository, as endless conditionals per sub-brand
- — Theme licenses are still required for each individual production store, and only staging stores are exempt
- — ~$3,750–$14,000/yr in upkeep (Deploi estimate, illustrative)
What Merchants Say
The recurring story in multi-brand Plus organizations is a fix that had to be applied five times: once per store, each theme slightly forked from a shared ancestor nobody has looked at since launch.
Low-star reviews on page builders cluster on the exit rather than the editor: pages that render as unstyled blocks once the app is removed, and content locked in a structure the theme can't read.
If You Change Your Mind Later
If you bought and outgrow it
Uninstalling a page builder is the risky direction: published pages commonly lose their layout and revert to raw content, and the vendor's page structure has no equivalent in the theme. Export or rebuild anything permanent as theme sections before you cancel, and keep campaign work in the builder where a short life expectancy is the point.
If you built and want out
Nothing strands. The theme lives in your repository, brand variants live in Shopify theme settings and metaobjects, and any store can keep running its current published theme indefinitely. A retreat to per-store themes is a fork of code you already own, which is the cheapest exit on this page.
When This Answer Changes
We're watching for:
- ▸ Any change to Shopify's documented 100-theme allowance or the per-production-store theme licence requirement (verified Sep 2026)
- ▸ Shopify shipping native cross-store content or theme sharing for organizations, which would move Shogun's $499/month syncing tier to WAIT (verified Sep 2026)
- ▸ A sixth or seventh sub-brand joining the portfolio, since a Plus contract covers ten stores at no additional cost and the maintenance curve steepens well before that
Verdict change log:
No changes since first publication (September 2026).
Common Questions
How many themes can a Shopify Plus store have?
Shopify Plus supports adding up to 100 themes to your Shopify account (verified Sep 2026). Theme licenses are required for each individual production store in a Plus organization, and staging stores are exempt from that requirement. A Plus contract covers ten stores at no additional cost: one main store and nine expansion stores. The theme count is generous; the license and store limits bind first.
Does a page builder solve sub-brand theme sprawl?
Page builders solve page sprawl inside one store, not theme sprawl across a portfolio. GemPages at $29–$199/month and PageFly at $24–$299/month build landing pages in the store where they are installed (verified Sep 2026). Shogun's $499/month Advanced tier is the only plan among the three that names content syncing between stores, and apps bill per store in a Plus organization.
What does a shared theme for sub-brands cost to build?
A shared theme for sub-brands costs $25,000–$70,000 one-time plus roughly 15–20% of build cost per year (Deploi estimate, illustrative). Scope covers one theme repository, brand variants driven by theme settings and metaobjects, and deployment to each store with the Shopify CLI's environments in a shopify.theme.toml file. Nine expansion-store themes maintained separately cost nine times every fix.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Audit every live and unpublished theme across the portfolio and record how far each has forked from its ancestor
- Draw the shared-versus-owned line explicitly, component by component, with merchandising in the room
- Model sub-brand variation as theme settings and metaobject entries before writing any section code
- Set up a shopify.theme.toml environment per store and rehearse deployments against staging stores
- Set the rule for page builders in writing: campaigns in the builder, anything permanent in a section
If you're going with BUY
- Pick one builder for the whole organization so five stores don't end up on three vendors
- Check the exit behavior on a test page before you publish anything permanent with it
- Budget per store, since apps bill per store rather than per organization
- Reserve the cross-store syncing tier for the stores that genuinely share content, not all of them
- Diary a re-decision when a design change first has to be applied store by store
Official Docs & Sources
- Shopify Plus plan features (100 themes, staging stores) — Shopify Help Center
- Expansion stores, theme licenses and per-store app billing — Shopify Help Center
- Theme CLI environments (shopify.theme.toml) — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Will Your Apps Survive a Move to Hydrogen?
Reviews, upsell and personalization apps that render through theme app extensions have nowhere to go on a Hydrogen storefront, because there is no Liquid theme.
Shopify Plus Multipass or a Modern SSO App?
Multipass needs legacy customer accounts, deprecated 2026-02-26 with the sunset date pending, and the only Shopify SSO app is delisted. Connect your IdP instead.
Should You Run Hydrogen and Your Theme in Parallel?
Hydrogen and an Online Store 2.0 theme can run against one catalog and cart. Shopify documents the compatibility; the routing layer between them is yours to build.
Should You Go Headless on Shopify or Stay on Your Theme?
A headless storefront pays off for a small minority of mid-market Shopify merchants; a well-built theme delivers most of the gains without the replatform.
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 the same theme five times?
We start by drawing the line between what every sub-brand shares and what each one owns, because that line is the whole architecture. Then we scope one theme repository with brand variants in settings and metaobjects, a deployment environment per store, and a clear rule for when a campaign belongs in a page builder instead.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Plan allowances and store limits quoted from Shopify's help documentation as of September 2026. 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.