Brands should think about review continuity before a SKU transition reaches the product-detail-page level.
A new version can look commercially weaker if it loses the visible benefit of older review history. That risk is higher when the new SKU changes flavor, formulation, function, pack structure, customer experience, or another attribute that may make inherited review strength less dependable.
Start with what is changing
The first question is not whether the brand wants to keep reviews. Of course it does.
The useful question is whether the new SKU still represents the same customer experience. Amazon’s review-sharing guidance points in that direction: review sharing depends on whether variation differences are minor and do not affect functionality.
If the product has changed enough that customers will experience it differently, teams should expect review continuity to be less certain.
Plan for standalone trust
SKU-transition planning should include review readiness.
That means identifying the old ASIN’s review strength, the new ASIN’s starting point, the launch traffic plan, and the risk of sending customers to a page with little standalone feedback.
The safer assumption is that each important SKU may eventually need enough review depth to stand on its own.
The practical takeaway
Review continuity should not be an afterthought in a SKU transition.
Brands should map the review risk before launch, understand which review strength is inherited and which is standalone, and build compliant feedback opportunities around the new customer experience instead of assuming old review equity will carry forever.