This tutorial shows how to scrape Amazon Japan product details from Amazon.co.jp ASIN URLs into CSV with the Amazon Japan Product Details Scraper template for UScraper. You will import the workflow, replace sample URLs, set the export folder, validate rows, and decide when an API or hosted scraper is a better fit.
Before you start
Prerequisites, inputs, and policy checks
You need UScraper installed as a local desktop app, a CSV folder, and a short list of Amazon.co.jp product detail URLs in the form https://www.amazon.co.jp/dp/ASIN or /gp/product/ASIN. Start with three to five URLs because product pages vary by availability, seller, language, delivery context, and verification state.
If you do not already have ASIN URLs, use a discovery workflow first. The Amazon Japan URLs Scraper and Amazon Japan Product Listings Scraper are better for search or category collection. This article is for known detail pages.
Review Amazon's current rules before automation. Check Amazon.co.jp's robots.txt, marketplace terms, and the official Product Advertising API Japan locale reference when you need approved API access or redistribution rights.
Technical access is not the same as permission. Do not bypass CAPTCHA, login walls, checkout flows, account pages, or access controls. Keep collection narrow, documented, and proportionate to the business question.
Workflow anatomy
What the Amazon Japan product scraper does
The JSON export is the authoritative workflow definition. Its graph is simple: Set Window Size -> Navigate -> Wait for Page Load -> Wait for Element -> Scroll -> Sleep -> Structured Export -> Loop Continue. Navigate stores the product URL list, the waits let the page settle, Structured Export writes the CSV row, and Loop Continue advances to the next product.
The template waits for body instead of only #productTitle. If Amazon returns an unavailable product page, translated variant, or verification screen, the loop can keep moving. The row may be partial, but you still get a URL for review.
| Export area | CSV fields | Validation question |
|---|---|---|
| Product identity | ASIN, Web_Page_URL, Title, Brand | Does the row identify the same product shown in the browser? |
| Commercial state | Price, Inventory, Seller | Is the price visible for this session, seller, and availability state? |
| Trust signals | Star_Rating, Number_of_Reviews, Best_Sellers_Rank | Did Amazon render the rating and ranking modules on this page? |
| Product details | Bullet_Points, Product_Information, Item_Model_Number, item_Weight, Date_First_Available | Are detail rows present in Japanese or English labels? |
| Media and audit | Image_URL_1 through Image_URL_6, Current_Time | Did image URLs load, and can you tie the row to a run time? |
Runbook
How to scrape Amazon.co.jp product data to CSV
Import the template
Open the Amazon Japan Product Details Scraper page, download the JSON, and import it into UScraper.
Replace the sample URLs
In Navigate, replace the bundled URLs with Amazon.co.jp product pages from your own catalog, search workflow, supplier sheet, or approved research list.
Keep waits and scroll
Keep the 45-second page load wait, the visible body check, the scroll, and the short sleep. These blocks reduce blank image, detail, and inventory cells.
Set the export path
In Structured Export, confirm the filename, headers, append mode, and a project-specific save folder before running client or category batches.
Run one product first
Run one URL, open the CSV, and compare ASIN, title, price, rating, seller, bullets, and image columns against the browser.
Run the remaining list
When the first row checks out, let Loop Continue process the remaining URLs and review partial rows at the end.
The default output file is amazon-japan-product-details-scraper.csv. Because the workflow uses append mode, clear or rename old test files before a production run.
Quality control
Validate the Amazon Japan CSV export
Open the CSV immediately after the dry run. Check the first row, then spot-check rows near the middle and end. Save the URL list, run date, filename, and selector changes.
| Symptom | Likely cause | Fix |
|---|---|---|
Blank Title | Verification page, unavailable ASIN, or changed product title selector | Open the URL in the browser, handle allowed prompts, and rerun one product. |
Empty Price | Price hidden by availability, seller state, account context, or page variant | Treat price as optional and verify whether the product had a visible offer. |
| Missing images | Image block loaded late or Amazon returned a placeholder | Keep the scroll and sleep, then rerun a single URL before editing selectors. |
| Product details missing | Technical table labels changed or the section did not render | Inspect the page language and update the JavaScript label fallbacks if needed. |
| Repeated rows | The same URL was supplied twice or append mode reused an old file | Dedupe by ASIN and page URL, then start the next run with a clean CSV. |
Alternatives
UScraper vs Amazon scraper APIs and hosted tools
The best Amazon Japan product scraper depends on the job. UScraper fits supervised CSV work from a controlled ASIN list. API and hosted tools fit programmatic ingestion, scheduling, or larger pipelines.
| Approach | Good fit | Trade-off |
|---|---|---|
| UScraper local desktop template | Analysts who need visible browser QA, editable selectors, and CSV output on disk | You own selector maintenance when Amazon changes markup. |
| Amazon Product Advertising API | Approved affiliate and commerce integrations | Requires account access, API rules, quotas, and approved use cases. |
| Octoparse Amazon Japan templates | No-code users who prefer a hosted visual task | Data and scheduling live in a vendor workflow. |
| Apify Amazon product actors | Cloud runs, datasets, and API-triggered collection | Vendor runtime, storage, and pricing shape the pipeline. |
| Bright Data, Oxylabs, or ScraperAPI | Managed scraping APIs that return structured product data | Better for engineering pipelines, less inspectable for one-off CSV review. |
If your search is "octoparse amazon scraper alternative", focus on custody and control. UScraper keeps the browser flow inspectable in a local desktop app and writes the file to a folder you choose. Hosted scrapers are often better for remote scheduling and managed infrastructure.
FAQ
Amazon Japan product scraping FAQ
Amazon.co.jp product pages can be visible in a browser, but automated collection may still be restricted by Amazon terms, robots directives, anti-abuse systems, intellectual property rights, privacy law, and local regulations. Review the current rules, use only URLs you are allowed to process, keep batches modest, and do not bypass CAPTCHA or access controls.
Next step
Download the Amazon Japan product details scraper
When you are ready to run the tutorial, download the JSON from Amazon Japan Product Details Scraper and keep this article open for validation. For adjacent Amazon workflows, browse the UScraper template library, pair detail pages with the Amazon Review Details Scraper for Japan, or return to the UScraper blog for more CSV export tutorials.