Amazon Seller Data Extractor And Product Catalog Scraper

Amazon Seller Scraper — Extract Profiles and Enriched Product Catalogs

This Actor extracts Amazon seller data from an ASIN, seller ID, storefront URL, or keyword search, returning each seller's profile — ratings, feedback, policy text — plus their complete storefront product catalog. Catalog products can be enriched with live availability, feature bullets, and variation data from their own product page. Every response is structured JSON, ready to pass to an LLM, load into a spreadsheet, or feed a monitoring pipeline. No Amazon account or login is required — only public pages are read.

What is Amazon Seller Scraper?

Amazon Seller Scraper resolves an Amazon seller from an ASIN, a seller ID, a storefront URL, or a discovery keyword, then reads that seller's public storefront page for ratings, feedback, and policy data. Its differentiator is the enriched product catalog: rather than stopping at the seller's profile, it follows the seller's own storefront listing (/s?me=<sellerId>), paginates it, and — for each catalog product — can fetch the product's own detail page for live availability, feature bullets, and size/color/style variations. No Amazon account, login, or API key is required; every page it reads is publicly visible to any storefront visitor.

• Resolve sellers from ASINs, seller IDs, storefront URLs, or discovery keywords (a real keyword → product → seller pipeline, de-duplicated by seller ID)
• Seller profile: name, star rating, real lifetime/12-month/3-month/1-month rating counts, feedback rows, business details, and shipping/return/privacy policy text
• Storefront product catalog: every ASIN, title, price, rating, and review count the seller lists, paginated up to a configurable page and product cap
• Optional per-product enrichment: live availability, feature bullets, and variation names/count from each product's own detail page
• Feedback sorting by recency, helpfulness, or star rating
• Multi-marketplace support across 20 Amazon domains with automatic proxy-country matching

What data can you get with Amazon Seller Scraper?

Amazon Seller Scraper returns two linked result types in one dataset — seller profile rows and storefront product-catalog rows, joined by parentId.

Result Type	Extracted Fields	Primary Use Case
Seller profile	seller_id, seller_name, description, detailed_info[], feedbacks[], stars, rating_positive, rating_count_m1/m3/m12/lifetime, return_policy[], shipping_policies, privacy_security, privacy_policy, help_content, seller_phone_number, products_link, country, url, timestamp	Seller vetting, reputation monitoring, lead generation
Product catalog (enriched)	asin, productTitle, imageUrl, price, retailPrice, productRating, reviewCount, prime, sponsored, manufacturer, salesVolume, catalogPage, enriched, availability, featureBullets[], variationNames[], variationCount, detailPrice, detailRetailPrice, parentId, productUrl	Competitor catalog tracking, price/availability monitoring, sourcing research

Enriched product catalog

Most seller scrapers stop at the storefront profile. This Actor follows the products_link every seller page exposes, paginates it (&page=N, capped by maxCatalogPages), and lists every product the seller sells as child rows linked to the parent seller via parentId. When enrichCatalogProducts is on, each catalog product (up to maxEnrichedProducts) gets an extra fetch of its own /dp/<ASIN> page, adding live availability, up to 10 featureBullets, and up to 30 variationNames with a variationCount, plus a live detailPrice/detailRetailPrice that can differ from the catalog-card price. A product that wasn't enriched (cap reached, or the feature turned off) still returns with enriched: false rather than fabricated values.

{
  "asin": "B0C2JP88N4",
  "productTitle": "SanDisk 64GB microSDXC-Card",
  "price": 34.22,
  "enriched": true,
  "availability": "Only 5 left in stock - order soon.",
  "featureBullets": ["Super-fast transfer speeds with up to 100MB/Sec"],
  "variationNames": ["128GB", "16GB", "256GB", "32GB", "64GB"],
  "variationCount": 5,
  "detailPrice": 26.33
}

Seller profile and real rating history

Every seller row includes rating_count_m1, m3, m12, and rating_count_lifetime, parsed from Amazon's own embedded data-a-state rating JSON rather than left as a placeholder, so a genuine zero and a parse miss are never confused. Feedback rows (feedbacks[]) carry stars, text, and date, sorted by feedbackSortOrder into recency, helpfulness, or star-rating order before maxFeedbackPerSeller truncates the list. Business fields (detailed_info[], seller_phone_number) and policy text (return_policy[], shipping_policies, privacy_policy) round out the profile, giving a seller-vetting workflow everything it needs from one row without opening the storefront page by hand.

