Amazon Seller Scraper

Amazon Seller Scraper is an Apify Actor for AI agents, analysts, and automation workflows that need one flat record per Amazon seller. It accepts seller IDs, seller profile or storefront URLs, product URLs, or product ASINs, then returns seller-level fields such as business name, legal address, feedback ratings, rating distribution, recent buyer feedback, storefront URL, and optional storefront products. This Actor is usable through Apify MCP and returns one dataset item per seller, so each record represents one seller with business identity, public reputation signals, and provenance in a single place.

Best fit and connected workflows

Use this Actor when your workflow starts with an Amazon seller identity and needs a structured seller profile record.

It fits well when you are:

• Enriching a seller list with legal business details and feedback summaries.
• Resolving a seller from a product ASIN before adding it to a CRM or lead list.
• Reviewing storefront breadth together with the seller's public rating profile.
• Feeding Amazon seller records into an AI agent that needs flat JSON for downstream reasoning.

A typical connected workflow starts with product research, then uses this Actor to turn the seller behind the listing into a seller record that can move into lead qualification, compliance review, marketplace monitoring, or account enrichment.

Practical scenario

Maya works in supplier research. She starts with a product ASIN from a marketplace listing and wants the seller behind it. She sends the ASIN to this Actor and receives one seller record with sellerId, sellerName, businessName, businessAddress, starRating, positivePercent12mo, ratingsCount12mo, and sourceType. Maya uses the legal business address to match the seller against her internal vendor list, then routes the record to compliance review or sales outreach.

Input

Provide at least one of:

• sellerIds - Amazon seller IDs, 13 to 14 uppercase characters.
• startUrls - seller profile, storefront, or product URLs.
• asins - product ASINs whose third-party seller(s) you want to find.

Other options:

• country - marketplace to use for sellerIds and asins.
• includeFeedback - include recent buyer comments from the seller profile.
• maxFeedback - maximum recent feedback comments to capture per seller.
• includeStorefrontProducts - add storefront products to the seller record.
• maxStorefrontProducts - maximum products to list from each storefront.
• maxStorefrontPages - maximum storefront pages to paginate per seller.
• proxyConfiguration - Apify Proxy settings.

Field	Type	Description
sellerIds	array of string	Amazon seller IDs such as A1ODG4ICFE5MU3. Each ID is resolved on the selected marketplace's /sp?seller=ID profile page.
startUrls	array of string	Amazon URLs for seller profile (/sp?seller=ID), storefront (/s?me=ID), or product (/dp/ASIN) pages. Product URLs are resolved to seller(s) in the buy box.
asins	array of string	Product ASINs such as B007ADJ4JI. The Actor opens each product, reads the Sold by seller(s), then scrapes their profile.
country	string	Marketplace code such as US, UK, DE, or JP. Defaults to US.
includeFeedback	boolean	When enabled, the record includes recentFeedback with visible buyer comments from the profile page.
maxFeedback	integer	Maximum recent feedback comments to capture per seller.
includeStorefrontProducts	boolean	When enabled, the Actor also opens the storefront and lists products into products.
maxStorefrontProducts	integer	Maximum products to list from each seller storefront.
maxStorefrontPages	integer	Maximum storefront result pages to paginate per seller.
proxyConfiguration	object	Apify Proxy settings.

Focused JSON example

