Product Price Monitor: Shopify, WooCommerce and Any Shop avatar

Product Price Monitor: Shopify, WooCommerce and Any Shop

Pricing

from $2.50 / 1,000 product row delivereds

Go to Apify Store
Product Price Monitor: Shopify, WooCommerce and Any Shop

Product Price Monitor: Shopify, WooCommerce and Any Shop

Track prices and stock of the shops and products you name: Shopify, WooCommerce and any shop with schema.org product data. Each run lists only new, changed and removed products. Obeys robots.txt, 1 request per second per shop. Pay per product row; unchanged rows and failed shops are free.

Pricing

from $2.50 / 1,000 product row delivereds

Rating

0.0

(0)

Developer

Tan Solutions

Tan Solutions

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Features

Limited permissions

Share

Track the prices and stock of the shops and products you name. One run reads Shopify stores, WooCommerce shops and any product page with schema.org product data, and gives you one clean row per product, variant or offer. Give it a Monitor ID and run it on a schedule: each run then lists only what changed since the last one (new products, price up, price down, back in stock, sold out, removed). An ecommerce scraper, price monitor and product price tracker in one.

Quick API and schedule example

Run it from code, then put the same call on a schedule (Apify Console > Schedules) for a daily price check:

curl -X POST "https://api.apify.com/v2/acts/tan-solutions~product-monitor/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"startUrls": ["allbirds.com", "https://shop.example/product/blue-mug/"], "monitorId": "my-shops", "maxItems": 500}'