How does Amazon Seller Scraper differ from the official Amazon API?

Amazon's Selling Partner API (SP-API) is authorized per selling-partner account through an OAuth flow (Login with Amazon) — an app can only act on behalf of the specific seller who authorized it, not on arbitrary third-party sellers. Amazon Seller Scraper instead reads whatever any storefront visitor can see, for any seller you point it at.

Feature	Amazon SP-API	Amazon Seller Scraper
Which sellers you can query	Only the seller account that authorized your app	Any public seller — by ASIN, seller ID, storefront URL, or keyword
Setup required	Developer registration, app approval, OAuth authorization from that seller	Add inputs and run — no Amazon account or API keys
Product catalog scope	Your own authorized account's listings	Any seller's full public storefront catalog, paginated
Per-product live detail	Separate calls against your own listings only	Automatic per-product enrichment for any seller's products
Seller reputation data	Ratings/feedback for competing sellers are not part of the API surface	Scraped directly from the public storefront page
Output format	Amazon's fixed per-endpoint schema	One flat JSON schema across seller and catalog rows

Use the SP-API when you manage your own Seller Central account and need to update listings, orders, or inventory. Use Amazon Seller Scraper when you need public profile and catalog data on other sellers — competitors, suppliers, or leads — that SP-API was never built to expose.

How to scrape Amazon with Amazon Seller Scraper?

1. Open Amazon Seller Data Extractor And Product Catalog Scraper on Apify.
2. Add one or more targets: Product ASINs, Seller IDs, Seller profile URLs, or Keywords — no field is required, mix any combination.
3. Leave Fetch storefront product catalog and Enrich catalog products on for the full seller + catalog + live-detail output, or turn either off for a lighter run.
4. Set the marketplace domain, feedback sort order, and page/product caps to match your target market and budget.
5. Start the run and read results as JSON or CSV from the dataset — seller rows and product rows share one table, distinguished by type/isChild.

{
  "sellerAsinTargets": ["B00P8XQPY4"],
  "marketplaceDomain": "amazon.com",
  "fetchProductCatalog": true,
  "enrichCatalogProducts": true
}

How to run multiple queries in one job

Every target field (sellerAsinTargets, sellerIdTargets, discoveryKeywords, sellerProfileUrls) accepts an array, and all four can be mixed in one run — each line becomes its own task, tagged with a section label in the output so you can tell which input row a row came from. Tasks run concurrently up to maxParallelSellers (max 20), each on its own sticky residential proxy session and cookie jar, so a batch of ASINs, a list of known seller IDs, and a set of discovery keywords can all run side by side in a single job instead of needing separate runs per input type.

⬇️ Input

Give it Amazon ASINs, seller IDs, seller profile URLs, or discovery keywords — every line resolves to a seller storefront, which is then optionally paginated for its full product catalog and enriched per product. No field is required.

Parameter	Required	Type	Description	Example Value
sellerAsinTargets	No	array	Product ASINs; the Actor opens the product page and resolves the seller behind the offer	["B00P8XQPY4"]
sellerIdTargets	No	array	Amazon seller IDs / merchant IDs to scrape directly	["A33W53J5GVPZ8K"]
discoveryKeywords	No	array	Search phrases; runs the search, opens matching products, resolves sellers, de-duplicated by seller ID	["handmade ceramics UK"]
sellerProfileUrls	No	array	Full Amazon seller storefront links	["https://www.amazon.com/sp?seller=A33W53J5GVPZ8K"]
fetchProductCatalog	No	boolean (default true)	Fetch and paginate each seller's storefront product listing	true
maxProductsPerSeller	No	integer (0–2000, default 20)	Cap on storefront products collected per seller (0 = unlimited, bounded by page cap)	20
maxCatalogPages	No	integer (1–50, default 5)	Safety valve on storefront pagination depth	5
enrichCatalogProducts	No	boolean (default true)	Fetch each catalog product's own page for live availability/bullets/variations	true
maxEnrichedProducts	No	integer (0–500, default 10)	Cap on per-product detail-page fetches per seller	10
marketplaceDomain	No	string (default amazon.com)	Amazon marketplace domain	amazon.co.uk
pageLocale	No	string	Optional locale sent as the Accept-Language header	en-GB
proxyCountryHint	No	string (default AUTO)	Proxy routing country, or AUTO to derive it from the marketplace domain	AUTO
captchaSolverAssist	No	boolean (default false)	Doubles the anti-bot retry ladder and backoff on soft blocks	false
feedbackSortOrder	No	string enum (default recent)	Order feedbacks[] before truncation: recent, helpful, or rating	recent
maxFeedbackPerSeller	No	integer (0–1000, default 10)	Cap on feedback rows per seller (0 = all the page allows)	10
maxParallelSellers	No	integer (1–20, default 10)	Max concurrent seller tasks	10
proxyConfiguration	No	object	Proxy settings; this Actor always runs on residential proxies regardless of this setting	{"useApifyProxy": false}

