Do I need a custom Shopify app, or can an existing app do it?

Start with the off-the-shelf app — really

There are thousands of apps in the Shopify App Store, and for most common needs — reviews, upsells, subscriptions, loyalty, bundles, popups, basic feeds — one of them already does what you want, maintained by a team that supports it full-time. An existing app you install in an afternoon will beat a custom build on price, on speed-to-live, and on who keeps the lights on when Shopify ships a platform change. That last point matters more than people expect: a published app gets updated by its developer; a custom build gets updated by whoever you can reach.

So the honest default is to start there. Search the App Store for your exact problem, read the recent reviews (sort by lowest first — that’s where the real limits show), and try the free trial against your actual catalog and your actual workflow, not the demo. Plenty of the “I think I need something custom” conversations I have end with me pointing someone at an app that already exists and costs a fraction of a build. I’d rather you spend a small amount once than a large amount on something the market already solved.

Signs an existing app is enough

If most of these are true, stop shopping for a developer and configure the app well instead:

• Your need is common — the kind of thing thousands of other stores also want.
• An app exists that does 90%+ of it, and the missing 10% is a nice-to-have you can live without.
• Its pricing is sane for your volume, and the recent reviews don’t describe the exact wall you’d hit.
• It plays nicely with your theme in the trial — no broken layout, no obvious slowdown.
• You’re mostly missing setup or configuration, not capability. If the app can do it and you just can’t get it dialed in, that’s a small app install & setup job, not a build.

Signs you’ve outgrown off-the-shelf apps

The flip side. When several of these hold, an existing app is fighting you, and custom starts to make real sense:

• You’ve tried two or three apps for the same job and each one is missing a different essential piece.
• Your workflow is specific to your business — the way you price, fulfil, or quote isn’t how the apps assume everyone works.
• You’re paying for an app and still doing manual work around it every week to make it fit.
• The capability you need simply doesn’t exist as an app — a storefront feature no one offers, or a two-way sync with a system that has no Shopify connector.
• An app technically does it, but its cost scales with your orders or SKUs in a way that’s become punishing as you’ve grown.

None of these on its own forces a build. Together, they’re the signal that you’re bending your business to fit software instead of the other way around — which is exactly the point where a build pays for itself.

When stacking multiple apps is the real problem

Here’s a pattern I see constantly: nobody decided to go custom, but the store ended up running five apps to accomplish one outcome — one to capture the data, one to transform it, one to display it, one to notify, one to report. Each was a reasonable choice on its own. Together they’re a Rube Goldberg machine, and you’re paying a monthly fee for every piece of it.

Stacking has a hidden second cost beyond the invoices: every one of those apps loads its own JavaScript and CSS on your storefront, and most of them load on every page whether it’s needed or not. That’s a direct hit to your page speed — it’s one of the most common reasons a store feels sluggish (I go deep on this in why is my Shopify store so slow). When a stack of overlapping apps is the situation, a single custom app shaped to your exact workflow can often replace the whole pile: one thing to maintain, one predictable cost, and a lighter storefront. The right move is to add up what you’re paying across the stack today and weigh a one-time build against that running total.

Back-office, ERP, and niche workflow needs

This is where custom most often wins outright, because it’s the work the App Store serves least. A few of the shapes it takes:

• Admin automation: the spreadsheet-and-export ritual you (or someone on your team) repeats every week — tagging, re-pricing, reconciling, generating a report — turned into a script that runs on its own.
• Two-way integrations: keeping Shopify in sync with the system that actually runs your business — an ERP, a warehouse or 3PL, accounting, a supplier’s feed — so inventory, orders, and pricing flow both directions instead of being keyed in twice.
• Internal tools: a small interface that shows your team exactly the orders, stock, or customer data they need, in their language, without handing everyone full admin access.
• Storefront features no app expresses: a configurator, a custom quoting flow, conditional content — logic your theme and existing apps simply can’t describe.

This is the work I do most. I’ve built 30+ custom Shopify apps, including builds approved through Shopify’s own app review, and the great majority of them exist because an off-the-shelf app couldn’t reach into a merchant’s back office or bend to a workflow that was genuinely their own. If that’s your situation, the details of how a private build is scoped, what access it needs, and how it’s delivered live on the custom Shopify apps & integrations page.

The cost and ownership trade-off

An existing app and a custom build aren’t just two prices — they’re two different deals. An app is a low monthly fee, instant setup, and a developer who maintains it for you, in exchange for living inside someone else’s decisions: their roadmap, their limits, their price changes, and the risk it gets discontinued. A custom build is a larger one-time cost in exchange for software that fits exactly, that you own, and that no one can take away or re-price out from under you — with the trade that you’re responsible for it over time as Shopify evolves.

So the comparison isn’t “cheap app vs expensive build.” It’s a recurring fee with constraints versus an owned asset with responsibility. For a need that’s common and well-served, the app wins easily. For a need that’s core to how your business runs and poorly served by the market, the build often pays for itself within a year of saved fees and saved manual hours. There’s no flat price for custom, because the cost is driven entirely by scope — I break down exactly what moves the number in how much a custom Shopify app costs.

How I help you decide (and when I say don’t)

You don’t have to figure this out alone, and you don’t need to know the answer before you reach out. Describe what you want it to do in plain English in the chat — “I want X to happen automatically when Y” is a complete brief — and I’ll tell you straight which side of the line you’re on. Sometimes that means I send you off to an app that already exists and we never do business, and that’s fine; I’d rather give you the honest answer than the profitable one.

If it genuinely calls for a build, here’s how it goes from there: we chat, I send a written proposal priced to the scope with a turnaround estimate (custom apps are typically an estimated 1–3 weeks; integrations roughly 3–8 business days; a bigger build gets its own estimate), you pay one Stripe invoice, and I build it — with progress updates along the way and a preview before anything touches your live store. It’s delivered as proposed or made right, and it comes with a 30-day defect warranty. Nothing about that starts until you’ve seen the scope and the price in writing and said yes.