Getting an app approved on the Shopify App Store starts long before you hit submit. The Shopify App Store guidelines shape how an app is built, authenticated, billed, designed, tested, marketed, and maintained after launch.
If you are the merchant paying for that app, those guidelines should be your concern.
After more than a decade around the Shopify app ecosystem, I have learned one lesson worth passing on to store owners:
Merchants who only think about App Store requirements at the end of a build are the ones who end up with delays, rework, and surprise costs.
The better move is to understand these standards before the first line of code. That way you can brief the project properly, ask your developer the right questions, and recognise finished work when you see it.
This guide walks through the practical lessons I use when helping merchants get a Shopify app listed.
Shopify App store guidelines are product requirements
It is easy to treat Shopify's requirements as a checklist your developer ticks off at the end. I would encourage you to see them differently.
Shopify evaluates whether an app is safe, functional, useful, clear for merchants, and compatible with the way its platform is designed to work.
Its requirements cover policy, functionality, installation, security, billing, App Store listings, and category-specific functionality. Shopify can also update these requirements as its platform evolves.
That means an app that passed review two years ago should not assume its old implementation is still enough.
⭐ The biggest lesson before I start: Compliance should be a part of the app development process.
1. Start with Shopify-native architecture
A technically functional SaaS product does not automatically make a good Shopify app. A Shopify app needs to behave like part of Shopify.
For new public apps, this starts with the platform itself. From April 1, 2025, new public apps must use the GraphQL Admin API rather than the legacy REST Admin API.
One thing to watch on any build: teams often request more permissions than the core feature actually needs. That creates needless privacy exposure and raises flags during review.
Shopify requires an app to request only the access scopes it needs to function, and sensitive scopes can need extra justification. When you go over the plan with your developer, ask exactly why each permission is on the list.
The same principle applies to storefront apps. Apps that modify themes should use theme app extensions instead of directly modifying theme code. Shopify also expects clear setup instructions for app embeds and blocks.
⭐ The lesson: Build the app around Shopify’s architecture from the beginning.
2. Installation and billing should be core features
It is natural for a build to pour most of its energy into the headline feature. Reviewers care just as much about everything around it, and installation is the first thing they touch.
Shopify requires installation to begin from a Shopify-owned surface. OAuth should happen immediately after installation, and the merchant should land inside the app UI after accepting permissions.
Here’s the complete journey I test: Install → OAuth → permissions → app UI → setup → uninstall → reinstall
Ask your developer to run this on a clean development store, not the environment they have used for months, where old data can hide broken steps.
Billing deserves similar testing.
Apps distributed through the Shopify App Store generally need to use Shopify App Pricing or the Shopify Billing API for app charges. Merchants should also be able to move between plans without contacting support or reinstalling the app.
Before submission, confirm the app has been tested for plan selection, upgrades, downgrades, subscription status, and usage charges where they apply.
⭐ Lesson: Insist that installation and billing get tested as carefully as the app's main features. A broken setup can stop the review on day one.
3. Build privacy and security before the review
Do not take security lightly. If something happens, it is your store's reputation and your customers' data at risk.
Apps need valid TLS/SSL certificates and secure authentication. Embedded apps should work without depending on third-party cookies. Shopify also expects the app to use session tokens correctly.
Customer data requires even more attention.
If your app needs access to protected customer data, determine that requirement early and apply for the appropriate access. Shopify evaluates whether requested customer information is genuinely required for the app’s functionality.
I follow one simple lesson here:
⭐ The lesson here is this: If the app does not need a piece of data, do not collect it.
It reduces technical risk, simplifies privacy management, and gives reviewers fewer unnecessary permissions to question.
4. Your listing is part of the product
If you are launching a public app, the listing is part of the product. It is the first thing a prospective merchant reads before they trust your app with their store.
The Shopify app store listing guidelines require the public listing to accurately represent what the app can actually do. Your name, pricing, screenshots, descriptions, supported languages, geographic restrictions, and claims all need to match the product.
Avoid claims such as “the best,” “the first,” or “the only” unless Shopify’s requirements clearly allow and the statement can be substantiated. Testimonials and merchant reviews should not be inserted manually into listing content or images either.
Images should focus on the actual product interface. Each image should add something new instead of repeating the same screen.
This is also where more focus should be put on Shopify app store optimization.
Shopify recommends an app card subtitle that explains merchant value, and the listing allows up to five relevant search terms, each a complete term with one clear idea. They specifically warns against forcing keywords into subtitles for search performance.
I normally think about the merchant’s search intent:
- What problem are they trying to solve?
- What would they call that problem?
- What outcome does the app provide?
- Which features actually differentiate it?
There is another reason listing quality matters in 2026.
Shopify introduced app discovery through Sidekick. It can recommend, compare, and surface apps using information from App Store listings. Shopify advises developers to keep listing information accurate, clear, and structured for this experience.
Your listing is now serving humans, App Store search, external search engines, and AI-assisted discovery.
⭐ The lesson here: Your app store listing should explain the app as clearly and accurately as the product itself.
5. Make the reviewer’s job easy
Shopify requires a demo screencast showing onboarding and the core features described in the listing. Test credentials must remain valid and provide access to the complete feature set needed for review.
I treat the reviewer like the app’s first merchant.
Make sure the submission hands the reviewer:
- Clear installation instructions.
- Working test credentials.
- Exact steps required to activate important features.
- A concise screencast showing the full workflow.
- Notes explaining unusual configuration requirements.
- Any category-specific setup the reviewer needs.
Then have someone test those instructions in a fresh store, ideally not the person who wrote them.
The current Shopify app review process moves an app through 4 stages:
Draft > Submitted > Reviewed > Published.
An app that fails core requirements can be paused until fixes are submitted. Once the core requirements are satisfied, a reviewer can continue with deeper testing and request further changes.
Shopify also now offers an AI self-review through its AI Toolkit. The tool can inspect a local codebase against App Store requirements that can be evaluated from code. It does not replace Shopify’s review team and cannot evaluate every live UX or listing requirement.
⭐ The lesson here: Give reviewers clear instructions, working credentials, and a complete path to test every important feature.
6. The most common rejections are often preventable
I have experienced app rejection coming from a policy that is hard to understand.
Usually, the causes are far less dramatic.
- Broken OAuth or installation flows.
- 404, 500, and other web errors.
- Inaccurate pricing.
- Billing implementation problems.
- Broken embedded behaviour.
- Missing testing instructions or credentials.
- Unfinished app functionality.
- Storefront apps that fail to use theme app extensions correctly.
These are mostly QA problems. That is why a solid pre-submission check runs the app as a complete merchant journey rather than testing features in isolation.
When you review a build, ask to see it run end to end, from install to uninstall.
⭐ The lesson here is: A thorough pre-submission QA check can prevent many of the issues that delay Shopify App Store approval.
7. Approval should be the starting line
Publishing the app is a milestone, but it is not the end of development.
Shopify continues to evaluate app quality. Performance, reliability, merchant experience, platform changes, API versions, privacy requirements, and listing accuracy need ongoing attention.
If you are in this for the long run, ask your developer about Built for Shopify.
Built for Shopify adds stricter quality standards around areas such as performance, integration, ease of use, safety, and proven merchant value. Qualifying apps can receive a badge, greater visibility, a search-ranking boost, and priority review for future apps from the developer.
⭐ The lesson here: Treat App Store approval as the beginning of ongoing improvement, not the final stage of app development.
What should merchants look for in a Shopify app development agency?
If you are hiring an agency to turn an app idea into a Shopify product, ask deeper questions than “Can you build this feature?”
Start by understanding what goes into Shopify custom app development. Ask the agency how they handle Shopify APIs, OAuth, billing, access scopes, protected customer data, app extensions, performance, App Store submissions, listing requirements, and post-launch API changes.
An experienced Shopify app development team should be thinking about approval while the app architecture is still being discussed.
Build for Shopify before you build for approval
The biggest mistake I see merchants make is treating the Shopify App Store review as the final hurdle. It should shape the product from the start.
Insist on Shopify-native APIs and installation that just works. Make sure billing is tested properly, customer data is protected, the listing is written around real value, and the reviewer is handed everything they need.
Then keep improving after approval.
That approach cuts avoidable rework and gets you something more valuable than an approved submission: a Shopify app that merchants can install, understand, and keep paying for.
FAQs
1. What are the Shopify app store guidelines?
Shopify App Store guidelines are the rules an app must follow to be listed on the Shopify App Store. They cover areas like security, functionality, billing, privacy, performance, and app listing content.
2. How much does it cost to develop a Shopify app?
The cost depends on the app’s features, complexity, integrations, and whether it is a custom or public app. A simple app can cost a few thousand dollars, while a complex public app can require a much larger budget.
3. Can I build my own Shopify app?
Yes. Shopify offers APIs, the Shopify CLI, App Bridge, and other tools for building an app. In practice it takes solid development knowledge across authentication, APIs, billing, webhooks, and security, so most merchants hire a developer, agency, or Shopify expert rather than building it in-house.
4. What are the different types of Shopify apps?
The main types are public apps and custom apps. Public apps are built for multiple merchants, while custom apps are usually created for the specific needs of one merchant or organization.
About the author
Vineet Nair
Vineet is an experienced content strategist with expertise in the ecommerce domain and a keen interest in Shopify. He aims to help Shopify merchants thrive in this competitive environment with technical solutions and thoughtfully structured content.