Amazon DE Search & Product Scraper avatar

Amazon DE Search & Product Scraper

Pricing

from $5.50 / 1,000 full products

Go to Apify Store
Amazon DE Search & Product Scraper

Amazon DE Search & Product Scraper

CommerceStack collects Amazon.de search results, ASIN details and seller catalogs. Monitor product prices with verified German delivery context and EUR. Use via API or Apify MCP.

Pricing

from $5.50 / 1,000 full products

Rating

0.0

(0)

Developer

Aleksandr Karavaev

Aleksandr Karavaev

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Categories

Features

Limited permissions

Share

CommerceStack collects Amazon.de search results, product details by ASIN and seller catalog listings with a verified German delivery postcode and EUR currency. No Amazon account or external scraping subscription is required. The Actor makes its own source requests and never launches another Actor.

Use with ChatGPT, Claude and AI agents

This CommerceStack Actor is available through the official Apify MCP server. It is an Apify tool, not a separate built-in CommerceStack app in every AI assistant. The client must support remote MCP and be connected to your Apify account. Actor runs use the current Apify pricing.

  • Claude: connect the official Apify connector, then name commercestack/amazon-de-search-product-scraper in your request.
  • ChatGPT: where your account and workspace allow custom MCP plugins, follow OpenAI's connection instructions. Use the server URL below and Apify OAuth.
  • Cursor, Claude Code, Codex and other MCP clients: add the same remote server using the client's MCP configuration. See Apify client setup. OAuth avoids pasting an API token into a conversation.

For this Actor plus its description, input schema and current pricing, use:

https://mcp.apify.com?tools=fetch-actor-details,commercestack/amazon-de-search-product-scraper

Copy this first-run prompt:

Use commercestack/amazon-de-search-product-scraper to look up ASIN B0BTJD6LCL, maximum one product, for delivery to 10115 in EUR. Read the schema and current pricing first. Return the title, featured-offer price or its explicit unavailable state, and deliveryContext. Inspect MANIFEST and report technical errors.

Before running, check the input schema, choose page/item limits and review the cost. Read the Dataset together with MANIFEST; an assistant should not infer a missing product, a final checkout price or complete coverage from an incomplete response. For repeated monitoring, keep the same watchlist key and delivery context and follow the monitoring instructions below.

Ready-to-use examples

Duplicate an example into your own Apify account and edit its input before running. Copying an example does not start it or enable a schedule.

Pick your workflow

  • Price monitoring: compare the same ASINs over time in a verified delivery postcode and currency. Set up a saved task.
  • One-off product data: use lookup_only for identity, images and the featured offer; use products for source-visible full-card fields.
  • Product discovery: use search_only or seller_catalog, then look up a selected list of ASINs.

Amazon marketplaces have separate Actors: US, Germany, UK. Keep each market and delivery context in its own watchlist.

Quick start

Product lookup:

{"mode":"lookup_only","products":["B0BTJD6LCL"],"maxItems":1}

Search:

{"mode":"search_only","queries":["sony kopfhörer"],"maxPagesPerSource":2,"maxItems":40}

Full cards:

{"mode":"products","products":["B0BTJD6LCL","B08C7KG5LP"],"maxItems":2}

Seller catalog:

{"mode":"seller_catalog","sellerIds":["A3JWKAKR8XB7XF"],"maxPagesPerSource":2,"maxItems":40}

Use products with queries to discover and hydrate results, or seller_catalog with enrichProducts: true to hydrate catalog listings. Page and item limits produce bounded coverage, not a complete-market or complete-catalog claim.

Output

ModeFields
search_onlyASIN, title, product URL, cover image, displayed price/rating and source placement
lookup_onlyIdentity, title, image gallery, featured price or explicit no-price state, seller and verified delivery context
productsLookup fields plus source-visible attributes, bullets, description, categories, observed variants and A+ content
seller_catalogMerchant-filtered listing traversal with optional full-card enrichment

With monitoring off, filter dataset rows using recordType: product. With monitor: true, consume recordType: monitor instead; a product-only filter would hide every monitoring observation. Free occurrence rows preserve query/page/rank relations. Always inspect MANIFEST: a successful run can have partial coverage or unattempted inputs. fieldAvailability distinguishes present, source_absent, not_requested and extraction_failed.

The default context is Berlin 10115 / EUR. Override it with locations.de.postalCode. Every returned source response must verify that postcode and currency; proxy egress country is not delivery location. A timeout, challenge, unknown404 or absent price never means the product was deleted. Recognized missing pages are reported as product_not_found and are not charged. Used-only featured offers are explicitly marked; unknown condition is not assumed to be New.

Pricing

EventPer 1000 successfully parsed products
Search / un-enriched catalog listings$0.90
Lookup / unchanged monitor observations$4.40
Full product / enriched products$5.50

Source infrastructure is included. Each run has a $0.02 start fee (fixed 1024 MB memory), including runs with no results. Product events are charged only for durable product rows without extraction failures. Confirmed missing products, failed products, occurrence rows and duplicate products within the same run have no per-product charge. A source-absent optional field is not an extraction failure. Distinct runs are separate observations. Normal Apify storage costs after a run may apply.

Coverage and operational limits

Search ranking, sponsored placements, variants and offers may differ between sessions even at the same postcode. The Actor preserves primary result cards in the received pages; it does not promise the same ranking as your browser. Exact-browser-DOM replay preserved all 37 primary cards across two sampled pages. This is parser evidence, not a universal recall or availability guarantee.

