Skip to content
Tutorials Center
My learning

Topics

Lesson 43 of 55 ยท Compliance, Security, Review

App Store Requirements and Review

Prepare a Shopify app for review: listing content, technical requirements, Built for Shopify, performance, common rejection reasons and a runnable pre-submission scorer.

Publishing a public app means passing through a review. Shopify's reviewers install your app on a test store, follow your instructions, and check that it works, behaves safely and is honestly described. Most first submissions come back with a list of fixes, and almost every item on that list could have been caught by the developer a week earlier.

This lesson is a map of what the review looks at and how to prepare. It builds on the rules you already know from Privacy, GDPR and Mandatory Webhooks and the App Security Checklist. The requirements change over time, so treat this page as a way of thinking, and always compare it with the current App Store requirements in the Partner or Dev Dashboard before you submit.

Everything about the real review process is read-only here: nobody can submit an app from this page. The runnable examples are stand-ins that model a checklist and a scoring routine so you can see how to organize your own preparation.

What the review looks at

Reviewers cover four areas. Knowing them helps you organize the work.

flowchart LR
    A["Your submission"] --> B["Listing content"]
    A --> C["Install and auth"]
    A --> D["Functionality and UX"]
    A --> E["Security and compliance"]
    B --> R["Review result"]
    C --> R
    D --> R
    E --> R
    R --> F["Approved"]
    R --> G["Changes requested"]
    G --> A

The review loop: every rejection returns you to the start, so each round costs days.

  1. Listing content. The text and images in your App Store listing must describe what the app really does.
  2. Install and authentication. Installing must work smoothly and use the supported flow.
  3. Functionality and user experience. The app must do what it claims, in an interface that fits the Shopify admin.
  4. Security and compliance. Permissions, data handling, mandatory webhooks and billing rules are checked.

Listing content

The listing is your sales page, and it is also reviewed. Prepare:

  • App name and tagline. Keep them short and accurate. Do not use another brand's name, and do not make claims you cannot support, such as "number one" or "guaranteed sales".
  • Description and feature list. Describe what the app does and what it needs. Say clearly if some features require a paid plan or an external account.
  • Icon and screenshots. The icon has a fixed size and format given in the dashboard. Screenshots should show the real interface, not mock-ups with features you have not built, and must not contain private store data.
  • Pricing details. The listing must match the pricing you implemented. If the plan is $19 per month with a seven-day trial, the billing code must charge exactly that. See App Pricing Models and Billing Options.
  • Support contact and privacy policy. Merchants need a real way to reach you and a policy URL that loads and describes the data you process.
  • Test instructions. Reviewers need a plain, step-by-step path: how to open the app, which settings to change, what result to expect. If the app needs an external account, provide working test credentials.

A good habit is to write the test instructions before you write the listing description. If you cannot describe the first successful use in five steps, merchants will struggle too.

Technical requirements

Reviewers test the technical basics on a fresh development store. The most common requirements are:

  • Immediate authentication. After installation, the app must start the install and authorization flow without asking the merchant for a shop URL or any other manual step. With managed installation this is mostly handled for you, but the app must still behave well if the install is interrupted.
  • Embedded experience and session tokens. Embedded apps use App Bridge and session tokens, not third-party cookies.
  • Valid redirects and URLs. The URLs in shopify.app.toml must be HTTPS, reachable and consistent with the production host. A leftover tunnel URL from development is a classic mistake.
  • Mandatory webhooks. The three privacy topics must be configured and must answer quickly with a success status. Shopify can also check that you verify the HMAC signature, so reject unsigned requests with 401.
  • Billing through Shopify. Charging merchants for use of the app must go through the Billing API or managed pricing. Collecting payment through your own checkout for the app itself is not allowed.
  • Least privilege. Request only the scopes you use. Reviewers compare the scopes with the features described, and unexplained access is a common reason for rejection.
  • Clean uninstall. After uninstalling, the app must stop acting on the store and must delete or anonymize data according to your policy. For storefront features, theme code should be removed or inactive; this is one reason to use theme app extensions rather than editing theme files.
  • No dead ends. No endless redirect loops, blank screens, error pages with stack traces, or pop-ups that browsers block.

Performance and user experience

