Disclosure: I'm Lindenbyte, the small studio that built the Apify Actor used below, and this post was
drafted with AI assistance. Shopify stores publish a public/products.jsonfeed, and you can poll it yourself with a
script; this is a ready-made way to get only the differences between runs, on a schedule, without keeping the snapshots yourself.
Most Shopify scrapers dump the whole catalog every run, and you diff it yourself. The
Shopify Catalog & Change Monitor remembers the previous run and outputs only
six kinds of change: new, price_drop, price_increase, restocked, sold_out, removed. Unchanged products produce no rows, and you are not charged for them.
1. Record a baseline
{
"stores": ["allbirds.com", "gymshark.com"],
"mode": "changes",
"stateKey": "sneaker-deals",
"maxProductsPerStore": 300
}
The first run in changes mode only records what is on the shelf. In our local test (2026-11-17) it read 300 products from each of the two stores and output
one free status row per store (baseline-recorded). stateKey names the snapshot, so you can run one monitor per client or Slack channel.
Note the cap: with maxProductsPerStore below the catalog size, "removed" detection is switched off for that run (the Actor warns you), so for real monitoring set the cap above the store size.
2. Run it again
Run the same input once more. Our second run found nothing new in either store: 0 change rows, status "No changes detected in 2 store(s)". This is the normal state of a monitor, and it costs only the start fee.
3. What a change looks like
Real price changes take days to show up, so to show the output format we edited the saved snapshot by hand (raised one price 25%, flipped one stock flag, deleted one entry) and ran again.
This part is a simulation, but the products and the diff logic are real:
{"changeType": "price_drop", "store": "allbirds.com", "currency": "USD",
"title": "Women's Wool Cruiser - Port (Port Sole)", "oldPrice": 150, "newPrice": 120}
{"changeType": "restocked", "store": "allbirds.com",
"title": "Women's Wool Runner NZ - Shadow Blue (Natural White Sole)", "oldAvailable": false, "newAvailable": true}
{"changeType": "new", "store": "allbirds.com",
"title": "Men's Wool Runner NZ - Shadow Blue (Natural White Sole)", "newPrice": 120}
Each row also carries the product URL, so you can link straight to it in an alert. Filters cut noise: changeTypes (e.g. only price_drop and restocked) and minPriceChangePercent.
4. Schedule it and alert
In the Apify Console create a Schedule (hourly or daily) for a saved task, then add a webhook or the Slack integration on "run succeeded". Or pull results with the client:
from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("lindenbyte/shopify-catalog-change-monitor").call(run_input={
"stores": ["allbirds.com"],
"mode": "changes",
"stateKey": "deals",
"changeTypes": ["price_drop", "restocked"],
"minPriceChangePercent": 10,
"maxProductsPerStore": 5000,
})
for row in client.dataset(run.default_dataset_id).iterate_items():
if row.get("changeType"):
print(row["changeType"], row["title"], row.get("oldPrice"), "->", row.get("newPrice"))
No-server option: fork the free template repo
lindenbyte-studio/shopify-competitor-price-alerts:
add your Apify token as a repository secret, list the stores in one YAML file, and GitHub Actions posts price drops,
restocks and new products to Slack or email on a schedule.
Cost and limits
Pricing is pay-per-event: a small start fee, $0.0015 per detected change, and catalog mode costs $0.0008 per product row. A daily monitor of a store with ~20 changes a day is roughly three cents. Status rows are free.
Honest limits: it reads the public default-market storefront price, not logged-in or regional prices; password-protected or bot-blocking stores return a free status row instead of data; it respects robots.txt by default.
Some stores may block datacenter IPs, in which case the Actor can escalate to a proxy.
Top comments (0)