The release uses residential discovery and a bounded inexpensive product route with residential recovery for technical failures. All routes share request, traffic and time limits. No interactive CAPTCHA solving, cart actions, text reviews, exhaustive seller offers or variant hydration are included. Catalog merchant identity is separate from the featured-offer seller.

Outputs are incremental. Controlled migration resumes checkpoints; ambiguous storage or billing acknowledgements stop for reconciliation. Keep restartOnError: false, set page/item/time and Apify cost limits, and pin a tested build for integrations. Large jobs may return partial results when a limit is reached.

Support

Open an Actor issue with the run ID, mode, ASIN/query and expected result. Never include API tokens. Use your own Apify token in the Authorization header.

Start a price monitor

  1. In this Actor's Console input, choose products, enable Monitor a fixed product list, and paste the monitoring example below. Replace the ASIN with a product you want to follow. Start with one product; increase maxItems to cover your list only after checking a complete run.
  2. Choose Save as a new task. Keep the same task and monitorKey for later runs, along with the same delivery postcode and currency. monitorKey is a watchlist label, not an API token; use a non-sensitive label.
  3. Run the task once to establish the baseline, then run the same task again. Inspect the Dataset and MANIFEST in the run's default key-value store. The first successful observation is new; a later observation is unchanged when no selected change meets the configured comparison rules. Sub-threshold price movement may still appear in monitorValues.
  4. In Schedules, add this saved task, choose your timezone and a daily time, and set a maximum cost per run. Enable the schedule only after both manual runs are acceptable. Keep resetMonitor: false and allow enough time between runs to avoid overlap. Apify schedule setup.
  5. Read recordType: monitor rows and deduplicate delivery using eventId. Process changedFields, previous and monitorValues; retain unchanged observations as freshness checks. If contextChanged is true, the seller/offer context changed: do not treat it as a like-for-like price movement.

For a 100-ASIN watchlist, the illustrative event bill is $0.57 for a first run where all 100 full cards are delivered and $0.46 for a run where all 100 are unchanged. One first run plus 29 unchanged daily runs totals $13.91. These figures include the current start fee, assume no discounts, no retries as separate runs, no changed/returned products, and exclude post-run storage charges. They are price calculations, not a 100-ASIN speed or completeness guarantee. Changed/returned products use the full-card rate.

MANIFEST.status: partial requires inspection of errors and coverage. A missing observation or a failed run is not a price drop or product removal. Confirmed not_found observations have no product-event charge; source failures do not advance the baseline. The Actor writes data to Apify and does not send customer emails or chat alerts automatically.

Scheduled product monitoring

Set mode: "products", monitor: true, and a fixed list of up to 200 ASINs or product URLs. Use the same monitorKey on each run, or save the input as an Apify task and schedule that task. History belongs to your account and is isolated by Actor, marketplace, delivery postcode and currency. Separate keys allow independent customer watchlists.

{
"mode": "products",
"products": [
"B0BTJD6LCL"
],
"monitor": true,
"monitorKey": "amazon-de-daily",
"monitorFields": [
"price",
"rating",
"reviewCount"
],
"minPriceChangePct": 3,
"resetMonitor": false,
"locations": {
"de": {
"postalCode": "10115",
"currency": "EUR",
"deliveryCountry": "DE"
}
},
"maxItems": 1
}

The first successful observation is changeType: "new". Later runs return a full card for changed and returned products and a compact row for unchanged products. These rows have recordType: "monitor", eventId, recordId, observedAt, changedFields, previous, and explicit monitorValues states. Full new/changed/returned rows use the existing Product with full fields (product-item) event. Unchanged rows use Product lookup (lookup-item); see the Pricing tab for current rates and any run-start fee. Unchanged rows are not charged again as full product rows. Unlike listing-based monitoring, Amazon monitoring still needs a current product-page response per ASIN; it does not eliminate those source requests.

  • monitorFields: choose price, rating, reviewCount, and/or availability. Default: price, rating and reviewCount. Availability is visible source text, not an exact stock quantity.
  • minPriceChangePct: cumulative price movement relative to the last notified price. A review-count or rating change does not reset that price baseline.
  • Prices are compared only within a verified delivery postcode/currency and the same seller, condition, price type and offer context. A verified offer-context change starts a new context (contextChanged: true); it is not presented as a like-for-like price change. A page hiding its price or showing no featured offer is an explicit source state, not a zero price.
  • A verified native Amazon not-found response produces a free result event, changeType: "not_found". This means not found in that observed response, not proof of permanent removal. Source errors, challenges, incomplete responses and unavailable required fields appear in MANIFEST.errors and never become disappearance notifications. All-not-found batches can complete successfully.
  • resetMonitor: true starts fresh baselines for successfully observed products; turn it off on the next scheduled run. It cannot bypass a pending unresolved delivery or charge.

Do not overlap runs sharing a history key. monitor_busy means another run owns that history. For monitor_reconciliation_required, keep the original run and history intact, share the run URL through Issues, and reconcile that run; changing the key or resetting must not be used to retry an uncertain charge. Resurrecting the original run can reconcile acknowledged output/charges, but may incur another platform run-start fee. monitor_source_interrupted prevents a resurrected run from silently resetting its paid source-request budget; the next ordinary scheduled run can make a fresh observation.

Only delivered, billing-confirmed observations advance history. Required field failures preserve the prior baseline. Read MANIFEST.status, errors, coverage, counts and billing on every run. Set limits large enough for the watchlist: maxItems, maxRequests, maxWireBytes and maxRunSeconds also apply in monitor mode. additionalOffers and query/catalog discovery are not accepted in this fixed-list monitor mode. Existing inputs with monitoring off keep their original behavior and output format.