Review velocity beats review count

Review count is the number every store watches and the one that tells you least. It only goes up, it says nothing about the last six months, and a shopper comparing two listings is not really counting. They are checking whether other people bought this recently and were fine.

The number that actually moves is velocity: how fast fresh reviews arrive, measured against the rest of your category. It is possible to gain reviews every month and still fall behind, and if you only watch the total you will not see it happen.

Why freshness beats volume

Recency does the work for three separate reasons, and they compound:

• Shoppers read the recent ones. A listing with 900 reviews whose newest is from last year reads as a product that used to be good. One with 200 and a steady flow this month reads as alive.
• Marketplace ranking appears to weight recency. No marketplace publishes its ranking factors, so treat this as the working consensus among sellers rather than something anyone can verify: the rate and freshness of reviews seem to matter, not just the raw total.
• Recent reviews describe the current product. If you changed a formula, a supplier or the packaging, old reviews are describing something you no longer sell.

The comparison that matters

So track two numbers per product: your fresh reviews per month, and the leading listing's. The ratio between them is the thing to move. Your own total is context at best.

If a competitor is adding reviews eight times faster than you, no amount of listing copy closes that gap.

Ask at the right moment

The most common mistake is asking on delivery. The product arrived, nobody has used it, and the honest answer is "I do not know yet." You get a lower response rate and shallower reviews, which are worth less to the next shopper.

Ask once they have had a real experience of it:

• 7 to 14 days after delivery for most products. Long enough to have formed an opinion, soon enough to still care.
• Later for anything with a slow effect, such as skincare or supplements, where the useful review is at 30 days rather than 7.
• Earlier for obvious-on-arrival products where the verdict is immediate, like apparel fit.

And keep the ask to one question and one click. Every extra step cuts response rate. Star rating in the email itself, comment optional, done.

Route the feedback before it is public

This is where stores get nervous, so be precise about what is and is not acceptable. You may not filter which customers get asked, and you may not suppress a negative review. That is review gating, it breaks marketplace policy, and it is dishonest.

What you can do is ask everyone the same first question and route on the answer, giving unhappy customers a support path as well as, never instead of, the public one:

1. Ask every customer the same question: how did it go, one to five stars.
2. Four and five stars go to the public review link, because they are already willing.
3. Three and below get BOTH at once, in the same message: the public review link, presented just as prominently, and an offer to put the problem right. Not one then the other. Most people who have a problem fixed would rather tell you than warn strangers, and the ones who still want to post can do it without waiting for you.

The distinction is simple: routing to support is fine, and everyone must still be able to leave a public review. Nobody gets excluded from being asked.

Mine the 3-star reviews

Your 1-star reviews are usually shipping and your 5-star reviews are usually a sentence of praise. Neither is useful. The 3-star reviews are the most valuable free research you have: they come from people who wanted to like the product and hit one specific problem, and they are calm enough to say what it was.

Read the last fifty across your catalogue and sort them into two piles:

• Repeated product problems. If eleven people mention the same thing, that is your next product or packaging fix, and it is already costing you sales.
• Repeated expectation gaps. If people are surprised by size, colour or what is in the box, that is not a product problem. It is a listing problem, and you can fix it this week by answering it in the images and bullets before anyone else raises it.

Where Wizzy comes in

Review collection fails quietly. It works for a month, then the timing drifts, the ask goes stale, nobody is watching the category, and the 3-star pile never gets read. Wizzy times each request to when the customer has actually used the product, routes the response so problems reach you before they reach the listing, tracks your velocity against the category rather than your own total, and surfaces the repeated complaint that your next listing update should answer.