What "custom Shopify app" actually means
The phrase covers two things that get confused constantly. A public app is the listing you install from the Shopify App Store — built for thousands of merchants, priced on a subscription, maintained by a vendor. A custom app (the term that replaced "private app") is software built for exactly one store, installed only there, and shaped around how that business actually runs.
Both extend Shopify through the same APIs. The difference is ownership and fit. A custom app reads and writes through the GraphQL Admin API into your store and, often, your own database. It can run Shopify Functions at checkout, listen to verified webhooks, and store structured data in metafields and metaobjects — without the extra scripts a public app injects into every page load. We unpack the trade-off in detail in private Shopify apps vs public apps, but the short version is this: public apps win for commodity features, custom wins when the logic is specific to your operation.
When custom development is justified
Building is not the default. A custom app earns its cost when one of these is true:
- Your workflow doesn't match any app's assumptions. B2B pricing tiers, complex bundles, multi-warehouse allocation, or an ERP a generic app can't model.
- You're paying per-order fees that scale against you. A usage-priced public app can quietly become one of your largest line items. A one-time build plus hosting often crosses below that cost at volume.
- The data has to stay yours. For compliance, portability, or because the logic is genuinely your competitive edge.
- Performance is a real constraint. Fewer storefront scripts, server-side logic at checkout, and clean event tracking instead of a stack of third-party tags.
If none of those apply, a well-chosen public app is the cheaper, faster answer — and we'll say so. The fastest way to know which side you're on is a Shopify CRO and tech audit that quantifies the cost of your current setup before anyone writes code.
Realistic CHF ranges
Swiss rates are higher than offshore, and the honest reason is accountability: you get engineers who own the outcome, work in your timezone, and stay reachable after launch. Treat these as planning ranges, not quotes — scope decides everything.
- A focused build sprint — one well-defined app: a bundle builder, a fulfilment sync, a single internal dashboard — typically runs from around CHF 4,000 to 15,000+. The spread depends on how many systems it touches and how much edge-case logic it has to express.
- A multi-system integration — Shopify wired to an ERP or WMS with queues, retries, and monitoring — sits at the upper end and beyond, because the hard part isn't the happy path, it's everything that can go wrong in production.
- Ongoing maintenance — API version migrations, monitoring, small changes — is usually a modest monthly retainer or a time bank, not a second project.
Anything advertised far below these numbers is usually hiding something: no error handling, no monitoring, no handover, or a junior building against a single happy-path assumption. We cover that trap in depth in how much a custom Shopify app costs in 2026.
The process, end to end
Good custom work follows the same shape regardless of size. The point of a defined process is that you can stop at any gate without having wasted the previous one.
1. Diagnose. Before scoping a build, we look at what you already have. Sometimes the answer is "remove three apps and fix a webhook," not "build software." Diagnosis is also where the real requirement surfaces — the workflow exception nobody documented but everyone works around.
2. Scope. A written spec: what the app does, which APIs and data it touches, the data model, the edge cases, and what's explicitly out of scope. This is where cost becomes predictable. A vague scope is the single biggest driver of overrun.
3. Build. Iterative, on a real Shopify development store, against your actual data shapes. You see working software early, not a reveal at the end. Functions, webhooks, and the admin surface come together in slices you can review.
4. Ship. Deploy with the unglamorous parts done properly: HMAC-verified webhooks, idempotent handlers, retries, logging, and monitoring so failures page someone instead of silently dropping orders.
5. Handover. Documentation, access, and a clear maintenance plan. You own the code and the data. If you ever want to take it in-house or hand it to another team, nothing is locked in a vendor you don't control.
Concrete examples
What this looks like in practice, drawn from the kinds of builds that recur:
- A bundle builder that prices and validates configurable bundles at checkout using Shopify Functions, instead of a storefront app that breaks on every theme update.
- A B2B portal with account-specific pricing, net terms, reorder flows, and approval logic that no off-the-shelf wholesale app models cleanly.
- Fulfilment automation that routes orders to the right warehouse or 3PL, writes tracking back to Shopify, and retries on failure — the kind of Shopify automation work covered in what to automate in a growing store.
- Internal dashboards that pull live data through the GraphQL Admin API and webhooks so your team stops reconciling three tools by hand. We explain that data layer in Shopify GraphQL, webhooks and dashboards explained.
Ownership and maintenance
A custom app is an asset, not a subscription — but it isn't fire-and-forget. Shopify ships API version changes on a schedule, dependencies need patching, and your business changes. Budget for a light maintenance relationship so the thing you paid to build doesn't quietly rot. Done right, that's a fraction of the build cost and far less than the per-order fees a usage-priced public app would have charged in the meantime.
If you're weighing a build, the cheapest first step is not a proposal — it's a diagnosis. Book a paid Shopify audit and you'll get an honest read on whether custom is justified, with the expensive problems ranked before anyone writes a line of code. If you'd rather start lighter, the free Shopify audit is a quick scan to point you in the right direction.