%20png%20copy.avif)
Most app teams treat reviews as something that happens to them. They ship, they wait, and they hope satisfied merchants wander back to the listing to leave five stars. They mostly don't. The result is predictable: roughly 35% of apps on the Shopify App Store have no reviews at all, sitting invisible in a marketplace where social proof is the deciding factor.
Reviews are the highest-leverage real estate on your listing because they do two jobs at once. They are a ranking signal — Shopify states plainly that positive reviews make your app appear higher in search results and category pages. And they are a conversion signal — the thing a merchant scans before deciding whether to trust you with their store. Get them flowing and they compound. Leave them to chance and you stall.
The catch is that the space between "ask for reviews" and "ask in a way that is both compliant and effective" is narrow, and full of ways to get reviews removed — or worse, to put your Partner Program standing at risk. Asking badly isn't just ineffective. It can be a policy violation.
This guide covers both halves: the rules that keep you safe, and the velocity tactics that actually move the number. They are not in tension. The teams that win reviews are the ones that built a compliant, repeatable engine — and never had to think about the rules again because they never came close to breaking them.
Start with what reviews actually buy you, because it's more than a star count.
The first thing they buy is rank. The Shopify App Store's search algorithm has been behavior-driven since its 2023 shift toward how merchants interact with results, and review quality feeds directly into that — apps with strong ratings and retention rank higher, while weak signals read as a mismatch. The second thing they buy is the install itself. The top rating brackets command the lion's share of organic discovery, accounting for the majority of installs across the platform. Reviews are simultaneously how merchants find you and why they choose you.
Now the detail that changes how you should think about all of this. Your overall rating is not a simple average of star ratings — Shopify weights it to prioritize recent, useful, and trustworthy reviews, and it updates dynamically as reviews are added or removed. Read that twice, because it has a direct strategic consequence. A burst of fifteen five-star reviews in 2023 does less for you today than a steady trickle of fresh ones. The system is built to reward recency. That is why review velocity — the pace at which you gather new reviews — matters more than the lifetime total most teams fixate on. A monitoring tool that tracks the App Store treats slowing review velocity as an early warning of engagement problems, before rankings even react.
So the worst position isn't a low rating. It's silence. Across the store, Shopify users have left over 1.3 million app reviews, and the apps capturing them are pulling away. The zero-review cold start is the single most common reason a good app stays invisible, and it's entirely self-correctable.
Before you build any asking strategy, you need to know who is eligible to say yes — because a surprising share of your happiest merchants may not be allowed to review you, and the timing of your ask depends on getting this right.
The base rule is simple: only merchants who have your app installed can leave a review, and they can also review within 45 days of uninstalling. Each merchant gets one review per app, which they can update later — including the star rating. When a review publishes, it shows the store name, country or region, and how long the merchant has had the app installed.
Here is the rule that trips up otherwise careful teams. As of December 11, 2024, merchants on any type of trial plan — including paid trials — are no longer eligible to leave a review. This quietly invalidates a common tactic: prompting for a review during the free trial, when enthusiasm is highest. If you ask a merchant who is still on a trial plan, the review won't post, and you'll have spent your one good moment on an impossible request. The implication is that your asking window should open after a merchant converts to a paid plan and has had enough real usage to have an opinion worth sharing.
One more thing to set expectations: submitting a review doesn't guarantee publication. There can be a delay while Shopify checks it against policy, and reviews can be removed or archived later if they become outdated or non-compliant. You're not owed a published review just because someone wrote one.
This is the section to internalize, because the downside here isn't a slap on the wrist. Manipulating reviews violates Shopify's review policies and your Partner Program Agreement — the agreement that lets you operate on the platform at all.
The entire rulebook collapses into one test: ask in neutral language, and never incentivize. You are allowed to ask merchants to review your app. You are not allowed to ask them to review it favorably, and you are not allowed to give them anything for doing it.
The line is easier to see with examples. Shopify's own guidance treats a request like "we value feedback, let us know how we're doing" as acceptable — it invites honest input without steering the outcome. By contrast, these cross the line:
Beyond solicitation, Shopify also polices content. It intervenes on reviews containing inappropriate content (swearing, slurs, threats) or personal information like phone numbers or email addresses — though it won't remove a review just for naming a first name and last initial. And reviews can be archived when they're judged outdated or less relevant, with no appeals accepted on archived reviews. The recency-weighting from Section 1 cuts both ways: fresh reviews count for more, and stale ones quietly fade.
The honest framing for your team: design your asking system so that compliance is automatic, not a judgment call someone makes under pressure to hit a number. If your prompt copy would still be fine if a Shopify reviewer read it tomorrow, you're safe. If it leans on the word "positive," a star count, or a reward, rewrite it.
There's one tactic worth addressing directly, because it's everywhere and the rules around it are genuinely unsettled: review gating.
Gating is the pattern where you first ask "how's your experience?" — and route the happy responses ("Good") to the public App Store review modal while sending the unhappy ones ("Bad") to a private feedback form. The logic is obvious: capture the good reviews publicly, intercept the bad ones before they go on your listing.
Here's what makes it a gray zone rather than a clear no. The pattern is widely used — and notably, Shopify's own apps like Shopify Bundles and Subscriptions have used a "Good routes to a review, Bad routes to feedback" card on their dashboards. When a partner asked Shopify Support whether third-party apps could replicate that exact logic, Support didn't give a definitive yes or no. The question, at least as of that thread, remained open.
The research-minded read: routing only satisfied merchants toward the public review effectively filters for positive reviews, which sits uncomfortably close to the prohibition on soliciting positive reviews — even if no single screen ever uses the word "positive." That Shopify does it in its own apps doesn't mean a third-party app gets the same latitude, and Support's non-answer is not the same as approval. If a tactic's compliance hinges on Shopify declining to clarify it, that's risk you're choosing to carry.
The safer version keeps the value of the pattern without the filtering: ask everyone for feedback through a neutral prompt, surface the "Get Support" path prominently so frustrated merchants have an obvious alternative to venting in a review, and let the review request itself go to all eligible merchants regardless of how they feel. You'll catch some criticism publicly. You'll also be unambiguously compliant — and a well-handled critical review with a thoughtful developer reply often reassures prospects more than a wall of flawless five stars.
Compliant copy is half the job. The other half is the mechanism — how and when the ask reaches the merchant. Shopify has made this materially easier than it used to be.
The biggest recent change is the Reviews API, which lets embedded apps trigger a native review modal directly inside the Shopify admin via App Bridge. This replaced the old flow, where you had to bounce merchants out to a multi-step App Store redirect — every extra step shedding people who would have left a review if it had been frictionless.
Three things matter about how it works:
If you're not yet on the Reviews API, there's a simpler lever in the meantime: you can deep-link straight to an open review modal by appending #modal-show=WriteReviewModal to your app listing URL. Drop that link into a post-success email or in-app message and you remove the "find the listing, find the button" friction that kills most review intentions.
The single biggest determinant of whether an ask converts is when it fires. Shopify's own guidance is explicit: request a review at the end of a successful workflow, not when a merchant first opens your app or in the middle of a task. And don't tie the prompt to a merchant's own action — if rate-limiting then suppresses the modal, your app looks broken.
The principle underneath: ask at the moment of realized value. Right after the merchant completes setup successfully. Right after your app does the thing it promised — recovers a cart, syncs an order, generates the report. That's when the experience and the gratitude are freshest. Asking before value has landed is asking a stranger to vouch for you.
Two more guardrails. Ask after a positive support interaction — a merchant you've just helped is often willing to share that experience. And always let a merchant who declines opt out of being asked again. Pestering doesn't just annoy — it's a documented thing not to do.
Now combine the rules and the mechanics into an actual engine. The goal is not a one-time campaign. It's a steady, self-sustaining flow of fresh reviews, because — recall Section 1 — the rating rewards recency, so the work is never finished.
The losing posture is the batch blast: you notice your review count is low, you email your entire user base asking for reviews, you get a small spike, and then nothing for six months as the rating slowly stales. The winning posture is to wire the ask into the product so it fires continuously at the right moments, for every newly-eligible merchant, without anyone remembering to run a campaign.
Building that engine comes down to a few decisions:
Done right, this turns reviews from a periodic scramble into a compounding asset that quietly lifts both your rank and your conversion rate every week.
You will get critical reviews. How you handle them is itself a signal — to the merchant, to prospects reading the thread later, and to Shopify.
Use the reply feature. You can respond to any review on your listing to add context, and both reviews and replies can be edited after publication. Know that when you reply, the merchant who left the review receives an email — and gets another email each time you edit it, so don't reply five times. Shopify's guidance for a negative review you disagree with is to respond, seek to understand the feedback, and share your perspective respectfully. A calm, specific, solution-oriented reply frequently earns an updated review — and because merchants can revise their rating, a one-star can become a four-star without a single new reviewer.
Keep your replies focused and functional. The reply box is not a place to argue. If a reply is reported for language that violates the Partner Program Agreement or creates a negative merchant experience, the developer — you — faces disciplinary action or removal. The same rules that govern how you ask govern how you respond.
Reserve removal requests for genuine violations. If a review is fake, incentivized, contains personal information, or breaches content rules, you can report it, and Shopify may edit or remove it. A merchant who is simply unhappy and wrong is not a violation — that one you answer, you don't report. Trying to scrub legitimate criticism is both futile and a bad look.
If you're standing this up from scratch, build it in this order.
Notice what's absent from this list: any version of "ask for five stars," any incentive, any filtering of who gets to review based on how they feel. The engine works precisely because it doesn't need those things.
Reviews behave like the App Store's ranking flywheel in miniature. Compliant, well-timed asks produce fresh reviews; fresh reviews lift your recency-weighted rating and your search placement; better placement brings more installs from merchants who, asked at the right moment, leave more fresh reviews. The loop compounds — but only if you keep feeding it, because recency-weighting means a rating you stop maintaining is a rating that's already decaying.
The teams that struggle with reviews are almost never the ones who got caught breaking a rule. They're the ones who never built the engine, waited for reviews to appear, and watched a third of the marketplace pass them with louder social proof. The rules aren't the obstacle. The silence is. Build the compliant engine once, point it at your real moments of value, and let velocity do the rest.
%20-%20white.svg)