Review Velocity (30d), Amazon Seller Central

Review Velocity (30d) for Amazon Seller Central. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Voice of Customer

At a glance

The rate at which new product reviews are arriving, tracked over time. Review velocity is a leading indicator of discoverability: reviews accrue roughly in proportion to sales, so a slowing review rate while sales hold steady usually means sales are slipping (you just have not seen it in revenue yet) or that something has broken your review flow. A sharp drop is an early SEO and conversion warning, falling reviews precede falling rank, which precedes falling sales.

What it counts	New reviews received per period, plotted as a line so the trajectory (accelerating, steady, slowing) is visible. Read across 90D to see the trend, with the trailing 30D as the headline rate.
Why velocity, not total	Total review count only ever goes up, so it hides trouble. Velocity (reviews per period) reveals when the inflow slows, which is the actionable signal.
Why it is a leading indicator	Reviews trail sales by the time it takes a buyer to receive and react to a product. A falling review rate today often reflects a sales softening that has not fully shown in revenue, and predicts rank erosion to come.
Causes of a drop	Genuine sales decline; a stockout (no sales means no new reviews); loss of the Buy Box (orders going to other sellers earn them the reviews); a broken review-request flow; or removal of incentivised/manipulated reviews.
Scope	Product reviews (star ratings on the ASIN), distinct from seller feedback. Seller feedback is tracked by Negative Feedback (30d).
Rating direction lives elsewhere	This card is about how many reviews, not how good. The quality direction is Star Rating Drift (top-50 revenue).
Time window	90D trend, with 30D headline velocity
Alert trigger	drop >40% vsP, a steep fall in the review inflow rate
Roles	owner, marketing

Calculation

Calculated automatically from your Amazon Seller Central data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A beauty-and-personal-care seller reviewing the 90D line on 01 May 26. Figures are illustrative.

Trailing 30D ending	New reviews	Sales trend	Review velocity read
01 Mar 26	320	steady	baseline
01 Apr 26	305	steady	normal variation
01 May 26	165	flat on revenue, but Buy Box slipping	drop ~46% vsP, alert fires

Velocity drop  =  (305 - 165) / 305  ≈  -46%  vs prior 30D   (past the 40% alert)
Revenue        =  roughly flat over the same window
Diagnosis      =  reviews fell far faster than revenue. The Buy Box was slipping on two hero ASINs,
                  so a growing share of orders went to other sellers who earned the reviews.

Four things to notice:

1. Reviews fell faster than revenue, that is the tell. Revenue looked flat, but review velocity dropped 46%. When reviews fall much faster than sales, the orders are still happening but you are no longer the seller capturing them. The most common cause is Buy-Box loss; check Buy-Box Win Rate (top-50 ASINs).
2. It is a leading indicator, act before revenue confirms it. By the time the revenue line bends, you have lost weeks. The review-velocity drop gave an early warning that something structural changed. Treat a 40%+ drop as a prompt to investigate rank and Buy Box now.
3. Rule out the mechanical causes first. Before assuming a demand problem, check: did an ASIN go out of stock (no sales, no reviews), did Amazon strip incentivised reviews, or did your review-request flow break. Each produces the same velocity drop with a very different fix.
4. Falling reviews feed a vicious cycle. Fewer fresh reviews weakens social proof, which lowers conversion, which lowers rank, which lowers sales, which lowers reviews. Catching the velocity drop early is how you break the loop before it self-reinforces.

Sibling cards merchants should reference together

Velocity is an early warning. These tell you the cause and the quality dimension:

Card	Why pair it with Review Velocity (30d)
Star Rating Drift (top-50 revenue)	Velocity is how many reviews; drift is how good. Falling velocity with falling stars is a product problem; falling velocity with stable stars is a sales or flow problem.
Buy-Box Win Rate (top-50 ASINs)	Lost Buy Box means orders (and their reviews) go to other sellers. A top suspect when reviews fall faster than revenue.
Return Rate	A quality issue can suppress positive reviews and lift returns at the same time.
Revenue Over Time	Compare the two trends. Reviews leading revenue down is the early-warning pattern.
ASINs Stocking Out <7 Days	A stockout zeroes new sales and therefore new reviews; rule it out before assuming demand loss.
Negative Feedback (30d)	The seller-feedback counterpart to product reviews; both are voice-of-customer health.

