When to Turn a Client Problem into a Shopify App
Short answer: A client problem is worth turning into a Shopify app when the same narrow problem recurs across different merchants, Shopify has an extension point that handles it natively, and a merchant could install the fix without a developer. If the problem is unique to one business, custom work is the better answer.
Why would a client problem become an app at all?
Most of my work is bespoke. A merchant has a particular process, I map it, and I build the right thing for them. That is the heart of what I do, and nothing about it should change.
But after enough projects, you start to see shapes repeating. The details differ, but the underlying problem is the same one wearing different clothes. When that happens, building a custom solution each time starts to look like the wrong tool for a very common job.
What signals say “this should be a product”?
I look for four things together. Missing any one of them is a reason to hold back.
- The problem recurs across unrelated businesses. Not three clients in the same niche, but different industries with the same pain.
- It’s narrow. You can describe the job in a sentence. “Sell digital downloads securely.” “Apply shipping rules by collection.” If it needs a paragraph, it’s probably several products tangled together.
- Shopify gives you a clean way in. The best apps work with the platform, not against it. A proper hook for apps to plug into means the app behaves like part of Shopify and survives platform updates.
- A merchant can install it without me. If every customer needs a consultation, you’ve built a service with extra steps.
What did that look like for my two apps?
Both of my Shopify apps fit that shape.
Vaulted Downloads has one job: selling digital downloads with secure delivery, with files held in encrypted storage that is either hosted for you or in your own Cloudflare R2 bucket. Parcel Rules has another: shipping and checkout rules, built on Shopify Functions so they run natively on Basic, Shopify and Advanced plans rather than only on Plus.
Each can be described in a sentence, each uses a mechanism Shopify provides rather than fighting it, and each can be installed by a merchant without calling me. You’ll find more about both in the Vaulted Downloads and Parcel Rules case study, and the how-to guides how to sell digital downloads on Shopify securely and free shipping by collection without Plus show the problems they address from a merchant’s side.
When should you keep it custom?
Plenty of work should stay bespoke, and I’d rather say so plainly. The Stone & Wood custom carton builder is a good example. It was designed around one brand’s products, tone and checkout flow. Turning it into a generic bundle app would have made it worse for the people it was built for.
Some problems are simply too tied to one business to generalise, and forcing them into a product helps nobody.
My rule: if the value comes from fitting one business exactly, stay custom. If the value comes from solving the same problem for many, think product.
What should you check before building an app?
Before writing a line of code, I’d ask:
- Does a good app already exist? If so, recommend it. Honesty about that earns more trust than a worse reinvention.
- Which plan can use it? Shopify says stores on any plan can use public apps that contain Functions, while only Plus stores can use custom apps with Function APIs. That shapes who can buy what you build.
- Who maintains it? An app is a commitment. Shopify changes, and every change is yours to follow. The Shopify Scripts shutdown is a good reminder of how quickly the ground can move.
- Can I support it? Real merchants will email. Plan for that.
- Is the price honest? It should reflect the value of the job, not the cost of the code.
What does this mean if you’re a merchant?
Two things. First, if you have a problem, there may already be an app for it, so check before commissioning anything. Second, if your problem is unusual, don’t squeeze it into a generic product. Custom work exists for that, and a good developer will tell you which one you need.
If you’re not sure which camp your problem sits in, that is exactly the sort of question I like to answer. Have a look at what I do, or tell me about the problem and I’ll give you an honest view on whether it’s an app, a custom build, or nothing you need to build at all.
Frequently asked questions
How do you know when a client problem should become a Shopify app?
Look for the same narrow problem showing up across different merchants, a platform extension point that handles it natively, and a fix a merchant could install without a developer. If all three are true, a product may beat repeated custom work. If the problem is unique to one business, build it custom.
Should I build a custom solution or buy an existing Shopify app?
Buy when your need is common and an app already does it well. Build when your logic is particular to your business and no app fits. Custom work also means you own the maintenance when Shopify changes, so weigh that ongoing cost alongside the build price.
What makes a good Shopify app idea?
A narrow, well-defined job that merchants already struggle with, built on Shopify's own extension points rather than fighting the platform. It should be understandable in a sentence, installable without a developer, and valuable enough that people would pay for it rather than patch around the problem.
Do I need Shopify Plus to build a Shopify app?
No. Building and distributing a public app through the Shopify App Store doesn't require Plus. Shopify says stores on any plan can use public apps that contain Functions. Plus is only needed when a single store wants a custom app containing Function APIs for itself.
