Shopify Custom App Development Cost in 2026: Real Ranges by Scope
Shopify custom app development cost in 2026: hour ranges by scope, what drives the price, ongoing costs, and when an App Store app beats a custom build.
Long Nguyen
Développeur fullstack · Ingénieur IA · Chercheur
How much does a custom Shopify app cost?
A custom Shopify app costs roughly 40 to 1,200+ developer hours, and the price is hours multiplied by the rate of whoever builds it. A one-way data sync sits at the low end. A two-way integration with an ERP, warehouse or marketplace, with queues, retries and reconciliation, sits in the middle. A public app with billing and App Store review sits at the top.
The table below shows the planning ranges I use to scope work. They are estimates for sizing a project, not quotes, and they assume one competent developer plus review and testing time.
| Scope | Typical example | Planning range (hours) |
|---|---|---|
| Utility, no UI | Nightly job that pushes inventory or tags orders through the GraphQL Admin API | 40 to 100 |
| Embedded admin app | OAuth, webhooks, a settings screen built with Polaris, a few merchant-facing actions | 120 to 300 |
| External integration | Two-way sync with an ERP, 3PL or marketplace, with a job queue, retries, idempotency and an error dashboard | 250 to 600 |
| Public App Store app | Everything above, plus Billing API, multi-tenant data isolation, onboarding, support tooling and app review | 500 to 1,200+ |
Most of the cost of an integration app is not the happy path. It is the code that handles a webhook arriving twice, a product deleted mid-sync, or an API call throttled halfway through a batch.
What changed in 2026: custom apps now start in the Dev Dashboard
Since , you can no longer create new custom apps from the Shopify admin. Existing custom apps keep working, but any new one is built as a regular Shopify app in the Dev Dashboard with custom distribution selected, then installed on the store.
This matters for cost in two ways. First, the old shortcut of clicking through the admin to get an Admin API token for a quick script is gone, so even a small utility now involves a proper app definition, scopes and an install flow. Second, quotes written before 2026 may assume that shortcut, so a low-ball estimate for a tiny integration is worth questioning.
Custom distribution vs public App Store: where the cost splits
According to Shopify's distribution documentation, the two methods differ in ways that change the budget directly:
| Custom distribution | Public distribution | |
|---|---|---|
| Who can install | Only stores you send the install link to | Any merchant on the App Store |
| App review | Not required | Required |
| Billing API | Not available | Available |
| Multi-store | Only stores inside one Plus organization | All merchants |
| Changing later | Cannot switch after you choose | Cannot switch after you choose |
The last row is the expensive one. You cannot change the distribution method after selecting it, so a custom app that later becomes a product means rebuilding under a new app, not flipping a setting. If there is a real chance you will sell the app to other merchants, decide that before writing the first line.
If your goal is one store or one Plus organization, custom distribution removes review, billing and multi-tenant work from scope. That is typically the difference between the 120 to 300 hour tier and the 500+ hour tier. If you are weighing a build against an existing integration approach, Shopify and ecommerce platform integration work is where I would start the scoping conversation.
What actually moves the price up or down
Hours grow with a short list of technical drivers. Ask any developer quoting you to say where your project sits on each one.
| Cost driver | Why it costs more |
|---|---|
| Data volume | Large catalogs push you off simple paginated queries toward bulk operations and background jobs |
| API rate limits | The GraphQL Admin API uses a calculated query cost. The limit is 100 points per second on standard plans, 200 on Advanced, 1,000 on Plus and 2,000 on Enterprise, and a single query cannot exceed 1,000 points. Sync code must throttle and back off |
| Bulk operations | They have no max cost or rate limit, which makes big exports and imports cheaper to run but adds asynchronous handling code |
| Two-way sync | Conflict rules, idempotency and reconciliation reports roughly double the logic compared with a one-way push |
| Embedded UI | Every screen adds design, states, validation and testing on top of the API work |
| Third-party system quality | A well-documented REST API is cheap. A legacy ERP with flat files or an unstable SOAP endpoint is not |
| Multi-store or Plus | Per-store config, per-store credentials and different rate limits per plan |
Rate limits deserve a second look because they scale with the merchant's plan, not with your app. An integration that runs comfortably on a Plus store can stall on a standard plan, so testing against the store's real plan tier belongs in the estimate.
Turning hours into dollars: the rate math
The US Bureau of Labor Statistics puts the median pay for software developers at $64.44 per hour as of May 2025. That is an employee wage, not a billing rate. A studio or freelancer has to cover benefits, idle time, project management and tooling, so billing rates run above it, and they vary a lot by country and seniority.
Rather than trusting a single averaged number from a listicle, multiply the hours from the first table by three rates you are actually comparing. The rates below are illustrative assumptions to show the spread, not market quotes.
| Scope (hours) | At $40/hr | At $80/hr | At $150/hr |
|---|---|---|---|
| Utility, 40 to 100 h | $1,600 to $4,000 | $3,200 to $8,000 | $6,000 to $15,000 |
| Embedded admin app, 120 to 300 h | $4,800 to $12,000 | $9,600 to $24,000 | $18,000 to $45,000 |
| External integration, 250 to 600 h | $10,000 to $24,000 | $20,000 to $48,000 | $37,500 to $90,000 |
| Public app, 500 to 1,200 h | $20,000 to $48,000 | $40,000 to $96,000 | $75,000 to $180,000 |
A cheaper rate does not always mean a cheaper project. A lower-priced developer who does not handle retries, duplicate webhooks and throttling costs you the difference later in support hours and bad data.
Costs after launch: hosting, API versions and support
A custom app is software you now own, so plan for running costs that are easy to forget in the build quote:
- Hosting. A small worker can run for a few dollars a month. An app with a database, a job queue and logging costs more, and the bill grows with the number of stores and events.
- API version upgrades. Shopify publishes dated API versions on a regular cadence and retires old ones, so the app needs periodic upgrades even when your requirements do not change. Budget a small block of hours each year for this.
- Monitoring and support. Someone has to notice when a sync fails and fix it. Without alerting, failures are discovered by customers.
- Scope changes. A new sales channel or a change in the ERP schema is a change request, not a warranty item.
A workable rule for annual upkeep is to reserve 15 to 25 percent of the original build hours per year for a stable integration. That is my planning figure, not a Shopify number, and it rises if the connected systems change often.
When an App Store app beats a custom build
Custom is the right call when the logic is specific to your business or an existing app forces workarounds you pay for every month. It is the wrong call when a mature App Store app already covers 90 percent of the need.
| Situation | Better route |
|---|---|
| Standard need such as reviews, loyalty or email | Install an existing app |
| Unique pricing, approval or fulfillment logic | Custom app |
| Sync with a proprietary ERP or internal system | Custom app |
| Existing app fee exceeds the yearly upkeep of a custom app | Run the numbers, custom may win |
| You might sell the tool to other merchants | Build it as a public app from day one |
The break-even check is simple. Compare the monthly fee of the closest existing app, multiplied by 36 months, with the build cost plus three years of upkeep. Include the cost of the workarounds the existing app forces on your team.
How to scope a custom Shopify app so it costs less
- Write down the one job. An app that does one thing well costs far less than a platform for everything.
- Choose custom distribution unless you will sell it. It removes review, billing and multi-tenant work.
- Start one-way. Push data from source to Shopify first, and add reverse sync only when a real workflow needs it.
- Skip the custom UI at first. Logs and an email alert are cheaper than an embedded dashboard, and you can add screens later.
- Ask for an hours estimate per feature. A single lump sum hides what you are paying for and makes cutting scope harder.
- Get the third-party API docs before quoting. The quality of the system on the other side is the biggest unknown in any integration.
If you already have a spec or a list of systems to connect, you can request a free quote from Netalith and get an hours breakdown per feature rather than a single number.
FAQ
Questions fréquentes
How much does it cost to build a custom Shopify app?
It depends on scope. Planning ranges are about 40 to 100 hours for a utility with no UI, 120 to 300 for an embedded admin app, 250 to 600 for a two-way integration with an external system, and 500 to 1,200 or more for a public App Store app. Multiply those hours by the hourly rate of whoever builds it.
Can I still create a custom app in the Shopify admin?
No. Since January 1, 2026, new custom apps must be built in the Dev Dashboard with custom distribution selected, then installed on the store. Custom apps created earlier in the admin keep working.
What is the difference in cost between a custom app and a public app?
A custom-distribution app skips App Store review and the Billing API, so it avoids billing, onboarding and multi-tenant work. A public app needs all of that. You also cannot change the distribution method after selecting it, so a custom app that later becomes a product has to be rebuilt.
Do Shopify API rate limits affect the cost of an app?
Yes. The GraphQL Admin API limits scale with the store's plan, from 100 points per second on standard plans to 1,000 on Plus, and a single query cannot exceed 1,000 points. Apps that sync large catalogs need throttling, backoff and often bulk operations, which adds development hours.
What does a Shopify custom app cost to maintain each year?
Expect hosting, periodic API version upgrades, monitoring and support. As a planning figure, reserve roughly 15 to 25 percent of the original build hours per year for a stable integration, more if the connected systems change often.
Should I build a custom Shopify app or use an App Store app?
Use an existing app when it covers about 90 percent of your need. Build custom when your logic is specific to your business, when you must connect a proprietary system, or when the existing app's fees and workarounds cost more over three years than the build plus upkeep.