Shopify Price & Stock Monitor: Product Scraper, New Products
Pricing
from $0.60 / 1,000 product checkeds
Shopify Price & Stock Monitor: Product Scraper, New Products
Shopify price tracker, stock monitor and product scraper for public stores: get price drops, sales, sold-out and back-in-stock changes and new or removed products across runs, or export the full catalog (prices, variants, stock) on every run. Failed stores incur no event charge.
Pricing
from $0.60 / 1,000 product checkeds
Rating
0.0
(0)
Developer
Altronite
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
19 days ago
Last modified
Categories
Features
Share
A Shopify price tracker and stock monitor for public stores, and a Shopify product scraper for full catalog exports. Add the home URLs of the stores you follow and schedule a run: the first run saves a baseline, and every later run returns only the products that changed, with the change named: price drops and rises, sales started or ended, sold out and back in stock, new products and removed products. Turn on Output every product to export the whole catalog on every run instead, with title, vendor, product type, URL, image, minimum and maximum price, compare-at price, discount, stock status and variants. It reads the store's public product feed (/products.json), so no login or store API key is needed. Failed stores never charge an event.
This actor is independent and is not affiliated with or endorsed by Shopify.

Who it's for
- Competitor tracking: follow new products, price drops, discounts and availability on rival Shopify stores.
- Dropshippers and resellers: watch supplier stores for price changes, sold-out products and restocks.
- Catalog research: keep a saved snapshot and inspect changes between runs.
- Automation pipelines: consume structured product events with a clear status.
What the Shopify price and stock monitor returns
One row per baseline product or changed product. A product with several changes is emitted and charged once. Each store also gets one summary row (productsSeen, baseline, changed, unchanged, removed, capped, productsCharged, and a note when capped), so a run with no changes still shows what was checked.
| Field | What it holds |
|---|---|
changeType | baseline, change, optionally unchanged, or summary |
changeTypes | new, removed, price_down, price_up, sale_started, sale_ended, sold_out, back_in_stock |
| Product fields | productId, handle, title, vendor, productType, url, imageUrl, publishedAt |
| Prices and stock | priceMin, priceMax, compareAtMax, discountPct, available, and variants keyed by variant ID |
variantChanges | Price changes for variant IDs present in both snapshots: variantId, previousPrice, price |
previous | Previous priceMin, priceMax, compareAtMax, available; null for baseline or new products |
| Also | status, store, currency, scrapedAt; errors include error and input |
Example change row with fake data:
{"status": "ok","store": "https://shop.example","scrapedAt": "2026-10-04T12:00:00+00:00","changeType": "change","changeTypes": ["price_down", "sale_started"],"productId": "1","handle": "cloud-shoe","title": "Cloud Shoe","vendor": "Example Footwear","productType": "Shoes","url": "https://shop.example/products/cloud-shoe","imageUrl": null,"priceMin": 80.0,"priceMax": 80.0,"compareAtMax": 100.0,"discountPct": 20,"available": true,"variants": {"101": {"price": 80.0, "compareAtPrice": 100.0, "available": true}},"publishedAt": "2026-01-01T12:00:00Z","variantChanges": [{"variantId": "101", "previousPrice": 100.0, "price": 80.0}],"previous": {"priceMin": 100.0, "priceMax": 100.0, "compareAtMax": null, "available": true},"currency": "USD"}
Use it from code, the API or MCP
Run this actor with the Apify API, the Apify Python or JavaScript (JS) clients, or as a tool through the Apify MCP server. Pass the same input JSON through any of these interfaces.
Every output row has a status field; inspect it before processing the row. For ok rows, inspect changeType and changeTypes; error rows explain failed stores. Reuse the same monitorName for later comparisons.
Minimal input:
{"storeUrls": ["https://store-one.example"]}
The Input tab is prefilled with a public store so a first run works as is.
How to monitor a Shopify store
Fill in the fields below, or paste JSON into the Input tab. Only storeUrls is required.
| Field | Default | What it does |
|---|---|---|
storeUrls | one public store (prefilled in the Input tab) | Public Shopify store home URLs. Scheme defaults to HTTPS; paths are removed, hosts lowercased, duplicates merged. At least one valid URL is required. |
monitorName | default | 1 to 40 lowercase letters, digits or hyphens. State is kept in the key-value store shopify-monitor-<monitorName>; reuse the name to compare with earlier runs. |
maxProductsPerStore | 1000 | 1 to 5,000. At the cap, unseen products are not reported as removed. |
includeUnchanged | false | Emit a row for every product on every run (a full export). Unchanged rows carry no change charge. |
resetBaseline | false | Ignore saved state and record a new baseline this run. |
proxyConfiguration | Apify Proxy on | If proxy setup fails the actor continues with a direct connection. |
Input examples
Full product export (Shopify product scraper)
Every run returns one row per product (title, vendor, type, URL, image, min and max price, compare-at price, discount, stock, variants), plus the change fields once a baseline exists.
{"storeUrls": ["https://store-one.example"],"monitorName": "catalog","includeUnchanged": true}
Shopify price tracker: one store, checked daily
{"storeUrls": ["https://store-one.example"],"monitorName": "daily","maxProductsPerStore": 1000}
Track new products and price drops on competitor stores
{"storeUrls": ["https://store-one.example","https://store-two.example","https://store-three.example","https://store-four.example","https://store-five.example"],"maxProductsPerStore": 500,"monitorName": "competitors"}
Shopify stock monitor: sold out and back in stock, twice a day
Schedule this input twice daily and filter the change rows for sold_out, back_in_stock and price_down in changeTypes.
{"storeUrls": ["https://store-one.example", "https://store-five.example"],"monitorName": "suppliers","maxProductsPerStore": 2000}
Reset the baseline once
Run this input once to replace the saved baseline for daily. Set resetBaseline to false or omit it on subsequent runs.
{"storeUrls": ["https://store-one.example"],"monitorName": "daily","resetBaseline": true}
Schedule it
In Apify Schedules, create a schedule for the actor or its saved task and set it to run daily. Use the same monitorName on each run to keep state and compare against the previous snapshot. Avoid overlapping runs that share a monitor name and store.
Pricing
Pay per event. You pay for three things:
| Event | Price | When |
|---|---|---|
product-checked | $0.0006 per product | every product read from a store, on every run (first run and later runs) |
change | $0.001 per changed product | once per product with a new, removed, price, sale or stock change on later runs, even if several change types apply |
apify-actor-start | $0.0005 per run | once per run, one event per GB of memory with a 1 GB minimum |
Free: baseline rows themselves (the products are charged as product-checked), unchanged rows (only emitted with includeUnchanged), the per-store summary row, and failed stores.
Examples:
- First run on a store with 1,000 products: 1,000 x $0.0006 + $0.0005 = $0.6005.
- Later run on the same store, 12 products changed: 1,000 x $0.0006 + 12 x $0.001 + $0.0005 = $0.6125.
- Later run, nothing changed: 1,000 x $0.0006 + $0.0005 = $0.6005.
- A store that fails (blocked, no
/products.json): $0 for that store; you still pay the start fee for the run.
Lower the cost with maxProductsPerStore (checked products are what you pay for). resetBaseline re-records the store; products are charged as checked, as on any run. Prices were read from the Store on 21 Oct 2026; the Pricing tab is the source of truth.
Reliability
Runs through Apify Proxy by default, because Shopify rate-limits datacenter IPs; turn it off in Proxy configuration if you run your own.
- Respects wildcard-user-agent robots.txt rules for
/products.json, including Allow/Disallow wildcards and longest-match rules. Missing or unreachable robots.txt is treated as allowed. - HTTP 429, 5xx, timeouts and network failures on product requests retry up to four attempts, with jittered exponential backoff starting at 3 seconds and capped at 60 seconds.
- Stores run sequentially. Requests within each store have a random 1.0-1.5 second pause between them, including retries.
- A failed store produces an uncharged error row and leaves its saved state intact. Other stores continue.
- Invalid input fails the run with a message saying what to fix. Invalid URLs alongside valid URLs produce free error rows.
- State is written after the catalog fetch and output delivery complete. Capped fetches retain unseen saved products and suppress removals.
Troubleshooting
You see in error | Cause | Fix |
|---|---|---|
| "not a Shopify store or products.json disabled (HTTP 404)" (or another status) | The store does not publish /products.json | Check the store is a public Shopify store; some stores disable the endpoint. Free, saved state kept. |
| "blocked by robots.txt" | The store's robots.txt disallows /products.json | Not bypassed by this actor. Free. |
| "products.json HTTP 429" or "HTTP 5xx", "network error" | Rate limit or server trouble; retried up to 4 times with backoff | Keep Apify Proxy on, run again later, or split the store list across runs. |
| "products.json returned non-JSON data" or "has no products list" | The URL is not a normal Shopify store front | Use the store home URL (for example the main domain). |
| Row "use an http(s) store URL with a host" | An entry in storeUrls is not a web link | Fix the entry; other stores still run. |
| Run fails with "add at least one valid http(s) URL to storeUrls" | Every entry was invalid | Provide at least one valid store URL. Nothing is charged. |
| Every product shows as a baseline again | A new monitorName, or resetBaseline is on | Reuse the same monitorName and set resetBaseline to false. |
No removed events although products disappeared | The summary says capped (maxProductsPerStore reached) | Raise maxProductsPerStore (max 5,000). |
| The same events appear twice | Two overlapping runs share a monitorName and store, or a delivery failure happened before state was saved | Avoid overlapping runs on one name. |
Use cases
-
E-commerce manager tracking rivals: A category manager at a mid-sized apparel brand enters the home URLs of five competing Shopify stores and schedules daily runs. They review the dataset for new arrivals, price drops and sale starts, and forward the rows to the merchandising team for weekly pricing and assortment decisions.
-
Dropshipper watching stock and prices: An individual dropshipper plugs in a short list of Shopify suppliers they resell from and runs the actor twice a day. They use the
sold_out,back_in_stockandvariantChangesfields to update their own listings so prices and availability stay in sync with each supplier's catalog. -
Market researcher building a snapshot archive: A research analyst runs the actor once with
resetBaselineset, saves the dataset as a baseline, then schedules weekly runs under the same monitor name. Each week they export the change rows to a spreadsheet to track how product counts, average prices and discount percentages shift over time. -
Developer feeding a product pipeline: A developer wires the actor into a scheduled run that pushes new dataset rows into a downstream queue. The pipeline reads
changeTypesto decide what to do next, e.g. postingnewproducts to a Slack channel, recordingprice_downrows in a deals database, or flaggingremoveditems for cleanup. -
Affiliate site curator: A deal-site editor monitors a list of Shopify merchants and filters the dataset for rows where
sale_startedis present ordiscountPctcrosses a threshold. Those rows feed an editorial workflow that drafts posts with the product title, URL and image pulled directly from the actor's output. -
Sustainability and supply-chain analyst: A consultant runs the actor across a portfolio of brand stores to compare
priceMin,priceMax, vendor and product type over time. The per-store summary row (productsSeen,baseline,changed,removed,capped) gives them a quick health check of each catalog, and the change rows provide evidence for client reports on assortment and pricing strategy.
FAQ
Is this a Shopify scraper?
It is a change monitor built on a catalog scrape. The first run records every product it can read from the store's public /products.json as baseline rows. After that, each run emits only what changed. It does not scrape reviews, emails or store owner details.
How do I track Shopify price drops and sold-out products?
Add the store home URL, run once for the baseline, then schedule runs with the same monitorName. Rows with price_down, sale_started, sold_out or back_in_stock in changeTypes are the changes you want. Use an Apify webhook or integration to forward rows to Slack, email or a sheet.
Does it work on every Shopify store?
Only on stores that publish /products.json publicly. Stores that disable it, require a login or block requests return an error row, which is free.
How does pricing work? It's pay-per-event: a small start fee per run, a per-product-checked fee for each product checked, and a per-change fee for each changed product on later runs. Unchanged product rows (only when requested), the per-store summary row, and failed stores are free. Exact event rates are shown on the actor's Pricing tab.
What happens if a store fails? The failed store produces an error row and is never charged an event. Its saved state stays intact, and the remaining stores continue normally.
What data does it collect?
Public product data from /products.json only, with currency from /meta.json. No login or customer data is used, and product body_html is never copied into snapshots or output.
What counts as a change? New arrivals, removals, minimum-price and shared-variant price changes, sale transitions, and overall stock transitions. Title, image, vendor and other descriptive edits alone do not create events.
What are the limits?
At most 5,000 products per store (maxProductsPerStore, default 1,000). Fetches use pages of 250 products and stop at a short page, the product cap, or 40 pages; products past the cap aren't monitored, and removals are suppressed.
What currency are prices in?
The store's own currency from /meta.json; no conversion is performed. Currency is null if that endpoint can't provide a string.
What does the first run do? It saves a baseline of the store's products. Later runs compare against that snapshot and emit only products with changes, plus one summary row per store even when nothing changed.
How do I monitor a store over time? Run again with the same monitor name to compare against its saved state, and schedule runs at your chosen interval. Avoid overlapping runs that share a monitor name and store.
Limits
- Stores that disable
/products.json, require authentication or block requests produce an error row. - At most 5,000 products per store (
maxProductsPerStore, default 1,000). Products past the cap aren't monitored, and the summary row says so. - Fetches use pages of 250 products, stopping at a short page, the product cap or 40 pages. Reaching the cap conservatively suppresses removals even if it happens to equal the catalog size.
- A partial catalog cannot establish that an unseen product was removed.
- Changes are observed between runs; intermediate changes between snapshots may not be captured.
- Saved state and dataset delivery are separate operations. A storage or delivery failure can cause events to appear again on the next run.
- Stores run one after another; large catalogs and retries take longer.
Related tools
- Google Sheets Export & Import: send any run's results to a Google Sheet.
- Website Screenshot API: capture pages as PNG, JPEG or PDF.
Support
Store not working? Open an issue on the Issues tab with your input. Published by Altronite.