Storefront-facing code can slow every page of a merchant's shop, so Shopify measures its impact. Admin-facing apps are measured on the speed of the pages merchants use. The exact thresholds and measuring method change, so look them up in the current documentation. The principles stay the same:

  • Load as little JavaScript and CSS on the storefront as you can, and load it only where it is needed.
  • Avoid layout shifts: reserve space for blocks that load later.
  • Keep your admin pages fast. Fetch only the fields you need, paginate lists, and show a loading state rather than a blank frame.
  • Follow the design guidance in Polaris and App Home Design: consistent navigation, a clear save bar, readable errors and an empty state that explains the first step.
  • Give new merchants an onboarding path: what the app does, what to configure first, and how to know it works.

Built for Shopify

Built for Shopify is a badge for apps that go beyond the minimum. It is optional, but it affects how your app is presented and often how merchants perceive it. The criteria fall into groups you can recognize from this lesson: strong performance numbers measured on real merchants, good use of modern platform features such as embedded navigation and the newest App Bridge, a polished and accessible interface, a solid onboarding flow, reliable behavior, positive merchant reviews and a minimum level of adoption. Because some criteria depend on real usage, you cannot earn the badge at your first submission; plan for it as a goal after launch.

Common reasons for rejection

These are patterns, not an official list, but they cover most first-round failures:

Problem Typical fix
The app cannot be installed or hits a login wall Test with a fresh dev store and remove manual steps
Mandatory webhooks missing or returning errors Configure all three and test with signed samples
Scopes that the features do not need Remove them and re-test
Pricing in the listing differs from billing Make code, listing and plans agree
Screenshots or description show features that do not exist Replace them with real ones
Broken or localhost URLs Use production HTTPS URLs
Missing test instructions or credentials Add a short walkthrough
Errors, blank pages or console errors in main flows Fix, then retest every page

The submission flow

In practice the sequence looks like this:

  1. Finish the listing in the dashboard and run your own checklist.
  2. Deploy the production app version and confirm the production URLs in the app configuration.
  3. Install on a clean development store and walk through your test instructions as a stranger would.
  4. Submit for review. You may get automated checks first, followed by a manual review.
  5. Read the feedback, fix every item, retest, and resubmit with a short note describing what changed.
  6. After approval, publish. Keep monitoring, because the app can be reviewed again after major changes.

Run your own review first. The program below turns a checklist into a weighted score and lists blockers separately, so a high score can never hide a missing mandatory item.

Node.js Pre-submission checklist scorer

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Notice the second report: the percentage is high, yet the verdict says not to submit, because a blocker is open. That is how reviewers think too: a beautiful listing does not compensate for broken privacy webhooks.

The second stand-in checks the part of a listing that is easiest to forget, consistency between what you promise and what you configured. It compares a listing description with the plans in the billing code and flags every mismatch.

Node.js Listing versus billing consistency check

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Real and stand-in: the reviewers, the dashboard and the exact criteria are real and live only in Shopify's tools. The scorer and the comparison are models that show how to turn a vague "are we ready?" into a repeatable check you can run before every submission.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. Your pre-submission score is 95%, but the mandatory privacy webhooks return errors. What should you do?

    Mandatory items are pass or fail. A high overall score cannot compensate for a blocker, which is why the scorer reports blockers separately.
  2. 2. Which is a typical reason for a first-round rejection?

    Reviewers compare listing and behavior. A price, trial length or feature that differs between them misleads merchants and is rejected.
  3. 3. How should an app charge merchants for using the app itself?

    App charges go through Shopify so merchants see them on their Shopify bill and can cancel in the admin.
  4. 4. Why should you request only the scopes you actually use?

    Least privilege protects merchant data and is checked in review. You can add scopes later, so there is no need to ask for more than the features use today.
  5. 5. Which statement about Built for Shopify is most accurate?

    The badge is a higher bar on top of the review. Several criteria depend on real usage and reviews, so it is a post-launch goal.

Summary

  • Review covers four areas: listing content, install and authentication, functionality and user experience, and security and compliance.
  • The listing, the billing code and the requested scopes must tell the same story.
  • Use HTTPS production URLs, session tokens, the three mandatory webhooks with HMAC verification, and the Billing API.
  • Keep storefront code light and admin pages fast; follow Polaris and give new merchants an onboarding path.
  • Built for Shopify is an optional higher bar, reached after launch.
  • Run your own review on a clean dev store first, treat blockers as pass or fail, and always check the current official requirements before submitting.

Next: Testing Shopify Apps shows how to catch most of these problems automatically.