INCIOGet INCIO ReviewsWhy export Amazon reviews to CSV?
A CSV turns separate review cards into rows that can be filtered, sorted, tagged, counted, and compared. That makes it useful for competitor research, negative-review analysis, product-development briefs, listing research, and customer-language studies. It is usually the simplest format when your next step is a spreadsheet.
| Choose CSV when | Choose JSON when |
|---|---|
| You want to filter, tag, count, or make a pivot table. | You need arrays, null values, or separate job metadata. |
| A researcher will inspect rows manually. | A script, notebook, database, or API will consume the file. |
| You need a portable import for Excel, Sheets, or Airtable. | You need a stable object structure for automation. |
Step-by-step export workflow
- Install INCIO Reviews from the Chrome Web Store.
- Sign in to a regular Amazon customer account if Amazon hides reviews while signed out.
- Open a product page or its reviews page. You can also enter a marketplace and ASIN manually.
- Open the extension and select CSV.
- Choose a review count, star filter, and sort option. The limit is 100 accessible reviews.
- Start the export and leave the Amazon tab available while collection runs.
- Open the downloaded CSV in your spreadsheet tool.
What the CSV can contain
When visible on the source page, each row can include review title, body, rating, reviewer display name, date and location text, normalized date, verified-purchase status, helpful count, variation, image links, review ID, review URL, source page number, ASIN, marketplace, and Amazon domain.
The file also includes export metadata such as requested and collected counts, selected filters, completion reason, dataset completeness, processed pages, timestamps, warnings, and error details. These columns help distinguish a complete requested scope from a partial result.
The 44 columns fall into four groups
| Group | Examples | Why it matters |
|---|---|---|
| Review evidence | title, body, rating, date, author_name | Contains the observed customer statement and basic context. |
| Product context | asin, variation, marketplace, amazon_domain | Prevents unrelated products or variations from being mixed silently. |
| Traceability | review_id, review_url, source_page_number | Supports source checks and auditable findings. |
| Collection quality | export_status, completion_reason, counts, warnings | Shows whether the file reached its requested scope or stopped early. |
Use the schema 1.2 reference for the exact header list, completeness values, warning semantics, and JSON equivalents.
Spreadsheet compatibility and safety
The CSV is created with UTF-8 encoding and a byte-order mark for common spreadsheet compatibility. Commas, quotes, tabs, and multiline text are escaped. Text beginning with spreadsheet formula characters is neutralized to reduce formula-injection risk when the file is opened.
Prepare the spreadsheet without losing evidence
- Import the CSV with UTF-8 encoding and confirm that multiline review text remains in one row.
- Freeze the source columns and preserve one untouched copy of the export.
- Add working columns to the right instead of overwriting review text or metadata.
- Check
source_dataset_completeness,completion_reason, and warning fields before analysis. - Filter or group by ASIN and variation before combining results.
- Keep blank fields blank; they mean unknown or unavailable, not necessarily “no.”
Image links use a pipe separator inside one CSV cell. Split that field only if your analysis actually needs one image URL per row. The extension exports links; it does not download the image files.
A simple review-analysis structure
- Keep the original export untouched as a source sheet.
- Create working columns for issue category, severity, product area, and action type.
- Filter one- to three-star reviews first, then compare with positive reviews.
- Group by variation to avoid mixing size-, color-, or model-specific problems.
- Count recurring issues and retain review IDs for every important claim.
- Separate product defects from packaging, instructions, delivery, and expectation gaps.
For a more rigorous framework, use the complete Amazon review analysis guide or the focused product pain-point guide.
Common CSV problems and fixes
| Problem | Likely cause | What to do |
|---|---|---|
| Everything appears in one column | The spreadsheet used a different delimiter. | Import the file explicitly as comma-separated UTF-8. |
| Fewer rows than requested | Filters, source availability, login, CAPTCHA, or early pagination end. | Inspect collected count, completion reason, warnings, and errors. |
| Variation or verified status is blank | The source page did not expose a parseable value. | Treat it as unknown and inspect the source row if material. |
| Image links do not open | A source URL expired or access conditions changed. | Return to the review page; do not assume the review has no image. |
| A formula-like review starts with an apostrophe | The exporter neutralized a formula-sensitive prefix. | Keep the text as evidence; the prefix is a spreadsheet-safety measure. |
Important limits
- The current limit is 100 accessible reviews per export.
- Filters may produce fewer rows than requested.
- Image links are exported; image files are not downloaded.
- Review visibility and pagination are controlled by Amazon.
- Reviews are not a representative market sample and may contain unreliable content.
INCIO Reviews creates the file locally and does not receive the dataset. If you upload it to another service, that provider's terms and privacy practices apply.
Can I merge several CSV exports?
Yes, if every row keeps its ASIN, marketplace, variation, export job ID, and collection metadata. Add a product label before merging and avoid comparing percentages when the collected scopes are materially different.
Does CSV preserve every JSON detail?
It preserves the current review and job fields in flat columns, but arrays are flattened. Choose JSON when you need warnings and errors as objects or image links as a native array.