Shopify Competitor Price & Restock Monitor

Know the morning a competitor cuts a price. This Shopify price tracker watches the rival stores you list and returns only what changed since the last run: price cuts with old price, new price and percent, restocks, sell-outs and new product launches, down to the variant and its SKU. It reads the public catalog Shopify serves on every storefront, so there is no login and no proxy setup.

Who uses this Shopify competitor price tracker

• DTC brands: get pinged when a competitor cuts prices, launches a product, or sells out of a bestseller.
• Pricing teams: feed price_change events straight into repricing rules via the Apify API or integrations.
• Dropshippers & resellers: catch restocks of high-demand items the hour they happen.
• Market analysts: track launch cadence and assortment moves across a niche.

Data you get on every change

Each dataset item carries type (price_change, restock, out_of_stock, new_product), store, product title, sku, productUrl, previousPrice, newPrice, changePercent and detectedAt. A SUMMARY record closes every run with per-store counts.

• Diff, not dump: the first run snapshots each store's catalog; every following run outputs only changes.
• Multi-store: watch up to 20 competitor stores per run — one scheduled task covers your whole competitive set.
• Resilient: a store that fails to fetch is reported as store_error and keeps its baseline; pagination caps never cause false "new product" alerts.

Input / Output example

Input:

{
  "storeUrls": ["https://shop.gymshark.com", "https://competitor2.com"],
  "maxProductsPerStore": 250
}

Output — one dataset item per change:

{
  "type": "price_change",
  "store": "https://competitor2.com",
  "title": "Sneaker Classique — 42",
  "sku": "SNK-42",
  "productUrl": "https://competitor2.com/products/sneaker-classique",
  "previousPrice": "89.00",
  "newPrice": "79.00",
  "changePercent": -11.24,
  "detectedAt": "2026-07-06T09:00:00.000Z"
}

The first run pushes one baseline item per store (products tracked count). Every later run pushes only changes. A SUMMARY record reports per-run counts.

How to run it as a daily price monitor

Create an Apify schedule with the same input and run it once a day. Run 1 saves a baseline per store; from run 2 on, an empty dataset means nothing moved and every item is a real change. Keep one monitorId per competitive set so baselines never mix.

Pricing

Pay per event: a small fee per change detected. No underlying scraper costs — the Actor reads Shopify's public catalog JSON directly, so a daily monitor of 5 stores costs cents per month in platform usage plus the per-result fee only when something actually changes.

FAQ

Which stores does this work on? Any Shopify storefront that exposes the standard public /products.json catalog (the default for Shopify stores). If a store has disabled it, you get a clear store_error item instead of silent gaps.

Why did my first run return almost nothing? By design: the first run saves the baseline and outputs one summary item per store. Changes start from the second run.

How is stock detected? From the available flag on each variant in the public catalog. If a store's catalog does not expose availability, stock alerts are skipped for it (prices and new products still work).

Can I track more than 250 products per store? Yes, raise maxProductsPerStore up to 1000. Products beyond the cap are ignored consistently and never generate false alerts.

Is this legal? The Actor reads a public, unauthenticated catalog endpoint that Shopify serves for every storefront, and collects no personal data. You are responsible for how you use the data.

This is an unofficial tool and is not affiliated with, endorsed by, or sponsored by Shopify.