Product Manufacturer and Responsible Person unable to change misleading informaiton in the Amazon catalogue.
Hi all,
We are the product manufacturer and legally responsible person for our products - light bulbs.
Amazon recently changed the attribute 'valid values' for item_shape for many of our products.
When we try to update the listings to the new Amazon valid value 'Globe(G)' it disagrees with the Amazon catalogue value for item_shape as the old value is 'Standard' so won' t update the value, even though 'Standard' is supposedly no longer a valid value?!
However worse still it won't recognise the existing Amazon catalogue value 'Standard' now either as valid value, meaning we cannot save the edit(s), so are in a Catch 22 where we cannot update or edit any of our listings. Uploading a 'full update' feed doesn't work either i.e.
1. Cannot save the new value as it disagrees with the Amazon catalogue value.
AND
2. Cannot save the old value as it is not a valid value.
It's enough to drive you insane - clearly nobody tested how this would work in practice?!
As the product manufacturer we should have complete control over editing the specifications listed on the Amazon ASIN.
Seller Support are being as hopeless as ever, some agents have updated a number of ASINs for us but other agents have no idea and keep saying the catalogue cannot be changed. Well it can, because your colleague did it last week on a different ASIN!?
Does anyone have any ideas how to get in contact with someone at SS who is senior enough to help get the catalogue change done on an number of ASINs, or is it a case of just raising nee case IDs until someone does something useful?!
As the manufacturer of the item it is a ridiculous situation to be in.
Cheers
Jeff
Product Manufacturer and Responsible Person unable to change misleading informaiton in the Amazon catalogue.
Hi all,
We are the product manufacturer and legally responsible person for our products - light bulbs.
Amazon recently changed the attribute 'valid values' for item_shape for many of our products.
When we try to update the listings to the new Amazon valid value 'Globe(G)' it disagrees with the Amazon catalogue value for item_shape as the old value is 'Standard' so won' t update the value, even though 'Standard' is supposedly no longer a valid value?!
However worse still it won't recognise the existing Amazon catalogue value 'Standard' now either as valid value, meaning we cannot save the edit(s), so are in a Catch 22 where we cannot update or edit any of our listings. Uploading a 'full update' feed doesn't work either i.e.
1. Cannot save the new value as it disagrees with the Amazon catalogue value.
AND
2. Cannot save the old value as it is not a valid value.
It's enough to drive you insane - clearly nobody tested how this would work in practice?!
As the product manufacturer we should have complete control over editing the specifications listed on the Amazon ASIN.
Seller Support are being as hopeless as ever, some agents have updated a number of ASINs for us but other agents have no idea and keep saying the catalogue cannot be changed. Well it can, because your colleague did it last week on a different ASIN!?
Does anyone have any ideas how to get in contact with someone at SS who is senior enough to help get the catalogue change done on an number of ASINs, or is it a case of just raising nee case IDs until someone does something useful?!
As the manufacturer of the item it is a ridiculous situation to be in.
Cheers
Jeff
3 replies
Ezra_Amazon
Hi @Seller_InOEEZHvO86Bu,
It seems you're encountering error 8541.
Have you reached out to Seller Support with all the ASINs you want to update this value for, in a single case?
If you have, could you please share the case ID with me? That way, I can escalate one case containing all the affected ASINs to our partner team for further investigation.
Thank you, Ezra
Seller_InOEEZHvO86Bu
Hi Ezra,
Thank you for your reply, which is appreciated.
We finally updated the listings via Seller Support assistance, however it took several agents to guide us in the right direction, even then it was our internal team who figured it out referencing ASIN in the feed rather than EAN.
The error codes really need to be more helpful.
Kind regards
Jeff
