@Seller_VygaQRBv4Ssmh
Thank you for your reply and follow-up.
Regarding the two cases you mentioned, I would like to provide you with an update:
Regarding Case 9802 – I understand the team is currently reviewing it, and I will wait patiently for their feedback.
Regarding Case 3732 – I have reviewed the response provided by the team 25 minutes ago, which reads as follows:
“We have received your appeal, but are currently unable to reactivate your ASIN. Why is this? The product detail page for the ASIN indicated in the following paragraph does not comply with our policies. What action do I need to take? To reactivate your ASIN, please remove the prohibited content from your product detail page or provide other evidence of compliance. Recommended changes: Please update the ‘customer_restriction_type’ attribute to ‘uk_18_knife’ on the detail page for further processing.”
The problem is: this is precisely what we have been doing repeatedly, but each time we do so, the situation gets worse.
We followed the instructions in the reply and updated the ‘customer_restriction_type’ to ‘uk_18_knife’ via the product spreadsheet, and also made the necessary edits on the inventory management page. However:
Every time we upload the spreadsheet to refresh this flag, we receive a new performance notification. Since 10 July, we have received over 150 duplicate notifications, and the number continues to rise. Uploading the spreadsheet has not only failed to resolve the issue but has actually triggered further system scans and violation flags.
Worse still, yesterday, whilst updating product variant information via the spreadsheet, almost all products that were already marked with ‘uk-18-knife’ and had been selling normally were reclassified by the system as ‘non-compliant’ and taken offline. In other words, this action not only failed to resolve the issue with the affected ASINs, but also impacted products that were previously compliant, leading to further losses.
What does this tell us?
This clearly demonstrates that the problem lies not with us, but with Amazon’s system.
* We have correctly uploaded this attribute countless times
*The “uk-18-knife” label is still visible on the front end for older listings, proving that the label itself exists
* Every time we follow the instructions, it triggers more notifications and affects more products
*This is not an isolated case—other sellers on the forum are reporting exactly the same issue
The advice provided by the Seller Support team (“Please update the customer_restriction_type attribute”) is a vicious cycle. We carry it out, but the system fails to recognise it, and then we are asked to do it again—and so on, ad infinitum. We went through exactly the same cycle back in April and May, and it was only resolved through manual intervention.
My request
*Please escalate cases 9802 and 3732 to both the Technical Team and the Internal Review Team, rather than continuing to have them handled by the Seller Support Team—as they are only able to send the same generic responses.
* Please ask the Technical Team to manually check our ASINs to confirm that the ‘uk-18-knife’ attribute does indeed exist in the system’s backend. Seller Support staff can already see this attribute in their system; the issue is that the review system is unable to read it correctly.
* Please immediately halt the automated scanning and repeated notifications for these ASINs until the root cause has been rectified.
*Please urgently address the batch of products that were incorrectly flagged yesterday—these products were originally compliant, bearing the required labelling and selling normally, but were erroneously flagged by the system following an update to variant information. This constitutes unacceptable collateral damage.
I am aware that moderators cannot directly rectify listings or overturn policy decisions, but I implore you to escalate this matter to the appropriate internal team so that they may conduct a root cause investigation and implement manual rectification. We have been going round in circles with Seller Support for several weeks and are unable to break this deadlock ourselves.
Thank you very much for your assistance.
Case:
12975443732
12974069802
Historical cases from April and May: 12587650942