Most Shopify stores publish their product catalog in a machine-readable form. That means you can see a competitor's prices, sale prices, variants (size/colour), SKUs and in-stock status without logging into anything — and if you snapshot it every day, you get a price and availability history for free.
This guide shows how to:
- Get a daily list of only what changed — price changes, sale prices, sell-outs, restocks, new and removed products — with no code (monitor mode).
- Export a whole Shopify store (or one collection, or one product) to CSV.
- For developers: diff snapshots yourself in Python.
First test costs well under a cent.
What you need
- A free Apify account.
- The Shopify Products Scraper | Variants & Inventory Actor.
- The competitor's store domain (e.g.
deathwishcoffee.com). You need to know the store — this tool doesn't discover Shopify stores for you.
The no-code way: monitor mode (recommended)
If all you want is "tell me every morning what my competitor changed", you don't need to export or compare anything yourself. Turn on monitor mode:
{
"domains": ["competitor-one.com", "https://competitor-two.com/collections/sale"],
"monitorChanges": true,
"maxProducts": 0,
"includeInventoryDetails": true
}
- First run saves a baseline and outputs every product once.
-
Every later run outputs only products that are
new,removed(checked when the whole store or collection is read, i.e.maxProducts: 0), orchanged. A changed row says what changed inchangeTypes(price, sale price, in-stock status, inventory quantity, variants) and lists each field inchangeswithbefore,after,variantIdandsku. - Unchanged products are not output and not charged. You pay $1 per 1,000 output products plus platform usage.
What this looked like in our test on November 17, 2026 (the Death Wish Coffee accessories collection): the first run saved a baseline of 32 products; the second run, with nothing changed, returned 0 rows and used about $0.0001 of platform usage.
Make it run every day:
- In the Actor's input form, click Save as a new task.
- Open Schedules → Create new, choose Daily, and add the task.
- Optional: on the task, add an integration — email, Slack, Google Sheets or a webhook — so each day's changes are delivered to you.
Open any run's Changes dataset view to see the day's changes as a table. Use monitorKey to keep separate watch lists (e.g. one per competitor) and resetMonitorBaseline: true to start over.
The rest of this guide covers one-off exports and doing the comparison yourself.
Step 1 — Run a 3-product test
Open the Actor, click Try for free, and keep the default input:
{
"domains": ["deathwishcoffee.com"],
"maxProducts": 3,
"pageSize": 3,
"maxRunSeconds": 90,
"proxyConfiguration": { "useApifyProxy": false }
}
You can paste three kinds of targets into domains:
| You paste | You get |
|---|---|
deathwishcoffee.com |
the store catalog |
https://www.deathwishcoffee.com/collections/accessories |
only that collection |
https://www.deathwishcoffee.com/products/peppermint-mocha-ornament |
that one product with all variants |
Up to 100 stores per run; maxProducts applies per store.
Step 2 — Read one row
Each row is one product with all its variants nested inside. Real row (trimmed) from November 16, 2026:
{
"store": "deathwishcoffee.com",
"title": "Valhalla Java Dark Chocolate Bark",
"vendor": "Ethereal Confections",
"productType": "Chocolate",
"url": "https://deathwishcoffee.com/products/valhalla-java-dark-chocolate-bark",
"currency": "USD",
"priceMin": 15,
"priceMax": 15,
"compareAtPrice": null,
"onSale": false,
"available": true,
"fullyOutOfStock": false,
"variantCount": 1,
"variants": [
{
"variantId": 39660132106295,
"title": "1 Pack",
"sku": "LFVJBK04",
"selectedOptions": { "Size": "1 Pack" },
"price": 15,
"compareAtPrice": null,
"available": true,
"updatedAt": "2026-11-16T03:11:53-05:00"
}
],
"tags": ["Gifting", "Merch"],
"publishedAt": "2026-11-11T12:53:59-05:00",
"observedAt": "2026-11-16T08:11:53.922016+00:00"
}
The fields that matter for competitor tracking:
-
priceMin/priceMax— price range across variants, already as decimals (15, not "1500"). -
compareAtPrice+onSale— whether they're running a markdown. -
variants[].availableandfullyOutOfStock— stock status per size/colour. -
variants[].skuandvariantId— stable keys for comparing snapshots. -
publishedAt— new launches. In this sample, holiday items (a Peppermint Mocha Ornament at $7, a pet bandana at $10) were published November 6–11: a competitor's seasonal line, visible a week in. -
observedAt— when you saw it. Keep this; it's your timeline.
Step 3 — Export the full catalog
Set "maxProducts": 0 (= no limit) and raise maxRunSeconds (e.g. 600) for a full store. In the run's Output tab:
- CSV/Excel: select the Nested variants view to get one line per variant (better for price sheets), or Products for one line per product.
- JSON: keeps everything nested.
Cost: $1 per 1,000 products ($0.001 each), plus Apify platform usage. A product with 20 variants still counts as one. Our 2-product test runs used about $0.0002 of platform usage.
Step 4 — Do I get actual inventory numbers?
Sometimes. Turn on "includeInventoryDetails": true and the Actor also reads each product's public detail endpoints. If the store exposes quantities for every variant, you get variants[].inventoryQuantity, a product inventoryCount, and inventoryAccuracy: "exact".
Real result from a 3-product run on November 17, 2026:
| Product | Price | inventoryAccuracy |
inventoryQuantity |
|---|---|---|---|
| Valhalla Java Dark Chocolate Bark / 1 Pack | $15 | exact | 100 |
| Nine Lives Pet Bandana | $10 | exact | 100 |
| Yule Cat Mug | $38 | exact | 100 |
These are the numbers the store itself publishes at that moment. Some stores publish a capped figure (every product showing exactly 100 is a hint), so treat quantities as "what the storefront reports", not audited warehouse stock — the change over days is usually more informative than the absolute number.
Many stores hide quantities. Then you get inventoryAccuracy: "unavailable" and should rely on the available true/false flags. The Actor won't guess or add up partial numbers — which is what you want if you're making pricing decisions on it. (Detail mode makes more requests per product, so test it on 3 products first.)
Step 5 — For developers: diff the snapshots yourself
Monitor mode (above) does this for you. If you'd rather keep full daily snapshots and compare them in your own code: in Apify Console: Saved tasks → Create task from your input → Schedules → daily at 06:00. Each run gets its own dataset.
Then compare today with yesterday. This Python script uses variantId as the key:
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
TASK = "your-username~competitor-deathwish-daily" # your saved task
runs = client.task(TASK).runs().list(desc=True, limit=2, status="SUCCEEDED").items
new_ds, old_ds = (client.dataset(r["defaultDatasetId"]).list_items().items for r in runs)
def by_variant(rows):
out = {}
for p in rows:
for v in p["variants"]:
out[v["variantId"]] = (p["title"], v["title"], v["price"], v["available"])
return out
old, new = by_variant(old_ds), by_variant(new_ds)
for vid, (title, var, price, avail) in new.items():
if vid not in old:
print(f"NEW {title} / {var} ${price}")
continue
_, _, old_price, old_avail = old[vid]
if price != old_price:
print(f"PRICE {title} / {var} ${old_price} -> ${price}")
if old_avail and not avail:
print(f"SOLD OUT {title} / {var}")
if not old_avail and avail:
print(f"RESTOCK {title} / {var}")
for vid in old.keys() - new.keys():
print(f"REMOVED {old[vid][0]} / {old[vid][1]}")
The script prints one line per change, in this format:
NEW Yule Cat Mug / Default Title $38
REMOVED Peppermint Mocha Ornament / Default Title
PRICE <product> / <variant> $old -> $new
SOLD OUT <product> / <variant>
(The first two lines are real output from comparing two of our test runs.) One important rule, learned while testing this: only compare runs of the same saved task with maxProducts: 0. Those two test runs had different inputs — one product URL vs. a 3-product sample of the store — so every product looked "new" or "removed". With a fixed full-catalog task, NEW and REMOVED mean what they say. Also skip REMOVED alerts when the run's SUMMARY says the store was partial (blocked or timed out).
No-code alternative: monitor mode (top of this guide) does the same comparison for you, and an Apify integration can send the result to Slack or email.
Limits to know
- Only public data. No admin access, no sales numbers, no customer data.
-
Some stores block automated access (password pages, 403/429). The Actor stops on that store and reports it in
SUMMARYrather than inventing data. You can opt into a proxy — that costs extra. -
A full catalogue is only claimed when the summary says
fullCatalog: true. A run that hit yourmaxProductslimit is a successful sample, not the whole store. -
Currency is the store's own; there's no conversion. Use
locale(e.g.en-gb) or a regional domain for other markets.
Independent tool, not affiliated with or endorsed by Shopify or any store shown.
Disclosure: I built and maintain this Actor.
Top comments (0)