Shopify custom app vs App Store app: which does your store need?
An App Store app is a product built for thousands of stores and rented monthly. A custom app is built for your store and owned by you. How they differ on cost, plan rules, data and upkeep, and when each one wins.

The short answer
- A public Shopify app is listed on the App Store, reviewed by Shopify and built for many stores. A custom app is built for one store and isn't listed.
- Stores on any plan can use public App Store apps that contain Shopify Functions, but only Shopify Plus stores can use custom apps that contain Function APIs.
- Checkout UI extensions on the Thank-you and Order status pages work on every plan. Extensions inside the information, shipping and payment steps need Shopify Plus.
- Shopify's Help Center notes that custom apps created in the Shopify admin don't support App Bridge, so Functions-based custom apps should be created through the Dev Dashboard.
- A custom Shopify app costs ₹80,000 to ₹6,00,000, or $1,600 to $10,000, on Tanuj Rajput's published pricing.
Want this done rather than explained? work with a Shopify Plus developer
An App Store app is a product built for thousands of stores. You rent it monthly and its vendor maintains it. A custom app is built for your store alone. You pay once, you own the code, and you or your developer maintain it. Most stores should use App Store apps for common jobs and a custom app only where their logic, systems or costs are their own.
Both kinds use the same Shopify APIs. The differences are in who they're built for, how you pay, which plan they need, where your data lives and who fixes them when Shopify changes something.
How do custom and App Store apps differ?
| App Store (public) app | Custom app | |
|---|---|---|
| Built for | Thousands of stores | Your store |
| Listed on the App Store | Yes, after Shopify's review | No |
| How you pay | Usually a monthly fee, often rising with plan or volume | A one-time build, plus optional upkeep |
| Shopify Functions | Works on every plan | Needs Shopify Plus |
| Checkout extensions inside the checkout steps | Needs Shopify Plus | Needs Shopify Plus |
| Checkout extensions on Thank-you and Order status pages | Every plan | Every plan |
| Where your data lives | The vendor's servers | A database set up for your business |
| Who owns the code | The vendor | You |
| Who maintains it | The vendor | You, or your developer |
The plan rule most people get wrong
Shopify's docs say stores on any plan can use public App Store apps that contain Functions. Only Shopify Plus stores can use custom apps that contain Function APIs.
So the same discount logic can work on the Basic plan inside a public app, and need Plus as a custom app. The rule turns on how the app is distributed, not on what the Function does. Before you commission custom Functions, check whether a public Functions app already does the job on your plan. I walk through examples in Shopify Functions: real examples worth building and the plan rules in Shopify checkout customization on Plus.
One more detail if you're getting quotes. Shopify's Help Center notes that custom apps created in the Shopify admin don't support App Bridge, so Functions-based custom apps should be created through the Dev Dashboard. A developer quoting a quick admin-created app for Functions work hasn't checked.
When does an App Store app win?
When the job is common and the vendor does work you'd never want to own:
- Product reviews. Moderation, photo reviews and syndication are the vendor's product.
- Subscriptions. Recurring payments and failed-payment retries need the vendor's infrastructure.
- Email, SMS and WhatsApp marketing. Deliverability and compliance are the product.
- Shipping aggregators. The courier integrations are the product.
- Standard discounts and bundles, especially on a non-Plus plan, where a public Functions app is the only way to use Functions.
If the fee is small and flat and the app doesn't slow your storefront, keep it. My notes on when a custom feature beats an app subscription go feature by feature.
When does a custom app win?
When the logic, the systems or the costs are yours:
- Your own logic. WeMust needed live pricing rules for custom print orders. I built the order flow, the pricing rules and automated invoices.
- Your own systems. For Mum & You, I rebuilt subscription flows on Shopify's APIs, with private sync workflows, during their Magento to Shopify Plus migration.
- Your own data. For a D2C brand, I built a private dashboard app with read-only Admin API access and webhooks. It syncs about 2,000 products and more than 100,000 orders into its own database for forecasting, margin and vendor purchase orders. No App Store app knew that brand's cost prices or vendor rules.
- Your own costs. An app fee that climbs with every order you take costs more each month you do well. Above a certain size, a one-time build pays for itself.
What does each cost?
App Store apps range from free to several hundred dollars a month, and many price by plan or order volume. A custom app costs ₹80,000 to ₹6,00,000 in India, or $1,600 to $10,000 for international brands, on my published pricing. Most builds take 45 to 60 days. The full breakdown is in Shopify app development cost in India (2026).
After launch, a custom app needs hosting and a check-up at least once a year. Shopify releases a new API version every quarter and supports each one for at least 12 months.
Can a custom app become an App Store app later?
Technically yes, but plan it as a new project. An App Store product has to:
- handle many stores at once
- pass Shopify's review
- charge merchants through Shopify
- offer support
I build custom apps for single stores and don't build App Store products today. If that's what you're planning, you want a team that does it full time.
What I'd do
Search the App Store for the job first, and check whether the closest app works on your plan. If it does the job for a fair, flat fee, install it. If it doesn't fit, or needs workarounds your team repeats every week, a custom app is worth scoping.
See custom Shopify app pricing or start a brief with the job you need done.
Related reads
- Shopify app development cost in India (2026)
- Custom Shopify feature or app subscription: when building pays off
- Shopify Functions: real examples worth building
- Custom Shopify app vs Zapier vs an off-the-shelf app
Sources
Frequently asked questions
What is the difference between a custom app and a public app on Shopify?
A public app is listed on the Shopify App Store, reviewed by Shopify and built for many stores, and you usually pay for it monthly. A custom app is built for one store, isn't listed anywhere, has no monthly fee and is owned by the store. Both use the same Shopify APIs.Do custom Shopify apps need Shopify Plus?
Most don't. Integrations, admin tools and checkout extensions on the Thank-you and Order status pages work on every plan. A custom app needs Plus if it contains Shopify Functions, or if it adds checkout extensions inside the information, shipping and payment steps.Can a public App Store app use Shopify Functions on the Basic plan?
Yes. Shopify's docs say stores on any plan can use public App Store apps that contain Functions. The Plus requirement applies to custom apps that contain Function APIs. That's why a public discount or bundle app can work on Basic while the same logic as a custom app needs Plus.Is a Shopify private app the same as a custom app?
Close enough for most merchants. Shopify used to call single-store apps private apps and now calls them custom apps. They are built for one store and installed only there.Who owns the data in a custom Shopify app?
You do. A custom app stores what it needs in a database set up for your business, and the code and IP are assigned to you. A public app keeps your data on the vendor's servers under the vendor's terms, so export anything you need before uninstalling.Can a custom Shopify app be turned into an App Store app later?
Technically yes, but it's real work. An App Store product has to handle many stores, pass Shopify's review, charge merchants through Shopify and offer support. Treat it as a new project rather than a quick conversion.
Revision history· 1 entry
November 13, 2026
First published.
Last updated November 13, 2026







