Reading an Amazon Brand Registry rejection email

Amazon Brand Registry (ABR) is the gold standard intake for anti-counterfeit takedowns. It’s also the source of the most demoralising rejection emails in the brand-protection operator’s inbox. The rejections sound bureaucratic and opaque — but they follow a small, learnable taxonomy. After categorising ~200 of them across our customer base, here are the seven patterns and what to do about each.

1. “Insufficient evidence of infringement”

The most common rejection. ABR’s reviewer looked at your notice and didn’t see a clear infringement signal. Most common cause: you submitted only the listing URL, no screenshots of the trademark or copyrighted asset being misused. ABR’s template asks for the listing URL but their reviewers want the visual evidence pack.

Re-file path:resubmit with annotated screenshots showing exactly which element infringes. Brand Protector’s evidence-pack PDF generator does this automatically; if you’re filing manually, mark the infringing region in red and add a one-line caption.

2. “Reported listing not found”

The listing was taken down before ABR’s reviewer got to it — usually by the seller switching the ASIN or the listing going inactive temporarily. ABR closes these as “unactionable” rather than “succeeded.”

Re-file path:wait 48 hours. If the listing reappears under a new ASIN with the same seller, that’s a new takedown. Brand Protector auto-flags this as a reappearance and routes it back into the inbox.

3. “Authorised distributor / Brand Registry seller”

The reseller you flagged is in fact authorised to sell your product. This is more common than brand owners want to admit — the chain of distribution between your brand and the marketplace is rarely fully visible to your IP team.

Re-file path:don’t. Update your per-tenant authorised-reseller list (Brand Protector calls this tenants/{tid}/config/seller_ids ) so future scans don’t flag the same seller. If you’re sure the seller isn’t authorised, escalate via your distribution-team contact at Amazon — not via another ABR filing.

4. “Trademark not registered for this product class”

Your trademark is registered for, say, IC 005 (pharmaceuticals and supplements), but the listing is in IC 031 (live animals and pet food). ABR’s reviewer concludes there’s no trademark conflict.

Re-file path:if the conflict is real, you’ll need to argue likelihood of confusion. Cite the substantially-similar-products doctrine and provide evidence the consuming public would be confused. This usually requires IP counsel for the language; brand-protection software won’t pre-fill it correctly. If the conflict ISN’T real, your detection tool flagged a false positive — re-tune your category configuration.

5. “Duplicate report”

ABR has already received a takedown notice for this listing from a different brand or your own team via a different operator. Their queue de-duplicates.

Re-file path:none. Wait for the existing notice to be processed. Brand Protector’s verifier-job will re-check the listing daily; if it stays up past the SLA window the rejection turns into an escalation candidate.

6. “Counterfeit determination requires test purchase”

ABR can’t determine counterfeit status from photos alone. They want a physical purchase verification. This is increasingly common for high-value categories (electronics, cosmetics) where photo-based detection isn’t enough.

Re-file path:you (or a test-buy service — Red Points runs one, BrandShield doesn’t) buy the product, photograph the difference between authentic and received, and resubmit with the test-purchase evidence attached. Brand Protector’s test-buy integration is on the roadmap (see ROADMAP Top-10).

7. “Notice withdrawn — submitted in error”

Either you withdrew the notice yourself, or ABR’s reviewer concluded the notice was filed in bad faith. The latter is rare but it carries reputational risk: too many bad-faith notices and ABR can suspend your reporter privileges. Two of those in a quarter is a yellow card.

Re-file path: understand which it was. If you withdrew, no action. If ABR concluded bad-faith, audit your detection threshold and your triple-validation gate. This is exactly the case § 512(f) liability is meant to prevent (see our companion piece on § 512(f) liability).

What to track

Every brand-protection program should track the following per platform per quarter:

• Notices filed
• Notices succeeded (listing removed)
• Rejection rate by reason class
• Time-to-removal median (filing to listing 404)
• Reappearance rate (succeeded notices where a new listing appears with the same seller within 30 days)

Brand Protector’s admin console surfaces all five for every customer; if you’re running this on a spreadsheet, the rejection-rate-by-reason-class column is the highest-value one to add.