What to Document Before Reporting an Amazon Listing Hijacker

Start with a timeline, not a conclusion

Calling a seller a hijacker does not explain what happened. Record the earliest time you noticed the change, the marketplace, the ASIN, the seller name and seller ID, the Buy Box position, and the specific customer-facing information that changed.

Take full-page screenshots where possible. Keep the date, time and page address visible. A short timeline helps a reviewer understand the sequence without reconstructing it from unrelated files.

Separate the offer from the detail page

An unfamiliar offer and an altered detail page are related but different problems. Capture the offer list, price, fulfilment method and seller identity separately from changes to the title, images, brand, bullets or variation structure.

• Offer evidence: seller identity, condition, price, fulfilment and Buy Box status
• Catalog evidence: changed field, previous value, current value and date observed
• Brand evidence: trademark record, Brand Registry access and authorization documents
• Customer-risk evidence: test-buy findings, packaging differences or support messages

Use test-buy evidence carefully

A test buy can be useful when the received product, packaging or inserts materially differ from the authentic product. Preserve the order details, unboxing sequence, labels and comparison photos. Do not edit images in a way that removes context.

Avoid stating that a product is counterfeit unless the evidence supports that conclusion. Describe observable differences precisely and let the documents carry the argument.

Submit one coherent record

Before submitting, check that names, dates and ASINs match across every file. Remove duplicate screenshots and label the remaining exhibits. The goal is not the largest attachment set; it is the clearest path from the problem to the requested action.