# Shopify Store Monitor - Prices, Stock & New Products (`onepierre/shopify-store-monitor`) Actor

Track any Shopify store: new products, price drops and increases, sales, stock-outs and restocks, and removed products. Scrapes full catalogs from public store data. Schedule it for daily competitor monitoring.

- **URL**: https://apify.com/onepierre/shopify-store-monitor.md
- **Developed by:** [Pierre Clarou](https://apify.com/onepierre) (community)
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 product-results

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 Store Monitor: Prices, Stock & New Products

Track any **Shopify store** and get notified of what changed since the last check: **new products, price drops and increases, sales started or ended, stock-outs, restocks and removed products**.

Point it at your competitors, schedule it daily, and get a clean list of changes. No more scrolling through catalogs by hand.

- ✅ Works on **any Shopify store**, including headless stores (custom sites built on top of Shopify)
- ✅ Monitor a **whole store** or a **single collection** (e.g. `/collections/sale`)
- ✅ Full catalogs: tested on stores with **10,000+ products**
- ✅ Uses public store data only: no login, no browser, fast and cheap

### How it works

1. **First run**: the Actor reads the full catalog and saves it as a baseline.
2. **Every next run**: it compares the catalog with the previous run and reports each change.
3. **Schedule it** (daily, hourly…) in Apify and connect the output to Slack, email, Google Sheets, Make, Zapier or n8n to get alerts.

### Detected changes

| Change | Meaning |
|---|---|
| `NEW_PRODUCT` | Product added to the store |
| `REMOVED_PRODUCT` | Product removed or unpublished |
| `PRICE_DROP` / `PRICE_INCREASE` | Variant price changed (with old price, new price and %) |
| `SALE_STARTED` / `SALE_ENDED` | A compare-at (strikethrough) price appeared or disappeared |
| `SOLD_OUT` / `RESTOCKED` | The whole product went out of or back in stock |
| `VARIANT_OUT_OF_STOCK` / `VARIANT_BACK_IN_STOCK` | A size or color went out of or back in stock |
| `NEW_VARIANT` / `VARIANT_REMOVED` | A size or color was added or removed |

Each product comes with a readable summary such as `Price drop -20% (3 variants), Sale started`.

### Output example

```json
{
  "status": "CHANGED",
  "changeSummary": "Price drop -20%, Sale started",
  "changes": [
    { "type": "PRICE_DROP", "variantId": 4012, "variantTitle": "M", "oldPrice": 50, "newPrice": 40, "changePercent": -20 },
    { "type": "SALE_STARTED", "variantId": 4012, "variantTitle": "M", "price": 40, "compareAtPrice": 50 }
  ],
  "store": "example-store.com",
  "storeName": "Example Store",
  "title": "Running Shoe",
  "url": "https://example-store.com/products/running-shoe",
  "vendor": "Example",
  "productType": "Shoes",
  "currency": "USD",
  "priceMin": 40,
  "priceMax": 40,
  "isOnSale": true,
  "maxDiscountPercent": 20,
  "available": true,
  "variantsCount": 6,
  "variantsAvailable": 5,
  "imageUrl": "https://cdn.shopify.com/...",
  "variants": [{ "id": 4012, "title": "M", "sku": "RS-M", "price": 40, "compareAtPrice": 50, "available": true }]
}
```

The `SUMMARY` record in the key-value store gives per-store totals: products scanned, new, changed and removed products, and counts by change type.

### Input

| Field | Description |
|---|---|
| `storeUrls` | Store URLs (`allbirds.com`) or collection URLs (`https://store.com/collections/sale`). |
| `outputMode` | **Changes only** (default, best for scheduled monitoring) or **Full catalog** (every product with its change status). |
| `includeVariants` | Include every variant with price, compare-at price, SKU and stock status. |
| `maxProductsPerStore` | Limit products per store (0 = whole catalog). |
| `stateStoreName` | Name of the monitor. Use different names to run independent monitors on the same stores. |

> **Tip:** with *Changes only*, the first run saves the baseline and outputs nothing. Use *Full catalog* if you also want the product list on the first run.

### Use cases

- **Competitor price monitoring**: get alerted when a competitor cuts prices or starts a sale.
- **Product research**: see what new products successful stores launch, and when.
- **Stock tracking**: find out when products sell out (a demand signal) or come back.
- **Catalog export**: export the full catalog of any Shopify store to CSV, Excel or JSON.

### Pricing

You pay a small fee per **250 products scanned** (the price follows the store size), plus a fee per product in the output. In *Changes only* mode, you only pay output fees for products that actually changed, so daily monitoring stays cheap. Stores that fail are never charged.

Blocked by a store? Large stores sometimes block shared datacenter IPs. The Actor then automatically retries through residential proxies, at no extra cost to you.

### FAQ

**Which stores are supported?** Any store running on Shopify that exposes its public catalog (the vast majority). If a store can't be read, it is listed in the `FAILED_STORES` record and isn't charged as scanned.

**Are stock quantities available?** Shopify's public data shows whether each variant is in stock, not the exact quantity.

**Is it legal?** The Actor reads only public product data that stores publish for their own storefront, and no personal data. You are responsible for using the data in line with applicable laws and each site's terms.

# Actor input Schema

## `storeUrls` (type: `array`):

Stores to monitor, e.g. 'allbirds.com'. Add a collection URL (https://store.com/collections/mens) to monitor only that collection. Headless stores are handled: if www.brand.com is not the Shopify storefront, brand.com is tried automatically.

## `outputMode` (type: `string`):

'Changes only' outputs new, changed and removed products since the previous run: ideal for scheduled monitoring. The first run saves a baseline and outputs nothing. 'Full catalog' outputs every product, each with its change status.

## `includeVariants` (type: `boolean`):

Include every variant (size, color...) with its price, compare-at price, SKU and stock status.

## `maxProductsPerStore` (type: `integer`):

0 = whole catalog. When limited, removed products are not detected.

## `stateStoreName` (type: `string`):

Name of the key-value store where the previous catalog is saved to detect changes. Use a different name for each independent monitor.

## `proxyConfiguration` (type: `object`):

Apify Proxy is recommended for large or frequent runs.

## `residentialFallback` (type: `boolean`):

Some large stores block shared datacenter IPs. When enabled, a blocked store is automatically retried through Apify residential proxies, at no extra cost to you.

## `maxConcurrency` (type: `integer`):

How many stores are scanned in parallel.

## Actor input object example

```json
{
  "storeUrls": [
    "https://www.allbirds.com/collections/mens",
    "kyliecosmetics.com"
  ],
  "outputMode": "all",
  "includeVariants": true,
  "maxProductsPerStore": 0,
  "stateStoreName": "onepierre-shopify-store-monitor",
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "residentialFallback": true,
  "maxConcurrency": 3
}
```

# Actor output Schema

## `changes` (type: `string`):

No description

## `catalog` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `failedStores` (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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "storeUrls": [
        "https://www.allbirds.com/collections/mens",
        "kyliecosmetics.com"
    ],
    "outputMode": "all",
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("onepierre/shopify-store-monitor").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "storeUrls": [
        "https://www.allbirds.com/collections/mens",
        "kyliecosmetics.com",
    ],
    "outputMode": "all",
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("onepierre/shopify-store-monitor").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 '{
  "storeUrls": [
    "https://www.allbirds.com/collections/mens",
    "kyliecosmetics.com"
  ],
  "outputMode": "all",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call onepierre/shopify-store-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,onepierre/shopify-store-monitor"
        }
    }
}
```

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 <APIFY_API_TOKEN>` 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/Z2ooiH1xDZC6hLWKT/builds/mnt4BEmDDHhTHyLZJ/openapi.json