A set of management blocks, small circles, and document-shaped rectangles connected by lines.
Platform Rulesthrough Where the Work Breaks

It’s Time to Build the First Services for Managing 10 Shopify Installs

Shopify app makers can now build small services that connect the manual work between admin dashboards, customer recruitment, and evidence submission rather than focusing only on pre-review checks.

Published 2026. 11. 19.

A new gate has appeared before the submit button

Shopify changed its App Store submission rules on November 10, 2026. An organisation that already has published apps must have at least 10 installations from active stores on paid Shopify plans for each existing app before it can submit another new app. Development stores and stores on free trials do not count.

If app A has 12 qualifying installations and app B has 9, the organisation cannot submit app C. The condition does not apply to an organisation submitting its first app, and it does not prevent updates to an already published app. Installation counts update once a day, so clearing the final installation threshold may still take about a day to remove the restriction.

This does not mean the app itself must be paid. The rule is based on whether the installing store uses a paid Shopify plan. However, it is unclear whether stores using an app’s free plan count as qualifying installations, so builders need to check how this appears in the actual admin dashboard.

An organisation can also have only one new app under review at a time. If it fails to resolve review feedback two or more times, or repeatedly resubmits while creating new issues, a resubmission waiting period may apply and become longer with repeated cases. Shopify shows the exact date when resubmission becomes available in the admin dashboard.

New app submitters must also complete identity verification and may be asked for a government-issued photo ID and a face capture. An app with zero active installations for more than six months from its most recent publication date is permanently deleted, removed from the store, and returned to draft status. It can request review again after waiting 90 days.

The break in the workflow comes before review

Consider the operator of a six-person app maker with two published apps. The first app has 14 qualifying installations, the second has 7, and a third app is ready for release. Previously, the priority would have been refining the third app’s listing copy and test account. Now, submission itself stops until the team finds three more real users for the second app.

The operator checks installation numbers in the Shopify admin dashboard and copies them into a spreadsheet. They then confirm which stores are on paid plans, find customers who promised to install through messaging tools, and ask again by email whether they are using the app. The status of one installation is split across three places: the dashboard, a customer list, and conversation records.

Finding customers does not end with installation. Someone still needs to check whether a customer completed initial setup, used the app in real work, or removed it immediately. If a team only fills the count, installations can return to zero six months later. It needs records that identify customers who reached a first result.

Review feedback creates another chain of handoffs. A manager reads the review email, moves tasks into a work list, sends requested changes to a developer, then captures the updated screens and attaches them to the reply. Missing even one issue can lengthen the resubmission waiting period, making it more important to view the email and proof of changes in one place.

Identity verification is a separate workflow too. An operator may be asked for government-issued photo identification and a face capture. A tool that shows the verification sequence before submission could reduce cases where development is complete but the release stalls over name formatting or document preparation.

After publication, each app needs its own clock. An app with zero active installations becomes a draft after more than six months from its most recent publication date, and it also cannot meet the 10-installation condition for the next app. Calendar reminders alone are not enough. Teams need to see installation counts, the latest customer contact, and the most recent publication date together to decide which app to revive first.

Not all of this work can be automated. Deciding whether a store received value from an app and hearing directly from that customer remain human tasks. The opportunity is not to replace customer recruitment, but to connect scattered numbers, conversations, and evidence so the next action is not missed.

Other app stores also require evidence of real use first

Google Play requires personal developer accounts created after November 13, 2023 to complete a closed test before an app can be released publicly. Currently, 12 testers must participate continuously for 14 days. After that, the developer must explain its testing approach and the feedback received, then apply for production access.

The initial threshold was 20 testers, but Google lowered it to 12 on December 12, 2024 after receiving developer feedback. Paying a registration fee does not immediately lead to public release. Developers first need to recruit real test users and explain the record of that testing.

Apple has long removed apps that are not maintained from its store. If an app has not released a new version in the past three years and its downloads over the past 12 months fall below Apple’s threshold, Apple notifies the developer and requires a new version within 90 days.

If the developer cannot submit a version eligible for approval within that period, the app is removed from the store. Returning it requires keeping developer status active, updating the app, and passing review, which makes managing an inventory of older apps and their last update dates a distinct task.

In European Union App Stores, identity and business information have become conditions for distribution. Under the European Union’s Digital Services Act, Apple requires people offering apps for business purposes to provide trader status, contact details, an address, and business evidence.

From February 17, 2025, apps without the required submitted or verified information may be removed from European Union App Stores. This creates work separate from completing the app file: preparing documents, tracking verification status, and checking public information.

Four small products to build now

1. A traffic light for the next app submission

This service shows qualifying installation counts for each published app, identity verification, the app under review, and waiting status on one screen. It is for Shopify app makers with two or more published apps that are preparing another app.

It is needed now because missing only one of several conditions can stop submission. The first screen can show items such as “14/10,” “7/10,” incomplete identity verification, and the next check date. At first, users can enter the numbers manually.

2. A first-10-stores operations board

This service manages stores considering installation alongside contact records, installation status, initial setup completion, and the outcome of first use. It is for small app makers that have published a first app but have between zero and nine stores using it in practice.

It is needed now because they need customers who continue using the app, not merely installations, to avoid dormant apps. The first screen can include the contact person at each store, whether it has a paid Shopify plan, installation status, and the next contact date.

3. A review-rejection evidence bundle

This service turns pasted review emails into separate tasks and stores updated screens, test accounts, and response text in one bundle. It is for app makers and outsourced app managers who need to revise and resubmit the same app two or more times.

It is needed now because repeated resubmissions without resolving issues can lengthen the waiting period. The first screen can show an owner, completion status, screen evidence, and response-readiness status for every issue.

4. A zero-installation app rescue alert

This service records an app’s most recent publication date and active installation count, helping a team decide whether to contact customers or retire the app before six months pass. It is for makers managing several public apps, including apps for a specific industry or one or two customers.

It is worth deciding early because an app with zero installations becomes a draft and cannot be submitted again for 90 days. The first screen can show days remaining until six months, current installation count, the last customer contact date, and a “revive or retire” choice.

Why this matters where you are

App stores may differ in their exact thresholds, but the examples here show a common operational burden: proving real use, maintaining an app, or verifying who is distributing it. Check whether the platforms your product depends on require user activity, testing records, review evidence, or business documents before release or continued distribution. If they do, a small tool that keeps those records connected may be more useful than another review checklist.

What to inspect in 30 minutes today

Call one Korean Shopify app maker that operates two or more published apps and ask them to show you 15 minutes of their most recent submission preparation process. If they copy the same information more than once, or move among three or more tools between checking installation counts, contacting customers, and replying to review feedback, one of these four products may be worth building in a small form.

Sources

7 sources

Every fact in this article came from the pages below. Check them yourself.

It’s Time to Build the First Services for Managing 10 Shopify Installs | Prometheon