{
  "sellerAsinTargets": ["B00P8XQPY4"],
  "sellerIdTargets": [],
  "discoveryKeywords": [],
  "sellerProfileUrls": [],
  "fetchProductCatalog": true,
  "maxProductsPerSeller": 20,
  "maxCatalogPages": 5,
  "enrichCatalogProducts": true,
  "maxEnrichedProducts": 10,
  "marketplaceDomain": "amazon.com",
  "pageLocale": "",
  "proxyCountryHint": "AUTO",
  "captchaSolverAssist": false,
  "feedbackSortOrder": "recent",
  "maxFeedbackPerSeller": 10,
  "maxParallelSellers": 10,
  "proxyConfiguration": { "useApifyProxy": false }
}

Common pitfall: maxProductsPerSeller and maxEnrichedProducts are separate budgets. Raising the catalog cap to, say, 200 while leaving maxEnrichedProducts at its default of 10 means only the first 10 catalog products per seller come back with live availability/variationNames — the rest return with enriched: false. Raise both together if you need full-catalog enrichment.

⬆️ Output

Results are pushed to the dataset in real time, one row per seller and one row per catalog product, exportable as JSON, CSV, or Excel. Every pushed row — seller or product — charges one row_result event. Three dataset views are available beyond the default: Sellers only, Product catalog only, and Full record (every field).

Scraped results

[
  {
    "type": "seller",
    "isChild": false,
    "parentId": null,
    "seller_id": "A3FM56HUALOR9M",
    "seller_name": "FC Ecom",
    "stars": "4.5 out of 5 stars",
    "rating_positive": "94% positive",
    "rating_count_m1": 42,
    "rating_count_m3": 118,
    "rating_count_m12": 408,
    "rating_count_lifetime": 8759,
    "products_link": "https://www.amazon.com/s?ie=UTF8&me=A3FM56HUALOR9M",
    "url": "https://www.amazon.com/sp?seller=A3FM56HUALOR9M",
    "productCatalogFetched": true,
    "productCatalogCount": 16,
    "productsEnrichedCount": 10,
    "country": "US",
    "timestamp": "2026-07-18T12:00:00Z"
  },
  {
    "type": "product",
    "isChild": true,
    "parentId": "A3FM56HUALOR9M",
    "asin": "B0C2JP88N4",
    "productTitle": "SanDisk 64GB microSDXC-Card Licensed for Nintendo-Switch, Yoshi Edition",
    "price": 34.22,
    "retailPrice": null,
    "productRating": "4.7 out of 5 stars",
    "reviewCount": 434,
    "prime": false,
    "sponsored": false,
    "productUrl": "https://www.amazon.com/dp/B0C2JP88N4",
    "catalogPage": 1,
    "enriched": true,
    "availability": "Only 5 left in stock - order soon.",
    "variationNames": ["128GB", "16GB", "256GB", "32GB", "64GB"],
    "variationCount": 5,
    "detailPrice": 26.33
  },
  {
    "type": "product",
    "isChild": true,
    "parentId": "A3FM56HUALOR9M",
    "asin": "B0BXQK7Z1T",
    "productTitle": "USB-C Fast Charging Cable 6ft, Braided Nylon",
    "price": 8.99,
    "retailPrice": 12.99,
    "productRating": "4.4 out of 5 stars",
    "reviewCount": 2109,
    "prime": true,
    "sponsored": false,
    "productUrl": "https://www.amazon.com/dp/B0BXQK7Z1T",
    "catalogPage": 1,
    "enriched": true,
    "availability": "In Stock",
    "variationNames": ["3ft", "6ft", "10ft"],
    "variationCount": 3,
    "detailPrice": 8.99
  },
  {
    "type": "product",
    "isChild": true,
    "parentId": "A3FM56HUALOR9M",
    "asin": "B09Q7X2WJH",
    "productTitle": "Wireless Bluetooth Earbuds with Charging Case",
    "price": 19.49,
    "retailPrice": 29.99,
    "productRating": "4.2 out of 5 stars",
    "reviewCount": 5872,
    "prime": true,
    "sponsored": true,
    "productUrl": "https://www.amazon.com/dp/B09Q7X2WJH",
    "catalogPage": 2,
    "enriched": false
  }
]

