Amazon DE Sellers Leads Scraper — Product Price & Ratings

Amazon DE Seller Leads Scraper — Price, Ratings & Business Data

Amazon DE Seller Leads Scraper — Price, Ratings & Business Data returns Amazon.de seller leads — one row per product–seller pair — enriched with business_name, vat_number, registration_number, phone_number, email, business_address, plus the product's own price, currency, rating, reviewCount and imageUrl pulled from the same page already visited to find the seller. Every lead also carries a computed productToSellerValueRatio sourcing score and a hasFullImpressum compliance flag. Built for sourcing teams, pricing analysts, and compliance reviewers who need seller contact data with price context attached in one pass, instead of two separate scrapes.

---

🧭 What is Amazon DE Seller Leads Scraper?

It's an Apify Actor that discovers third-party sellers on Amazon.de and, for every product they sell, extracts the seller's business identity (name, VAT/registration numbers, address, phone, email) alongside that product's live price, list price, star rating, review count and image. No Amazon account, Seller Central login, or API key is required — you supply a search keyword and category, or paste Amazon.de search/product URLs, and the actor runs the discovery-to-extraction pipeline itself.

Key capabilities:

• 🔎 Discovery by keyword + category, or by direct URL — search Amazon.de like a shopper (searchKeyword + productCategory), or feed it exact amazonUrls (search-result pages or /dp/ product pages) for precision runs.
• 💶 Price and ratings on the same pass — price, currency, listPrice (only when genuinely higher than price), rating, reviewCount and imageUrl are read from the product page the actor already opens to find the seller — no second request.
• 🧮 Two derived, non-fabricated fields — productToSellerValueRatio (a price-vs-demand sourcing score) and hasFullImpressum (a compliance flag), both computed only from fields already on the row; either is null when an input is missing, never guessed.
• 🏢 Seller business/Impressum data — business name, business type, trade-register number, VAT number, phone, email and address, read from the seller's public business-information page.
• 📈 Seller performance history — lifetime, 1-year and 3-month average rating and review counts for the seller (separate from the product's own rating).
• 🔁 Backward-compatible input — the original field names (keyword, amazon_category, sort_by, maxResults, startUrls) still work as fallback aliases, so existing base-actor input JSON runs unchanged.

---

📋 What data can I extract with Amazon DE Seller Leads Scraper?

Every dataset row is one seller lead — a product ASIN paired with the seller behind it — carrying product data, seller business data, seller performance history and two derived scoring fields:

Field	Example value	Use case
asin	"B0FCS9LBVN"	Product identifier, join key back to the listing
product_name	"Ficerd 3er Pack Langarm Shirts für Damen"	Human-readable product label
product_url	"https://www.amazon.de/dp/B0FCS9LBVN"	Link back to the live listing
seller_id	"A3OJWAJQNSBARP"	Amazon's internal seller identifier
seller_page_url	"https://www.amazon.de/sp?ie=UTF8&seller=A3OJWAJQNSBARP"	Link to the seller's storefront
category	"Fashion > Damen > Bekleidung > Tops, T-Shirts & Blusen"	Breadcrumb category, or the input category when no breadcrumb is found
price	24.99	Current product price
currency	"EUR"	Currency code parsed from the price string
listPrice	29.99	Struck-through "was" price — only present when genuinely higher than price
rating	4.3	Product-level star rating (0–5)
reviewCount	512	Product-level review count
imageUrl	"https://m.media-amazon.com/images/I/71abcXYZ.jpg"	Main product image URL (metadata only, no file download)
list_price	29.99	Legacy snake_case duplicate of listPrice
product_rating	4.3	Legacy snake_case duplicate of rating
product_review_count	512	Legacy snake_case duplicate of reviewCount
image_url	"https://m.media-amazon.com/images/I/71abcXYZ.jpg"	Legacy snake_case duplicate of imageUrl
rating_lifetime	4.6	Seller's lifetime average rating
reviews_lifetime	18420	Seller's lifetime review count
rating_1_year	4.5	Seller's 1-year average rating
reviews_1_year	3210	Seller's 1-year review count
rating_3_months	4.4	Seller's 3-month average rating
reviews_3_months	540	Seller's 3-month review count
about_seller	"Amazon Export Sales, LLC..."	Free-text "About seller" section
business_name	"Amazon Export Sales LLC"	Registered business name from the Impressum page
business_type	null	Business type label ("Geschäftsart")
registration_number	"82-0544687"	Trade register number
vat_number	null	VAT identification number
phone_number	"+1206-266-1000"	Business phone
email	"ags-prodm-us-de@amazon.com"	Business email
business_address	"410 TERRY AVE N, Seattle, WA, 98109-5210, US"	Full registered address
country_code	"US"	Last address component, used as the seller's country
productToSellerValueRatio	3.9762	Computed sourcing score: price ÷ (rating × ln(reviewCount + 1)) — lower means better value relative to demand
hasFullImpressum	false	true only when business_name, business_address, vat_number and registration_number are all present
scrapedAt	"2026-08-12T10:00:00+00:00"	ISO-8601 timestamp of extraction
scraped_at	"2026-08-12T10:00:00+00:00"	Legacy snake_case duplicate of scrapedAt

💶 Price, ratings and sourcing score

price, currency, listPrice, rating and reviewCount are pulled from the product page — the same fetch already made to locate the seller, so enabling them costs no extra request. productToSellerValueRatio weighs price against demand (rating × ln(reviewCount + 1)); a sourcing analyst can sort a run by this field to surface sellers whose product is cheap relative to how well-reviewed and popular it is, without opening every listing individually. Both price/rating fields and the ratio are controlled by the includePriceAndRatings and computeLeadScore toggles — turn either off to get a leaner, faster row.

🏢 Business identity and compliance fields

business_name, business_type, registration_number, vat_number, phone_number, email, business_address and country_code come from the seller's public business-information page — Amazon.de's equivalent of a German Impressum. hasFullImpressum flags, per lead, whether all four of the core disclosure fields (name, address, VAT number, registration number) are present, so a compliance reviewer can filter a run down to sellers with incomplete public disclosures without reading every row by hand.

---

🆚 How does Amazon DE Seller Leads Scraper differ from Amazon's official Product Advertising API?

As of 2026-08-15, Amazon's Product Advertising API 5 (PA-API) has been deprecated: calls now return an HTTP 403 with the message "Product Advertising API is deprecated. Please migrate to Creators API" (Amazon Associates / Creators API documentation, checked 2026-08-15). Before deprecation, PA-API required an active Amazon Associates account with at least 10 qualified affiliate sales in the trailing 30 days just to keep a key active (Amazon Associates PA-API eligibility documentation, checked 2026-08-15) — and even then it returned catalog and pricing data for a requester's own affiliate content, not a seller's Impressum-style business registration, VAT number or contact details, which live only on the seller's own storefront pages.

Feature	Product Advertising API (PA-API 5)	Amazon DE Seller Leads Scraper
Current availability	Deprecated, returns HTTP 403 (checked 2026-08-15)	Runs on demand via Apify
Access requirement	Active Amazon Associates account, 10+ qualified sales / 30 days, while it was active	No Amazon account or API key — set input, run
Seller business/Impressum data	Not in scope — product/catalog data only	business_name, vat_number, registration_number, phone_number, email, business_address per lead
Price + rating in one call	Available while active, for catalog items	price, listPrice, rating, reviewCount, imageUrl from the same page used to find the seller
Search by keyword/category	Supported while active	searchKeyword + productCategory (15 categories), or direct amazonUrls

Why can't I just use Amazon's official API for seller leads?

Even leaving deprecation aside, PA-API was never built for this job — it is an affiliate-content API for pulling catalog items to link to, not a directory of the third-party sellers behind those items. Seller business identity, VAT/registration numbers, and Impressum-style contact details have never been part of its response shape; that data only exists on each seller's own public storefront and business-information pages. Amazon DE Seller Leads Scraper covers this gap by visiting those pages directly — the seller profile and the business-information page — for every product it processes.

If you already have PA-API/Creators API access for pulling your own catalog links, keep using it for that. For finding and profiling the sellers behind Amazon.de listings — with price and rating attached — this actor is the practical path, since no current Amazon API serves that combined use case.

---

🎯 How to use data extracted from Amazon DE Seller Leads Scraper

🏢 Sourcing and procurement teams

Run a searchKeyword + productCategory search, leave includePriceAndRatings and computeLeadScore on, and sort the resulting dataset by productToSellerValueRatio to shortlist sellers whose product is priced well relative to its rating and review volume. business_name, email, phone_number and business_address go straight into an outreach list; hasFullImpressum flags which leads have complete public disclosures before you spend time on them.

📊 Pricing and competitive analysts

Feed a list of competitor product URLs into amazonUrls and let the actor return price, listPrice, rating and reviewCount for each one alongside the seller behind it. Re-running the same URL list on a schedule produces a time series of price and rating per ASIN without needing to re-discover sellers each time.

🔬 Market and category research

Run the same productCategory across resultsSortOrder values (e.g. "Best Sellers" vs "Price: Low to High") to see how seller mix, rating_lifetime, and price distributions shift by category and ranking. country_code on each business record shows where sellers of a given category are legally registered.

🤖 AI agents and automated pipelines

Because the actor is a standard Apify Actor reachable through apify_client, an agent framework can call it as a tool, pass a category and keyword, and get back structured JSON rows — no HTML parsing on the agent's side. hasFullImpressum and productToSellerValueRatio are ready-made signals for an automated lead-scoring or compliance-monitoring pipeline.

---

⬇️ Input

Required inputs: none. You must supply either amazonUrls (or its legacy alias startUrls), or both a keyword and a category (new or legacy field names) — otherwise the run exits immediately with a warning and produces no rows.

Parameter	Required	Type	Constraints	Description
searchKeyword	No	string	—	What to search for (e.g. shirt, shoes, phone case) to discover products and their sellers on Amazon.de. Falls back to the legacy keyword field when left empty.
productCategory	No	string	enum: fashion-womens, fashion-mens, fashion-kids, electronics, grocery, toys, sports, books, beauty, home-garden, automotive, pet-supplies, tools-garden, baby, health	Category to narrow results and find relevant sellers faster. Falls back to the legacy amazon_category field when left empty.
resultsSortOrder	No	string	enum: Featured, Best Sellers, Price: Low to High, Price: High to Low, Avg. Customer Review, Newest Arrivals, Relevance, Select...	How Amazon search results should be ordered before seller/price extraction. Falls back to the legacy sort_by field when left empty.
maxLeads	No	integer	minimum 1, maximum 50000	Maximum number of unique seller leads to collect in this run. Falls back to the legacy maxResults field when left empty. Higher values may increase run time.
amazonUrls	No	array	—	Optional: paste Amazon.de search/product URLs to scrape directly. Falls back to the legacy startUrls field when left empty.
keyword	No	string	—	Legacy alias of searchKeyword. Only used when searchKeyword is empty.
amazon_category	No	string	enum: same 15 values as productCategory	Legacy alias of productCategory. Only used when productCategory is empty.
sort_by	No	string	enum: same 8 values as resultsSortOrder	Legacy alias of resultsSortOrder. Only used when resultsSortOrder is empty.
maxResults	No	integer	minimum 1, maximum 50000	Legacy alias of maxLeads. Only used when maxLeads is empty.
startUrls	No	array	—	Legacy alias of amazonUrls. Only used when amazonUrls is empty.
includePriceAndRatings	No	boolean	default true	When on, each lead includes the product's price, currency, list price (guarded), star rating, review count and image URL. Turn off to skip these six fields.
computeLeadScore	No	boolean	default true	When on, each lead gets a computed productToSellerValueRatio and hasFullImpressum, derived only from already-collected fields. Requires includePriceAndRatings on for the ratio to populate.
proxyConfiguration	No	object	default: Apify Proxy, RESIDENTIAL group, apifyProxyCountry: "DE"	Uses Apify Proxy, pinned to Germany, by default for reliable access to Amazon.de. Change this only if you have a specific reason to.

Example input

{
  "searchKeyword": "shirt",
  "productCategory": "fashion-womens",
  "resultsSortOrder": "Best Sellers",
  "maxLeads": 50,
  "includePriceAndRatings": true,
  "computeLeadScore": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "DE"
  }
}

