Review collection rate is the number of reviews submitted divided by the number of review requests sent, measured for one group of orders after a fixed response window. For example: 14 reviews from 100 requests sent in March, counted 21 days after the last send, is a 14% collection rate. Track eligible orders, sends, clicks, submissions and published reviews separately to see which step is weak.
How to calculate review collection rate
Review collection rate = reviews submitted by a request cohort ÷ requests sent to that cohort, after a fixed response window.
Three words in that sentence do the heavy lifting:
Cohort. A defined batch of requests, usually "all review requests sent in a given week or month".
Submitted. Reviews the customer actually sent, before your moderation. Published reviews are a different number.
Response window. How long you wait before you call the cohort finished. I'd pick 21 or 30 days and never change it mid-comparison.
You can define it differently. Plenty of stores use published reviews divided by orders. That's fine too, but it's a different metric, and the mistake I see most often is comparing one month calculated one way with another month calculated the other way. Write the formula in the cell next to the number. Future you will be grateful.
Track the funnel, not just the final percentage
A single percentage hides where things break. Count every stage:
Stage
What you count
What a weak number usually means
Eligible orders
Orders that should get a request (delivered, not refunded, not excluded)
Missing phone numbers or emails, broken automation, opt-outs
Link clicks
Clicks on the review link
Bad timing, unclear message, customer doesn't recognise the order
Reviews submitted
Reviews received in your review app
Form too long, wrong product shown, broken mobile form
Reviews published
Reviews live on the store
Moderation backlog, spam filtering
The first stage where the numbers fall off a cliff is where you work. If only 70 of 120 eligible orders get a request, rewriting the message won't help. You've got a coverage problem, probably missing phone numbers or a Flow condition that's too strict.
Wait for the cohort to finish before you judge it
This one catches everybody. Requests sent yesterday haven't had a chance to produce reviews yet. If you compare "reviews per request this month" on the 5th of the next month, the late-month requests look terrible, and it's not their fault.
Two habits fix this:
Report by request date, not review date. A review that arrives on April 3 belongs to the March cohort if the request went out in March.
Only compare closed cohorts. If your window is 21 days, March's cohort closes 21 days after the last March request. Until then, label it "in progress".
A report of "reviews received this month" is still useful for planning moderation time. It just doesn't tell you whether this month's requests worked.
A worked example (hypothetical numbers)
Say you sell kitchen storage and you're looking at the March cohort, with a 21-day window:
Eligible orders: 120
Requests sent: 100 (20 orders had no valid phone number or email)
Link clicks: 31
Reviews submitted: 14
Reviews published: 13 (one was spam)
Now the maths:
Request coverage: 100 ÷ 120 = 83%
Click rate: 31 ÷ 100 = 31%
Review collection rate: 14 ÷ 100 = 14%
Click-to-review rate: 14 ÷ 31 = 45%
These are example figures, not benchmarks. What they tell you: 20 customers were never asked, and more than half the people who clicked didn't finish. I'd look at the review form on a phone before touching the message wording. If you're still building the process from scratch, start with how to collect your first product reviews.
WhatsApp vs email: keep the channels honest
If you send review requests on both WhatsApp and email, each tool will happily report its own success. Add them up and you'll often count the same review twice: the customer got the email, ignored it, tapped the WhatsApp link two days later and submitted. Both channels were involved. Only one review exists.
What I'd do:
Count requests sent per channel from each tool.
Count reviews submitted once, from your review app, which is the source of truth. Judge.me, for example, separates invited, web and imported reviews, and you should keep those apart too.
If you want click data per channel, use a separate tagged review link for each (for example with a UTM parameter), as long as your review app's link still works with it.
When you can't attribute a review cleanly, say so in the report rather than guessing.
Read customer replies alongside the numbers. They explain things a percentage can't.
"I haven't received it yet." Your request is going out too early. Move it later, or trigger it from delivery instead of fulfilment. Our guide on when to ask for a review after delivery covers the timing.
"Which order is this?" Name the product in the message. Customers with several orders need the context.
"The link doesn't work." Test it on Android and iPhone, on mobile data, for a product with variants.
With WhatFlow, review requests go out on WhatsApp as approved template messages, typically triggered by an order event in Shopify Flow, and they link to your review app's form. Customer replies land in the shared inbox, so someone sees "the link doesn't work" the same day instead of a month later.
Don't over-read small samples
Twenty requests and three reviews is not a trend. Neither is a jump from 11% to 15% across two months with 60 requests each. With small numbers, one product, one courier delay or one big sale can swing the result more than any wording change.
Keep raw counts visible next to every percentage. Change one thing at a time. Write down anything else that happened that month: a Diwali sale, a stock-out, a new courier. If your list is small and you still want to test message wording, A/B testing WhatsApp messages on a small list shows how to do it without fooling yourself.
Free plan available
Run WhatsApp for your Shopify store with WhatFlow
Templates, COD confirmation, Shopify Flow automations and a shared team inbox with no seat fees. Every feature is included on every plan, including Free.
Divide the number of reviews submitted by customers in a request cohort by the number of review requests sent to that cohort, after a fixed response window such as 21 days. Write the formula next to the number so everyone reads it the same way.
What is a good review collection rate for a Shopify store?
There's no reliable universal benchmark, because product type, delivery time, channel and audience vary so much. Compare your own finished cohorts month to month instead of chasing someone else's number.
Why did my review rate drop when I sent more requests?
Usually because the denominator grew faster than the reviews, or because recent requests haven't had time to get responses yet. Compare only cohorts whose response window has closed.
Should I count WhatsApp and email review requests separately?
Yes. Track requests and submissions per channel, and don't add up each tool's reported conversions, because two tools can claim the same review.
