Why be on the Shopify App Store
Being part of the most widely adopted e-commerce ecosystem is an obvious choice from an ROI perspective — you won't slow down your growth or lose relevance.
Benefits
What you gain as a public app in the Shopify ecosystem.
Instant reach and trust
Simple monetization
Faster development
Stable API
Strong ecosystem
Global readiness
Marketing & insights
Security by design
Requirements
Basic requirements for a public app on the Shopify App Store.
Use Shopify Billing
All payments and trials through the Billing API.
Impact: Automatic billing, no payment method management required.
Pass review and maintain standards
OAuth, scopes, data deletion, performance, and basic compliance.
Revenue share: 0% on the first $1M USD, then 15%.
Types of Shopify apps and integrations we develop
Typical collaboration process
Initial consultation and briefing
In the first phase, you present your idea to us. We discuss all project details, specific requirements, and the context of your business. Based on this information, we prepare a detailed work plan including a task list and an estimated timeline.
Questions we get asked most often
How much does it cost to develop a Shopify app?
It depends on the type and complexity of the app. A basic custom app for internal use starts at around 200,000 CZK. A public App Store app with full functionality typically costs 500,000–1,500,000 CZK.
The price is mainly influenced by the scope of features — a simple integration is quick and affordable, while complex workflows with custom logic can take months of work. A public app also requires the App Store review process, a payment system, and broader testing, which extends development compared to a custom solution.
Public App Store app or custom app: Which is better for us?
Choose a public app if you want to offer it to hundreds or thousands of stores. It goes through App Store approval, requires a public pricing plan, and Shopify takes a 15% revenue share on earnings above $1 million USD annually. It's suitable for a product with a clear market and scalable model.
A custom app is for the specific needs of one store or company. It doesn't need App Store approval, you don't pay a revenue share, and you go live much faster. Ideal for unique workflows or custom integrations.
Not sure? We'll help evaluate your goals, potential market, and the path from a custom solution to a public app if you decide to scale later.
How long does development take and what most commonly delays App Store approval?
Public app: 4–8 weeks for developing the basic version + 3–7 days for App Store approval.
Most common rejection reasons: poorly set up login or payment process, missing test credentials for the Shopify team, inaccurate App Store description or unclear documentation, and UI bugs or Shopify policy violations.
Custom app: No App Store approval, so you go live much faster — typically 3–6 weeks from kick-off to launch.
Who will support app users after launch?
For a custom app, support works like any other internal tool — your team handles it for your people. We'll deliver complete documentation, train your team, and if you want, we'll provide technical support through an SLA package (Service Level Agreement).
For a public App Store app, you as the publisher support the merchants. Shopify requires a response within 24 hours. We'll help you set up customer support, prepare documentation and FAQs, and cover higher-level technical support through an SLA.
Before launch, we'll set up together how support will work and who is responsible for what.
What technical architecture should we choose?
We build most apps as embedded in the Shopify admin — they run directly within the Shopify admin interface. This approach is fast, well-supported, and doesn't require complex infrastructure.
We only choose a standalone app outside the Shopify admin in exceptional cases — for example, when you need a custom login system for multiple services at once, a complex interface for external operators, or integration with specific internal tools.
Before kick-off, we'll review your requirements and jointly design a technical solution that will work long-term. If needed, we'll build a proof-of-concept prototype to validate key features.
How should we price the app: subscription, usage-based fees, or one-time payment? And what about a trial period?
The most common model for a public app: several subscription tiers (Basic, Pro, Enterprise) based on store size, overage charges — for example for higher order or user counts, and a 7–14 day free trial.
For the App Store you must use Shopify's billing API. Shopify takes a revenue share: 0% up to the first million USD annually, then 15% on each payment.
For a custom app outside the store, you pay no revenue share to Shopify — only development and hosting costs.
We'll help design a pricing strategy that fits the market and your goals. The key is to start simple and adjust based on feedback.
How do you ensure reliable data synchronization with our systems?
We design synchronization based on your needs. Real-time sync transfers data immediately after each change — ideal for inventory levels, orders, or product availability. Scheduled syncs run at regular intervals (hourly, overnight) — sufficient for price lists, catalogs, or reports.
In both cases: automatic retries if a sync fails, no duplicates — each operation is performed only once even if received multiple times, and error tracking — problematic cases are set aside and you receive a notification.
For demanding operations, we add continuous monitoring of critical flows with guaranteed response times per SLA.
How will the app handle thousands of orders per day without downtime?
The app handles high volumes through efficient architecture. It processes data intelligently — batching queries and caching. It doesn't block operations — tasks run in the background via job queues.
It automatically retries errors — if something fails, the system tries again. It monitors performance in real time — we receive alerts before your customers notice anything.
We always build on cloud infrastructure (Google Cloud Platform or Amazon Web Services), which automatically scales capacity based on load. We work with the latest Shopify API versions and regularly migrate to current standards.
On top of everything runs continuous monitoring that tracks response times, error rates, and system capacity. The result: the app runs stably even during Black Friday peaks.
How do you ensure GDPR compliance and customer data security?
We address security and GDPR from day one. We request only the data the app actually needs — nothing more. We encrypt data at rest and in transit. We implement automatic data deletion and export on request per GDPR. We clearly define how long we retain data and why.
Every operation is recorded in an audit log, so you know who accessed data and when. We configure access so that everyone has only what they genuinely need to do their job.
If you have specific security requirements (ISO or SOC2 certification), we'll discuss them before development begins.
What standards must an app meet for the Built for Shopify badge?
The Built for Shopify badge is awarded only to apps that meet strict quality standards. The app must load quickly and must not slow down admin work or the online store. Error rates must be minimal — the app must not crash even under heavy load. The merchant is guided through a clear installation process, knowing exactly what to do step by step.
We use the latest Shopify extensions rather than older solutions. The app is localized, documentation is complete, and customer support is fast.
If you're targeting the Built for Shopify badge, we'll design the app to meet these requirements from the start. That will save you months of rework later.
How do you ensure reliable operations for complex systems?
For complex systems, we have a clear reliability plan. Continuous monitoring runs 24/7, tracking performance, error rates, and response times non-stop. If anything is off, we receive automatic alerts.
The SLA contract clearly defines guaranteed response times by issue severity. The system automatically scales capacity during Black Friday, holiday campaigns, or unexpected traffic spikes. Before major events, we run load tests and strengthen monitoring.
Specific parameters and response times will be set according to your needs in the SLA contract.
What happens after completion? Who owns the code and how do you transfer knowledge to our team?
Code and intellectual property ownership is handled individually based on the type of engagement. In most cases, the rights remain with you as the client.
After completion, we do a full handover — we transfer access to the code and infrastructure, and train your team on how the app works and how to manage it. The scope of documentation and handover depends on the agreement and project complexity.
If you don't want to handle operations internally, we offer SLA packages with technical support and maintenance.
Can we test the app before the official launch?
Yes, testing is a standard part of every project. Before the official launch, we'll give you access to a test version of the app on a development store, where you can try all the features in a safe environment without impact on production.
For public App Store apps, we also work with pilot merchants — selected merchants who test the app in real operations before the official launch. This gives you valuable feedback and lets you refine details based on actual usage.
Only after all tests are approved and you complete your final review do we launch the app live. We never rush — we'd rather spend a few extra days testing than have you dealing with issues in production.
What if we discover during development that we need to change the functionality?
Changes during development are normal — often it's only during testing that you see what works and what doesn't. That's why we work in iterations and regularly show you progress.
Minor adjustments and improvements are included in the original scope as long as they don't affect the timeline or overall architecture. Larger changes we'll discuss — we'll assess the impact on schedule and budget, and you decide whether to implement the change now or leave it for a later phase after launch.
Thanks to our agile approach, we're flexible and can respond to your needs. We'd rather develop an app that truly solves your problem than blindly follow the original plan.
How often will you update the app after launch?
It depends on the type of app and the agreement. Shopify releases a new API version every 3 months, and each version is supported for a minimum of 12 months. This means at least once a year it's necessary to update the API version — even if nothing in the app code changes.
For public App Store apps, regular updates are a must — Shopify requires that apps use current API versions and comply with the latest security standards. Without this, Shopify will remove your app from the App Store.
For custom apps you have more flexibility, but we still recommend at minimum an annual API version update. If you don't want to handle technical maintenance internally, we offer SLA packages that include regular updates, monitoring, and fast response to critical issues.
They praise us...
We went with Shopify, because …
Sounds Good? Let’s do this together. On Shopify.