⚠️ Common pitfall: leaving both amazonUrls/startUrls empty and searchKeyword/productCategory (or their legacy aliases) empty does not error — the run simply exits with a warning and zero dataset rows. If you fill in both a new-named field and its legacy alias, the new field always wins; the legacy value is only read when the new field is blank.

---

⬆️ Output

Each dataset item is one seller lead — a product ASIN paired with the seller found on that product's page. The actor pushes each row to the dataset the instant it's collected, deduplicated on the (asin, seller_id) pair. Output is standard Apify dataset JSON, downloadable as JSON, CSV, Excel, XML or RSS from the Apify Console.

Example output item

{
  "asin": "B0FCS9LBVN",
  "product_name": "Ficerd 3er Pack Langarm Shirts für Damen",
  "product_url": "https://www.amazon.de/dp/B0FCS9LBVN",
  "seller_id": "A3OJWAJQNSBARP",
  "seller_page_url": "https://www.amazon.de/sp?ie=UTF8&seller=A3OJWAJQNSBARP",
  "category": "Fashion > Damen > Bekleidung > Tops, T-Shirts & Blusen",
  "price": 24.99,
  "currency": "EUR",
  "listPrice": 29.99,
  "rating": 4.3,
  "reviewCount": 512,
  "imageUrl": "https://m.media-amazon.com/images/I/71abcXYZ.jpg",
  "list_price": 29.99,
  "product_rating": 4.3,
  "product_review_count": 512,
  "image_url": "https://m.media-amazon.com/images/I/71abcXYZ.jpg",
  "rating_lifetime": 4.6,
  "reviews_lifetime": 18420,
  "rating_1_year": 4.5,
  "reviews_1_year": 3210,
  "rating_3_months": 4.4,
  "reviews_3_months": 540,
  "about_seller": "Amazon Export Sales, LLC...",
  "business_name": "Amazon Export Sales LLC",
  "business_type": null,
  "registration_number": "82-0544687",
  "vat_number": null,
  "phone_number": "+1206-266-1000",
  "email": "ags-prodm-us-de@amazon.com",
  "business_address": "410 TERRY AVE N, Seattle, WA, 98109-5210, US",
  "country_code": "US",
  "productToSellerValueRatio": 3.9762,
  "hasFullImpressum": false,
  "scrapedAt": "2026-08-12T10:00:00+00:00",
  "scraped_at": "2026-08-12T10:00:00+00:00"
}

