Policy Violation: Inconsistent Child Variations
We have been battling with "inconsistent child variation" policy warnings and are unable to get any resolution from the performance team. The error is;
You created one or more ASIN variations that violate our ASIN Creation policies. Selling partners may not:
-- Change the product’s detail page (parent or child) to become fundamentally different from the original product listed.
-- Change the parent product's detail page so it does not match the children.
-- Add incorrect child variations that are not true variations of the parent product.
-- Add multi-pack variations that are not manufacturer created to an already existing parent.
On listing:
https://www.amazon.co.uk/Hairpin-Table-Legs-Construction-Mid-Century/dp/B00TQZ1BDK
We are about 5 months into this and over 1000 messages/cases opened with seller support. Hours on the phone to support teams. We even managed to get through to speak to the catalogue team once and they went through all our listings and confirmed there were no issues.
About a month ago, our case was passed to the "Amazon Leadership Team," who was able to remove the policy violations on our account. They are now back again, and we have zero information from the Account Health team to let us know what the issue is.
These listings are nearly 10 years old and have had no issues of any kind until this.
We would absolutely love the fix the issues, but the performance team just won't let us know what the issue actually is!
Policy Violation: Inconsistent Child Variations
We have been battling with "inconsistent child variation" policy warnings and are unable to get any resolution from the performance team. The error is;
You created one or more ASIN variations that violate our ASIN Creation policies. Selling partners may not:
-- Change the product’s detail page (parent or child) to become fundamentally different from the original product listed.
-- Change the parent product's detail page so it does not match the children.
-- Add incorrect child variations that are not true variations of the parent product.
-- Add multi-pack variations that are not manufacturer created to an already existing parent.
On listing:
https://www.amazon.co.uk/Hairpin-Table-Legs-Construction-Mid-Century/dp/B00TQZ1BDK
We are about 5 months into this and over 1000 messages/cases opened with seller support. Hours on the phone to support teams. We even managed to get through to speak to the catalogue team once and they went through all our listings and confirmed there were no issues.
About a month ago, our case was passed to the "Amazon Leadership Team," who was able to remove the policy violations on our account. They are now back again, and we have zero information from the Account Health team to let us know what the issue is.
These listings are nearly 10 years old and have had no issues of any kind until this.
We would absolutely love the fix the issues, but the performance team just won't let us know what the issue actually is!
9 Antworten
Seller_rMl5YA3AZSVeQ
Your listing looks fine to me. Where is the problem?
Seller_tRuvBEHDedp4q
Variations on Amazon are where the Parent only differs from the children based on colour and/or size.
Looking at your listing and you have 2 different types of legs - Coffee and Bench have 2 rods, Table and Counter have 3 rods
Size option should just be that - but you have added the types Coffee, Bench, Table and Counter which are NOT valid sizes but the type of leg (3 or 2 rods)
Although the listing may have existed for 10 years, the bots will keep picking up that problem.
You should split into 2 listings - one for Coffee/Bench (the 2 rod legs), the other for Table/Counter (the 3 rod legs). Make the size variation just be a size with no mention of Coffee/Bench/Table/Counter
Also 2 variations look exactly the same to me - '71cm 3 rod/Table' seems identical to '71cm / 28 inch Table' so perhaps remove one of those variations altogether ?
Seller_67lspoZjiBFVQ
UPDATE:
We attempted to regroup our listings into pure size/colour parent variations as advised here and by the account health team, but this failed again.
I have 3/4 main scenarios remaining:
1. Inconsistent Attributes
Although we have been told by account health that these do not factor in, we have noticed some inconsistencies in attributes such as "material", "leg_shape" etc.
Most of these were never submitted by us and auto-generated by Amazon as new fields were presumably added. For example, in material they have sometimes entered "glass". Our legs are made of metal, but designed originally by Henry P. Glass, so this is where that has come from!
There are several attributes like this that we are attempting to update.
2. Inconsistent Item Package Quantity
I don't know for sure, but I feel the importance of this attribute is under-appreciated.
As per the Amazon Docs:
This field indicates the quantity of individually packed items that have their own barcode and could also be sold individually. For example, this entry would be valid for a set of two coffee items, if each could be sold individually. In this case, you would enter "2" into this field.
What I have noticed is that we actually have some duplicated ASINs for the same EAN which were created by Amazon Vendor/Retail teams.
It appears that a combination of EAN and "item_package_quantity" is actually responsible for ASIN generation, however as a seller you are unable to generate two ASINs with the same EAN. As a vendor, however, you can.
Due to this, our children have a mix of item_package_quantity = 1 or item_package_quantity = 4, depending on whether is pulls the Vendor or Seller ASIN. Our ASINs should all be 1, but Amazon refuses to fix this error in the data.
3. Parent / Child Grouping
We have already split out products that have an extra "rod" into a new parent grouping, so I can't see what else there is here to change.
4. Appeal formatting
Finally, maybe we have already fixed the issue but they are just not like the way we have written the appeal. Impossible to tell, but a possibility.
When we had appeals revoked in over marketplaces, the formatting did not seem to matter assuming the issue was fixed,
