Case study

Reporting a hijacker without evidence achieves nothing

Amazon hijacker removal for a registered brand whose listings had been attached to by a seller shipping a different product. The report only worked once the difference was documented properly.

What it looked like

The symptoms

  • An unauthorised seller winning the Buy Box on the brand’s own ASINs
  • Customers receiving a product that was visibly not the brand’s
  • Negative reviews landing on the brand for someone else’s stock
  • Earlier unevidenced reports dismissed without action
Diagnosis

What was actually wrong

Unevidenced reports are routinely dismissed, and repeated ones make later reports easier to ignore. What moves a case is a documented comparison showing exactly how the received item differs from the genuine article, tied to an order record that establishes where it came from.

The work

What was done, in order

01

Brand Registry position and registered trade mark confirmed first, since most enforcement routes are unavailable without them

02

A test purchase made from the infringing seller with the order trail preserved

03

Fifteen comparison exhibits documented — a different chain, a different pendant, plain unbranded packaging, no inserts — photographed against the genuine product

04

Reported through the programme matching the infringement type and escalated when the first response was automated

Outcome

Result

A complete enforcement record: registered mark, test purchase, documented comparison and the correspondence trail. That is the standard a takedown request has to meet to be actionable rather than dismissed.

Client details are kept confidential.

Next step

Got the same problem?

Send the error text, the ASIN or a screenshot. You will get a straight read on the cause before anyone talks about scope.

Not ready to hand over access? Send one question about your account instead — ask without booking anything. Or read the numbers first on client results.