Each successfully pushed row is billed under the row_result pay-per-event — there are no separate uncharged accounting or error rows mixed into the dataset, since failed page fetches (blocks, missing seller, timeouts) simply produce no row rather than a placeholder one.

---

🎯 How do you filter and target specific seller leads?

Category vs. free-text query. searchKeyword + productCategory searches Amazon.de the way a shopper would — broad and fast to set up, but the result mix depends on Amazon's own ranking. amazonUrls (direct product or search-result URLs) is the precise mode: paste the exact product pages or the exact search-result URL you already trust, and the actor extracts only those.

Scope precision. productCategory narrows the search to one of 15 Amazon.de departments before any seller is fetched, and resultsSortOrder (Best Sellers, Price: Low to High, Price: High to Low, Avg. Customer Review, Newest Arrivals, Relevance, Featured) controls the order sellers are discovered in — useful when maxLeads is set below the total available results and you want the top-ranked or cheapest sellers first, not an arbitrary slice.

Quality thresholds. There is no input-level minimum-rating or minimum-review filter — the actor collects what it finds. Instead, filter downstream on the output fields: hasFullImpressum for compliance completeness, or sort/filter on productToSellerValueRatio, rating and reviewCount in the dataset after the run.

Volume controls. maxLeads (1–50,000) caps unique seller leads for the run; the actor stops as soon as it hits that count, whichever discovery mode is running.

