When is custom Shopify app development worth it?
The Shopify App Store covers many standard cases. A custom app pays off where your business process deviates from the norm: special tax logic, a link to your ERP or warehouse, automated documents or a B2B workflow no existing app handles cleanly. Instead of stitching three apps together, you model the process in one app you control.
A second driver is data protection and data sovereignty. When sensitive customer or revenue data is involved, you want to know where it lives. A custom solution hosted in Germany with a GDPR-compliant architecture is often the more honest answer than a US SaaS. Our own products set the bar: create Shopify invoices automatically or connect Shopify to sevdesk are exactly this kind of deeply integrated app.
Custom app vs. public app: the decisive difference
Before cost, settle the app type, because it drives effort and review. A custom app (custom distribution) runs only in your own store or a small set of selected stores and goes through no public App Store review. A public app is listed in the Shopify App Store, installable by any merchant and must pass the official review.
For most merchants who want to automate their own process, the custom app is the faster route: no listing, no marketing review, fewer obligations. A public app makes sense when you want to sell the app as a product or roll it out broadly.
- Custom app: one or few stores, no App Store listing, no public review, faster delivery.
- Public app: App Store listing, installable by any merchant, full Shopify review and ongoing compliance.
- Embedded vs. standalone: embedded apps run inside the admin (App Bridge, Polaris), standalone apps outside.
- Both types use the same building blocks: OAuth authentication, Admin API and webhooks.
What does custom Shopify app development cost?
Flat prices are unserious, cost depends on scope. Drivers are: the number and complexity of integrations (Shopify API, ERP, accounting, payment providers), UI depth (a simple settings dialog vs. a full dashboard), hosting and operations, and the degree of automation via webhooks. An app that only reads orders is far cheaper than one that generates documents, calculates tax and writes back.
The biggest lever for a predictable budget is a tightly scoped MVP (minimum viable product): the one core function that delivers value immediately, built well instead of a wishlist that never ships. After that you extend iteratively. Don't forget recurring costs in planning: hosting, maintenance and keeping up with new Shopify API versions all count. An overview of our services helps define the scope.
The project process: from idea to finished app
A good app project follows clear phases so budget and expectations stay in sync. It starts with discovery: which process is being modelled, which data flows, which scopes does the app need? Only then do you build, test and roll out.
It matters to clarify early whether the app produces legally relevant documents, such as invoices under § 14 UStG or GoBD-compliant archiving. These requirements are not an afterthought feature but an architecture decision. Thinking about them upfront avoids costly rebuilds. If you want to connect Shopify to Lexware Office, for example, the data model decides the quality of the result.
- Discovery: define the process, data flows, required API scopes and success criteria.
- Concept & prototype: data model, OAuth/webhook architecture, UI sketch, MVP cut.
- Development: Admin API integration, webhook processing, settings UI with Polaris.
- Test & review: end-to-end tests, App Store review if needed, then rollout to the store.
- Operations: monitoring, maintenance and updates to new Shopify API versions.
Understanding the Shopify App Store review
If you want to publish a public app, Shopify reviews it before listing. The review looks at function, security and user experience: the app must do what it promises, implement the OAuth and permission flows cleanly and request only the scopes it truly needs. Embedded apps are also checked for consistent behaviour in the admin.
A common stumbling block is the mandatory privacy webhooks (customer data request, customer redact, shop redact). Anyone processing customer data must implement them: they are review-required and part of GDPR compliance. A well-thought-out architecture with clear data flows and correct webhook handling saves several review rounds here.
Building tax and compliance logic into the app correctly
In the DACH region especially, tax logic decides between success and frustration. An app that produces documents must handle the special cases correctly: 19 % or 7 % domestically, the OSS scheme in Shopify for EU B2C distance sales above the EU-wide threshold of €10,000, reverse charge on B2B sales to the EU with a valid VAT ID (0 %), and the small-business rule under § 19 UStG.
E-invoicing also belongs in the plan: since 1 January 2025, companies in Germany must be able to receive B2B e-invoices, with the issuing obligation staggered through 2028. Formats like ZUGFeRD and XRechnung under the EN 16931 norm are not plain PDFs, an e-invoice contains structured XML data. Planning for this makes the app future-proof. Reach out for such requirements via our contact page.
