A small online store selling handmade ceramics ships around a thousand orders a month. Its product pages carry a few dozen reviews in total, most of them written by friends and early customers in the first year. The most visible review on the best-selling mug is a one-star complaint about a breakage in transit from eighteen months ago. Meanwhile, hundreds of happy customers have their mugs, use them every morning, and have never been asked what they think.
That gap between satisfied customers and visible reviews is common, and it's mostly a process problem. Stores that collect reviews steadily ask every customer, at a sensible moment, in a way that takes seconds to answer, and they respond to what comes back. None of that requires a big budget, but it does require being deliberate about timing and fair about who gets asked.
This article covers what to decide before automating review requests, what the automated version does step by step around Shopify and your review app, and the rules you need to stay within.
Why most stores have fewer reviews than they should
When a store's review count is low, the cause is usually one of a few things:
- Nobody asks. The review app is installed, but the request email was never switched on or was turned off after a complaint.
- The timing is wrong. The request goes out with the shipping confirmation, days before the customer has the product, or so long after delivery that the moment has passed.
- The request is generic. A plain email titled "How did we do?" with no product photo gets ignored next to everything else in the inbox.
- It's too much work. The customer has to log in, find the product and fill in several fields.
- Problems go public first. A customer with a damaged item has no easy way to get help, so the review becomes the complaint channel.
The evidence suggests that asking works. BrightLocal's Local Consumer Review Survey 2026 found that 83% of people who were asked to leave a review went on to leave one, and that 74% of consumers look for reviews written in the last three months. The survey covers local businesses, so treat it as a signal about how people respond to being asked and how much they value recent reviews, rather than a benchmark for online stores. The recency point matters for any store: a page whose newest review is a year old tells shoppers something, even if the product is excellent.
Fix the process before you automate it
Time the request to the product
Base the timing on the delivery date. Most carriers report a delivered event that your store or shipping app can read. Then add a delay that suits the product: a few days for a mug or a phone case, two or three weeks for skincare or anything that takes time to judge. Set this per product type, since one delay for the whole store will be wrong for most of it.
Ask everyone the same way
Send the review request to every customer on the same terms, whatever you think their experience was. Google's review policies prohibit selectively asking happy customers for reviews, and the US Federal Trade Commission's rule on fake reviews and testimonials, announced in August 2024, bans incentives that are conditioned on a review being positive or negative, along with misrepresenting suppressed reviews. Setting the request up to be even-handed from the start keeps you on the right side of both.
Give problems a separate, easy route
Make it easy for a customer with a problem to get help: a clear link to support in every post-purchase email, and a fast response when they use it. Helping an unhappy customer is good service. Using that help to stop them leaving a review is something the rules above are designed to prevent, so keep the two separate. Everyone still gets the review request.
Decide where reviews should go
Product reviews on your own site, seller ratings that show up in Google Shopping, a third-party review site: each serves a different purpose. Pick one primary destination for the request so customers aren't asked to do three things. Your review app can often syndicate reviews to Google once collected.
What the automated version does
- Waits for delivery. When the carrier reports an order delivered, the system starts the clock for that order based on the product type.
- Sends a personal request. At the right time, the customer gets an email, or a text if they've opted in to texts, showing a photo of the exact product they bought, with a one-tap star rating that opens a short review form already filled with their order details.
- Reminds once. If there's no response after a week or so, one reminder goes out. Then the system stops.
- Flags problems to support. A low rating or a review mentioning damage, a missing item or a sizing issue creates a support ticket so someone can contact the customer and fix the problem. The review is published like any other.
- Drafts replies to reviews. For each new review, the system drafts a reply in your brand's voice, thanking positive reviewers specifically and responding to criticism with what you're doing about it. Someone approves the reply before it posts.
- Summarizes themes. Each month, you get a summary of what reviews are saying: recurring praise, recurring complaints, sizing or packaging issues, product questions that the listing should answer.
Replying to reviews matters as well. In the same BrightLocal survey, 80% of consumers said they were likely to use a business that responds to all of its reviews. Responding to every review by hand is the step most stores drop when they get busy, and it's where drafted replies save the most time.
Our review and referral engine handles this loop alongside your existing review app, and the ecommerce and retail page shows how it fits with listings, reordering and repeat customer systems.
A worked example
Take the ceramics store from the opening. Its shipping app already reports delivered events, so the review request is retimed to go five days after delivery for mugs and plates and ten days after for larger pieces like planters. The request shows a photo of the exact item, asks for a star rating with one tap, and only then asks for a few words and an optional photo. Every customer gets the same request. A customer who rates a mug two stars and mentions a chip in the glaze gets a message from support the same day offering a replacement, and her review is published as written. The owner spends ten minutes each morning approving drafted replies to the previous day's reviews, editing a few to add a personal detail. As new reviews come in from customers who use the mug every day, the eighteen-month-old complaint stops being the first thing shoppers see.
What to watch out for
- Review incentives. If you offer anything for a review, such as a discount on the next order, it must not depend on what the review says, and you should disclose it where your review platform requires. Check the rules of each platform you collect on.
- Marketplace rules. Marketplaces such as Amazon tightly control how sellers may contact buyers and ask for reviews. Follow each marketplace's own process for marketplace orders, and keep your automated requests to orders from your own store.
- Email consent and frequency. Review requests are transactional in spirit, but they still count toward how many emails a customer gets from you. Coordinate them with marketing emails so customers aren't flooded in the week after purchase.
- Generated replies that sound generated. Replies that all read the same put people off. Keep them short, specific to what the reviewer said, and approved by someone who knows the product.
- Product claims in reviews. In categories like supplements or skincare, reviews can make health claims you couldn't make yourself. Know your review platform's moderation options and your obligations in your category.
How to tell whether it's working
Track the share of delivered orders that produce a review, the average time from delivery to review, and the number of reviews per product in the last three months, since recency is what shoppers look at. Measure the share of reviews that get a reply and how quickly. Watch the support tickets created from low ratings, both how quickly they're resolved and what they're about, because recurring themes such as packaging damage point to fixes that will improve future reviews. If the response rate is low, test the timing and the wording of the request before assuming customers won't review.
Where to start this week
Check whether your store can see the carrier's delivered event for each order, because review timing depends on it. Look at your review app's settings and confirm the request is switched on, timed from delivery and sent to every customer. Rewrite the request so it shows the product photo and asks one simple question first.
Then reply to your last twenty reviews, good and bad, in your own words. It will show you how long replying really takes and what a good reply sounds like for your brand, which is exactly what you'll want the drafted replies to match once you automate them.
For a quick read on where reviews sit among the other jobs worth automating in your store, run the free PATH report on your website. If you'd like to talk it through, book a call.