{ "searchKeyword": "phone case", "productCategory": "electronics", "resultsSortOrder": "Best Sellers", "maxLeads": 200 }

{ "amazonUrls": [{ "url": "https://www.amazon.de/dp/B0FCS9LBVN" }, { "url": "https://www.amazon.de/dp/B0D1234ABC" }] }

{ "searchKeyword": "shoes", "productCategory": "fashion-mens", "resultsSortOrder": "Price: Low to High", "maxLeads": 25, "includePriceAndRatings": true, "computeLeadScore": false }

---

🔗 Want to try other SimpleAPI scrapers?

More Amazon scrapers:

Scraper	What it extracts
../../Amazon-Price-Tracker/amazon-price-tracker-title-image-and-product-updates	Tracks a product's title, image and price/status changes over time
../../amazon-product-details-scraper/amazon-product-details-scraper-bestsellers-and-new-releases	Full product-page details for bestseller and new-release listings
../../amazon-search-scraper/amazon-search-scraper-by-country-currency	Search results across Amazon marketplaces with country-specific pricing/currency

Comparable marketplace and seller-directory scrapers:

Scraper	What it extracts
../../../Shopify-Merchant-Scraper/shopify-merchant-scraper-niche-and-keyword-store-search	Discovers Shopify merchants by niche/keyword, with store details
../../../walmart-reviews-scraper/walmart-reviews-scraper-with-seller-and-variant-details	Walmart product reviews plus seller and product-variant data
../../../eBay-Product-Listing-Scraper/ebay-product-listing-scraper-with-sold-price-data	eBay listings enriched with sold-price history

