This tutorial shows how to scrape Mercari products from a reviewed list of item URLs into CSV with UScraper. Use the maintained Mercari Product Details Scraper by URL template as the download path, then follow this runbook to replace URLs, set the export folder, validate rows, and troubleshoot common product-page issues.
Before you start
Prerequisites for a Mercari product URL scraper
This approach is for known product URLs, not keyword discovery. Start with five to ten reviewed Mercari item links, a clean output folder, and a clear reason for collecting the data. If you still need item links, run a listing workflow first and pass selected detail URLs into this scraper.
Prepare:
- UScraper installed as a local desktop app.
- The free Mercari Product Details Scraper by URL template.
- A short test list of Mercari product URLs, preferably from
jp.mercari.com/item/.... - A project-specific folder for CSV exports.
- Permission to access and process the pages you collect.
Review Mercari's current Terms of Service and robots.txt before automation. This tutorial does not cover login-only areas, checkout flows, private account data, CAPTCHA bypassing, or access workarounds.
Technical access is not permission. Keep batches narrow, document your purpose, and stop when Mercari shows verification, login, regional, or unavailable-item pages you are not allowed to process.
Workflow anatomy
How the Mercari product details scraper works
The JSON export is the authoritative workflow definition. The bundled flow is intentionally compact:
Navigate -> Wait for Element -> Sleep -> Inject JavaScript
-> Structured Export -> Loop Continue
Navigate holds the Mercari item URLs. Wait for Element checks for body, then Sleep gives the client-side page time to hydrate. Inject JavaScript creates window.__US_MERCARI_ITEM__, a normalized object built from embedded JSON, Open Graph meta tags, the item ID, and visible Japanese labels.
Structured Export reads that object into CSV columns. Loop Continue advances to the next URL in the Navigate array, so every product URL can land in one appended file.
Output shape
Mercari product details exported to CSV
The default export file is mercari_product_detail_url_scraper_cloud.csv. Headers are enabled and file mode is append, which is useful for URL loops but easy to misuse during testing. Clear the old CSV or change the filename before a final run.
| CSV group | Columns | Validation check |
|---|---|---|
| Traceability | keyword, product_url | Confirm every row maps to the expected item page. |
| Product | product_name, description, image_url | Compare title, long text, and image against the browser. |
| Market state | price, stock, category, brand, item_condition | Treat blanks as review signals, not automatic failures. |
| Shipping | shipping_payer, delivery_method, shipping_from_region, shipping_duration | Validate carefully because shipping labels affect resale analysis. |
| Seller | seller_url, seller_name | Keep for traceability; avoid republishing personal data without permission. |
Runbook
How to scrape Mercari product details by URL
Import the template
Open the Mercari Product Details Scraper by URL page, download the JSON, and import it.
Replace the sample URLs
In Navigate, replace the five sample Mercari Japan item URLs with approved product-detail URLs. Avoid search pages.
Keep the hydration wait
Leave Wait for Element and Sleep in place. If pages load but rows are blank, test a longer pause before changing extraction logic.
Set the export folder
In Structured Export, choose the save location, confirm the filename, keep headers enabled, and review append mode.
Run one URL first
Export one item, then compare name, price, stock, brand, shipping, seller, image, and description against the browser.
Scale the batch
When the first row checks out, run the list. Pause on verification pages, repeated blanks, or unexpected redirects.
Validation
Validate the Mercari CSV before using it
Open the CSV beside the browser. Check the first, middle, and last rows. Marketplace data changes quickly, so preserve the run date with the file.
| Symptom | Likely cause | Fix |
|---|---|---|
| Blank product fields | Page did not hydrate, item is unavailable, or access was challenged | Open the URL manually, rerun one item, then increase wait time if allowed. |
| Duplicate rows | Append mode reused an old test file | Clear the CSV or deduplicate by product_url and keyword. |
| Missing shipping fields | Listing does not expose the label or markup changed | Treat as optional, then inspect the page. |
| Empty seller details | Seller object was unavailable or profile link moved | Keep the product URL and rerun a small batch after updates. |
Alternatives
UScraper, Octoparse, Apify, and Mercari scraper APIs
If your search is octoparse mercari alternative or mercari cloud scraper, compare the workflow model first. Octoparse-style templates fit vendor-hosted no-code tasks. Apify actors and scraper APIs fit scheduled remote runs, datasets, or programmatic ingestion.
Best when you already have Mercari item URLs and need an inspectable CSV workflow with visible browser QA.
Trade-off: you own validation and selector maintenance.
For neighboring workflows, browse the UScraper template library or return to the UScraper blog.
FAQ
Mercari product scraping FAQ
Mercari product pages can still be governed by terms, robots directives, intellectual property rights, privacy law, and local rules. Review policies, keep runs modest, and do not bypass access controls.
Next step
Download the Mercari product scraper template
Use the Mercari Product Details Scraper by URL when you need to export known Mercari item URLs into a structured CSV for pricing checks, resale research, catalog QA, or marketplace reporting. Start with one URL, validate every field, then run the rest of the batch into a clean file.