Frequently Returned Item badge
I currently have this badge for one of my listings. I did not have many returns in the past 90 days. I also checked voice of the customer in seller central and there were actually no "voices" or concerns. The NCX is actually healthy, nowhere near poor or very poor at all.
I would actually say this badge hurts the seller when the metrics for the most part is very healthy. This badge is obviously using an algorithm but from my observation, it is quite flawed and I can see the negative impact its had on my listing already. Sales stopped and how can I even get sales to reduce the "return rate" when the sales completely stopped? This badge is a nail in the coffin for a listing.
Frequently Returned Item badge
I currently have this badge for one of my listings. I did not have many returns in the past 90 days. I also checked voice of the customer in seller central and there were actually no "voices" or concerns. The NCX is actually healthy, nowhere near poor or very poor at all.
I would actually say this badge hurts the seller when the metrics for the most part is very healthy. This badge is obviously using an algorithm but from my observation, it is quite flawed and I can see the negative impact its had on my listing already. Sales stopped and how can I even get sales to reduce the "return rate" when the sales completely stopped? This badge is a nail in the coffin for a listing.
4 replies
Danny_Amazon
Hey there @Seller_mIbDW34868CxW- thanks for sharing this here on the seller forums. I can advise that the "Frequently Returned" label is shown on the detail page of ASINs with a significantly higher return rate for its product category, and know that our teams consider multiple factors, including the return rate for the ASIN relative to the average return rate for the product category, and whether ASINs have had sufficient recent sales to determine an accurate return rate.
If you believe an error has been made in this calculation at all, I would recommend creating a case with our support team for more technical troubleshooting!
Thanks,
Danny