---

💻 How to extract Amazon.de seller data programmatically

Amazon DE Seller Leads Scraper is a standard Apify Actor: one API call starts the run, one call reads back structured JSON — no HTML parsing, no Amazon session of your own to manage.

Python example

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
    "searchKeyword": "shirt",
    "productCategory": "fashion-womens",
    "maxLeads": 100,
    "includePriceAndRatings": True,
    "computeLeadScore": True,
}

run = client.actor("<YOUR_USERNAME>/amazon-de-sellers-leads-scraper-product-price-and-ratings").call(run_input=run_input)

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

Export to spreadsheets or CRM

From the Apify Console's Output tab, export the dataset directly to CSV or Excel. business_name, email and phone_number map straight to CRM contact fields; price, rating and productToSellerValueRatio map to numeric columns for a pricing or lead-scoring sheet — no reshaping needed, since every row is already flat JSON.

---

⚖️ Is it legal to scrape Amazon.de?

Yes — Amazon DE Seller Leads Scraper reads only publicly visible pages: product listings, seller storefronts, and the seller's own public business-information (Impressum) page, which German commercial law requires sellers to display publicly. Most of the output is business/product data — price, rating, category, business registration and VAT numbers — governed by Amazon's Terms of Service and database-rights considerations rather than data-protection law. Some fields (a sole trader's business_name, email or phone_number) can identify a natural person; where they do, GDPR/CCPA-style lawful-basis obligations apply to storing and using that portion of the data. No private, password-protected or login-gated data is accessed. Consult legal counsel for commercial applications involving bulk storage of personal data.

---

❓ FAQ

What happens if a product or seller listing is no longer available?

The actor simply doesn't return a row for it — a blocked, missing, or removed product/seller page produces no lead rather than a row with fabricated data. There is no separate "delisted" flag; absence from the dataset is the signal.

Can I get price and ratings along with the seller records?

Yes, by default. includePriceAndRatings is true unless you turn it off, and it costs no extra request — price, currency, listPrice, rating, reviewCount and imageUrl are read from the same product page already fetched to find the seller.

How accurate is the business/contact data?

The actor returns exactly what's published on the seller's public business-information page at request time. Accuracy depends on whether the seller keeps that page current — Amazon does not verify it on the actor's behalf. Missing fields come back null, never guessed; the standard practice is to spot-check a sample before using the data for outreach.

How many seller leads can I get per run?

Up to maxLeads (1–50,000, default 10). The actor stops as soon as it collects that many unique (asin, seller_id) pairs, whether it's running in keyword+category mode or against a list of amazonUrls.

How do I target a specific Amazon.de category or ranking?

Set productCategory to one of the 15 supported categories and resultsSortOrder to control which products are discovered first (e.g. "Best Sellers" or "Price: Low to High") — useful when maxLeads is lower than the total number of matching products and you want the highest-value slice, not an arbitrary one.

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

It has no dedicated MCP server. Any agent framework that can call an HTTP API can run it through the standard Apify API or the apify_client SDK — start the run, poll or wait for it to finish, then read the dataset.

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

Amazon Price Tracker (title/image/price change tracking) and Amazon Product Details Scraper (bestseller/new-release product pages) return product-level data without seller business identity. Amazon Search Scraper covers country/currency search results. This actor is the one in the set that pairs product price/rating with the seller's business and contact data behind it.

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

Yes. You need only an Apify account to run the actor. No Amazon Associates membership, Seller Central login, or API key is required — the actor reads public Amazon.de pages through Apify Proxy.

---

Conclusion

Amazon DE Seller Leads Scraper — Price, Ratings & Business Data turns a keyword, category, or list of Amazon.de URLs into structured seller leads that already carry product price, rating, and the seller's own business identity in one row. It's built for anyone who would otherwise open a search, a product page, and a seller page separately for every listing they care about — sourcing teams, pricing analysts, and compliance reviewers alike. Set your search or paste your URLs, and start the run from the Apify Console or the apify_client SDK.