# Price Drop & Stock Monitor: Shopify & WooCommerce Alerts (`f0rty7even/price-drop-monitor`) Actor

Watch any Shopify or WooCommerce store and get a row for every price drop or increase, sell-out, restock, launch and removal since the last run. Schedule it and pipe changes anywhere. First run builds a free baseline; you only pay per product checked and per real change found.

- **URL**: https://apify.com/f0rty7even/price-drop-monitor.md
- **Developed by:** [Michael Yousrie](https://apify.com/f0rty7even) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Price Drop & Stock Monitor: Shopify & WooCommerce Alerts

Watch any Shopify or WooCommerce store and get a clean row for **everything that changed since your last check**: price drops, price increases, sell-outs, restocks, new products and removed products.

A scraper tells you what a store sells today. This tells you what your competitor *did* overnight: which products they discounted, what they quietly raised, what sold out, and what they just launched. That is the part worth acting on, and the part you cannot see by looking at the store.

Run it on a schedule (hourly, daily, weekly) and pipe the dataset anywhere Apify integrates: Slack, email, Google Sheets, Zapier, Make, or your own webhook.

### What you get

| Field | What it tells you |
| --- | --- |
| `changeType` | `price_drop`, `price_increase`, `out_of_stock`, `back_in_stock`, `new_product` or `removed_product`. Runs with nothing to report emit one free receipt row per store instead: `baseline` (first run), `no_changes` (quiet day) or `not_compared` (hit the cap), each with an `offersChecked` count and a plain-language `note`. |
| `oldPrice` / `newPrice` | The price before and after the change. |
| `priceChangePct` | The move as a percentage, negative for drops. |
| `title` / `variantTitle` | The product, down to the exact variant on Shopify. |
| `available` | Whether the offer is in stock right now. |
| `url` | The product page, ready to open or send. |
| `store` / `platform` | Which store and which platform it runs on. |
| `checkedAt` | When this run checked the store (UTC). |

### Example output

```json
{
  "store": "example-store.com",
  "platform": "shopify",
  "offerKey": "8734712398:45123409821",
  "title": "Trail Runner SWT",
  "variantTitle": "US 10 / Charcoal",
  "url": "https://example-store.com/products/trail-runner-swt",
  "sku": "TR-SWT-10-CHR",
  "currency": "USD",
  "changeType": "price_drop",
  "oldPrice": 145.0,
  "newPrice": 98.0,
  "priceChangePct": -32.41,
  "available": true,
  "checkedAt": "2026-08-12T09:00:00+00:00"
}
```

### What to use it for

#### Competitor price intelligence

Point it at competitor stores and schedule a daily run. Every discount, price rise and stockout lands in one dataset, with percentages, ready for a Slack alert or a pricing meeting. This is the core of what re-pricing SaaS charges hundreds a month for.

#### Restock and drop alerts

Watch a `/collections/sale` URL or a product you resell. `back_in_stock` and `price_drop` rows are exactly the alert, and Apify's integrations turn them into an email or webhook without any code.

#### Catalog change feeds

Agencies and marketplaces: monitor client or supplier stores and get `new_product` and `removed_product` rows as a feed, instead of re-scraping full catalogs and diffing them yourself.

### How it works

- **Shopify** stores are read through the public `products.json` endpoint and monitored **per variant**, because that is where prices actually change. Currency is detected from the storefront.
- **WooCommerce** stores are read through the public Store API and monitored per product, with prices correctly converted from the API's integer minor units.
- The platform is **detected automatically** per store; you can also pin it in the input.
- Each run stores a compact baseline in a key-value store and compares the next run against it. No login, no browser, no API keys.

### Pricing, and what is never charged

You pay one small event per **offer checked** plus one premium event per **change found**. Everything below is free, by design:

- **The first run for a store.** It establishes the baseline; every offer would be trivially "new", which is not an insight, so it is not billed as changes.
- **Stores that cannot be fetched.** Not Shopify or WooCommerce, endpoint blocked, site down: you get an error row, not a bill.
- **Capped runs.** If a store's catalog is larger than `Max products per store`, the fetched slice cannot be honestly compared against the last run (catalog order is not stable), so nothing is compared and nothing is charged for changes. Raise the cap or monitor a collection URL instead.
- **Changes you turned off.** Untracked change types are neither reported nor billed.
- **Unchanged offers.** Even with `Include unchanged offers` on, only real changes bill as changes.
- **Receipt rows.** A store with nothing to report still leaves one `baseline`, `no_changes` or `not_compared` row so you can see the check happened. Receipts are never billed as changes.

### Tips

- **Set a threshold.** `Minimum price change (%)` at 2 to 5 filters out penny jitter. Small moves are remembered, not lost: once a price has drifted past the threshold in total, one change fires against the original price.
- **Scope big Shopify stores** with a `/collections/...` URL. Each collection gets its own baseline.
- **Two schedules, two baselines.** Running hourly and daily over the same stores? Give each schedule its own `Baseline store` name so they do not overwrite each other.

# Actor input Schema

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

Shopify or WooCommerce store URLs, one per line. The platform is detected automatically. For a huge Shopify store, paste a /collections/... URL to monitor just that collection instead of the whole catalog.

## `platform` (type: `string`):

Skip auto-detection when you already know what the stores run. Every store in one run must then be that platform.

## `trackPriceDrops` (type: `boolean`):

A row whenever an offer got cheaper since the last run.

## `trackPriceIncreases` (type: `boolean`):

A row whenever an offer got more expensive since the last run.

## `trackStockChanges` (type: `boolean`):

A row whenever an offer went out of stock or came back in stock since the last run.

## `trackNewProducts` (type: `boolean`):

A row for every offer that appeared in the catalog since the last run.

## `trackRemovedProducts` (type: `boolean`):

A row for every offer that disappeared from the catalog since the last run. These rows carry the last known price rather than fresh data.

## `minPriceChangePct` (type: `integer`):

Ignore price moves smaller than this percentage. Small moves are remembered, not discarded: once a price has drifted past the threshold in total, one change fires with the original price as the old price. 0 reports every change, however small.

## `includeUnchanged` (type: `boolean`):

Also push a row for every offer that did NOT change, so each run doubles as a full catalog snapshot. Unchanged rows are never billed as changes.

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

Hard stop per store. IMPORTANT: a store that hits this cap is fetched partially, and a partial catalog cannot be compared against the last run, so no changes are reported or charged for it. Set it above the store's catalog size, or monitor a collection URL.

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

Name of the key-value store holding each store's baseline between runs. The default is fine. Change it only to keep two schedules from overwriting each other, for example an hourly and a daily run over the same stores.

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

Both platforms throttle datacenter IPs, so Apify Proxy (residential) is on by default and recommended.

## Actor input object example

```json
{
  "storeUrls": [
    "allbirds.com",
    "https://store.example.com/collections/sale",
    "barefootbuttons.com"
  ],
  "platform": "auto",
  "trackPriceDrops": true,
  "trackPriceIncreases": true,
  "trackStockChanges": true,
  "trackNewProducts": true,
  "trackRemovedProducts": true,
  "minPriceChangePct": 0,
  "includeUnchanged": false,
  "maxProductsPerStore": 5000,
  "stateStoreName": "price-monitor-state",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

One row per change. Export as JSON, JSONL, CSV or Excel.

# 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": [
        "allbirds.com"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("f0rty7even/price-drop-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": ["allbirds.com"],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("f0rty7even/price-drop-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": [
    "allbirds.com"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call f0rty7even/price-drop-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,f0rty7even/price-drop-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/berEAh1bVdOMHphrK/builds/2t28quOgdyx2wUxFu/openapi.json