WooCommerce Price Monitor avatar

WooCommerce Price Monitor

Pricing

$30.00 / 1,000 results

Go to Apify Store
WooCommerce Price Monitor

WooCommerce Price Monitor

Watches WooCommerce stores for new and removed products, price drops and rises, sales that start or end and stock changes since its last run, read from each store's public Store API.

Pricing

$30.00 / 1,000 results

Rating

0.0

(0)

Developer

Umberto Vignetta

Umberto Vignetta

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Categories

Features

Limited permissions

Share

What it does

Give it the addresses of WooCommerce stores and it tells you what changed since its last run: new and removed products, price drops and rises, sales that started or ended, and products that went out of stock or came back. Each run reads every store's public Store API (/wp-json/wc/store/v1/products), compares the products with the snapshot the previous run saved, and saves the new snapshot in its place.

The first run for a store only saves this baseline and reports no changes. Changes show from the second run on, so schedule the monitor, for example once a day, to keep watch.

Input

  • stores: the home page addresses of WooCommerce stores, one per line, such as https://shop.example. A store that lives in a folder keeps it, such as https://example.com/shop. A run without any store fails and says so.
  • monitorName (default default): the name of the watch list. Each name keeps its own snapshots, so one account can watch separate lists of stores, or the same store for different purposes. Use at most 50 letters, digits, hyphens and underscores. The first check of a store under a new name saves a new baseline.
  • maxProductsPerStore (default 10000, at least 1): the most products read from each store, in the order of their product ids. When a store has more, only those are compared, and a product past them is never reported as new or removed.

Sample output

{"store": "https://mercantile.wordpress.org", "checkedAt": "2026-11-16T23:22:02Z", "previousCheckAt": "2026-11-16T23:21:58Z", "baseline": false, "productsChecked": 20, "changesFound": 0, "new": 0, "removed": 0, "priceDown": 0, "priceUp": 0, "saleStarted": 0, "saleEnded": 0, "outOfStock": 0, "backInStock": 0, "changes": []}

This is the second check of a store, a few seconds after the first, in which nothing had changed. Each run saves one item for each store checked:

  • store: the store address that was checked.
  • checkedAt: when it was checked, in UTC.
  • previousCheckAt: when the snapshot it was compared with was taken, or null for a baseline.
  • baseline: true when this was the store's first check under this monitor name. A baseline reports no changes.
  • productsChecked: how many products were read and compared.
  • changesFound, then new, removed, priceDown, priceUp, saleStarted, saleEnded, outOfStock and backInStock: how many changes were found, in all and of each type.
  • changes: the changes themselves, by type and then by product id. Each one holds:
    • changeType: new, removed, price-down, price-up, sale-started, sale-ended, out-of-stock or back-in-stock. One product can show more than one change, such as sale-started and price-down.
    • productId, sku (empty when the product has none), name and permalink, the address of the product's page.
    • currency, oldPrice and newPrice (null where there is no price, such as the old price of a new product), and percentChange from the old price to the new one.
    • oldStock and newStock: in stock, on backorder or out of stock.

The dataset has two views: Overview, one row for each store checked, and Changes, one row for each change.

The snapshots are kept in the key-value store named woocommerce-price-monitor in your account, one record for each monitor name and store. Deleting a store's record makes its next check a new baseline.

Price

One result event is charged for each store checked, that is for each item in the dataset, the first check that saves a store's baseline included. Changes are not charged one by one. A store that refuses, does not answer or has no Store API is skipped and not charged. The price per result is shown on the Actor's page.

Limits

  • It reads only the stores it is given, one request a second, with plain requests and no proxy. It sees what any visitor without an account sees: published products, at the prices the store shows to the public.
  • It needs the store's Store API, which WooCommerce stores have on unless the owner turned it off. A store without it is skipped and named in the run's status message.
  • When a store refuses (HTTP 401, 403 or 429) or answers with a CAPTCHA page, that store is skipped at once, without a retry, and named in the run's status message. It never works around a refusal. The run fails with the status message blocked: <what> only when every store refused.
  • A store that cannot be read in full in a run, because it stops answering part way, is skipped for that run. Its snapshot stays as it was, so the next run compares with the last full read.
  • Changes are found by comparing two runs. A price that changed and changed back between two runs is not seen.
  • A product with options, such as sizes, is compared by its lowest price; its options are not checked one by one. A product on backorder counts as in stock, as WooCommerce counts it.
  • A price that appears or disappears, or a change of the store's currency, is not reported as a price change.
  • Near the run's time limit it starts no new store and ends with the stores it checked, naming the others in the status message.
  • One item holds the changes of one store up to about 8 MB of data, tens of thousands of changes. The counts always cover every change found.
  • It reads no reviews, customers or orders, and stores no data about people.