Skip to main content
Card class: Standard • Category: Voice of Customer

​
At a glance

The trajectory of your star ratings on the ASINs that actually pay the bills. It tracks how the average rating on your top-50 revenue ASINs is moving over time, and fires the moment any top-20 ASIN drops by more than three-tenths of a star. Rating is one of the strongest conversion levers on Amazon: a slide from 4.4 to 4.0 stars on a hero ASIN can quietly cut its conversion and its rank. By focusing on revenue-weighted ASINs, the card ignores the noise on the long tail and watches the listings whose ratings move real money.
What it tracksThe change over time in average star rating for your top-50 ASINs by revenue, plotted as a line so you see drift, not just a snapshot.
Why revenue-weightedA rating dip on a SKU that sells five units a month does not matter. A dip on a hero ASIN doing thousands of units does. Scoping to top-50 revenue keeps the card focused on listings where rating moves money.
Why “drift”A single bad review barely moves a well-established average; sustained drift signals a real, ongoing problem (a quality change, a bad batch, a listing that oversells). Drift is the actionable signal, not any one review.
Conversion impactStar rating is a top-tier conversion factor on Amazon. Crossing thresholds (notably below 4.0, and below 3.5) tends to depress conversion sharply because shoppers filter and skim by rating.
Rank impactLower conversion feeds lower search rank, so a rating slide compounds: worse rating, lower conversion, lower rank, fewer sales.
Direction, not volumeThis card is about how good the rating is and where it is heading. How many reviews arrive is Review Velocity (30d).
Time window90D (the selected period)
Alert triggerdrop >0.3 stars on any top-20 ASIN, a meaningful slide on a top-revenue listing
Rolesowner, operations, 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 home-fragrance seller reviewing 90D rating drift across the top-50 revenue ASINs on 01 May 26. Figures are illustrative.
ASIN (revenue rank)Rating 90D agoRating nowDriftFlagged?
Reed diffuser (#1)4.54.1-0.4Yes (top-20, >0.3)
Scented candle (#3)4.34.2-0.1No
Room spray (#7)4.64.60.0No
Wax melts (#12)4.23.8-0.4Yes (top-20, >0.3)
Gift set (#34)4.03.6-0.4No (outside top-20)
Two top-20 ASINs drifted past the -0.3 threshold:
  Reed diffuser (#1):  4.5 → 4.1  (-0.4)   - a hero ASIN crossing toward the 4.0 cliff
  Wax melts (#12):     4.2 → 3.8  (-0.4)   - already below 4.0, conversion likely hit
The gift set (#34) drifted too, but sits outside the top-20, so it does not alert (still worth a glance).
Four things to notice:
  1. The 4.0 line is where conversion bites. The reed diffuser sliding from 4.5 to 4.1 is the urgent one: it is approaching the psychological 4.0 floor where shoppers start filtering it out. The wax melts at 3.8 are already across that line, so their conversion is probably already suffering. Threshold crossings matter more than the raw size of the drift.
  2. A drift this size means a real problem, not bad luck. Three or four tenths of a star on an established ASIN takes a sustained run of poor reviews, not one unlucky buyer. The cause is almost always a quality change (a new supplier batch), a fulfilment issue, or a listing that oversells. Cross-check Return Reason Clusters by ASIN for the why.
  3. Revenue weighting is doing its job. The gift set (#34) drifted by the same -0.4 but does not alert because it sits outside the top-20. That is intentional: the card protects attention for the ASINs whose ratings actually move the business, while still showing the long-tail drift for context.
  4. Rating and returns usually move together. A quality-driven rating slide normally coincides with a rise in quality-coded returns on the same ASIN. If both move on the reed diffuser, the product or its packaging is the issue, not the listing copy. Pair with Return Rate.

​
Sibling cards merchants should reference together

Drift is the symptom. These give the cause, the volume dimension, and the downstream damage:
CardWhy pair it with Star Rating Drift (top-50 revenue)
Return Reason Clusters by ASINThe diagnostic. A rating slide plus a quality cluster on the same ASIN pinpoints a product problem.
Review Velocity (30d)The volume counterpart. Drift is how good; velocity is how many. Read together for the full review picture.
Return RateRatings and returns share root causes. A falling rating with a rising return rate on the same ASIN is a clear product signal.
Top ASINs by RevenueDefines the population this card watches. A rating slide on a top-3 ASIN is far more costly than on #45.
Order Defect RateQuality issues that drag ratings can also feed ODR and threaten account health.
A+ Content Coverage (top-50 revenue)Better A+ content can lift conversion to partly offset a rating dip while you fix the root cause.

​
Reconciling against Amazon Seller Central

Where to look in Seller Central: The closest Amazon-native views are:
The product detail page per ASIN (current average rating and rating distribution), and for brand-registered sellers the Brand Dashboard / Customer Reviews tools that show rating trends and recent reviews with response options.
Amazon shows the current average rating per ASIN but does not give non-brand-registered sellers a tidy account-wide “rating drift over time” view. This card assembles that trend across your top revenue ASINs so a slide is caught early rather than noticed when a hero listing has already lost conversion. Timing, settlement, and reporting-lag table:
TopicDetail
Rating inertiaAn established ASIN with thousands of reviews moves its average slowly; a newer ASIN with few reviews swings fast. The same -0.3 drift means different things depending on review count, fast movement on a low-count ASIN can be a handful of reviews.
Review moderationAmazon adds, removes, and moderates reviews. A removal of policy-violating reviews can shift an average up or down independent of any real sentiment change.
Posting lagReviews post after a buyer reacts and after moderation, so the rating trend lags the experience that caused it by days or weeks.
Top-50 membership churnThe top-50 revenue set changes as sales mix shifts. An ASIN entering or leaving the set changes which lines the card tracks, independent of any rating movement.
Why our number may legitimately differ from Seller Central:
ReasonDirectionWhy
Average computationSmallRounding and the exact set of reviews counted (verified-only vs all) can shift a displayed average by a fraction.
Moderation timingEither directionA removal wave moves the average without any real sentiment change; the detail page and the card may update at slightly different times.
Low-count volatilityLarger swingsA newer ASIN with few reviews can swing by more than 0.3 on a handful of reviews; treat the alert with context.
Top-50 churnSet changesThe tracked population shifts as revenue rank changes, so the card’s scope is not a fixed list.
Cross-connector reconciliation against other connectors the same seller may run:
CardExpected relationshipWhat causes legitimate divergence
amazon.review_velocity_30dQuality vs volume, same stream. Both read the review feed; one tracks the average rating, the other the inflow rate.A drop in rating does not require a drop in velocity, and vice versa; they answer different questions.
shopify product-review appsSeparate rating pools. The same product can hold a different average on Amazon vs a DTC review app, different audiences and prompts.Amazon ratings and DTC ratings rarely match exactly; use each within its own channel.

​
Known limitations / merchant FAQs

Why only the top-50 revenue ASINs? Because a rating dip only matters where it moves money. A slide on a SKU selling a handful of units a month is noise; a slide on a hero ASIN doing thousands is a real revenue threat. Scoping to top-50 revenue (and alerting only on top-20) keeps the card focused on the listings whose ratings actually change the business. Why does a 0.3-star drop trigger an alert? On an established ASIN, three-tenths of a star is a sustained run of poor reviews, not bad luck, so it signals a genuine, ongoing problem. It also frequently spans the conversion-sensitive thresholds (around 4.0 and 3.5) where shopper behaviour changes sharply. It is large enough to act on, small enough to catch early. My rating moved a lot on a new product, is that the same risk? Be careful with low-review-count ASINs. With few reviews, a couple of bad ones swing the average fast, so a 0.3 drop can be just two or three reviews rather than a trend. Weigh the drift against the review count; the same alert means more on a high-count hero than on a brand-new listing. What usually causes a rating slide? On an established ASIN, almost always a real change: a new supplier batch with a quality issue, a fulfilment or packaging problem, or a listing edit that started overselling the product. Diagnose it with Return Reason Clusters by ASIN, a quality cluster appearing alongside the rating drop confirms a product problem. How much does a falling rating actually cost me? Indirectly, a lot. Rating is a top conversion factor; dropping below 4.0 stars tends to cut conversion noticeably because shoppers filter and skim by stars. Lower conversion then drags search rank, which lowers sales further. A rating slide compounds, which is why catching the drift early matters. Does this measure how many reviews I get? No, that is Review Velocity (30d). This card is purely the direction and size of the average rating on your top-revenue ASINs. Read the two together: velocity tells you the inflow is healthy, drift tells you the sentiment is.

​
Tracked live in Vortex IQ Nerve Centre

Star Rating Drift (top-50 revenue) 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.