What Drives the Cost of a Custom Shopify App
The scope, integrations, data, screens, hosting and upkeep that set what a custom Shopify app costs, how to get quotes you can compare, and how to spend less.
In this guide
“How much does a custom Shopify app cost?” has no honest single answer. The same sentence, “we need an app that sends orders to our warehouse”, can describe a small job or a large one depending on what sits behind it. Two quotes for that sentence can differ a lot, and both can be fair.
What you can do is understand what moves the number. Once you know the drivers, you can write a brief that pins them down, compare quotes that actually describe the same work, and cut cost where it does not hurt.
This guide does not give price ranges or hourly rates. They depend on the developer, the country and the job, and any figure here would mislead you more than help. It explains where the money goes instead.
If you are not yet sure you need custom work at all, read custom Shopify app or off-the-shelf first.
Build cost and running cost are two different bills
Most quotes cover the build: the first working version. A custom app also costs money every month and every year after launch, and those costs are easy to forget when you compare a quote with a public app’s monthly fee.
| Bill | What it covers | When you pay |
|---|---|---|
| Build | Design, development, testing on a development store, launch | Once, or in stages |
| Hosting | The server, database and any services the app runs on | Every month |
| Upkeep | API version updates, dependency and security updates, small fixes | Every year at least |
| Changes | New features when your process changes | Whenever you ask |
| Your time | Writing the brief, answering questions, testing, approving | During the build and each change |
A cheap build with no plan for upkeep can end up the most expensive option. Our guide to maintaining a custom Shopify app covers what that upkeep involves.
The seven drivers of build cost
1. Scope: how many jobs the app does
Scope is the biggest driver. Count the distinct things a person can do with the app and the distinct things it does on its own. “Export unfulfilled orders to a CSV every morning” is one job. “Export orders, let the warehouse mark them packed, sync tracking back, and alert us on failures” is four.
Each extra job adds screens, data, error cases and tests. A developer quoting a vague brief has to guess the scope, and guesses are priced with a safety margin.
2. Integrations: what it talks to besides Shopify
An app that only reads and writes Shopify data is the simpler case. Every outside system adds work:
- learning that system’s API, file format or quirks;
- handling its errors, outages and rate limits;
- mapping its fields to Shopify’s (SKUs, locations, customer IDs);
- deciding which side wins when the two disagree.
A modern API with good documentation is cheaper to connect than an old system that only exchanges files over SFTP, or one with no documentation at all. Our checklist for integrations that don’t break shows what a reliable connection needs, and the ERP and 3PL integration guide covers the most common case.
3. Data volume and timing
Ten orders a day and ten thousand are different problems. Volume decides whether the app can process things one by one or needs queues, batching and bulk operations. Timing matters too: “once a night” is simpler than “within seconds of every order”.
Shopify’s APIs have rate limits, and webhooks can arrive late, twice or not at all. Shopify’s webhook best practices recommend handling duplicates and reconciling periodically. The more data and the tighter the timing, the more of this work the app needs.
4. Screens and who uses them
An app with no interface, one that runs in the background and sends a file, costs less than one with screens. Each screen needs design, permission checks and testing. Who uses the screens changes the effort too:
- One trained person on your team can live with a plain screen.
- A whole team needs roles, approvals and a record of who did what.
- Your customers need a polished interface on the storefront, checkout or customer account pages, which is a different kind of work.
Our guide to back-office tools for Shopify teams covers what internal screens usually need.
5. Where the logic has to live
Some jobs must run inside Shopify. Custom discounts, payment and delivery options, and cart and checkout validation are built with Shopify Functions, which Shopify executes for you. That removes a server for the function itself but adds Functions-specific development and testing.
The plan rule matters here: only stores on Shopify Plus can use custom apps that contain Function APIs, while public apps with functions work on any plan. Off Plus, a custom Function is not an option, which changes the whole approach. See custom logic with Shopify Functions and custom app vs public app.
6. Rules, approvals and safety
An app that only reads data is low risk. An app that changes prices, stock, orders or refunds needs safeguards: previews, approvals, limits, logs and a way to undo. These are worth paying for, but they are real work, so say up front which actions need a person’s approval.
7. Unknowns
Every unknown adds risk, and risk is priced in. Typical unknowns: an outside system nobody has documented, data that is messier than expected, or a process nobody has written down. A short paid discovery step, where the developer checks the unknowns before quoting the full build, often costs less than a quote padded to cover them.
Running costs to ask about
Hosting
A custom app runs on a server somewhere, unless it is entirely Functions or extensions that Shopify runs. Ask:
- where it runs and who pays the bill;
- whether the account is in your name or the developer’s;
- what happens to it if you stop working with that developer.
Upkeep and platform changes
Shopify releases a new API version every three months and supports each stable version for at least 12 months. When an app keeps calling a version that is no longer supported, Shopify answers with the oldest supported version instead, which can quietly change results. Someone has to review and update the app at least once a year.
Bigger platform changes happen too. Shopify Scripts ended on June 30, 2026, according to Shopify’s migration guide, and their logic moved to Functions. Our Scripts to Functions migration guide shows what that involved. Changes like these are not bugs in your app, but they still need paid work.
Changes you ask for
Your process will change. Ask how change requests are quoted and how quickly small fixes are handled.
How to get quotes you can compare
Two quotes are only comparable if they describe the same work. Use these steps:
- Send everyone the same brief. Our guide on how to brief a developer shows what a short brief contains: today’s process, the pain, what “done” looks like, systems and data, rules, stores and plans, and any deadline.
- Ask for scope in plain words. What is included, and what is explicitly not.
- Ask for the approach. Where the logic will live (Flow, a Function, a custom app, an outside service) and why.
- Ask for running costs separately. Hosting, third-party services and yearly upkeep, not just the build.
- Ask what happens after launch. Who fixes bugs, who handles API version updates, and how those are charged.
- Ask about ownership. Who owns the code, which account the app is created under, and what you receive at handover.
Then put the answers side by side:
| Question | Quote A | Quote B |
|---|---|---|
| Jobs included | ||
| Jobs excluded | ||
| Where the logic lives | ||
| Integrations covered | ||
| Approvals and logs | ||
| Hosting: where, whose account, monthly cost | ||
| Upkeep: what is included, how it is charged | ||
| Code ownership and handover | ||
| Build cost |
If one quote is much lower, look at the rows above the price first. The difference is usually there: fewer jobs, no error handling, no upkeep, or hosting left out. Our guide to hiring a Shopify app developer covers how to judge the people behind the quote.
How to spend less without cutting corners
Build a smaller first version
Pick the one job that costs your team the most time and build only that. Leave the second and third jobs until the first is in use. You learn what you actually need, and the next quote is more accurate.
Use what Shopify already gives you
Shopify Flow is a free Shopify app on the Basic, Grow, Advanced and Plus plans. Many “when X happens, do Y” jobs need no custom app at all. On Grow, Advanced and Plus, Flow’s Send HTTP request action can call an outside system, so the custom part shrinks to whatever receives that request. Our comparison of Shopify Flow and a custom app shows where the line usually falls.
Use an existing app for the common part
If a public app covers most of the job, keep it and build only the gap. A small custom piece next to a good public app is often cheaper than replacing the app.
Remove unknowns before the build
Document the outside system, clean up the data and write the process down. Every unknown you remove is margin the developer does not need to add.
Be available
Slow answers stretch the work. Name one person on your side who answers questions and tests each step.
When not to pay for custom work
Hold off when:
- a public app does the job and the missing part is a preference, not a need;
- the process changes every month and nobody owns it;
- you cannot describe what “done” looks like in two sentences;
- nobody will pay for upkeep after launch.
In those cases, the cheapest answer is to fix the process first or use an existing app.
FAQ
Why do quotes for the same custom app differ so much?
Usually because the developers assumed different scope. One included error handling, approvals, hosting and upkeep; another did not. Send the same brief to everyone and compare the scope, approach and running costs before the price.
Is a custom app cheaper than paying for public apps every month?
Sometimes. Compare the build plus hosting and yearly upkeep against the apps’ fees over the same period, and add the time your team spends on workarounds today. If a public app fits well, it is often the cheaper answer.
What ongoing costs does a custom Shopify app have?
Hosting, any third-party services it uses, and upkeep. Shopify releases a new API version every three months and supports each for at least 12 months, so the app needs review and updates at least once a year, plus changes when your process or Shopify’s platform changes.
Can a custom app with Shopify Functions run on any plan?
No. Only Shopify Plus stores can use custom apps that contain Function APIs. Public apps with functions work on any plan.
How can I lower the cost of a custom app?
Build the single most valuable job first, use Shopify Flow or an existing app for what they already cover, and remove unknowns (undocumented systems, messy data) before the build starts.
Get a quote from us
Our custom solutions page describes the four kinds of Shopify work the team behind Storefleet Store Ops takes on. A short brief is enough to start, and we reply with how we would approach it.