Vine Enrollment now not working for Handmade
I previously enrolled in Amazon Vine with my handmade products, and it was a great way to receive reviews for new items. However, now when I try to enroll an ASIN, I receive the error message: 'VINE ERROR Browse path ineligible - 909.' I opened a case, and Amazon Selling Partner Support provided the following information:
"My name is Kim and I am a Live Channel Specialist. I'm contacting you to follow up on your concern regarding Vine enrollment for your ASIN. I have contacted two different internal department to work on it, they have reviewed the issues. Both ASINs are already assigned to the requested node us-handmade:/Categories/Jewelry/Necklaces/Pendant, however, as the whole handmade structure is hidden it does not show the node in all tools. Hence your product is not eligible for vines. I will now close this case. "
Is there any way to bypass this issue, or when will I be able to add my products to Vine again?
Vine Enrollment now not working for Handmade
I previously enrolled in Amazon Vine with my handmade products, and it was a great way to receive reviews for new items. However, now when I try to enroll an ASIN, I receive the error message: 'VINE ERROR Browse path ineligible - 909.' I opened a case, and Amazon Selling Partner Support provided the following information:
"My name is Kim and I am a Live Channel Specialist. I'm contacting you to follow up on your concern regarding Vine enrollment for your ASIN. I have contacted two different internal department to work on it, they have reviewed the issues. Both ASINs are already assigned to the requested node us-handmade:/Categories/Jewelry/Necklaces/Pendant, however, as the whole handmade structure is hidden it does not show the node in all tools. Hence your product is not eligible for vines. I will now close this case. "
Is there any way to bypass this issue, or when will I be able to add my products to Vine again?
2 yanıt
priscilla_amazon
Hi @Seller_Cxu8I031rdTzN, thank you for sharing this detailed information. We're investigating further internally, would you be able to share the affected ASINs as soon as you can, please?
