Share reviews across Shopify variants when the variants are the same product in a different color or pattern. When they differ in size, capacity or compatibility, keep the variant visible on each review so shoppers know which one it describes. Never group unrelated products to inflate the count, and never guess a missing variant. The goal is reviews a shopper can actually interpret.
Why variant context matters
"Fits perfectly" is a great review. It's also useless if the shopper choosing between S, M and L can't see which size the reviewer bought.
Same with "holds everything I need" on a bag that comes in 20L and 35L, or "works great with my phone" on a case that comes in four models. The review is honest. Without the variant, it's just not much help.
Which variant differences actually matter?
Go through your catalog and sort variant types into two groups.
Variant type
Does it change the experience?
What to do
Color, print, pattern
Usually not (except "the color looks different in person")
Share reviews across all; showing the color is a nice extra
Share, but show the variant; consider separate listings if very different
Model or compatibility
Yes, a lot
Show the variant, or keep reviews separate
Old vs new version
Can be
Keep history; explain what changed
Your review app can't work this out from a variant label. "Blue / Large" and "V2" mean nothing to software. You decide which differences matter, then configure the app and your product copy to match.
Check what your review app stores
Before you configure anything, check what your review app actually records. Does each review keep the variant the customer bought? Does that survive an import, a product merge or a migration to another app? Does the variant show on mobile, or only on desktop?
Submit a test review for a specific variant, then look at it on your product page on your phone. If you can't tell which variant it was, neither can a shopper.
If you're planning to switch review apps, add variant data to the checklist. It's one of the things that gets lost. Our guide to migrating review apps without losing context covers what to check.
Don't invent missing variant data
Some reviews won't have a variant attached: older imports, reviews from a web form, reviews from before you added sizes. Leave them as they are.
It's tempting to go back and label them ("this one probably bought the large"). Don't. A precise-looking label based on a guess is worse than no label, because shoppers trust it. Review content belongs to the person who wrote it, and the record of what they bought should come from the order, not from your memory.
Grouping: when it's fine and when it isn't
Many review apps let you group reviews across products, for example when the same item is listed separately for each color. That's fine. It's the same product.
It's not fine when the products are materially different. Grouping your premium leather wallet with your budget canvas one so the canvas wallet shows 300 reviews instead of 12 tells shoppers something that isn't true. They'll find out when the canvas one arrives.
A simple test: would a shopper reading a review on this page reasonably assume it's about the thing they're looking at? If not, don't group it.
When the product changes
Say you sell a water bottle and redesign the lid because the old one leaked. You now have 40 reviews mentioning leaks, all about the old lid.
Don't delete them. They're honest, and hiding negative reviews is its own trust problem. Instead:
Say what changed in the product copy. "Updated in March 2026: new screw-top lid with a silicone seal."
Reply to the old leak reviews if your app allows it: "Thanks for flagging this. We redesigned the lid in March 2026 to fix exactly this problem."
If your app supports it, show the version or date on each review.
The opposite applies too. If old reviews praise a feature you've removed ("love the built-in strap"), don't let that read like a current spec. Update the product page so nobody buys expecting the strap.
Example: a two-size bottle with a lid change
Imagine a bottle sold in 500ml and 1L, with the lid redesigned this year.
A review saying "fits in my car cup holder" is about the 500ml. Shown without the size, it misleads 1L buyers.
A review saying "lid leaks in my bag" from last year is about the old lid. Keep it, reply to it, and make the new lid obvious on the page.
A review with no size and no date stays as it is. Don't label it.
Then ask a colleague to pick a size on their phone and tell you which reviews apply.
Ask for the detail you'll need later
You can make future reviews easier to interpret at the point you ask for them. If your review app supports custom questions, add one or two that matter for your product: "What size do you usually wear?", "What height are you?", "Which phone model do you have?". A review saying "fits perfectly, I'm 160cm and usually a small" is worth three that just say "fits perfectly".
You can nudge it in the request message too:
Hi {{1}}, how's the {{2}} fitting? If you leave a review, mentioning your usual size really helps other shoppers choose: {{3}} If they can't, adjust the display or add a line of copy above the reviews.
Let shoppers ask when reviews don't answer it
Even with perfect variant labels, some shoppers will still be unsure: "will the 35L fit as cabin baggage on this airline?", "does this case fit the Pro or only the standard model?". Reviews can't answer every case.
Give them a quick way to ask. A WhatsApp chat button on the product page means the question comes to you rather than to a competitor's product page. With WhatFlow, those chats land in a shared team inbox inside Shopify, and the chat button is free and matches your theme. Answer from your spec sheet, not from a review. Our guide to pre-purchase product questions on WhatsApp has reply examples.
Free plan available
Run WhatsApp for your Shopify store with WhatFlow
Templates, COD confirmation, Shopify Flow automations and a shared team inbox with no seat fees. Every feature is included on every plan, including Free.
Every time you add a variant, merge listings, change a product significantly or switch review apps, open three or four product pages on your phone and check the reviews still make sense. It takes ten minutes. If you use structured data for review stars in search, our guide to product review schema explains what search engines expect to match.
Frequently asked questions
Should reviews be shared across product variants?
Yes when the variants are the same product in a different color or pattern. Be more careful when variants differ in something that changes the experience, like size, capacity or compatibility, and make sure shoppers can see which variant each review is about.
Can I group reviews from different products to get a higher review count?
Only if the products are genuinely the same item sold under different listings. Grouping materially different products so one borrows the other's reviews misleads shoppers.
What do I do with old reviews after I change a product?
Keep them, because they're honest history. Make the change clear in your product copy, and don't let praise for a removed feature read like a claim about the current version.
Can I add the variant to a review that doesn't have one?
Not by guessing. If the original order or submission doesn't show the variant, leave it unknown rather than inventing a label.
