Listing tampering and counterfeit offers: an incident response plan
Detection, containment, evidence, recovery and hardening: treat unauthorised page changes and counterfeit offers like the security incidents they are.
On this page
A tampered listing is a security incident with a revenue counter attached. Someone is either rewriting your product page or selling counterfeit stock through it, and every hour costs sales, trust and sometimes safety. Brands with a rehearsed plan recover in days; brands improvising recover in weeks. This is the plan.
Know what you are dealing with
Content takeover: an account gains edit influence and changes your title, images or details, occasionally merging your listing with another product entirely. Counterfeit or materially different offers: sellers attach to your ASIN with stock that is not the genuine product as listed. Both are reportable. An authentic reseller competing for the Buy Box is neither: that is legitimate competition, answered with a stronger authorised offer, not a report. They can look similar from a sales chart, so diagnosis is step zero.
Detection: minutes matter more than dashboards
The incident clock starts when the change happens, not when you notice. Monitor continuously for new offers on your ASINs, Buy Box loss, and content changes to titles, imagery and bullets, with alerts that reach a human the same hour. A weekly review is an archaeology programme, not detection.
Containment: the first day
- Capture evidence first. Screenshots of the altered page or suspect offers, timestamps, seller identifiers, before anything changes again.
- Pause paid traffic. Do not fund visits to a page you do not control; advertising resumes when the page is yours again.
- For suspected counterfeit offers, test buy immediately. The order ID and unboxing photographs become the evidence; if the product proves genuine, there is nothing to report.
- For content takeovers, submit your correct content through Brand Registry channels and open the case with the evidence of the unauthorised change.
Reporting and recovery
Work the appropriate channels in order: Brand Registry support with a precise, evidenced case; counterfeit reporting, or Project Zero where Amazon has granted it, only where the test buy proves fakes; and catalogue correction cases for merges and content damage, where persistence and documentation win. Track everything in one incident log, case IDs, timestamps, outcomes, both for follow-up and for the post-incident review.
Recovery is not just restoration: audit the blast radius. Rank lost during the incident, reviews collected while someone else’s stock shipped, price history damage, and subscriber cancellations all deserve a number, because that number funds the hardening below.
Hardening: make the next attempt boring
- Brand Registry fully configured, with your content authority actively claimed on every ASIN.
- Transparency on the ASINs that attract counterfeits; serialisation stops most of them at the warehouse.
- Monitoring with same-hour alerting, owned by a named person, tested like a fire alarm.
- An incident runbook: who does what in the first hour, with the evidence checklist attached.
- A quarterly desktop drill on one ASIN, because rehearsed teams are calm teams.
Go deeper
More Brand protection
Protect product, page and provenance.
Want this applied to your brand?
Book a walkthrough and we'll map it to your category on Amazon.