Shopware Products Scraper
Pricing
from $0.85 / 1,000 products
Shopware Products Scraper
Use this actor to collect public Shopware catalog data from storefront pages. It discovers product pages through product sitemaps and storefront HTML, normalizes titles, prices, stock signals, SKUs, images, categories, and product URLs for price monitoring, competitor analysis, and market research.
Pricing
from $0.85 / 1,000 products
Rating
0.0
(0)
Developer
Trove Vault
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
7 days ago
Last modified
Categories
Share
Shopware Products Scraper: Scrape Public Product Data from Shopware Stores
Use this actor to collect public Shopware catalog data from storefront pages that expose products through SEO URLs, sitemaps, and structured markup. It discovers product pages through product sitemaps and storefront HTML, then normalizes titles, prices, stock signals, SKUs, images, categories, and product URLs for price monitoring, competitor analysis, and market research.
Why use Shopware Products Scraper?
- Use Shopware Products Scraper to collect normalized product data from one store or many stores without building a private integration first.
- Use Shopware Products Scraper when you need repeatable output fields such as URL, title, SKU, brand, price, currency, availability, image, categories, and description.
- Use Shopware Products Scraper when your workflow depends on the Apify API, scheduling, dataset exports, and pipeline fields such as
datasetIdandrunId.
What data can Shopware Products Scraper extract?
| Field | Description |
|---|---|
url | Product page URL that was scraped |
title | Product title from structured data or page markup |
sku | SKU or product code when it is visible publicly |
brand | Brand or manufacturer label |
price | Parsed product price |
currency | Currency code such as USD or EUR |
available | In-stock signal normalized to true or false |
image | Primary product image URL |
categories | Breadcrumb or category labels |
sourceType | Whether the record came from JSON-LD, meta tags, or a mix |
discoveredVia | Whether the URL was found through API, sitemap, or HTML |
error, errorType, message, reason, fix | Structured soft-fail fields for blocked, timeout, not-found, and network errors |
Which use cases fit Shopware Products Scraper?
Price monitoring
Use Shopware Products Scraper to track visible prices, compare-at prices, and stock signals across public Shopware product pages.
Competitor analysis
Use Shopware Products Scraper to compare titles, prices, brands, and category structures across several stores in one run.
Catalog QA and market research
Use Shopware Products Scraper to spot weak product pages, missing images, missing descriptions, and assortment changes while supporting broader market research projects.
Why use Shopware Products Scraper instead of alternatives?
| Feature | Alternatives | This Actor |
|---|---|---|
| Public storefront scraping | Often needs store-specific scripts | One reusable actor pattern |
| Output structure | Raw HTML or partial JSON | Normalized dataset fields |
| Monitoring | Manual reruns | Ready for schedules and API workflows |
| Error handling | Whole run fails or hides bad pages | Structured soft-fail rows |
How do you use Shopware Products Scraper?
- Add one or more store root URLs in
storeUrls. - Start with
maxProductsat 3 to 5 for a smoke test, then raise it for production runs. - Keep
discoveryModeonAUTOunless you are debugging sitemap or HTML discovery. - Run the actor and export the dataset through the Apify Console or API.
How does Shopware Products Scraper work?
- Shopware Products Scraper normalizes storefront roots and validates the input.
- Shopware Products Scraper discovers product URLs through public API, sitemap, and HTML paths when they are available.
- Shopware Products Scraper extracts Product JSON-LD, product meta tags, breadcrumbs, images, stock signals, and pricing data from each product page.
- Shopware Products Scraper emits product rows and structured error rows, then writes a
RUN_SUMMARYrecord to the key-value store.
What input does Shopware Products Scraper accept?
| Field | Type | Default | Description |
|---|---|---|---|
storeUrls | array of strings | demo store prefill | Store root URLs or domains to scrape |
maxProducts | integer | 25 | Maximum number of products to extract per store |
discoveryMode | string | AUTO | Chooses between auto, sitemap-only, and HTML-only discovery |
requestTimeoutSecs | integer | 30 | Timeout used for storefront requests |
includeRawJsonLd | boolean | false | Includes the parsed Product JSON-LD object in the output |
proxyConfiguration | object | Apify Proxy off | Applies proxy settings to discovery, product pages, and supported API calls |
datasetId | string | blank | Appends results to an existing dataset as well as the run dataset |
runId | string | blank | Associates results with a previous step in a pipeline |
Example input for a quick test
{"storeUrls": ["https://demo.themeware.design/modern/en/"],"maxProducts": 10,"discoveryMode": "AUTO"}
Example input for a pipeline run
{"storeUrls": ["https://demo.themeware.design/modern/en/"],"maxProducts": 25,"discoveryMode": "AUTO","datasetId": "your-shared-dataset-id","runId": "previous-run-id"}
What does the output from Shopware Products Scraper look like?
Shopware Products Scraper writes one dataset item per product and uses the same dataset for structured error rows.
| Output use case | Main fields |
|---|---|
| Product analysis | title, price, currency, brand, sku, available |
| URL mapping | url, canonicalUrl, slug, categories |
| Discovery QA | sourceType, discoveredVia |
| Soft-fail debugging | error, errorType, reason, fix |
{"store": "demo.themeware.design","platform": "Shopware","title": "Product page with large image","url": "https://demo.themeware.design/modern/en/Product-page-with-large-image/TWT10012","canonicalUrl": "https://demo.themeware.design/modern/en/Product-page-with-large-image/TWT10012","slug": "TWT10012","sku": "TWT10012","brand": "Themeware Demo","price": 99.95,"compareAtPrice": null,"currency": "EUR","available": true,"image": "https://demo.themeware.design/modern/en/sample-image.jpg","images": ["https://demo.themeware.design/modern/en/sample-image.jpg"],"imageCount": 1,"categories": ["Shop"],"description": "Product page with large image product page extracted from a public Shopware storefront.","sourceType": "jsonld","discoveredVia": "sitemap","attributes": null,"lastModified": null,"rawJsonLd": null,"scrapedAt": "2026-04-21T09:00:00.000Z","error": false,"errorType": null,"message": null,"reason": null,"fix": null}
How can you use Shopware Products Scraper via the Apify API?
Yes. Shopware Products Scraper works through the Apify API like any other actor.
curl -X POST "https://api.apify.com/v2/acts/trovevault~shopware-products-scraper/runs?token=YOUR_APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"storeUrls": ["https://demo.themeware.design/modern/en/"],"maxProducts": 10,"discoveryMode": "AUTO"}'
What are the limitations of Shopware Products Scraper?
- Shopware Products Scraper only works with data exposed publicly on the storefront.
- Shopware Products Scraper depends on the store exposing enough public product links for discovery.
- Shopware Products Scraper can still be blocked by rate limits, bot protection, or regional filtering.
FAQ
Does it work on all Shopware stores?
No. Shopware Products Scraper works best on stores that expose product sitemaps, JSON-LD product blocks, or stable product page markup.
Can I scrape multiple stores at once?
Yes. Add multiple root URLs in storeUrls and Shopware Products Scraper will process them in one run.
How do I monitor for changes over time?
Schedule Shopware Products Scraper in Apify and append each run to a shared dataset or export destination.
What if the site returns a 403 error?
Shopware Products Scraper keeps the run successful and emits a structured row with errorType: "BLOCKED".
How do I schedule the actor to run automatically?
Create a schedule in the Apify Console and attach your preferred input.
Can I use this via the Apify API?
Yes. The curl example above is enough to start a run and collect the dataset programmatically.
Can I use this through an MCP Server?
Yes. If your MCP workflow can trigger Apify actors or consume Apify datasets, you can use Shopware Products Scraper in a broader automation.
Is scraping Shopware data legal?
That depends on your jurisdiction, your use case, the site terms, and the type of data you collect. Shopware Products Scraper is intended for public product data, but you should review the target site terms and get legal guidance when needed.
Related actors
If you also work across storefront platforms, see these related TroveVault actors: Magento and Adobe Commerce Products Scraper, BigCommerce Products Scraper, PrestaShop Products Scraper, Salesforce Commerce Cloud Products Scraper.
Changelog
0.1: First TroveVault-aligned release of Shopware Products Scraper with public storefront discovery, normalized product output, structured soft-fail rows, and daily test input.
Feedback
Open an issue if you need another discovery path, output field, or storefront pattern supported by Shopware Products Scraper.