Most brands treat a rejected takedown as a final answer. It is not. Marketplaces reject valid complaints constantly, for thin evidence, wrong-category filings, or simply because the review queue is staffed by contractors measured on speed. The brands that get fakes removed treat the first rejection as round one: they fix the filing, escalate through the right channels, and document every step so the next submission is harder to dismiss.
Start by understanding the machine you are filing into. Major marketplaces process millions of complaints a month through a mix of automated filters and outsourced reviewers. The automated layer rejects filings with missing fields, mismatched product IDs, or trademark registrations it cannot verify. The human layer, where it exists, spends minutes per case. A complaint that says "this is fake" with one screenshot loses to a complaint that says "this is fake" with a test buy, side-by-side photos, and the trademark registration number.
Category errors are the silent killer. Filing a counterfeit complaint through the copyright channel, or the trademark channel when the issue is actually a design patent, routes your case to reviewers who cannot act on it. Each marketplace has its own taxonomy, and using the wrong door gets you a form rejection that tells you nothing about what to fix.
Step one is always a better refile, not a louder complaint. Strengthen the evidence packet: add a test buy with unboxing photos, include your trademark registration certificate, and quote the exact listing claims that infringe. File through the brand-registry or verified-rights-owner portal if you have access, since those queues get priority handling.
Step two is the marketplace escalation channel. Amazon has escalation paths through Brand Registry support, eBay has its VeRO escalation, and most other marketplaces have a rights-owner contact that is not the public form. These channels exist but are poorly documented, and a single well-formed escalation with a case history often succeeds where three public-form filings failed.
Step three is outside pressure. A letter from counsel to the marketplace legal department changes the calculus, because now the rejection carries liability risk. For persistent sellers, the platform repeat-infringer program, where one exists, targets the seller account rather than the single listing. And for the truly stubborn cases, reporting the seller to the payment processor cuts off the money rather than the storefront.
Every rejection, every refile, every support ticket number goes into a log. That log becomes leverage: when you escalate to legal or to counsel, the paper trail of ignored valid complaints is what makes the marketplace move. Note dates, case IDs, the exact reason given for rejection, and what you changed in response.
This discipline also fixes your future filings. Patterns in rejections reveal what the review queue actually wants: more photos, the registration number up front, the infringing text quoted verbatim. Brands that log rejections stop getting them. The marketplace did not become reasonable; the filings became undeniable.
Check the report for the usual failure points before assuming bad faith: a missing or wrong registration number, listing URLs that do not match the evidence, or a claim filed under the wrong policy. Resubmit with a complete packet and a cover note referencing the original report number and date. Many ignored reports are incomplete reports.
Use the platform brand protection program if you are enrolled, since those channels carry case management and appeal routes the public form lacks. Beyond the platform, options include payment processor reports, customs recordation for imported goods, and regulator complaints for hazardous products. Escalation works best as a documented ladder, each step referencing the last.
Platforms act on patterns. A brand that can show dates, report numbers, repeat sellers, and test buy evidence gives a trust team everything needed to justify account level action. A brand that files scattered one off complaints looks like noise. The log you keep during ordinary monitoring is what makes escalation credible.