Amazon Search Products Scraper: Brand Comparison Details

Amazon Product Scraper — Brand Share, Price and Seller Contact Data

Run an Amazon keyword search or paste a search URL and get back every matching product — ASIN, title, price, rating, review count, sponsored flag, and brand — plus a per-search brand roll-up (brandSharePercent, brandCountInSearch, uniqueSellerCount) that shows who owns the shelf for that query. Turn on seller enrichment and each row also carries soldBy, fulfillmentType (FBA/FBM/AMZ), and the seller's businessName, businessAddress, and rating history. Built for brand managers, pricing analysts, and marketplace researchers who need structured JSON, not a spreadsheet of screenshots.

What is Amazon Search Products Scraper: Brand Comparison Details?

It's a keyword-market scraper for Amazon: give it one or more search terms (or full Amazon search URLs), and it returns every product on the requested result pages, computes a brand-share roll-up across that result set, and — optionally — looks up who actually sells and fulfills each listing. No Amazon account, Associates login, or API key is required; it reads Amazon's public search, product, and seller pages directly.

• Discover products by free-text keyword or by pasting a full Amazon search URL — department, browse-node, and brand refinements in the URL are preserved, not stripped
• Narrow to specific brands with brandFilter, applied both server-side (Amazon's own rh=p_89 refinement) and re-checked locally against each product's byline
• Get a live brand-share-of-search roll-up: how many products a brand has in the result set, its share %, how many distinct brands appear, and how many unique sellers are behind them
• Optionally enrich each product with seller identity (soldBy, sellerId, fulfilledBy, derived FBA/FBM/AMZ fulfillment type)
• Optionally go one step further and pull the seller's business profile — business name, address, positive-feedback %, and lifetime/12-month/3-month rating counts
• Runs against 16 Amazon marketplace domains with per-country proxy pinning and automatic datacenter → residential proxy fallback

What data can I extract with Amazon Search Products Scraper: Brand Comparison Details?

Every run returns one JSON row per product, covering identity, pricing, brand-share analytics, seller identity, and search context. The dataset's default view surfaces the 43 columns below; the underlying JSON/API/CSV export additionally carries page, nodeHierarchy, categories, similarKeywords, deliveryMessage, series, variations, productDetails, secondaryOffer, sellerStarBreakdown, sellerAboutText, and the full brandShare array — none of these are hidden, they're just not in the default table view.

Field	Example Value	Use Case
asin	B07PYLPCB6	Unique product identifier for de-duping and joins
productDescription	"Dymatize ISO100 Hydrolyzed Protein Powder, Fudge Brownie, 5 Lb"	Product title for catalog matching
brand	Dymatize	Brand-level grouping and filtering
brandSource	byline	Discloses whether brand came from an explicit byline or a title guess
manufacturer	Dymatize	Byline-derived brand/manufacturer label
brandProductCount	9	How many results in this search belong to the brand
brandSharePercent	3.7	Brand's % share of this search's result set
brandCountInSearch	63	Total distinct brands found in the search
uniqueSellerCount	41	Distinct seller IDs seen across the search (requires seller details)
soldBy	Nutrition Depot LLC	Who sells the listing
sellerId	A3EXAMPLE123	Amazon seller ID for joins/lookups
fulfillmentType	FBA	Derived FBA / FBM / AMZ classification
fulfilledBy	Amazon	Who ships the order
sellerName	Nutrition Depot LLC	Seller display name from the profile page
businessName	Nutrition Depot LLC	Registered business name (seller profile)
businessAddress	"1200 Commerce Way, Reno, NV 89502, United States"	Business location for outreach/verification
sellerPositivePercent	96%	Feedback-positive percentage
sellerRatingCountLifetime	18320	Lifetime seller rating count
sellerRatingCount12m	3104	Rating count, trailing 12 months
sellerRatingCount3m	812	Rating count, trailing 3 months
sellerAvgRatingLifetime	4.6	Star average derived from the rating breakdown
sellerStorefrontUrl	https://www.amazon.com/s?ie=UTF8&me=A3EXAMPLE123	Link to the seller's storefront
sellerUrl	https://www.amazon.com/sp?ie=UTF8&seller=A3EXAMPLE123	Link to the seller profile page
price	54.49	Current listed price
retailPrice	64.99	Reference/strikethrough price
productRating	"4.6 out of 5 stars"	Star rating as displayed
countReview	42117	Number of ratings
salesVolume	"2K+ bought in past month"	Amazon's own recent-demand signal
prime	true	Prime eligibility
sponsored	false	Whether the result is a sponsored placement
dpUrl	https://www.amazon.com/dp/B07PYLPCB6	Absolute product detail-page URL
imgUrl	https://m.media-amazon.com/images/I/71abcXYZ._AC_SL1500_.jpg	Main product image
keyword	whey protein	The query that produced this row
domainCode	com	Amazon marketplace domain (e.g. com, co.uk, de)
selectedCategory	grocery	Department/search-alias detected for the query
browseNode	null	Amazon browse-node ID, when present in a pasted URL
resultCount	7000	Total results Amazon reports for the query
currentPage	1	Result page this row came from
sortStrategy	relevanceblender	Sort order applied to the search
searchResultPosition	5	Position of the product on its result page
statusCode	200	HTTP-style status for the row (200/403/404/408/500)
statusMessage	FOUND	Human-readable status (FOUND, BLOCKED, NOT_FOUND, TIMEOUT, ERROR)
scrapedAt	2026-07-25T18:42:11Z	UTC timestamp the row was collected

Price, rating, and brand-share data

The fields that drive buying and pricing decisions are price, retailPrice, productRating, countReview, salesVolume, prime, and sponsored — enough to compare a listing's real price against its reference price and gauge organic demand versus paid placement. Layered on top is the brand-share roll-up: brandProductCount and brandSharePercent tell you what fraction of a keyword's result page a brand occupies, while brandCountInSearch and uniqueSellerCount describe how fragmented or concentrated that market is. A pricing analyst pulling whey protein can immediately see, for example, that Dymatize holds a 3.7% share of the result set behind Optimum Nutrition's 5.8%, sold across 41 distinct seller IDs — a live shelf snapshot, not a modeled estimate.

Brand and category targeting data

Targeting runs on three axes: brandFilter (which brands to keep), selectedCategory/browseNode/nodeHierarchy (which department or category the query resolved to), and marketplace/domainCode (which of the 16 Amazon storefronts to query). Together they let a researcher scope a run to "Dymatize and Optimum Nutrition, in Sports Nutrition, on amazon.com" rather than an entire unfiltered keyword.

How does Amazon Search Products Scraper: Brand Comparison Details differ from the official Amazon API?

Amazon's own Product Advertising API 5 (PA-API) has been deprecated in favor of the Creators API, and both sit behind Amazon's affiliate program: the Creators API is described by Amazon as REST access to catalog data "for publishers, influencers, and affiliate partners" (Amazon Associates Central, Creators API — PA-API v5 deprecation notice, checked 2026-07-26) — meaning you need an approved Associates account before you can call it at all, and it's built to return catalog/offer data for content and affiliate links, not seller identity or brand-share analytics.

Feature	Amazon Creators API (formerly PA-API)	This Scraper
Access requirement	Approved Amazon Associates/affiliate account	No Amazon account or API key
Intended use	Catalog data for affiliate publishers/influencers	Open-ended brand, price, and seller research across a keyword market
Seller identity	Not exposed	soldBy, sellerId, fulfilledBy, fulfillmentType per product
Seller business profile	Not available	businessName, businessAddress, feedback %, rating history (opt-in)
Brand-share analytics	Not provided	brandProductCount, brandSharePercent, brandCountInSearch, uniqueSellerCount per search
Query input	ASIN/keyword lookups via signed requests	Free-text keyword or a pasted Amazon search URL, refinements preserved
Output	JSON via signed REST calls	One structured JSON dataset row per product

Why can't I just use Amazon's own API for brand research?

Because access to it is gated behind the affiliate program, not behind a general data-access application — Amazon documents the Creators API as a tool for publishers, influencers, and affiliate partners, not for market or competitor research. Even with an approved account, catalog lookups return item/offer data for the ASINs you request; they don't return who sells a listing, that seller's business address or feedback history, or any aggregate of how many products a brand holds within a given search's result set. This scraper covers that specific gap: it works from a keyword or category, not a pre-known ASIN list, and it computes the brand and seller roll-up itself from the live result page.

If you're already an approved Associate building affiliate content around specific known products, the Creators API is the right, sanctioned tool. If you need to map a whole keyword market — which brands and sellers show up, in what share, under what fulfillment type — without applying for or maintaining affiliate status, that's what this Actor is for.

How to use data extracted from Amazon?

Competitive pricing analysis

Set marketQueries to your product category's core keywords, add brandFilter for the brands you track, and run with default sort. The output gives price, retailPrice, productRating, countReview, and salesVolume side by side for every competing listing, so a pricing analyst can land the dataset in a sheet or BI tool and see, per brand and per seller, who's undercutting whom and by how much on any given day. Re-running the same marketQueries on a schedule turns this into a recurring price-position check without touching Amazon's UI.

Brand-management agencies

Agencies managing a client's Amazon presence run the same marketQueries and brandFilter repeatedly to audit how the client's brand actually appears in search — its brandSharePercent, whether third-party sellers are appearing under the client's brandFilter term, and whether those sellers' sellerId/businessAddress match approved distributors. It's a fast way to flag unauthorized resellers or MAP-violating listings for a client without manually paging through search results.

Market research and intelligence

Run the same category keyword across several markets and compare brandSharePercent, brandCountInSearch, and uniqueSellerCount to see how concentrated or fragmented each one is — a category with 5 brands holding 80% share behaves very differently from one with 60 brands each under 3%. Swapping marketplace across runs extends the same comparison across Amazon's regional storefronts.

AI agents and automated pipelines

Because input and output are both plain JSON, an agent can call this Actor as a tool to pull a live brand/seller snapshot for a category, ground a pricing or sourcing recommendation in real price/brandSharePercent data, or feed a monitoring pipeline that re-runs marketQueries on a schedule and diffs the results.

🔼 Input sample

None of the 12 input parameters are required — omit everything and the Actor runs on its prefilled example queries.

Parameter	Required	Type	Description	Example Value
marketQueries	No	array	Keywords or full Amazon search URLs to scan; each entry is scanned separately	["whey protein", "https://www.amazon.com/s?k=wireless+earbuds"]
brandFilter	No	array	Keep only products of these brands (server-side rh=p_89 + local byline check); empty = all brands	["Optimum Nutrition", "Dymatize"]
includeSellerDetails	No	boolean	Fetch each product's detail page for soldBy, sellerId, fulfilledBy, fulfillmentType. Default false	true
includeSellerProfile	No	boolean	Also fetch the seller-profile page for business name/address and ratings. Implies includeSellerDetails. Default false	true
maxSellerLookups	No	integer	Max products per search that get the extra seller fetch (min 0, max 200). Default 10	25
fulfillmentFilter	No	string (enum)	Keep only any / fba / fbm / amazon fulfillment. Default any	fba
marketplace	No	string (enum)	Amazon marketplace domain, e.g. amazon.com, amazon.co.uk, amazon.de (16 supported)	amazon.com
language	No	string (enum)	Page language override; empty auto-detects from marketplace	en-US
sortOrder	No	string (enum)	relevanceblender / price-asc-rank / price-desc-rank / review-rank / date-desc-rank. Default relevanceblender	review-rank
maxPages	No	integer	Max result pages per query (min 1, max 1000). Default 1 (auto-continues until 2 empty pages)	3
proxyCountry	No	string (enum)	Pin the proxy exit country, or AUTO. Default AUTO	US
proxyConfiguration	No	object	Apify proxy settings. Default: no proxy; falls back datacenter → residential if blocked	{"useApifyProxy": true}

{
  "marketQueries": ["whey protein"],
  "brandFilter": ["Optimum Nutrition", "Dymatize"],
  "includeSellerDetails": true,
  "includeSellerProfile": true,
  "maxSellerLookups": 25,
  "fulfillmentFilter": "any",
  "marketplace": "amazon.com",
  "sortOrder": "relevanceblender",
  "maxPages": 2,
  "proxyCountry": "US",
  "proxyConfiguration": { "useApifyProxy": true }
}

Common pitfall: fulfillmentFilter only takes effect when includeSellerDetails is true. If you set fulfillmentFilter: "fba" but leave includeSellerDetails at its default false, fulfillmentType is never populated and the filter is silently skipped — you'll get every product back, unfiltered, not an empty result set.

🔽 Output sample

Each run pushes one typed, normalized JSON row per product to the dataset. Beyond the platform's built-in JSON/HTML/CSV/Excel/XML export, this is a plain Apify dataset, so any of those formats reflect the full record below, not just the 43-field default view.

{
  "asin": "B07PYLPCB6",
  "productDescription": "Dymatize ISO100 Hydrolyzed Protein Powder, 25g Protein, 5.5g BCAAs, Gluten Free, Fudge Brownie, 5 Pound",
  "imgUrl": "https://m.media-amazon.com/images/I/71abcXYZ._AC_SL1500_.jpg",
  "price": 54.49,
  "retailPrice": 64.99,
  "productRating": "4.6 out of 5 stars",
  "countReview": 42117,
  "dpUrl": "https://www.amazon.com/dp/B07PYLPCB6",
  "prime": true,
  "sponsored": false,
  "salesVolume": "2K+ bought in past month",
  "deliveryMessage": "FREE delivery Tue, Jul 29",
  "manufacturer": "Dymatize",
  "brand": "Dymatize",
  "brandSource": "byline",
  "series": null,
  "variations": ["Fudge Brownie", "Gourmet Chocolate", "Birthday Cake"],
  "productDetails": ["25g protein per serving", "Hydrolyzed whey isolate", "5.5g BCAAs"],
  "secondaryOffer": null,
  "statusCode": 200,
  "statusMessage": "FOUND",
  "keyword": "whey protein",
  "domainCode": "com",
  "page": 1,
  "selectedCategory": "grocery",
  "browseNode": null,
  "nodeHierarchy": ["Health & Household", "Sports Nutrition", "Protein"],
  "resultCount": 7000,
  "categories": ["Health & Household", "Sports Nutrition", "Protein"],
  "similarKeywords": [{ "keyword": "whey protein isolate", "url": "https://www.amazon.com/s?k=whey+protein+isolate" }],
  "currentPage": 1,
  "sortStrategy": "relevanceblender",
  "searchResultPosition": 5,
  "soldBy": "Nutrition Depot LLC",
  "sellerId": "A3EXAMPLE123",
  "sellerUrl": "https://www.amazon.com/sp?ie=UTF8&seller=A3EXAMPLE123",
  "fulfilledBy": "Amazon",
  "fulfillmentType": "FBA",
  "sellerName": "Nutrition Depot LLC",
  "businessName": "Nutrition Depot LLC",
  "businessAddress": "1200 Commerce Way, Reno, NV 89502, United States",
  "sellerPositivePercent": "96%",
  "sellerRatingCountLifetime": 18320,
  "sellerRatingCount12m": 3104,
  "sellerRatingCount3m": 812,
  "sellerAvgRatingLifetime": 4.6,
  "sellerStarBreakdown": { "star5": "82%", "star4": "9%", "star3": "3%", "star2": "2%", "star1": "4%" },
  "sellerStorefrontUrl": "https://www.amazon.com/s?ie=UTF8&me=A3EXAMPLE123",
  "sellerAboutText": "Family-owned sports nutrition distributor.",
  "brandProductCount": 9,
  "brandSharePercent": 3.7,
  "brandCountInSearch": 63,
  "uniqueSellerCount": 41,
  "brandShare": [
    { "brand": "Optimum Nutrition", "count": 14, "sharePercent": 5.8 },
    { "brand": "Dymatize", "count": 9, "sharePercent": 3.7 },
    { "brand": "MuscleTech", "count": 7, "sharePercent": 2.9 }
  ],
  "scrapedAt": "2026-07-25T18:42:11Z"
}

How do you filter and target specific products?

Targeting starts with the query itself: a plain keyword in marketQueries scans Amazon's full relevance-ranked result set for that term, while a pasted Amazon search URL keeps whatever department (i=), browse-node (rh=n:), and brand refinement (p_89) it already carried — so a URL copied straight from a filtered Amazon category search stays scoped to that category instead of widening back out. brandFilter layers a brand scope on top of either input style, applied both server-side and re-checked against each product's byline so a request for two named brands doesn't quietly pick up a third. There's no numeric price- or rating-threshold parameter; the closest thing to a quality/trust signal is fulfillmentFilter (fba/fbm/amazon), which requires includeSellerDetails: true to do anything, combined with sortOrder: "review-rank" to surface the most-reviewed listings first. Volume is controlled by maxPages (leave at 1 for auto-continue until two empty pages, or set a hard cap) and maxSellerLookups (how many products per search get the extra seller/profile fetch).

{ "marketQueries": ["https://www.amazon.com/s?k=protein+powder&rh=n:6973665011,p_89:Optimum%20Nutrition"] }

{ "marketQueries": ["wireless earbuds"], "brandFilter": ["Anker", "JBL"], "fulfillmentFilter": "fba", "includeSellerDetails": true }

{ "marketQueries": ["protein powder", "creatine monohydrate", "pre workout"], "sortOrder": "review-rank", "maxPages": 5, "maxSellerLookups": 50 }

▶️ Want to try other Amazon scrapers?

Scraper Name	What it extracts
Amazon Bestsellers Scraper with Price Drop Report	Amazon bestseller rankings and price-drop tracking
Amazon Seller Data Extractor With Business Contact Enrichment	Third-party seller identity and business contact details
Alibaba Email Scraper & Trade Assurance Details	Supplier contact emails and Trade Assurance status
eBay Scraper By Buyer Interest & Seller Feedback	eBay listings with buyer-interest and seller-feedback signals
eBay Seller Scraper With Business Seller Info	eBay seller identity and business details
Facebook Marketplace : Listing Location Details Scraper	Facebook Marketplace listings with location details

How to extract Amazon data programmatically

This Actor runs as a standard Apify Actor: one authenticated POST to start a run, one dataset-items GET to read results back as structured JSON — no Amazon-side credentials involved.

Python example

from apify_client import ApifyClient

client = ApifyClient("<APIFY_API_TOKEN>")

run = client.actor("SimpleAPI/amazon-search-products-scraper-brand-comparison-details").call(
    run_input={
        "marketQueries": ["whey protein"],
        "brandFilter": ["Optimum Nutrition", "Dymatize"],
        "includeSellerDetails": True,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["brand"], item["brandSharePercent"], item["price"])

MCP for AI agents

This Actor is callable through Apify's Actors MCP Server, which exposes any Apify Actor as an MCP tool:

$npx -y @apify/actors-mcp-server --actors SimpleAPI/amazon-search-products-scraper-brand-comparison-details

An agent can use this to pull a live brand-share/seller snapshot for a category as part of a larger pricing or sourcing workflow. Any MCP-compatible client — Claude Desktop, Claude Code, or another MCP host — can register the server and call the Actor as a tool.

Export to spreadsheets or CRM

The dataset exports directly to CSV or Excel from the Apify Console or API. Map asin to a SKU column, brand/manufacturer to a Brand column, price/retailPrice to pricing columns, and sellerId/businessName/businessAddress into CRM contact fields for outreach or distributor-verification lists.

Is it legal to scrape Amazon product search data?

Yes — scraping publicly listed product and search data is legal in most jurisdictions; these are records Amazon publishes openly so shoppers can find and compare products, and no login is required to view them. The legal framing here is primarily Amazon's Terms of Service and database rights, not privacy law, since the core output — ASIN, price, brand, rating, review count — is product and business data. Some optional fields (sellerName, businessName, businessAddress) identify a business entity, which for a sole-proprietor seller can also be personal data; treat bulk storage of those fields with the same care you would any personal data under GDPR/CCPA. Consult legal counsel for commercial applications involving bulk storage of personal data.

❓ FAQ

What happens if a product is delisted or goes out of stock?

The Actor returns a live snapshot of what Amazon's search results show at request time — there's no per-product "delisted" or "out of stock" flag. If a product no longer appears in Amazon's results, it simply stops appearing in the next run's output rather than being flagged as removed.

Can I get seller data along with the main product results?

Yes — set includeSellerDetails: true for soldBy/sellerId/fulfilledBy/fulfillmentType, and includeSellerProfile: true for business name, address, and rating history. Both are capped by maxSellerLookups (default 10, max 200, counted per product, not per seller).

How accurate is the seller and business contact data?

The Actor returns data exactly as it appears on the public product and seller-profile pages at request time. Accuracy depends on whether the seller keeps their profile current; business/rating fields populate mainly for third-party sellers, since Amazon-direct listings don't carry a seller profile. Verify any address before using it for outreach.

How many records can I get per run?

There's no fixed item cap — volume is governed by maxPages (1 to 1000 per query; leave at 1 to auto-continue until two empty result pages) and, for enrichment, maxSellerLookups (0–200 per search, 0 = uncapped). Every pushed dataset row, including a status row returned when a search is blocked or errors out, is billed under the same row_result event, so a blocked query still produces one billed row rather than silently costing nothing.

What does the brand comparison actually compute?

brandSharePercent, brandProductCount, brandCountInSearch, and uniqueSellerCount are all computed live from that run's own search result set — essentially a "share of shelf" snapshot for one keyword, marketplace, and moment in time. It is not a historical trend, a sales-revenue-based market-share estimate, or a comparison against a competitor's own sales data; it only reflects who and how many appear in the scraped result pages.

Can I filter by brand and fulfillment type at the same time?

Yes — brandFilter narrows the result set to named brands (server-side and by byline), and fulfillmentFilter (fba/fbm/amazon) narrows further by who fulfills the order, provided includeSellerDetails is enabled. There's no numeric price- or rating-threshold parameter; use sortOrder: "review-rank" combined with a page cap to approximate a "most-reviewed first" cut.

Does this Actor work with Claude, ChatGPT, and AI agent frameworks?

Yes — it's reachable through Apify's Actors MCP Server for MCP-compatible clients (Claude Desktop, Claude Code), and it's callable as a standard HTTP/REST endpoint by any agent framework via the Apify API.

How does this compare to other Amazon scrapers in this account?

Compared to Amazon Bestsellers Scraper with Price Drop Report (rankings and price history) and Amazon Seller Data Extractor With Business Contact Enrichment (seller-first lookups), this Actor is keyword/market-first: it starts from a search term or category and layers the brand-share roll-up and optional seller enrichment on top of the full result set, rather than starting from a known ASIN or seller ID.

Can I use this without an Amazon API key or developer account?

Yes — no Amazon account, Associates approval, or API key is needed. You only need an Apify account to run the Actor; Apify Proxy is optional and recommended for the seller/detail page fetches.

Conclusion

This Actor turns an Amazon keyword or category into a structured brand-share and seller-identity dataset in one run — no affiliate account, no ASIN list, and no manual result-page counting required. It's built for pricing analysts, brand-management agencies, and market researchers who need to know not just what's for sale, but who's selling it and how concentrated the brand landscape really is. Every field is documented above exactly as the Actor writes it, with no invented caps or accuracy claims. Start a run from the Actor's page on Apify to pull your first brand and seller snapshot.