How to Export Competitor Amazon Reviews by ASIN

To export competitor Amazon reviews, collect the competitor ASINs from one marketplace, save them as an AMZShark Product Search, filter the available review rows, and download the result. The hard part is not the file format; it is choosing comparable products and preserving enough context to interpret the rows correctly. Start with the main download and export workflow if you have not created a Product Search before.

Build the comparison set

Include direct substitutes serving the same customer and use case. Add a category leader, a price leader, and any product repeatedly mentioned by buyers. Keep separate searches for products that differ materially in marketplace, format, or customer segment.

1. Open each relevant Amazon listing and copy its ten-character ASIN.
2. Record why the product belongs in the comparison.
3. Remove duplicate ASINs and obvious accessories unless accessories are part of the research question.
4. Create one Product Search for the marketplace and paste the ASIN list.

Choose filters that answer one question

Do not export every available row simply because you can. Create narrower evidence sets:

• One- and two-star rows for failures, defects, returns, and unmet expectations.
• Four- and five-star rows for valued outcomes, memorable features, and customer vocabulary.
• Phrase filters such as “broke,” “replacement,” “gift,” “travel,” or a category-specific material.
• Discovery-date windows for recent snapshots and recurring research.

Export and label the evidence

Choose CSV or Excel for analyst review, JSON or JSONL for code and language-processing pipelines, and Parquet for larger analytical workflows. Keep the ASIN, product title, marketplace, review URL, rating, discovery date, review title, and review text columns intact.

Create a competitor matrix

Count the number of distinct products showing a theme, not only the number of reviews. Twenty complaints from one troubled ASIN mean something different from the same complaint appearing across ten competitors.

Avoid common research mistakes

• Do not treat the available rows as a statistically complete sample of all Amazon reviews.
• Do not compare products from different marketplaces without labeling the difference.
• Do not assume AMZShark's discovery date is the customer's original posting date.
• Do not turn one vivid review into a product requirement without repeated evidence.
• Do not republish customer text as marketing copy without evaluating permission and policy.

Turn findings into decisions

Translate repeated evidence into a concrete action: a sourcing requirement, a quality-control test, a listing clarification, a product image, a support article, or an experiment. Keep a link back to the supporting review rows so the decision remains auditable.