How can I use the data extracted with Amazon Seller Scraper?

• Competitive seller and catalog research: e-commerce sellers and category managers pull a competitor's full product lineup — productTitle, price, availability, variationNames — to see exactly what they sell, at what price, and in which variants.
• Reputation and compliance monitoring: brand-protection and marketplace-integrity teams track stars, rating_positive, and rating_count_m1/m3/m12 for known sellers to catch reputation shifts or spot new sellers via discoveryKeywords.
• AI engineers and LLM developers: an agent issues a seller or keyword query, receives structured seller + catalog JSON, and passes it to the model as grounded context for sourcing recommendations or competitor summaries.
• Market researchers: aggregate productCatalogCount, price, and manufacturer across many sellers in a niche to measure category assortment depth and price spread.

How do you monitor a seller's product catalog over time?

Catalog and reputation monitoring means re-running the same seller targets on a schedule and comparing each run's output to the last, rather than treating a single run as a snapshot. Because every product row carries a stable asin and parentId, and every seller row carries a stable seller_id, you can diff two runs on those keys to see exactly what changed: a new asin appearing in the catalog means a new listing; a missing one means it was delisted or the seller stopped carrying it; a changed price or detailPrice is a price move; a changed availability string is a stock-status change; and a shift in rating_count_m1 or stars signals a reputation change worth flagging.

A practical loop: schedule a run across your tracked sellerIdTargets or sellerAsinTargets, keep the previous run's dataset export, and compare the new run's rows on asin/seller_id — alert when price, availability, productCatalogCount, or stars moves beyond a threshold you set. The same loop works for discoveryKeywords: re-run a keyword on a schedule and a new seller_id showing up in the results means a new competitor has entered that niche. Since this Actor runs on Apify, use the platform's Schedules feature to trigger the run automatically and its Webhooks or API to deliver each run's dataset to your own storage or alerting pipeline for the comparison step, rather than re-checking storefronts by hand.

Integrate Amazon Seller Scraper and automate your workflow

Amazon Seller Scraper works with any language or tool that can send an HTTP request, since it runs as an Actor on the Apify platform.

REST API with Python

import requests

ACTOR_ID = "Scrapier~amazon-seller-data-extractor-and-product-catalog-scraper"
TOKEN = "YOUR_APIFY_TOKEN"

resp = requests.post(
    f"https://api.apify.com/v2/acts/{ACTOR_ID}/run-sync-get-dataset-items",
    params={"token": TOKEN},
    json={"sellerAsinTargets": ["B00P8XQPY4"], "fetchProductCatalog": True},
)
for row in resp.json():
    if row["type"] == "seller":
        print(row["seller_name"], row["stars"], row["productCatalogCount"])

MCP for query-grounded AI agents

Amazon Seller Scraper is callable through Apify's official Actors MCP Server, which exposes any Apify Actor as a tool for MCP-compatible clients such as Claude Desktop and Cursor:

npx -y @apify/actors-mcp-server --actors Scrapier/amazon-seller-data-extractor-and-product-catalog-scraper

An agent asks a question about a seller or product, the tool call runs this Actor with the resolved input, and the returned seller-plus-catalog JSON grounds the agent's answer instead of a guess — useful for sourcing assistants and competitor-research copilots that need current storefront data, not stale training data.

Scheduled monitoring and delivery

Apify's built-in Schedules let you trigger this Actor on a recurring interval without external cron infrastructure. Combine a schedule with Apify Webhooks (fired on run completion) or the Apify API to push each run's dataset to your own storage, spreadsheet, or alerting system for the run-over-run comparison described above.

Is it legal to scrape Amazon seller data?