Reconciling against Amazon Seller Central

Where to look in Seller Central:

The closest Amazon-native views are:

The product detail page review section per ASIN (review count and recent reviews), and for brand-registered sellers the Brand Dashboard / Customer Reviews tools that surface recent reviews and let you respond.

Amazon does not provide a single account-wide “reviews per period” tile for non-brand-registered sellers, so this card’s velocity view is something you would otherwise have to assemble by hand across detail pages. Brand-registered sellers get the richest native review tooling.

Timing, settlement, and reporting-lag table:

Topic	Detail
Review posting lag	A buyer can review days or weeks after purchase, and Amazon moderates reviews before they post. So the review-velocity line lags the sales that generated those reviews.
Moderation and removal	Amazon removes reviews that violate policy (incentivised, manipulated). A removal wave can drop velocity sharply even though no real change in customer sentiment occurred.
Reviews vs ratings	Star-only ratings (no written text) and full reviews may be counted or surfaced differently. The card focuses on the inflow of reviews/ratings as a sales proxy.
Brand-registry access	Brand-registered sellers have richer, more timely review data. Non-registered sellers rely on what is visible on detail pages, which can be slightly less complete.

Why our number may legitimately differ from Seller Central:

Reason	Direction	Why
Moderation timing	Ours may dip on removals	When Amazon strips policy-violating reviews, velocity drops without any underlying sales change.
No native account-wide tile	Not directly comparable	Amazon shows reviews per ASIN, not an account velocity figure. Reconciliation is per-ASIN, summed.
Posting lag	Ours lags sales	Reviews trail purchases by the buyer’s reaction time plus moderation, so velocity will not line up with same-day sales.
Ratings vs written reviews	Definition difference	If you compare written-review counts to a figure that includes star-only ratings, the totals differ.

Cross-connector reconciliation against other connectors the same seller may run:

Card	Expected relationship	What causes legitimate divergence
amazon.star_rating_drift_top_50_revenue	Volume vs quality, same source. Both read the review stream; one counts inflow, the other tracks the average rating.	A drop in velocity does not necessarily move the average rating, and vice versa; they answer different questions.
shopify review-app cards	Separate review pools. Amazon reviews live on Amazon; a Shopify store’s reviews (via a review app) are independent.	The same product accrues reviews at very different rates on Amazon vs a DTC store because traffic volume differs.

Known limitations / merchant FAQs

Why track velocity instead of total reviews? Total reviews only ever climb, so they never warn you of trouble. Velocity, the rate of new reviews, falls the moment something slows, which is exactly the signal you want. A flat or rising total can hide a collapsing inflow.

My reviews dropped but my sales look fine, what does that mean? Usually that the sales are still happening but going to someone else, most often because you lost the Buy Box, so a competing seller earns the reviews. It can also mean a stockout on a review-generating hero ASIN, a broken review-request flow, or an Amazon removal wave. Check the Buy Box first.

Why is this called a leading indicator? Because reviews trail sales and rank trails reviews. A falling review rate today often reflects a sales softening you have not fully seen in revenue, and it predicts the rank erosion that will reduce sales further. It buys you time to act before the revenue line confirms the problem.

Could a drop just be Amazon removing fake reviews? Yes. If reviews were incentivised or manipulated and Amazon strips them, velocity falls sharply with no real change in genuine customer sentiment. Rule this out before assuming a demand problem, the fix is completely different (and incentivised reviews should never be used in the first place).

Does this measure review quality? No. This card is purely about how many reviews arrive. For the quality direction (is the average rating rising or falling) use Star Rating Drift (top-50 revenue). The two together give the full picture.

Is this the same as seller feedback? No. Product reviews sit on the ASIN and reflect the product; seller feedback rates you as a seller (shipping, service) and feeds account health. Seller feedback is covered by Negative Feedback (30d).

---

Tracked live in Vortex IQ Nerve Centre

Review Velocity (30d) is one of hundreds of KPI pulses Vortex IQ tracks across Amazon Seller Central and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.