Web and domains
E-commerce Price Tracker: WooCommerce, Magento and Any Store
Most online stores publish their catalog somewhere public: WooCommerce and Magento through storefront APIs, Shopify through products.json, and almost every other platform as schema.org Product data on each product page. This Actor detects the platform, reads the catalog the cheapest public way, writes one record per variant or product in one shape, and in changes mode reports only what moved since the last run.
E-commerce Scraper & Price Monitor — WooCommerce, Magento. Pay per result; see the Store page for current pricing.
The source and its limits
| Platform | How it is read | Products per request |
|---|---|---|
| WooCommerce | Store API /wp-json/wc/store/v1/products, the unauthenticated API WooCommerce's block checkout uses; variations by id | 100 |
| Magento 2 / Adobe Commerce | Guest storefront GraphQL /graphql, configurable products with their variants | 50 |
| Shopify | Public products.json | 250 |
| Squarespace, BigCommerce, Wix, Salesforce Commerce Cloud, custom stores | Product URLs from the store's XML sitemap, then the schema.org Product / ProductGroup JSON-LD on each product page | 1 per page |
The Actor looks at a store's home page once to detect the platform. If a catalog API is disabled, blocked or disallowed by robots.txt, auto mode falls back to the product pages' JSON-LD. You can also skip discovery and pass productUrls to watch a fixed set of product pages on any platform. Every record has the same shape as the Shopify price tracker's, plus platform, source, currency and categories, so datasets from both Actors line up. No browser, proxy, login or API key.
In changes mode it keeps the previous snapshot of each store in a key-value store you name and writes only what changed, with before and after values and the percentage price move. Change types are new-product, removed-product, new-variant, removed-variant, price-changed, availability-changed and title-changed.
Limits worth knowing
- robots.txt is read first and honored for every request. If it cannot be reached, the store is not read.
- Requests to one store are spaced at least 500 ms apart, and each store has a time budget (
maxSecondsPerStore, default 900 seconds). When a store stops early, what was read is kept, and in changes mode no removals are reported for that store. - The JSON-LD route needs one request per product page and reads at most 25 sitemap files per store. Product pages without Product JSON-LD and an offer are counted and reported, not guessed at.
- Ecwid and Shopware 6 are not supported, because their storefront APIs need the merchant's access token. Stores that block datacenter traffic return an error item; the Actor does not use proxies or browsers to get around that.
Fields you get
| Field | What it holds |
|---|---|
storeDomain, platform, source | The store, its detected platform and the reader used (woocommerce-store-api, magento-graphql, shopify-products-json or json-ld) |
productId, productHandle, productTitle, productUrl | The product |
vendor, productType, categories, tags | As set by the store |
variantId, variantTitle, sku, barcode, option1-3 | The variant; JSON-LD records take barcode from a GTIN |
price, compareAtPrice, currency | Numbers in the store's currency; on JSON-LD pages compareAtPrice comes from a strike-through price |
available | Availability; null when a JSON-LD offer does not say |
imageUrl, fetchedAt | Image and read time |
recordType, changeType, changedFields, before, after, percentChange | snapshot, baseline, change or error; change fields in changes mode |
Example output
A variant record from the WooCommerce Store API (from the Actor's README):
{
"storeDomain": "mercantile.wordpress.org",
"platform": "woocommerce",
"source": "woocommerce-store-api",
"productId": "34907",
"productHandle": "blue-wordpress-flannel-button-down",
"productTitle": "Blue WordPress Flannel Button-down",
"vendor": null,
"productType": "Apparel",
"categories": [
"Apparel",
"Unisex"
],
"tags": [],
"productUrl": "https://mercantile.wordpress.org/product/blue-wordpress-flannel-button-down/",
"variantId": "34916",
"variantTitle": "Adult Unisex MD",
"sku": "A8C-151-M",
"barcode": null,
"price": 48,
"compareAtPrice": null,
"currency": "USD",
"available": true,
"option1": "Adult Unisex MD",
"imageUrl": "https://mercantile.wordpress.org/wp-content/uploads/2026/10/Howdy-51.png",
"fetchedAt": "2026-11-09T06:04:35.773Z",
"recordType": "snapshot"
}
Use cases
Competitor price tracking across platforms
Run changes mode daily on competitor stores, whatever they run on, and send price-changed events with the percentage move to a webhook.
Watch specific products
Pass a list of product page URLs in productUrls to track price and availability of the items you care about, on any platform that publishes Product JSON-LD.
Catalog export
Snapshot mode exports every variant with price, currency, SKU, categories and image, for analysis, MAP checks or a product feed.
How to run it
You need an Apify account and its API token (Console → Settings → API & Integrations). Each run is billed per result to your account; set a maximum total charge for the run to cap spend.
With curl
The sync endpoint starts a run, waits up to 300 seconds and returns the dataset items. A daily price and stock monitor on one WooCommerce store, posted to a webhook (from the Actor's README; the first run writes the baseline):
export APIFY_TOKEN=<your Apify API token>
curl -sS -X POST \
"https://api.apify.com/v2/acts/owlabee~ecommerce-scraper/run-sync-get-dataset-items" \
-H "Authorization: Bearer ${APIFY_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"storeUrls": [
"mercantile.wordpress.org"
],
"mode": "changes",
"granularity": "variant",
"stateStoreName": "mercantile-price-watch",
"webhookUrl": "https://hooks.example.com/price-changes"
}'
From an AI agent (MCP)
Apify hosts an MCP server. This config exposes only this Actor to the agent:
{
"mcpServers": {
"owlabee-ecommerce-scraper": {
"url": "https://mcp.apify.com/?tools=owlabee/ecommerce-scraper",
"headers": {
"Authorization": "Bearer ${APIFY_TOKEN}"
}
}
}
}
Then ask, for example: Every morning check these three Magento and WooCommerce competitor stores for price drops and new products and post only the changes to my webhook.
Python, Node.js and more examples
Runnable curl.sh, python.py, node.mjs and mcp.json files for this Actor are in examples/ecommerce-scraper on GitHub.
FAQ
Does it need an API key or proxies?
No. It reads public catalog endpoints and product pages with plain HTTP. Stores that block datacenter traffic return an error item.
Which platform will my store be read with?
The platform and source fields on every record say so. Set platform to force one.
Why does the first changes run return so many records?
There is nothing to compare against yet, so the full catalog is stored as baseline records. Later runs return only changes.
Is there a Shopify-only version?
Yes, the Shopify price tracker, which also reports collection membership. This Actor reads Shopify stores too, without collections.
Does it touch carts, checkout or customer data?
No. It reads only the product data the store publishes to every visitor.