Shopify Catalog & Price Monitor

Scrape public Shopify product catalogs and optionally monitor stores for new products, price changes, restocks, sell-outs, and removed products.

This Actor is built for predictable output. In normal catalog mode, the number entered in Max products per store is the maximum number of product rows written to the dataset for each store.

What You Get

• Product title, handle, URL, vendor, type, tags, images, and publish dates
• Variant IDs, titles, SKUs, prices, compare-at prices, and availability
• Product-level minimum and maximum prices
• Product-level availability and sale status
• Optional change monitoring between runs

Quick Start

1. Enter one or more Shopify store domains, for example deathwishcoffee.com.
2. Set Max products per store to the number of product rows you want.
3. Leave Monitor changes since last run off for a one-time catalog scrape.
4. Turn Monitor changes since last run on for scheduled tracking.
5. Keep Output only the changes off unless you want change events instead of product rows.

Result Limits And Billing

Apify charges for dataset results based on rows written to the dataset. This Actor keeps that simple:

• If Max products per store is 20, normal output writes up to 20 product rows per store.
• Turning on Monitor changes since last run does not double the normal dataset output.
• Monitoring snapshots and latest change details are saved in a named key-value store so scheduled runs can compare against previous runs.
• Change rows are written to the dataset only when Output only the changes is enabled.

Recommended setup for most monitoring users:

• Monitor changes since last run: on
• Output only the changes: off
• Max products per store: the number of product rows the user wants

With that setup, the user receives the latest product catalog while the Actor quietly keeps monitoring state in storage.

Monitoring Logic

When monitoring is enabled, the Actor:

1. Fetches the current Shopify catalog.
2. Applies the selected product limit.
3. Compares the current products with the previous snapshot for that store.
4. Saves the new snapshot to a named key-value store.
5. Saves latest detected changes to a key such as changes-example.com.
6. Outputs either product rows or change rows, depending on Output only the changes.

Detected change types:

• new_product
• removed_product
• price_change
• restock
• out_of_stock

Input Options

Shopify Store Domains

One or more Shopify store domains or URLs. Both example.com and https://example.com are accepted.

Max Products Per Store

Maximum number of products to fetch and output per store in normal catalog mode. Use 0 to fetch the full public catalog.

Monitor Changes Since Last Run

Compares the current run with the previous saved snapshot for each store. This is most useful when running the Actor on a schedule.

Output Only The Changes

Outputs change events instead of product rows. Use this when you want the dataset to contain only detected changes.

Proxy Configuration

Most public Shopify stores work without a proxy. If a store blocks datacenter requests with HTTP 403 or 429, enable Apify Proxy with a residential proxy group.

Output

Normal output rows are product rows. Each row includes product metadata, prices, availability, and variants.

When Output only the changes is enabled, output rows are change events. Change events include the store, change type, product ID, and the relevant price or availability information when available.

Storage

The Actor uses the named key-value store shopify-catalog-price-monitor-state for monitoring state:

• snapshot-<store> stores the latest product snapshot for comparison.
• changes-<store> stores the latest detected changes for that store.

Notes

• The Actor uses Shopify public catalog endpoints where available.
• Password-protected, custom headless, Hydrogen, or heavily protected storefronts may not expose a public catalog endpoint.
• For scheduled monitoring, keep the same store domain format between runs so snapshots match cleanly.