What it does

  • Shop home pages or bare domains: reads the whole public catalogue. Shopify stores through /products.json (the feed Shopify publishes for every store), WooCommerce shops through their public Store API, page by page.
  • Shopify collection pages (/collections/<handle>): that collection only.
  • Single product pages: Shopify (/products/<handle>), WooCommerce (/product/<slug>/) or any shop whose page carries schema.org Product data (JSON-LD). Prices, currency and stock come from that data.
  • Home pages of other shops (the site root, or a language home page such as /fr/ or /en-us/): when the home page itself carries no product data, the Actor reads the shop's sitemap (the Sitemap: lines of its robots.txt, else /sitemap.xml), keeps the pages that look like product pages (sitemaps named for products first, else addresses with /product/, /products/, /p/ or /item/), skips every page robots.txt disallows, and reads each one as a product page, up to "Max products per shop" and at the same 1 request per second. Shops whose product addresses have no such marker (for example /blue-mug or /Blue-Mug/SW10001, in plain or gzip .xml.gz sitemaps): the Actor reads 3 pages spread over each sitemap file (largest file first, at most 3 files) and reads the first file whose sample carries product data. It never follows links. If the sitemap lists no product pages, the shop gets one free no_products row that says so.
  • One row per variant or offer, the same shape for every platform: price and compareAtPrice as numbers, currency (ISO code), availability (in_stock, out_of_stock, preorder, backorder, limited, discontinued), sku, image, platform (shopify, woocommerce, jsonld) and path (json or jsonld).
  • Stock from schema.org data: all 12 ItemAvailability values are read, with https://schema.org/ or http://schema.org/ in front: InStock, InStoreOnly and OnlineOnly = in_stock; OutOfStock, SoldOut and Reserved = out_of_stock; PreOrder and PreSale = preorder; BackOrder and MadeToOrder = backorder; LimitedAvailability = limited; Discontinued = discontinued.
  • WooCommerce variable products: one row at the lowest price, with priceIsFrom: true and the highest price in priceMax.
  • urlSource says where a row's url comes from: shop-data when the shop's own product data gives it (WooCommerce permalink, the page's structured data), fetched when it is built from the address the Actor read. A shop-data link can point to another domain of the same shop.
  • A shop or URL that cannot be read gets one free shop row that says why (robots_disallowed, no_products, password_protected, blocked, rate_limited, not_found, error, stopped_by_limit, time_budget, invalid_input), with the number of products delivered before it stopped. A page without product data gets a free no_products row.
  • Run time: the Actor starts no new request once the run is close to its timeout, so a run on slow shops still ends normally. It keeps back enough time for the slowest possible request: the shop's robots.txt and two tries at the request timeout, redirects included, a wait of up to 30 seconds when the shop asks for one, and 5 seconds to save the summary. That is 127 seconds at the default request timeout of 30 seconds (never less than 10 % of the run and never more than half of it; a shop that asks for a slower pace in robots.txt keeps back a little more). Set the run timeout to at least 6 times the request timeout plus 74 seconds: 254 seconds (about 4 minutes) at the default. Shorter runs still read pages, but a very slow shop can then run into the timeout. Each shop not fully read gets one free time_budget row ("time budget reached; 40 of 100 pages read"); rows already delivered stay, and nothing is reported as removed for that shop. Raise the run timeout to read more.

Who it is for

  • E-commerce teams and brands that watch competitors' prices, discounts and stock.
  • Resellers, deal finders and analysts who track a list of products across many shops.
  • Developers and AI agents that want clean, typed price data from one API call.

Quick start

  1. Add shops or product pages in Shops or product pages, one per line: allbirds.com, a collection page like https://store.com/collections/sale, or any product page.
  2. Type a Monitor ID, for example my-shops.
  3. Click Start. The first run lists every product as new.
  4. Put the same input on a schedule. From the second run on, the Output tab shows only what changed. Download it as JSON, CSV or Excel, or read it through the API.

Left empty, the run reads nothing and ends with one free row that asks you to add a shop or product URL.

Input

Field (Console name)What it doesDefault
startUrls (Shops or product pages)Shop home pages, domains, Shopify collections or product pages (at most 50 shops, 500 URLs)empty (add at least one)
monitorId (Monitor ID)Turns on change tracking: use the same ID on every runempty (off)
onlyChanges (Only changed products)With a Monitor ID: list only new, changed and removed productson
maxItems (Max rows per run)Product rows per run across all shops20
maxProductsPerShop (Max products per shop)Products read per shop, 1 to 25,0005,000
maxConcurrency (Shops in parallel)Shops read at once, 1 to 5 (each shop still gets 1 request per second)3
timeoutSecs (Request timeout)Per request, redirects included, 5 to 120. Keep the run timeout at least 6 times this plus 74 seconds (254 s at 30)30
{
"startUrls": ["allbirds.com", "https://kith.com/collections/footwear", "https://shop.example/product/blue-mug/"],
"monitorId": "my-shops",
"maxItems": 2000
}

How change tracking works

Each row gets change (new, price_up, price_down, availability or removed), previousPrice and previousAvailability, compared with the last finished run of the same Monitor ID. availability and previousAvailability are text states (in_stock, out_of_stock, preorder, backorder, limited, discontinued), not true/false, because shops state more than in or out of stock. The first run lists every product as new. With "Only changed products" on (the default), unchanged products are left out and cost nothing; turn it off to get every product with change: "unchanged" as well (charged at a lower price). A product counts as removed only when its shop or collection was read to the end, or a product page you named is gone; a run cut short by your limits or a shop error never reports removals. Keep the same list of URLs per Monitor ID. Without a Monitor ID every row has change: null and the Actor works as a plain ecommerce scraper.

Output example

A real row from a cloud run (build 0.1.3, 14 Nov 2026, first run of a Monitor ID, so change is new):

{
"recordType": "product",
"status": "ok",
"shop": "https://colourpop.com",
"shopDomain": "colourpop.com",
"sourceUrl": "https://colourpop.com/",
"platform": "shopify",
"path": "json",
"productId": "7449951076434",
"title": "Liked Christmas a Lot…",
"updatedAt": "2026-11-14T00:28:41-08:00",
"priceIsFrom": false,
"priceMax": null,
"url": "https://colourpop.com/products/liked-christmas-a-lot-shadow-stix-set?variant=42014435213394",
"urlSource": "fetched",
"variantId": "42014435213394",
"variantTitle": null,
"sku": "Kit-LikedChristmasALot",
"price": 16,
"compareAtPrice": null,
"currency": "USD",
"availability": "in_stock",
"image": "https://cdn.shopify.com/s/files/1/1338/0845/files/Kit-LikedChristmasALot_00461_75fe9a29-0b61-4050-934a-822cb7c5709c.jpg?v=1760723628",
"change": "new",
"previousPrice": null,
"previousAvailability": null,
"missingFields": [],
"currencyMissing": false,
"billable": true,
"productsDelivered": null,
"error": null,
"scrapedAt": "2026-11-14T08:28:40.372Z"
}

Pricing

You pay per product row delivered (the product event): every new, changed or removed row, and every row of a run without a Monitor ID. Unchanged rows left out by "Only changed products" are free; unchanged rows you ask for (the option off) cost less (unchanged-json for shop JSON, unchanged-html for product pages).

Apify planPer 1,000 product rowsPer 1,000 unchanged rows (shop JSON / product page)
Free$4.00$0.30 / $0.80
Bronze$3.30$0.30 / $0.80
Silver$3.00$0.30 / $0.80
Gold, Platinum, Diamond$2.50$0.30 / $0.80

Free rows: every shop row, rows without a price, rows whose currency is unknown (currencyMissing: true), the free no_products row of a page without product data, rows past your "Max products per shop" or "Max rows per run" settings, and rows over the size limit. A removed row is charged like any change. If your spending limit is reached, the run stops cleanly and tells you so. The run's SUMMARY record (key-value store) counts every charged event. Its redirects field lists each redirect hop the run followed (from, to, status, n times); a hop that comes from a robots.txt request is tagged robots: true. Apify's standard Actor start event is charged when a run starts, at the platform's default price.

Limits

  • Speed: one request at a time per shop, at most 1 per second. Shopify reads up to 250 products per page, WooCommerce 100; each product page is one request. Shops in parallel (up to 5) add up.
  • At most 50 different shops and 500 URLs per run, and 25,000 products per shop (default 5,000). The Actor never discovers shops by itself and never follows links: it reads the shops, collections and pages you name, and for a home page (or language home page such as /fr/) without product data the product pages its sitemap lists.
  • Coverage: some shops' product pages are not found yet (for example when the shop's sitemap lists no page the Actor recognises as a product page). Such a shop gets a free no_products row and nothing is charged.
  • Public pages only. No login, no cookies, no passwords, no carts, checkouts, accounts, orders or customer data. Password-protected shops are reported as password_protected and left alone.
  • It obeys robots.txt (the TanForgeBot token, then *) and reads at most 1 request per second per shop.
  • It stops a shop at the first block (403 or a bot wall: blocked) and after one polite retry on 429 Too Many Requests (rate_limited). It does not use proxies, rotate addresses or hide who it is.
  • It identifies itself as Mozilla/5.0 (compatible; TanForgeBot/1.0; +https://apify.com/tan-solutions). Shop owners can allow or block it in robots.txt with the TanForgeBot token.
  • A shop is fully read when a page comes back with fewer products than asked for (250 on Shopify, 100 on WooCommerce); no further page is asked for. A shop that sends the same full page for every page number is read from its first page only, and with a Monitor ID it then reports no removed products. A free shop row (status ok, code PAGES_REPEAT) says so.
  • Shopify's catalogue feed names no currency: the Actor takes it from one page of the shop. If no page states it, the rows are delivered free with currencyMissing: true.

FAQ

Which shops work? Shopify stores and WooCommerce shops that keep their public catalogue on, and any product page with schema.org Product data (most shop platforms add it for search engines). Anything else gets a free row.

How fresh is the data? It is read live at run time; scrapedAt says when.

Do I pay for products that did not change? No, with "Only changed products" on (the default).

Can I call it from an AI agent? Yes, through the Apify API, SDKs or MCP: pass startUrls and monitorId, read the dataset items.

Your responsibilities

You are responsible for the shops and pages you submit and for lawful use of the data you get back (each shop's terms, database and copyright rights, and competition law). The Actor reads only public product data, obeys robots.txt, does not log in and stops at blocks. It is provided without warranty; liability is capped at the fees you paid in the last 12 months. Questions and issues are answered within 14 days through the Actor's Issues tab.

Not affiliated with or endorsed by Shopify, WooCommerce or Automattic. All product names belong to their owners.

Made by Tan Solutions.