Install another Shopify App Store app when the need is common, reversible, and already solved well by the ecosystem. Commission a custom app when the workflow is proprietary, spans multiple systems, creates security or ownership risk, or when stacking more apps would raise cost and complexity faster than it raises capacity. This article gives you a scorecard and a build-trigger ladder so you can make that call before you add another monthly subscription—or fund a build you do not need.
Key takeaways
-
Shopify treats public App Store apps and custom apps as different distribution models with different limits—especially around review, billing, and how many stores you can install on.
-
App sprawl usually fails quietly: duplicated features, overlapping permissions, fragile handoffs between tools, and ops teams who stop trusting the stack.
-
Use the App Sprawl Scorecard before every install. Build only when two or more high-weight triggers fire, not because a vendor demo looked polished.
-
A custom app should own one operational outcome. It should not become a second storefront architecture project by accident.
What “buy” and “build” actually mean on Shopify
On Shopify, “buy” usually means installing a public app from the Shopify App Store after reviewing ratings, compatibility, and access scopes. Shopify also distinguishes listed and unlisted public apps; both go through Shopify’s app review process.
“Build” means commissioning a custom app for your store—or for stores in the same Plus organization when custom distribution allows multi-store installs. According to Shopify’s app distribution documentation, distribution method is a permanent choice: public distribution can reach many merchants through the App Store, while custom distribution is limited to one store or multiple stores in the same Plus organization and cannot charge merchants through Shopify’s app billing system.
That distinction matters for buyers, not only developers. An App Store app is a product you rent. A custom app is an operational asset you own—with maintenance, hosting decisions, and a clearer need to define the problem before anyone writes code.
The App Sprawl Scorecard
Score each factor from 1 to 5. Higher scores push toward a custom app. Lower scores favor buying or configuring an existing App Store app first.
|
Factor |
Score 1 (buy first) |
Score 5 (build pressure) |
|
Workflow uniqueness |
Common ecommerce need already covered by mature apps |
Process is proprietary and central to how you win customers or fulfill orders |
|
System coupling |
Works inside Shopify with light configuration |
Must sync reliably with ERP, WMS, CRM, pricing engine, or custom SaaS |
|
Data sensitivity and ownership |
Standard store data with acceptable vendor scopes |
Customer, inventory, or pricing logic that you cannot afford to rent from multiple vendors |
|
Stack friction |
Current apps do not conflict; one install closes the gap |
You already have overlapping apps, broken handoffs, or manual CSV workarounds |
|
Change velocity |
Requirements are stable and vendor roadmaps are acceptable |
Rules change weekly and you need direct control over behavior |
Interpretation: Total 5–12 favors buy/configure. Total 13–18 is mixed—pilot an App Store option with a hard exit date. Total 19–25 typically justifies a scoped custom app, especially if system coupling and uniqueness both score 4+.
The Build Trigger Ladder
Do not jump to custom development because the scorecard is uncomfortable. Climb this ladder in order.
-
Define the outcome in one sentence. Example: “Every B2B reorder must inherit the account’s negotiated price list without staff editing line items.”
-
Search the App Store with constraints. Shopify recommends comparing ratings, review summaries, Built for Shopify badges, and installation compatibility before installing. Reject apps that demand broad scopes you cannot justify.
-
Pressure-test with a 14-day pilot. Measure whether the app removes manual work, conflicts with existing extensions, or creates new exceptions.
-
Map the gap, not the wishlist. Write the three behaviors the app cannot do and the business cost of each gap.
-
Commission a custom app only for the gap. Keep the successful App Store tools. Replace only the failing link in the chain.
This ladder prevents a common failure pattern: rebuilding an entire operations stack because one vendor feature is missing.
Buy vs build tradeoffs that actually matter
|
Decision lens |
App Store app |
Custom app |
|
Time to value |
Usually days if scopes and setup are clear |
Weeks, because discovery and acceptance criteria come first |
|
Control |
Vendor roadmap and settings |
Your rules, integrations, and release timing |
|
Cost shape |
Subscription plus possible usage fees |
Build cost plus ownership (hosting, updates, monitoring) |
|
Risk |
Vendor churn, feature overlap, permission creep |
Scope creep, unfinished ownership model, under-specified edge cases |
|
Best fit |
Commodity capabilities with strong market proof |
Differentiating workflows and durable integrations |
Shopify’s own distribution rules reinforce one more tradeoff: if you later want to productize an internal tool for many unrelated merchants, custom distribution is the wrong starting point. Distribution cannot be changed after selection, so treat “internal ops tool” and “future App Store product” as different projects.
Worked example: a mid-market catalog brand
Consider a hypothetical brand selling industrial supplies on Shopify. The team already uses apps for reviews, email capture, and returns. Ops now wants “smart replenishment alerts” that combine Shopify inventory, supplier lead times in a Google Sheet, and open purchase orders in an ERP.
App Sprawl Scorecard scores:
-
Workflow uniqueness: 4 (alert rules are company-specific)
-
System coupling: 5 (Shopify + Sheet + ERP)
-
Data sensitivity: 3 (operational, not payment data)
-
Stack friction: 4 (staff currently export CSVs twice a week)
-
Change velocity: 4 (supplier lead times change often)
Total: 20. The ladder still starts with an App Store search. If inventory-planning apps only cover Shopify-native data and cannot read the ERP purchase-order state cleanly, the gap is the integration layer—not “another planning UI.” The right custom scope is a narrow sync-and-alert app that writes exceptions into Shopify admin and Slack, while leaving reviews and returns apps alone.
This is also where architecture choices inside the custom app matter. Shopify’s App Home guidance recommends a developer-hosted iframe model for most apps that need server-side logic, webhooks, and multi-page workflows. A Shopify-hosted App Home UI extension can fit lightweight custom-distribution apps with no backend, but it is intentionally constrained. Do not force a backend-heavy replenishment workflow into the lighter model.
Mistakes, limitations, and exceptions
Common failure patterns
-
Buying for novelty. Installing an app because a competitor uses it, without measuring your own bottleneck.
-
Building a second theme. Turning a custom app brief into storefront redesign, checkout experiments, and CRM migration at once.
-
Ignoring uninstall cost. Every app adds permissions, theme embeds, pixels, or admin extensions. Shopify’s managing-apps workflow exists because cleanup is part of ownership.
-
Assuming custom is always safer. A poorly owned custom app can be riskier than a well-reviewed public app with a clear support path.
When the advice does not apply
If you are still validating product-market fit and ship fewer than a handful of orders a day, prefer App Store tools and manual process. Custom apps typically become important when process failure creates measurable margin loss, stockouts, or support tickets—not when the admin simply feels cluttered.
If the real issue is storefront architecture (theme vs headless vs custom storefront), that is a different decision. Do not use an “apps vs custom app” brief to reopen storefront platform questions that belong in a separate project.
What to do next
-
List every installed app and the single outcome each one owns. Uninstall or replace duplicates.
-
Write the one-sentence outcome for the next capability you think you need.
-
Run the App Sprawl Scorecard and record the five scores with evidence.
-
If the total is 18 or below, pilot an App Store option for 14 days with a written exit rule.
-
If the total is 19 or above and the gap is integration or proprietary workflow, brief a custom app around that gap only—including acceptance tests, monitoring, and who maintains it after launch.
If you want help translating the scorecard into a scoped build or a cleaner app stack, Oasbit’s website and SaaS development services cover Shopify integrations, custom apps, and the operational workflows around them. Related reading on storefront path choices is available in Theme, Headless, or Custom App: Choosing Your Next Shopify Storefront Path, and plan-level constraints are covered in Shopify Advanced or Shopify Plus: How to Decide When to Upgrade.
When the decision is stuck between another subscription and a custom build, book a growth strategy session and bring your scorecard scores, current app list, and the one-sentence outcome. The useful conversation is which gap deserves ownership—not which tool looks impressive in a demo.
