# WooCommerce Product Feed & Catalog Monitor: Price/Stock Alerts (`dheerajitbhu/woocommerce-catalog-monitor`) Actor

Your catalog changes daily: prices move, stock flips, products appear and vanish. This monitor records a baseline of any WooCommerce store catalog, then diffs the live catalog on every scheduled run and reports exactly what changed: new products, removed products, price changes, stock flips.

- **URL**: https://apify.com/dheerajitbhu/woocommerce-catalog-monitor.md
- **Developed by:** [dheeraj kumar](https://apify.com/dheerajitbhu) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 change detecteds

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

## WooCommerce Catalog Monitor

Track any WooCommerce store's catalog over time: **new products, removed products, price changes, and stock flips** — read from the store's public WooCommerce Store API. No scraping, no browser, no proxies, nothing to break when a site redesigns.

Run it once to record a baseline, then **schedule it** (daily, hourly — your call). Every scheduled run diffs the live catalog against the last snapshot and pushes one row per change. The first run for a store never charges for changes.

### What it monitors

| Change type | Meaning |
|---|---|
| `new` | Product appeared in the catalog |
| `removed` | Product disappeared from the catalog |
| `price_changed` | Price (or currency) changed — old and new values included |
| `stock_changed` | Stock status flipped (e.g. `instock` → `outofstock`) |

Each change row carries the product name, SKU, permalink, prices, stock status, and detection timestamp. Every run also writes a `store-summary` row per store with counts.

### Pricing — pay per event, no subscription

| Event | Price |
|---|---|
| Run started | $0.001 per run |
| Product checked | $0.0002 per product read ($0.20 per 1,000) |
| Change detected | $0.005 per new / removed / price-changed / stock-flipped product |

Typical run: a 1,000-product store with 10 changes costs about **$0.25** ($0.001 run + $0.20 products + $0.05 changes).

Failed stores (no public Store API, private/B2B, network errors) return an error row and are **not charged**. Set **Maximum charge per run** and the actor stops cleanly before exceeding it.

#### Example input

```json
{
  "storeUrls": ["https://your-store.com"],
  "maxProductsPerStore": 1000,
  "outputMode": "changes",
  "stateName": "woo-catalog-monitor",
  "maxChargeUsd": 5
}
```

#### Example output (one row per change)

Prices are in the store currency's minor units (e.g. cents), exactly as the Store API returns them.

```json
{
  "recordType": "change",
  "store": "https://your-store.com",
  "storeUrl": "https://your-store.com",
  "productId": "1234",
  "changeType": "price_changed",
  "name": "Ceramic Mug - 12oz",
  "sku": "MUG-12",
  "price": 1650,
  "regular_price": 1650,
  "sale_price": 1650,
  "oldPrice": 1400,
  "currency": "USD",
  "oldCurrency": "USD",
  "stock_status": "instock",
  "is_in_stock": true,
  "permalink": "https://your-store.com/product/ceramic-mug-12oz",
  "detectedAt": "2026-10-16T09:00:00+00:00"
}
```

### Input

- **Store URLs** — one or more WooCommerce store URLs, e.g. `https://competitor-store.com`.
- **Max products per store** (default 1,000) — caps catalog reads and your per-run cost.
- **Output mode** — `Changes only` (one row per change; best for monitoring) or `Full catalog snapshot` (every product).
- **Snapshot store name** — the named key-value store holding baselines. Keep it constant across scheduled runs; change it to start a fresh baseline.
- **Maximum charge per run (USD)** (default $5) — hard spending cap.

### Requirements and limits

- The store must expose the public WooCommerce Store API (`/wp-json/wc/store/v1/products`). The vast majority of WooCommerce stores do — it's on by default. Private, password-protected, and B2B stores are reported as unsupported, not charged.
- Prices come from the store's own API in its own currency.
- Polite by design: sequential requests, small delays between pages.

### Use it from code

```bash
curl -X POST "https://api.apify.com/v2/acts/dheerajitbhu~woocommerce-catalog-monitor/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"storeUrls": ["https://competitor-store.com"], "outputMode": "changes"}'
```

```python
from apify_client import ApifyClient
client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("dheerajitbhu/woocommerce-catalog-monitor").call(run_input={
    "storeUrls": ["https://competitor-store.com"],
    "outputMode": "changes",
})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    if row.get("recordType") == "change":
        print(row["changeType"], row["name"], row.get("permalink"))
```

Schedule it in Apify with a daily (or hourly) schedule and a fixed snapshot store name — each run then reports only what changed since the last one.

*Independent tool. Not affiliated with or endorsed by WooCommerce / Automattic. Use monitored data in line with each store's terms.*

# Actor input Schema

## `maxChargeUsd` (type: `number`):

Hard spending cap for this run. The actor stops cleanly before exceeding it; everything already processed is kept and charged normally.

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

Catalogs are read newest-first; stops here. Lower it to cap your per-run cost.

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

'Changes only' pushes one row per detected change (best for scheduled monitoring). 'Full catalog snapshot' pushes every product plus the diff.

## `stateName` (type: `string`):

Named key-value store holding each store's last snapshot. Keep the same name across scheduled runs so changes are detected; use a different name to start a fresh baseline.

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

One or more WooCommerce store URLs to monitor (e.g. https://competitor-store.com). The store must expose the public WooCommerce Store API — most do by default. Leave empty to run the built-in demo.

## Actor input object example

```json
{
  "maxChargeUsd": 5,
  "maxProductsPerStore": 1000,
  "outputMode": "changes",
  "stateName": "woo-catalog-monitor",
  "storeUrls": []
}
```

# Actor output Schema

## `results` (type: `string`):

Monitored catalog rows: one per product (full mode), per detected change (changes mode), plus a per-store summary row.

# 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": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("dheerajitbhu/woocommerce-catalog-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": [] }

# Run the Actor and wait for it to finish
run = client.actor("dheerajitbhu/woocommerce-catalog-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": []
}' |
apify call dheerajitbhu/woocommerce-catalog-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dheerajitbhu/woocommerce-catalog-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/WAI6Wq7MrDqFZdyBF/builds/aDhcutc9I003h0cjT/openapi.json