{
  "sellerIds": ["A1ODG4ICFE5MU3"],
  "country": "US",
  "includeFeedback": true,
  "maxFeedback": 5,
  "includeStorefrontProducts": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Output

The Actor writes one seller record per dataset item to the default dataset. The output is flat JSON that is easy to pass into AI prompts, CRMs, enrichment chains, and downstream transforms. Read the dataset items from {{links.apiDefaultDatasetUrl}}/items.

Field	Type	Description
sellerId	string	Amazon seller (merchant) ID
sellerName	string or null	Public seller display name
marketplace	string	Marketplace code such as US, UK, or DE
sellerUrl	string	Seller profile page URL
storefrontUrl	string or null	Seller storefront URL
logo	string or null	Seller logo image URL
businessName	string or null	Legal business name from Detailed Seller Information
businessAddress	string or null	Full business address, comma-joined
addressLines	array or null	Business address lines as listed
businessCountryCode	string or null	Two-letter business country code
hasBusinessDetails	boolean	True when a business name or address was found
starRating	number or null	Seller star rating from 0 to 5
positivePercent12mo	number or null	Percent positive feedback over the last 12 months
ratingsCount12mo	integer or null	Number of ratings in the last 12 months
ratingDistribution	object or null	Percent of ratings at each star level
aboutText	string or null	Seller "About" description text
recentFeedback	array or null	Recent buyer feedback comments
productCount	integer or null	Storefront products listed when enabled
products	array or null	Storefront products when enabled
sourceType	string	Discovery path: sellerId, sellerUrl, storefrontUrl, or product
scrapedAt	string	ISO timestamp of the scrape

Illustrative JSON record

{
  "sellerId": "A1ODG4ICFE5MU3",
  "sellerName": "Dreamfarm",
  "marketplace": "US",
  "sellerUrl": "https://www.amazon.com/sp?seller=A1ODG4ICFE5MU3",
  "storefrontUrl": "https://www.amazon.com/s?me=A1ODG4ICFE5MU3",
  "logo": "https://m.media-amazon.com/images/I/example-logo.jpg",
  "businessName": "Dreamfarm Inc",
  "businessAddress": "165 S River Road, Bedford, NH, 03110, US",
  "addressLines": ["165 S River Road", "Bedford", "NH", "03110", "US"],
  "businessCountryCode": "US",
  "hasBusinessDetails": true,
  "starRating": 4.5,
  "positivePercent12mo": 92,
  "ratingsCount12mo": 225,
  "ratingDistribution": {
    "fiveStar": 91,
    "fourStar": 5,
    "threeStar": 1,
    "twoStar": 1,
    "oneStar": 2
  },
  "aboutText": "Seller about text from the profile page.",
  "recentFeedback": [
    {
      "rating": 5,
      "comment": "Great product, fast shipping.",
      "author": "Gma",
      "date": "June 11, 2026"
    }
  ],
  "productCount": 48,
  "products": [
    {
      "asin": "B007ADJ4JI",
      "title": "Example product title",
      "price": "$19.99",
      "rating": 4.6,
      "url": "https://www.amazon.com/dp/B007ADJ4JI"
    }
  ],
  "sourceType": "sellerId",
  "scrapedAt": "2026-06-19T12:00:00.000Z"
}

How it works

This Actor uses CheerioCrawler, Apify Proxy, and session pooling. It resolves sellers from the configured entry points, opens the seller profile page, and extracts the public seller identity and business details. When feedback is enabled, it reads the recent buyer comments rendered on the profile. When storefront products are enabled, it opens the storefront page and lists products into the products array. The Actor supports 18 Amazon marketplaces: US, UK, DE, FR, CA, ES, IT, JP, AU, IN, MX, BR, NL, SE, PL, TR, AE, and SG.

Pricing

This Actor uses Pay per event pricing, plus Apify platform usage charges that apply separately to your account and resource use. Open the live Pricing tab on the Actor page for the current pricing details.

Charged events:

• Actor start
• Seller scraped
• Storefront product listed

For example, a run that scrapes one hundred sellers and lists no storefront products is billed for one hundred seller scraped events plus the actor start event. If storefront products are enabled, each returned storefront product adds its own event. The live Pricing tab shows the current event-based billing and Apify platform usage.

Use with AI agents (MCP)

This Actor is available as an Apify Actor usable through Apify MCP. It works as a structured seller-enrichment tool for agent workflows that need seller identity, legal business details, feedback summaries, and optional storefront product listings.

Precise tool description: resolve an Amazon seller from a seller ID, seller URL, storefront URL, or product ASIN, then return one flat seller record in Apify dataset JSON.

Exact Actor identity: khadinakbar/amazon-seller-scraper

"Find the seller behind this Amazon product ASIN and return one flat seller record with business name, legal address, rating summary, recent feedback, and storefront products if available."

Output interpretation:

• sellerId, sellerUrl, and storefrontUrl identify the seller record and its public Amazon pages.
• businessName and businessAddress are the legal business details published on the seller profile.
• starRating, positivePercent12mo, ratingsCount12mo, and ratingDistribution summarize public seller feedback.
• recentFeedback contains the latest buyer comments rendered on the profile when that input is enabled.
• products contains storefront products when storefront listing is enabled.
• sourceType shows whether the seller came from a seller ID, seller URL, storefront URL, or product ASIN.
• scrapedAt marks when the record was collected.

Provenance and scope:

• Data comes from public Amazon seller profile, storefront, and product pages.
• One dataset record corresponds to one seller.
• Product ASIN input resolves through the product's "Sold by" seller in the buy box.

Pagination and cost guidance:

• maxStorefrontPages controls storefront pagination.
• maxStorefrontProducts sets the maximum products collected per seller.
• Each storefront product returned is billed as one storefront-product event.
• When includeFeedback is on, maxFeedback caps the number of recent profile comments collected from the visible seller page.

Apify API example

JavaScript example with APIFY_TOKEN and dataset readback:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor('khadinakbar/amazon-seller-scraper').call({
  sellerIds: ['A1ODG4ICFE5MU3'],
  country: 'US',
  includeFeedback: true,
  includeStorefrontProducts: false,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Best results and outcome guidance

Start with the most direct identifier you already have.

• Use sellerIds when you already know the merchant ID.
• Use startUrls when you have exact seller, storefront, or product URLs.
• Use asins when the goal is to resolve the seller behind a product.
• Keep includeFeedback on when your workflow depends on recent buyer comments.
• Turn on includeStorefrontProducts when you need catalog breadth in the same record.
• Match the country setting to the Amazon marketplace you are targeting, or provide a start URL with the exact domain.
• Use proxyConfiguration with Apify Proxy settings that fit the scale of your run.

Continue the workflow

• Then use Amazon Bestsellers Scraper — Rankings, BSR & Trends to extend Amazon Seller Scraper research with a complementary discovery contract.
• Then use Avito Scraper — Listings, Prices, Sellers & Item Data to extend Amazon Seller Scraper with a neighboring commerce research source when the brief calls for Avito data.

Design note

I found that the dataset contract is intentionally flat and seller-centric: one record carries business identity, feedback summaries, provenance, and optional storefront products in a single object.

FAQ

How do I choose between seller IDs, URLs, and ASINs?

Use sellerIds for direct seller enrichment, startUrls for already-known Amazon pages, and asins when the starting point is a product listing and you want the seller behind it.

What changes when storefront products are enabled?

The Actor opens the seller's storefront and adds a products array plus productCount to the seller record.

Which marketplaces are supported?

The Actor supports US, UK, DE, FR, CA, ES, IT, JP, AU, IN, MX, BR, NL, SE, PL, TR, AE, and SG.

How is the data organized for AI agents?

Each run returns flat JSON with one seller per dataset item, which makes the output easy to pass into prompts, enrichment chains, and downstream transforms.

What can I use as the next workflow after seller scraping?

Common next steps include CRM enrichment, lead qualification, seller verification, compliance review, and catalog analysis.

Responsible use

Use the output in ways that respect Amazon's public data presentation, your applicable laws, and your internal policies. Review any personal or business data handling requirements that apply to your workflow before storing, sharing, or automating with the results.