Yes — Amazon Seller Scraper only reads pages any storefront visitor can already see; no login, password, or private account access is used. Courts have generally treated scraping of publicly accessible web data as not violating the Computer Fraud and Abuse Act, as in hiQ Labs v. LinkedIn (9th Cir., 2022). Most fields returned here are business data — storefront name, ratings, policy text, product listings — not personal data, and this Actor's feedbacks[] rows carry only a star rating, review text, and date, with no reviewer name attached. Two fields can carry personal information for individual/sole-proprietor sellers: detailed_info[] (business name/address) and seller_phone_number — treat those under GDPR/CCPA if your use case involves EU or California residents. Scraping for one-off research carries a different risk profile than bulk storage or resale of seller data. Consult your legal team for commercial use cases involving bulk data storage.

Frequently asked questions

How many results does Amazon Seller Scraper return per query?

Per seller, catalog products are capped by maxProductsPerSeller (default 20, max 2000, or 0 for unlimited bounded by the maxCatalogPages page-depth cap of up to 50 pages), and enrichment is capped separately by maxEnrichedProducts (default 10, max 500). Feedback rows are capped by maxFeedbackPerSeller (default 10, max 1000, or 0 for all the page allows). Keyword discovery resolves up to 15 unique sellers per keyword.

Which Amazon marketplaces does it support?

20 domains with automatic proxy-country matching: amazon.com, .co.uk, .de, .fr, .it, .es, .ca, .com.mx, .com.br, .co.jp, .in, .com.au, .ae, .sa, .nl, .com.tr, .se, .pl, .sg, and .eg — set via marketplaceDomain.

Can I control how feedback is ordered?

Yes — feedbackSortOrder sorts feedbacks[] before maxFeedbackPerSeller truncates it: recent (newest first), helpful (most "found helpful" votes first), or rating (highest stars first).

How does Amazon Seller Scraper handle Amazon's anti-bot measures?

Each seller task runs its own sticky residential proxy session with a homepage warm-up before the target page, rotating to a fresh IP and user agent on a detected block, with an escalating retry backoff. Turning on captchaSolverAssist doubles the retry attempts and backoff for stubborn soft blocks — no third-party CAPTCHA-image-solving service is used.

Does Amazon Seller Scraper extract the product catalog with live enrichment?

Yes — every catalog product row includes enriched: true plus availability, featureBullets, variationNames/variationCount, and detailPrice when enrichCatalogProducts is on and the product is within the maxEnrichedProducts cap. Products beyond the cap, or when enrichment is turned off, return enriched: false with those fields absent rather than guessed.

How do I use Amazon Seller Scraper to monitor a seller's catalog over time?

Schedule a recurring run across your tracked seller IDs or ASINs, diff each run's rows on asin and seller_id against the previous run, and alert on changes to price, availability, productCatalogCount, or stars. Use Apify's Schedules to trigger the run and Webhooks or the API to deliver each run's results.

Does Amazon Seller Scraper work with Claude, ChatGPT, and AI agent frameworks?

Yes on both fronts — it's callable as an HTTP endpoint by any agent framework, and it's also reachable through Apify's Actors MCP Server (npx -y @apify/actors-mcp-server --actors Scrapier/amazon-seller-data-extractor-and-product-catalog-scraper) for MCP-compatible clients, so an agent can retrieve live seller and catalog data before answering.

How does Amazon Seller Scraper compare to other Amazon seller scrapers?

Most Amazon seller scrapers stop at the storefront profile — name, rating, feedback — and print the products_link without ever following it. Amazon Seller Scraper follows that link, paginates the seller's full storefront catalog, and optionally enriches each catalog product with a live detail-page fetch, returning both result types linked in one dataset.

Can I use Amazon Seller Scraper without managing proxies or an Amazon account?

Yes — it always runs on residential proxies internally and handles session warm-up, IP rotation, and retry on block automatically. You supply only the ASINs, seller IDs, URLs, or keywords you want to scrape; no Amazon account, login, or API credentials are needed.

Does it still accept the original base scraper's input field names?

Yes — asinInputs, usernameInputs, keywordInputs, startUrls, amazonDomain, proxyCountry, maxComments, maxConcurrency, language, useCaptchaSolver, and sortOrder all still work as fallbacks alongside this Actor's own field names.

Your feedback

Found a bug or missing a field? We want to know. Report it through this Actor's Issues tab on its Apify Store page, or reach out through Scrapier's support channel with a run ID — reports like these directly shape what gets fixed and maintained next.