deploteka ← All guides

By DeploTeka · Last updated July 18, 2026

How to install a Shopify app on multiple stores: the real options

Short answer: a single Shopify custom app can only be installed on multiple stores if those stores are in the same Shopify Plus organization. There is no supported way to install one custom app across stores owned by different merchants. If you're a vendor or agency running one app for many clients, your real options are: (1) a public App Store app, (2) an unlisted public app, (3) a separate custom-distribution app per client store, or (4) — historically — a merchant-created custom app per store, a path Shopify closed to new apps in January 2026.

This guide walks through each option honestly, including the one Shopify's docs describe but most forum answers miss.

Why is this confusing?

Because "custom app" has meant three different things over the years (admin-created legacy apps, Partner-Dashboard custom-distribution apps, and now Dev Dashboard apps), and because one 2023 change — multi-store install for Plus organizations — is routinely misread as "custom apps can now be installed anywhere." They can't.

The rule that decides everything: Shopify scopes custom-distribution apps to a single organization. Multiple stores, yes — but only inside one Plus org. Different merchants means different orgs, means a different app.

Option 1: A public app on the Shopify App Store

If your app is a general product for any merchant, the App Store is the intended path: one app, one codebase, unlimited installs, billing built in.

The cost: Shopify's app review (functional, UX, and API-usage requirements), an ongoing compliance surface, public exposure of your product, and App Store revenue share where applicable. For a genuinely public product this is the right answer. For a private tool you deploy for your clients — bespoke integrations, agency-built functionality, white-label products — it usually isn't: you don't want strangers installing it, and review cycles slow every release.

Choose this when: you're building a product for the open merchant market.

Option 2: An unlisted public app

Shopify supports public apps that are unlisted: they don't appear in App Store search, and merchants install them via a direct link. One app, many merchants, no public listing.

The catch: an unlisted app is still a public app. It goes through Shopify's app review and must meet public-app requirements — you're accepting the compliance and review burden of Option 1 to avoid only the visibility. You also can't switch a custom app to unlisted later: Shopify's distribution docs are explicit that the distribution method can't be changed after you select it.

Choose this when: you want one multi-merchant app, can pass and keep passing app review, and simply don't want a public listing.

Option 3: One custom-distribution app per client store

This is the option vendor forums keep circling without naming: instead of one app installed everywhere, you create a separate custom-distribution app for each client store, all running your same backend and codebase. Each app lives in your Partner organization, gets its own API credentials, and installs on exactly one merchant's store (or one Plus org) via an install link.

Why vendors end up here:

  • No app review — you ship on your schedule.
  • Your client never has to create anything in their admin or hand you tokens.
  • Clean isolation: per-store credentials, per-store scopes, revocation per client.
  • It works for non-Plus merchants, which the multi-store install path doesn't.

The honest downside: you now operate N apps. Creating each app, configuring scopes and webhooks, deploying every release N times, rotating N sets of credentials, and noticing when one install breaks — that's real operational load, and doing it by hand stops scaling somewhere around the tenth store.

Where DeploTeka fits: this is exactly the model DeploTeka automates — it creates a dedicated custom-distribution app per client store from one codebase, in your own Partner organization, and handles fleet-wide deploys, health monitoring, and credential management. We run our own pixel product across roughly 94 client stores this way, so the tooling exists because we needed it first.

Choose this when: you're a vendor or agency running one product across many client stores and you want control without App Store review.

Option 4: Merchant-created custom apps (the legacy path — now closed to new apps)

For years, the workaround was to have each merchant create a "custom app" in their own admin (Settings → Apps → Develop apps) and send you the API token. It required no Partner org and no review — which is why so many integrations quietly ran on it.

What changed: as of January 1, 2026, new legacy custom apps can no longer be created. Existing ones keep working, but every new store onboarded needs an app created through the Dev Dashboard, using OAuth client-credentials instead of a permanent token. The new flow also assumes the app and store belong to the same organization — which is awkward when the "developer" is an outside vendor, a pain point actively discussed on Shopify's dev forums.

If your multi-store setup runs on merchant-created legacy apps today, it still works — but it no longer scales to new clients. See our companion guide on the January 2026 deprecation.

Special case: multiple stores in one Shopify Plus organization

If — and only if — all target stores belong to a single Plus organization, one custom-distribution app can be installed on all of them. When generating the install link, enable "Allow multi-store install for one Plus organization"; apps created before July 26, 2023 need Partner Support to unlock this. This is the right answer for a brand running several of its own storefronts. It does nothing for the agency/vendor case, because your clients are separate organizations.

Decision table

Your situationBest option
Product for any merchant, open marketPublic App Store app
One app, many merchants, no public listing, review is acceptableUnlisted public app
Your product on many client stores, no review, full controlOne custom-distribution app per store (automatable)
All stores in one Plus organization you/your client ownOne custom app, multi-store install enabled
Existing merchant-created legacy appsKeep running; new stores need the Dev Dashboard path

Sources: [Shopify — About app distribution](https://shopify.dev/docs/apps/launch/distribution), [Shopify — Select a distribution method](https://shopify.dev/docs/apps/launch/distribution/select-distribution-method), [Shopify changelog — multi-store install for Plus](https://shopify.dev/changelog/install-custom-apps-on-multiple-shopify-plus-stores), [Shopify changelog — legacy custom apps after Jan 1, 2026](https://changelog.shopify.com/posts/legacy-custom-apps-can-t-be-created-after-january-1-2026).

Frequently asked questions

Can one Shopify custom app be installed on multiple stores?

Only if all the stores belong to the same Shopify Plus organization. A custom-distribution app cannot be installed on stores owned by different merchants or different organizations — that limit is enforced by Shopify, not by the app.

Can I distribute a Shopify app to many merchants without the App Store?

Not with a single custom app. Your options are an unlisted public app (still goes through Shopify's app review), or a separate custom-distribution app per merchant store running your same codebase.

What replaced merchant-created legacy custom apps?

Since January 1, 2026, new custom apps can no longer be created from the Shopify admin. New custom apps are created in the Dev Dashboard and authenticate with OAuth client-credentials instead of permanent admin tokens.

Is there a limit on how many apps a Partner organization can create?

Shopify doesn't publish a hard cap that affects normal use. Vendors run tens to hundreds of custom-distribution apps in one Partner organization; the practical limit is operational — configuring, deploying, and monitoring each one.