Amazon variations do not populate correct data.
Hi all, I am having trouble with 2 Amazon variation families which do not populate should-have values for 2 of the child ASINs and which do not show correct number of reviews at parent-ASIN level. My problem can be summarized as follows:
I have created 8 ASINs under the same category using "copy ASIN" functionality, so I can 100% say that all values are the same across all ASINs other than quantity. So they include varying numbers of single products from 40 all the way to 800. That is why variations are for.
When I created variations under 2 parents, I encounter 2 problems:
1. All reviews are merged at parent ASIN level for all except 1 child which shows different number of reviews. For this problematic child ASIN, I can confirm that 3 child ASINs under the same parent show the SAME number of reviews while this problematic one shows the number of reviews only belonging to this child ASIN.
2. per count informative pricing does not populate for 2 ASINs under each parent, making a total of 4 child ASINs not displaying the per count price. Needless to say, this will confuse customers and reduce conversion rates. See below ss:
Any idea how to solve these 2 problems?
10 replies
Danny_Amazon
Hello @Seller_mGWoqAZvKQxvf- and thanks for seeking some insight on this here on the seller forums.
I do know that inconsistent review counts like you mention can occur in situations where the system detects that the products are not materially the same or listed in different categories. This FAQ on reviews, and this one on variations have some further detail.
I would recommend processing an inventory file upload to ensure that the product details, including title, images, and descriptions, are consistent across all child ASINs within the variation family. Inventory files can help data flow more smoothly through the Amazon ecosystem. You can also monitor the review count for the problematic child ASIN, as it may align with the parent-level count over time as more reviews are accumulated.
To the per count pricing issue, my best recommendation is ensuring that the pricing information, including the "per count" value, is correctly entered and consistent across all child ASINs within the variation family.
As I understand you've already looked to confirm all information is consistent, it may be necessary to reach out to our support teams for more technical assistance.
Thanks again for visiting us here on the forums, and I hope this information helps!
