A seller in r/FulfillmentByAmazon reports that Amazon has stopped combining reviews across their variation family — down to separating ratings by size — while direct competitors with even broader parent-child structures (size and style) still show pooled reviews. If your review count suddenly looks fragmented, this covers what’s being observed and what’s actually within your control.
What’s being reported
- Ratings and reviews are being separated at the child-ASIN level even when the variation template appears correctly built.
- The enforcement looks selective and inconsistent: competitors in the same category and with the same or more complex variation themes retain combined reviews.
- In this case, the split happens by size alone — historically one of the least controversial reasons to keep reviews unified, since size rarely changes the product experience.
- No confirmed policy announcement is cited in the thread, so the working assumption in the community is a rollout or catalog-side reclassification rather than a seller error.
Why it matters commercially
- Social proof dilution. A parent listing with 800 reviews converts very differently from six children showing 90–150 each, even with identical total volume.
- Badge and placement risk. Lower per-child review counts can weaken competitiveness for Amazon’s Choice-style treatments and organic placement where review signals contribute.
- PPC efficiency. The same click cost now lands on a listing with visibly thinner validation, which tends to show up as a conversion-rate drop before it shows up in revenue.
- Competitive asymmetry. When the enforcement is uneven, you’re not just losing your own social proof — you’re losing it while a rival keeps theirs, which widens the gap on the same search results page.
Practical steps sellers typically take
- Audit the variation family first. Confirm the parent is a valid non-buyable parent, all children share the same variation theme, and no child has drifted into a different browse node or product type. Catalog inconsistencies are the most common fixable cause.
- Document the competitor comparison. Screenshot competitor parent listings showing combined reviews across equal or broader variation themes. A concrete side-by-side is far more effective in a Seller Support case than a general complaint.
- Open a case through Catalog / Variations, not Reviews. Review teams generally can’t act on variation-level review pooling; the catalog team can act on how the family is structured.
- Avoid “fixing” it by breaking the family apart or re-parenting repeatedly. Repeated variation surgery risks losing review history entirely and can suppress listings.
- Rebuild proof at the child level in the meantime. Vine enrollment on the affected children and a consistent post-purchase follow-up sequence help each child stand on its own if the split persists.
- Watch for silent recombination. Several of these rollouts have historically reverted or been applied unevenly over weeks, so it’s worth re-checking before making drastic structural changes.
How Squatio helps
The hard part here isn’t the diagnosis — it’s proving the asymmetry and quantifying what the split is costing you.
- Use Squatio Decode (ASIN lookup, listing visibility & Sentiment IQ review analysis) to pull review counts and ratings at both the parent and individual child level for your listing and your competitors. That gives you a dated, comparable record of who is pooling reviews and who isn’t — exactly the evidence a catalog case needs. Sentiment IQ also tells you which themes in your existing reviews carry the most weight, so you know what to reinforce on the children that lost the most social proof.
- Run Reveal (Reverse ASIN) against the affected children to see which keywords they were ranking for before and after the split, isolating where lost review depth is actually costing you placement rather than guessing.
- If organic placement slips, Squatio Optimize (PPC intelligence) helps you see where competitors are advertising on those same terms so you can decide whether to defend with ad spend during the recovery period instead of bleeding conversion rate quietly.
Has anyone successfully gotten reviews recombined across a variation family recently — and if so, did it come from a catalog case, a variation rebuild, or did it just quietly revert on its own?
Source: Reviews being separated by size variation — r/FulfillmentByAmazon