ASIN not showing on its browse node
So, our ASIN (brand owned, sole seller) has the right browse nodes. I can see that from the edit listing page.
However, when browsed to that category, the listing does not show. I have created cases with seller support which keeps closing them with ‘we are unable to accept your request for browse category node change’.
And frustratingly, they keep closing the case without allowing to reopen them. This is pure evil.
I have opened cases repeatedly each being more vocal saying I do not need the node to be changed, but just fix the bug that is causing it to not appear in its browse node.
But, the result is the same, a template answer with a closed case that can not be reopened.
What can I do? Is there another way to reach the catalogue team without going via seller support? Perhaps there is a Amazon forum moderator who could help?
I would really appreciate any tips or help on how to get this fixed.
Seller_LnhtxRbgL9RW2
Replying to give an update on this because I believe this was a strange thing and might help others. Finally, the problem was solved after a higher level support from Amazon was involved. Took multiple calls and escalations, but it was solved in the end.
The issue was a word in the product title. Somehow the algorithm decided that the word did not belong to the leaf category so assigned the ASIN to the root category. After we used a synonym for that word, the issue was solved. We got no error or indication of this happening.
It was not like we were trying to fill the title with keywords. The word in question was genuinely part of the product title, but somehow triggered the algorithm. To give a hypothetical but analogues example, let us say you have a product listed in ‘Pet bowl cleaner’ product listed in ‘Pet feeding accessories’ browse node category. The word ‘cleaner’ triggers the bot and the bot thinks ‘cleaner’ should not be in this node. So it was assigning the ASIN to the root category ‘Pets’.
8 replies
Seller_f5cnodyVjLD4S
Hi summer.glau
Firstly ensure that you have entered a UK postcode / location top left when searching as a buyer on the UK site, otherwise the system defaults to your IP address which can show you a different set of offers available to you.
Seller_LnhtxRbgL9RW2
Replying to give an update on this because I believe this was a strange thing and might help others. Finally, the problem was solved after a higher level support from Amazon was involved. Took multiple calls and escalations, but it was solved in the end.
The issue was a word in the product title. Somehow the algorithm decided that the word did not belong to the leaf category so assigned the ASIN to the root category. After we used a synonym for that word, the issue was solved. We got no error or indication of this happening.
It was not like we were trying to fill the title with keywords. The word in question was genuinely part of the product title, but somehow triggered the algorithm. To give a hypothetical but analogues example, let us say you have a product listed in ‘Pet bowl cleaner’ product listed in ‘Pet feeding accessories’ browse node category. The word ‘cleaner’ triggers the bot and the bot thinks ‘cleaner’ should not be in this node. So it was assigning the ASIN to the root category ‘Pets’.
