error 8541
I own a range of UPC/GTINS from GS1. When I assign new ones in the GS1 system and try to create listings in the Amazon catalog for then I am thwarted from saving them because the Amazon system throws up this 8541 error and tells me my assigned GTIN is some sort of pre-workout supplement and not the toy item I assigned it to.
I open cases and provide all the relevant information to seller support and their response provides no workable remedy. They tell me to either use the existing description (In other words, sell a shoe rack) or assign a different GTIN - but why can't I use a GTIN I own? It seems ALL of my unused GTINS have been hijacked by a seller of Shoe Racks in the past. The shoe racks are no longer available for sale on Amazon but they still commandeer my GTINs.
I paid a bunch of money for my GTINS and I pay $150 a year to GS1 to maintain ownership. I can provide proof I own them but I cannot use them on Amazon because of the misdeeds of a past seller.
This problem has happened before and I was never able to overcome it and just gave up in frustration. After a year I decided I would like to sell more items on Amazon and against my better judgement tried to add a NEW product with a NEW GTIN and I immediately hit the same wall as in the past. I sent very detailed and very clear explanations of the problem along with screen captures and official GS1 certificates proving my ownership to Seller Support, what I get back is very boiler-plate responses that are not enactable. Their solutuions are always either "Use the existing description" or "use a different GTIN",, but what if NONE of my unassigned GTINS work because they have all been hijacked?
PLEASE.. does ANYONE know how to overcome the round-and-round with seller support to correct this sort of situation?
error 8541
I own a range of UPC/GTINS from GS1. When I assign new ones in the GS1 system and try to create listings in the Amazon catalog for then I am thwarted from saving them because the Amazon system throws up this 8541 error and tells me my assigned GTIN is some sort of pre-workout supplement and not the toy item I assigned it to.
I open cases and provide all the relevant information to seller support and their response provides no workable remedy. They tell me to either use the existing description (In other words, sell a shoe rack) or assign a different GTIN - but why can't I use a GTIN I own? It seems ALL of my unused GTINS have been hijacked by a seller of Shoe Racks in the past. The shoe racks are no longer available for sale on Amazon but they still commandeer my GTINs.
I paid a bunch of money for my GTINS and I pay $150 a year to GS1 to maintain ownership. I can provide proof I own them but I cannot use them on Amazon because of the misdeeds of a past seller.
This problem has happened before and I was never able to overcome it and just gave up in frustration. After a year I decided I would like to sell more items on Amazon and against my better judgement tried to add a NEW product with a NEW GTIN and I immediately hit the same wall as in the past. I sent very detailed and very clear explanations of the problem along with screen captures and official GS1 certificates proving my ownership to Seller Support, what I get back is very boiler-plate responses that are not enactable. Their solutuions are always either "Use the existing description" or "use a different GTIN",, but what if NONE of my unassigned GTINS work because they have all been hijacked?
PLEASE.. does ANYONE know how to overcome the round-and-round with seller support to correct this sort of situation?
0 replies
Manny_Amazon
Hello @Seller_EjWcBPZB21wgc,
I'm sorry you're running into this error while attempting to add your product. This error is commonly referred to as a “single matching error” and occurs when your Product ID, such as UPC, EAN, JAN, and ISBN, corresponds to the Product ID of an existing ASIN. You will find some potential solutions to this in the Error 8541 help page. More specifically, I would recommend watching the Seller University video included in the page, and the "How to solve this error" section for specific steps you can take to fix it.
If you have reviewed the details above and still running into this error, please you share your case ID, and I'll review to ensure it is being properly addressed.
Regards,
- Manny