Does One App Subscription Cover Every Plus Expansion Store?
Buying the same app once per store stays cheaper below the crossover, because apps are billed on a per-store basis rather than for the entire organization (verified Sep 2026). Five stores means five subscriptions. Replacing one app with a custom app costs $25,000 to $75,000 (Deploi estimate, illustrative), which pays back only when that single job runs past roughly $1,000 a month across the portfolio.
Your profile — see how the verdict shifts
- Confidence
- High — Shopify's expansion-stores page, read on 2026-09-05, states that apps are billed on a per-store basis rather than for the entire organization, and that a Plus contract covers a maximum of ten stores, one main and nine expansion, at no additional cost. No App Store listing changes that: a subscription is charged per store install through Shopify's billing, so an organization-wide license is a vendor sales conversation rather than a product. Category browsing found nothing addressing cross-store license bundling, because this is a billing-policy gap, not a feature gap an app could fill. The crossover figure is Deploi's own cost reasoning, not a Shopify position.
- Reference scenario
- $20M–$100M GMV · Plus organization with five production stores · 18–25 paid apps per store · roughly $2,000–$4,000 a month of app spend per store (illustrative) · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Two production stores | BUY | Doubling a stack is the cheapest thing you will do all year. A second subscription on a $100 a month app costs $3,600 over three years (illustrative), which no build touches. |
| Three to five stores, no app above $200 a month (illustrative) | BUY | The multiplier hurts but the per-job numbers stay small. Audit the stack per store, cut what store three never needed, and negotiate the two or three expensive vendors instead of writing code. |
| Six to ten stores on one Plus contract | DEPENDS | At eight installs, a $300 a month app is $28,800 a year (illustrative) for one job. Two or three jobs at that level fund a custom app that installs everywhere and bills nothing per store. |
| A single app above $500 a month per store (illustrative) | BUILD | One expensive app across five stores runs $30,000 a year (illustrative) before usage tiers. If the requirement is stable and narrow, a custom app pays for itself inside two years and one release serves every store. |
What Per-Store App Subscription Billing Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | Every app in the stack is configured, updated and supported once per store, so the operating load of the portfolio grows with store count rather than with revenue. |
| Revenue — indirect | Medium | Money released by cutting duplicated subscriptions funds merchandising, content and paid acquisition, which are the lines that actually move sales. |
| Data & insight | Medium | Five vendor databases hold five slices of one operation, so portfolio questions get answered by exporting from each store and reconciling by hand. |
| Customer experience | Low | Shoppers never see app billing, but they do see the drift it causes when the same app is configured differently on each storefront. |
Spend ceiling: Spend to the multiplier, not the sticker price. A $50 a month app across ten stores is a $6,000 a year decision (illustrative) and deserves that much scrutiny; a $500 a month app on two stores deserves less. Rank the stack by multiplied cost before anyone proposes building.
What buying enables (top apps)
- + Same-day capability on every store in the organization, with no engineering and no release process
- + A vendor absorbing API version changes, support and roadmap across all your installs at once
- + Free first-party coverage for automation through Shopify Flow, which never bills per store (verified Sep 2026)
- + A cancellable line per store, so a pilot market that fails costs one subscription rather than a build
What building additionally unlocks
- + Zero marginal cost per additional store, so opening store six adds no recurring software line
- + One release across the whole organization, with a revert available, instead of five configurations drifting apart
- + One data schema covering every store, which is what portfolio reporting and AI-assisted analysis actually need
- + A narrow surface matched to the job, with none of the vendor features you pay for five times and never use
Find Your Verdict in 3 Questions
Does the app in question cost more than $200 a month per store (illustrative)?
Yes: Go to question 2.
No: Your verdict: BUY — cut the installs store three never needed and keep paying; a cheap app across a few stores never funds a build.
Will the job run on six or more stores within the next two years?
Yes: Your verdict: BUILD — a custom app installs everywhere with no per-store fee, and one release serves the whole organization.
No: Go to question 3.
Is the requirement stable and narrow enough to specify in a page?
Yes: Your verdict: DEPENDS — get portfolio pricing from the vendor first, then compare it with $25,000 to $75,000 for a custom app (Deploi estimate, illustrative).
No: Your verdict: BUY — a moving requirement belongs with a vendor whose roadmap you rent rather than in code you maintain five times.
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 | An app installs on each store the same afternoon; a custom app runs 8 to 14 weeks before the fifth store has it. | ||
| Recurring fees | The app fee multiplies by store count forever, and usage tiers are computed per store, so portfolio volume never earns a discount; a custom app adds no per-store line at all. | ||
| Maintenance & upgrades | The vendor absorbs API changes, support and roadmap across all five installs; owning the app means owning all of that for every store at once. | ||
| Switching & exit | Uninstalling an app on five stores is five clicks and five data exports; a custom app has no vendor to leave, only code to retire. | ||
| Risk | |||
| Vendor risk | A price change, an acquisition or a sunset hits every store in the portfolio on the same day, which is five times the exposure of a single-store merchant. | ||
| Security & compliance surface | Each install grants its own scopes on its own store, and Shopify offers no consolidated cross-app permissions view, so the review burden multiplies with store count. | ||
| Platform-deprecation exposure | Public apps track Shopify's API versions for you, while a custom app containing Shopify Functions also carries a plan gate: only Plus stores can run those. | ||
| Value | |||
| Fit to requirement | An app fits the average merchant; a custom app fits the one job your five stores actually repeat, with none of the surface you never use. | ||
| Time to market | Install today across the portfolio versus a quarter of build before store one benefits. | ||
| Performance & scale | Adding store six costs another subscription on the app path and nothing on the build path, so the build's economics improve exactly as the portfolio grows. | ||
| Data ownership & AI-readiness | Five vendor databases hold five slices of the same operation; one custom app writes one schema you can query across the whole organization. | ||
| Focus & opportunity cost | Every hour spent rebuilding a commodity app is an hour not spent on merchandising, and most stack lines are not worth owning. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Per-store app billing (Shopify organization) | Native — Organization membership consolidates roles and analytics, never billing. Apps are billed on a per-store basis rather than for the entire organization, exactly as they would be across unrelated merchants, and app settings don't travel between stores either. | Up to nine expansion stores are included on the Plus contract at no additional cost; every paid app bills again per store (verified Sep 2026) | Budgeting store two before it opens |
| Shopify Flow | Native — Per july 2026 research. Shopify's own automation layer — the WAIT option to exhaust first | Free at entry volumes; scales with volume (verified Sep 2026) | Retiring paid automation apps across a portfolio |
| Vendor portfolio or organization pricing | Category — Not something you can install. Because a subscription is charged per store install, an organization-wide license only exists as a negotiated contract, and no App Store listing publishes one. Ask before store two opens, while your install count is still leverage. | Quote-based; no listing publishes an organization-wide license (verified Sep 2026) | Portfolios with two or three expensive apps and a renewal date coming |
| Custom app across the organization | Build lane — One codebase, installed on each store, with no per-install vendor fee. Releasing an app version replaces the active version served to every store that has it installed, and you can revert to a previous version at any time (verified Sep 2026). Custom apps containing Shopify Function APIs run on Plus stores only. | $25,000–$75,000 one-time plus roughly 15–20% a year in upkeep (Deploi estimate, illustrative) | One stable, expensive job repeated across six or more stores |
The Build Path
- Audit the stack per store, then price the repeat: List every paid app by store and multiply. Most portfolios find that three or four lines carry most of the multiplied cost, and that a third of the stack on store three was inherited from store one and never used. Cutting comes before building.
- Move the automation jobs into Flow first: Shopify Flow is free on Basic, Grow, Advanced and Plus (verified Sep 2026), so tagging, routing and alerting jobs that a paid app performs per store can often be rebuilt as workflows for nothing. Plus stores can also use tasks published by custom partner apps.
- Build one custom app and install it on every store: A custom app carries no per-install fee. One release replaces the active version on every store that has it installed, and reverting is a single action, so the portfolio stays on one version instead of five configurations. Functions-based logic inside it needs Plus.
- Effort band
- $25,000–$75,000 to replace one app's job with a custom app across the portfolio — Deploi estimate (illustrative); lands in the $25–75K contact-form band
- Typical timeline
- 8–14 weeks to a custom app installed and configured on every store (Deploi estimate, illustrative)
- Maintenance, honestly
- Roughly 15–20% of build cost a year, about $4,000–$15,000/yr (Deploi estimate, illustrative): API version bumps, scope changes, and the support a vendor used to absorb for you.
- What you own — and what you take on
- You own: the app, its release cadence across every store, its data schema and its roadmap. You take on: the support desk, the security review and the upgrade work the vendor was doing five times over.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$2,500 | $25,000–$75,000 |
| Years 1–3 (recurring) | $36,000 | $12,000–$45,000 (maintenance) |
| 3-year total | ≈$36,000–$38,500 | ≈$37,000–$120,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: one representative app at $200/month, installed on five production stores, held flat for three years; real vendors raise prices and usage tiers are computed per store.
- † Build column: one custom app replacing that job, installed on all five stores, with annual upkeep; three-year horizon.
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), so every price rise multiplies by store count
- — Usage tiers are computed per store, so a portfolio doing real volume never reaches the discount a single big store would get
- — Settings don't travel between stores, so each install is configured again and drifts from the others
- — Each install grants scopes on its own store and Shopify offers no consolidated cross-app permissions view, so the security review repeats per store
On the build path
- — Shopify's app review covers listed and unlisted public apps (verified Sep 2026); a custom app you build is outside that pipeline, so your review is the only one
- — Releasing an app version replaces the active version on every store that has it installed, so a bad release lands everywhere at once, though reverting is available
- — Custom apps containing Shopify Function APIs run on Plus stores only, which matters if a lower-plan store joins the portfolio later
- — Roughly 15–20% of build cost a year, about $4,000–$15,000/yr (Deploi estimate, illustrative), plus the support the vendor used to absorb
What Merchants Say
Merchants opening a free expansion store describe the surprise as the second app invoice rather than the store itself: a stack they already paid for started billing again on day one.
The other recurring theme is configuration drift: the same app set up five times ends up with five slightly different settings, and nobody can say which store is correct.
If You Change Your Mind Later
If you bought and outgrow it
Leaving an app across five stores means five uninstalls and five data exports, and the export completeness is whatever each plan allows. Nothing is technically hard here; the cost is that five stores of configuration and history disappear at once, so export before you cancel.
If you built and want out
A custom app has no vendor to leave, only code to retire. Uninstall it per store, keep the data in your own schema, and fall back to a public app if the requirement changes shape. The exit is cheap, which is a fair part of the build case.
When This Answer Changes
We're watching for:
- ▸ Shopify moving app billing from per-store to organization-level, which would delete this decision for every multi-store merchant
- ▸ App vendors publishing multi-store or portfolio plans on their listings rather than quoting them privately
- ▸ Your portfolio passing six stores, where the multiplier turns two or three stack lines into build candidates
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Do Shopify apps bill per store or per organization?
Per store. Shopify states that apps are billed on a per-store basis rather than for the entire organization (verified Sep 2026), so a five-store portfolio pays five subscriptions for the same app. A Plus contract covers a maximum of ten stores, one main and nine expansion, at no additional store cost, but that allowance covers stores only, never their apps.
How many stores make a custom app cheaper than an app subscription?
Roughly six stores, for a job priced around $200 a month per store. Five installs at that price cost $36,000 over three years (illustrative), which sits inside the $25,000 to $75,000 range for a custom app (Deploi estimate, illustrative). Fewer stores, or a cheaper app, and buying wins. More stores, or usage-based tiers, and building wins sooner.
Can an app vendor give you one price for all your stores?
Sometimes, but only by contract. No App Store listing publishes an organization-wide license, because a subscription is charged per store install, so portfolio pricing happens in a sales conversation. Ask before store two opens, when your install count is still leverage, and put the rate in writing for all ten stores your Plus contract allows.
Your Next Steps
If you're going with BUY
- Export the app list and monthly cost for every store into one sheet, then multiply
- Cut the installs a store inherited but never used, before negotiating anything
- Ask your three most expensive vendors for portfolio pricing across all ten contract stores
- Standardize configuration per app so five installs stop drifting apart
- Re-run the multiplication the month before each new store opens
If you're going with BUILD
- Pick the single job with the highest multiplied cost and the most stable requirement
- Rebuild the automation parts in Flow first, since Flow is free on every store
- Scope the custom app narrowly, and keep Shopify Functions logic out if a non-Plus store may join
- Ship to one store, run it a month, then release to the rest of the organization
- Budget upkeep at roughly 15–20% of build cost a year and name an internal owner
Official Docs & Sources
- Expansion stores — Shopify Help Center
- Custom apps — Shopify Help Center
- Installing apps and reviewing permissions — Shopify Help Center
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 price your stack per store instead of per app?
We audit the portfolio line by line, find the jobs where the multiplier has already passed the crossover, and build the one custom app that replaces five subscriptions.
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.