# Shopify Products Scraper + Change Tracker ($0.9/1k) (`rikkadawufa/shopify-products-scraper`) Actor Scrape every product from any Shopify store (prices, variants, stock, images) and see what changed since the last run: new products, price drops, stock changes and removed products. - **URL**: https://apify.com/rikkadawufa/shopify-products-scraper.md - **Developed by:** [Rikka Dawu](https://apify.com/rikkadawufa) (community) - **Security:** Limited permissions - **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.90 / 1,000 products This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Shopify Products Scraper + Change Tracker Get every product from any Shopify store: titles, prices, compare-at prices, variants, SKUs, stock, images, tags and vendor. Run it again later and each product is marked with what changed since the last run: new products, price changes, stock changes, removed products and products that came back. You don't need a login, an API key or access to the store. The Actor reads the public product feed that every Shopify storefront serves. ### What you get - The whole catalog of one or many stores in one dataset, ready for CSV, Excel, JSON or the API. - A change status on every product: `new`, `changed` (with the old and new price, compare-at price or stock status per variant), `removed` (with the reason), `reappeared` or `unchanged`. - A completeness check for each store, which compares the number of products found with the number in the store's own product sitemap. If a run missed something, you'll see it. - A one-page HTML report and a CSV of changes for each run. A product that disappears from the feed is loaded on its own page before anything is reported. It's marked removed only when the store answers 404 or 410, or redirects to a page that isn't a product. If any page of the store failed to load, the run marks nothing as removed. ### Use cases - Watch competitors' prices and get a list of every price drop each morning. - See new launches and discontinued products in a store you track. - Restock alerts: variants that go from out of stock to in stock. - Export a full catalog for analysis, migration or a product feed. ### Input | Field | What it does | | --- | --- | | Shopify store URLs | Any page of each store. Only the domain is used. | | Track changes since the last run | On by default. The first run of a store saves a baseline. Later runs compare against it. | | Output | **All products**, or **Only changed products** (best for scheduled monitoring). | | Tracking name | Optional. Use different names to track the same store on two separate schedules. | | Max products per store | 0 means no limit. With a limit, the run doesn't see the whole store, so removed products aren't detected, and products it hasn't seen before are marked `baseline` instead of `new`. | | Include variants | Adds each variant's title, SKU, options, price, compare-at price and stock. | | Proxy | Optional. Most stores work without one. Turn it on if a store keeps rate-limiting your runs. | ```json { "startUrls": [{ "url": "https://example-store.com" }], "trackChanges": true, "outputMode": "all" } ``` ### Output One item per product. This one had a price drop on one variant since the last run: ```json { "store": "example-store.com", "id": 7012345678901, "handle": "classic-hoodie", "title": "Classic Hoodie", "url": "https://example-store.com/products/classic-hoodie", "vendor": "Example Store", "productType": "Hoodies", "tags": ["fall", "unisex"], "minPrice": 49.0, "maxPrice": 59.0, "currency": "USD", "available": true, "variantCount": 2, "image": "https://cdn.shopify.com/s/files/.../hoodie.jpg", "images": ["https://cdn.shopify.com/s/files/.../hoodie.jpg"], "createdAt": "2025-09-01T10:00:00-04:00", "updatedAt": "2026-11-02T08:15:00-05:00", "publishedAt": "2025-09-01T10:05:00-04:00", "variants": [ { "id": 41234567890001, "title": "M", "sku": "HD-M", "price": 49.0, "compareAtPrice": 59.0, "available": true, "options": ["M"], "grams": 600 }, { "id": 41234567890002, "title": "L", "sku": "HD-L", "price": 59.0, "compareAtPrice": null, "available": false, "options": ["L"], "grams": 650 } ], "changeStatus": "changed", "changes": [ { "type": "price_changed", "variantId": "41234567890001", "variantTitle": "M", "old": "59.00", "new": "49.00" }, { "type": "compare_at_price_changed", "variantId": "41234567890001", "variantTitle": "M", "old": null, "new": "59.00" } ], "removedReason": null, "firstSeen": "2026-10-20T07:00:04+00:00", "lastSeen": "2026-11-02T07:00:03+00:00" } ``` `changeStatus` is one of `baseline` (seen for the first time while the history was still incomplete, for example on the first run of a store), `new`, `changed`, `unchanged`, `removed` or `reappeared`. A `changes` entry has a `type` of `price_changed`, `compare_at_price_changed`, `stock_status`, `variant_added` or `variant_removed`. A removed product keeps its last known data and gets a `removedReason` such as `HTTP 404`. Each run also saves these files in its key-value store: - `REPORT`: an HTML page with each store's completeness check, the change counts, failed pages and a table of changes. - `CHANGES`: a CSV with one row per change. - `SUMMARY`: the same numbers as JSON. ### How change tracking works The Actor keeps a history for each store in a named key-value store, `shopify-products-state`, in your own Apify account. Each run compares the store with that history and then updates it. To monitor a store, schedule the Actor (for example daily) with **Output: Only changed products**. The first run saves the baseline and returns nothing. From then on, each run returns only the products that changed. Connect the run to email, Slack, Google Sheets or a webhook through Apify's integrations. If a run can't read a store completely (a page failed, or a product limit is set), the products it misses aren't reported as new later. The first time a product shows up after an incomplete baseline, it's marked `baseline`. Once a run has read the whole store, products that appear after that are marked `new`. ### Pricing You pay per event: - $0.90 per 1,000 products in the dataset. - $0.002 per changed product (new, changed, removed or reappeared). Unchanged products and first-run baselines are never charged as changes. For example, a daily check of a 2,000-product store with 30 changes a day in **Only changed products** mode costs 30 × ($0.0009 + $0.002), about $0.09 a day. The same store with **All products** costs about $1.86 a run. Apify also charges its standard small fee for each run start. Set a maximum cost per run in the run options. The run never goes over it. When it reaches the limit, it stops cleanly and saves the history only for the products it delivered. The products it didn't deliver, and the stores it didn't reach, keep their old history, so the next run reports their changes. You aren't charged twice for anything. ### Use it from code, n8n or Make Call the Actor through the [Apify API](https://docs.apify.com/api/v2), the Apify n8n node or the Apify Make module, then read the dataset items. In the API, `outputMode: "changesOnly"` gives you a short list that fits straight into an alert. ### Limits - Works with stores that serve the public Shopify product feed (`/products.json`). Password-protected stores and stores that turned the feed off are reported as errors and skipped. The other stores in the run still finish. - Shopify limits how fast one IP address can read a store. When a store answers 429 or 430, the Actor waits 20 s, then 40 s, then 80 s before trying again, and reads the rest of that store more slowly. It stops waiting after about 5 minutes per store. If the store still refuses, the status message says the store rate-limited the run. Run again later, or turn on a proxy. Pages that fail after the first one are listed in the report, and the store is marked incomplete. For stores with tens of thousands of products, give the run at least 2 GB of memory. - Only products published to the online store are in the feed. Draft and hidden products aren't. - `currency` comes from the store's `meta.json` and is the store's default currency. The prices are in that currency. - The feed has no inventory counts, only in stock or out of stock per variant. ### FAQ **Do I need access to the store?** No. It only reads what any visitor's browser can load. **Does it work on any Shopify store?** On any store that serves the public product feed, which is most of them. The run report says when a store doesn't. **Can I track the same store for two different purposes?** Yes. Give each schedule its own **Tracking name**. **How do I reset the history?** Delete the store's record in the `shopify-products-state` key-value store in your Storage tab, or use a new tracking name. ### Feedback Found a store that doesn't work, or need another field? Open an issue in the Issues tab with the store URL and the run ID. # Actor input Schema ## `startUrls` (type: `array`): Any page of each Shopify store, for example its home page. Only the domain is used. ## `trackChanges` (type: `boolean`): Compare each store with what the previous run saw and mark new, changed, removed and reappeared products. The first run of a store saves a baseline. ## `outputMode` (type: `string`): All products, or only the products that changed since the last run (for monitoring on a schedule). ## `stateKey` (type: `string`): Optional. Runs with the same store and the same tracking name share one change history. Use different names to track the same store on two separate schedules. ## `maxProductsPerStore` (type: `integer`): 0 means no limit. With a limit set, the run doesn't see the whole store: removed products are not detected, and products not seen before are marked baseline instead of new. ## `includeVariants` (type: `boolean`): Add each product's variants (size, color, SKU, price, stock) to the output. ## `proxyConfiguration` (type: `object`): Optional. Most stores work without a proxy. ## Actor input object example ```json { "startUrls": [ { "url": "https://www.deathwishcoffee.com" } ], "trackChanges": true, "outputMode": "all", "maxProductsPerStore": 0, "includeVariants": true, "proxyConfiguration": { "useApifyProxy": false } } ``` # Actor output Schema ## `products` (type: `string`): No description ## `report` (type: `string`): No description ## `changes` (type: `string`): No description ## `summary` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://www.deathwishcoffee.com" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("rikkadawufa/shopify-products-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [{ "url": "https://www.deathwishcoffee.com" }] } # Run the Actor and wait for it to finish run = client.actor("rikkadawufa/shopify-products-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://www.deathwishcoffee.com" } ] }' | apify call rikkadawufa/shopify-products-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,rikkadawufa/shopify-products-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/aCChinbNWdxA2QRAx/builds/farHg6nkczvdx1grF/openapi.json