This tutorial shows how to scrape Amazon Japan reviews into CSV with the Amazon Review Details Scraper for Japan for UScraper. You will import the workflow, add ASIN review URLs, set the export path, handle prompts, validate rows, and know when to stop.
Before you start
Prerequisites, scope, and Amazon.co.jp checks
You need UScraper installed as a local desktop app, a short list of Amazon.co.jp product review URLs you are allowed to process, and a local folder for the CSV. Start with one or two ASINs because review pages can change by language, region, account state, product availability, and verification prompts.
This guide is for supervised research exports from review pages you can inspect in a browser. It is not a guide to bypass sign-in, CAPTCHA, rate limits, access controls, payment pages, seller dashboards, or private account data. Review Amazon's conditions of use, robots rules, and internal compliance policy before automation.
Technical access is not the same thing as permission. Keep runs modest, document the reason for collection, and prefer official or partner routes when you need contractual rights, redistribution, or production-scale ingestion.
Workflow anatomy
What the Amazon Japan review scraper exports
The companion JSON is the workflow contract. Navigate owns the review URL list, waits give the page time to render, Element Exists detects blocked states and review cards, Structured Export writes rows, and the pagination branch clicks Next until no more review pages are available.
The scraper is built for Amazon review details, not general Amazon search results or product catalog enrichment. Use product review URLs like /product-reviews/<ASIN>?reviewerType=all_reviews&pageNumber=1&sortBy=recent, then let pagination move through the rest of the visible review pages.
| CSV field | What it captures | Validation check |
|---|---|---|
page_url | Current Amazon.co.jp review page URL | Confirms the row came from the expected review page. |
ASIN | Product identifier parsed from the review URL | Compare it with the ASIN in your input list. |
product_title | Product title visible near the review list | Expect blanks if Amazon hides product context. |
review_id | Review card ID or review data attribute | Use it as a dedupe key with ASIN. |
posting_date | Date text shown on the review card | Confirm locale-specific date text is acceptable. |
star_rating | Visible star rating text | Spot-check against the star icon on the page. |
reviewer_name | Profile name on the review card | Treat as personal data and minimize downstream use. |
review_title, review_body | Review headline and body text | Check that body text is not truncated. |
helpful_vote_text | Helpful-vote statement when visible | Blanks can be valid for reviews with no count. |
Runbook
How to scrape Amazon Japan reviews to CSV
Import the template
Open Amazon Review Details Scraper for Japan, download the JSON, and import it into UScraper.
Replace the sample ASIN URLs
In the Navigate block, replace the sample Amazon.co.jp review URLs with approved product review URLs. Keep reviewerType=all_reviews, pageNumber=1, and any sorting choice you want to preserve.
Confirm the blocked-page branch
Keep the sign-in and CAPTCHA selectors enabled. They prevent the workflow from waiting forever when Amazon shows a login, verification, or disabled search state instead of review cards.
Set the CSV destination
In Structured Export, confirm the file name, headers, append mode, and a project-specific save folder before running. Clear an old CSV if you want a clean export.
Run one ASIN and inspect
Start with one product. Solve any visible prompt manually, wait for review cards, export the first page, and compare five rows against the browser before running the rest of the list.
Do not scale until the first ASIN looks clean. The right workflow is the one you can verify, not the one that only completes quickly.
Quality control
Validate the Amazon.co.jp review export
Open amazon-jp-review-details-scraper.csv after the dry run. Sort by ASIN, review_id, posting_date, and star_rating, then spot-check the first page and a later paginated page. If you use the file for sentiment analysis or competitive research, keep the input URLs and run date beside the CSV.
| Symptom | Likely cause | Fix |
|---|---|---|
| Zero rows | Amazon showed sign-in, CAPTCHA, an unavailable product, or no review cards | Use an allowed browser profile, solve prompts manually, and rerun one ASIN. |
| Only first page exported | The Next selector did not match, or the final page was already reached | Inspect the pagination area and update the Next selector only if a live link exists. |
| Duplicate reviews | The same ASIN URL was entered twice, or append mode wrote over multiple runs | Dedupe by ASIN plus review ID, or clear the CSV before a fresh run. |
| Blank product title | Amazon hid the product context on that review view | Keep the row if ASIN and review fields are valid. |
| Truncated body text | The page changed review-body markup or collapsed text differently | Inspect one card and adjust the review body selector. |
API and alternatives
Amazon Product Advertising API, Octoparse, Apify, and UScraper
People searching for an amazon product advertising api reviews answer are usually asking whether an official Amazon API can replace a scraper. Treat that as a separate decision. Amazon's Product Advertising API documentation is product and affiliate oriented, so check the current Product Advertising API documentation before planning around review data access.
Hosted scrapers and marketplace actors can also be useful. Octoparse has Amazon Japan review templates, Apify has Amazon review actors, and code-first examples exist for teams that maintain selectors themselves. UScraper fits a supervised local CSV workflow where an analyst wants to see the page, control the run, and keep the file on disk.
| Approach | Best fit | Trade-off |
|---|---|---|
| UScraper local desktop template | Analyst-led review exports to CSV | You verify prompts and maintain selectors when Amazon changes layout. |
| Hosted scraper actor | Cloud scheduling and managed execution | Vendor pricing, limits, and data custody apply. |
| Code-first scraper | Engineering teams that want full control | Requires maintenance, anti-bot handling decisions, and deployment work. |
| Official or partner API | Contractual access and production systems | May not expose the review detail fields you need. |
Troubleshooting
Common Amazon Japan review scraping issues
Legality depends on jurisdiction, permission, data type, volume, and use case. Review Amazon.co.jp terms, robots rules, intellectual property rights, privacy obligations, and local law before automation. Do not bypass sign-in, CAPTCHA, paywalls, or access controls.
Next step
Download the Amazon Review Details Scraper for Japan template
When you are ready to run the tutorial, download the JSON from Amazon Review Details Scraper for Japan and keep this article open for QA. For adjacent no-code scraping workflows, browse all UScraper templates or the UScraper blog for more CSV export tutorials.