# Catalog Change Tracker — Shopify & WooCommerce (`rikayushi/catalog-change-tracker-shopify-woocommerce`) Actor

Monitor public Shopify and WooCommerce catalogs and detect new, removed, repriced, or availability-changed items after a safe baseline.

- **URL**: https://apify.com/rikayushi/catalog-change-tracker-shopify-woocommerce.md
- **Developed by:** [Diego Andrés Macedo](https://apify.com/rikayushi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 catalog changes

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

## Catalog Change Tracker — Shopify & WooCommerce

Export a public catalog once, then schedule the same input to receive only useful changes: new items, removals, price changes, compare-at-price changes, and availability changes. Shopify variants and WooCommerce products share one normalized output format.

### Why this Actor

Most catalog scrapers charge for or return the whole catalog every day. This Actor keeps a private snapshot in a named Apify key-value store shared by its runs and emits compact, explainable change rows by default. Complete scans replace the snapshot; capped scans update only the items they actually saw and retain unseen prior state. A truncated or failed crawl never creates false removal alerts.

### Input

```json
{
  "storeUrls": ["https://www.allbirds.com"],
  "platform": "auto",
  "monitorName": "daily-footwear",
  "maxProductsPerStore": 1000,
  "includeBaseline": true,
  "includeUnchanged": false
}
```

Supported public sources:

- Shopify `/products.json`, one normalized row per variant.
- WooCommerce public Store API, one normalized row per product.

No login, cookies, private inventory, CAPTCHA bypass, or hidden Admin API is used. Shopify's public feed exposes availability, not inventory quantity, and usually does not expose currency; unknown fields stay `null`.

### Output

- `catalog_change`: `baseline`, `new`, `updated`, `removed`, or optional `unchanged`.
- `store_error`: a store failed without breaking the rest of the batch.
- `run_summary`: coverage and row counts per store.

Updated rows include `changedFields` and the previous values. Removals are emitted only after a complete catalog fetch. Set a stable `monitorName` and store list before scheduling.

### Positioning and launch price

Recommended Store price: **$0.50 per 1,000 delivered `catalog-change` rows** and **$0.20 per 1,000 `baseline-item` rows**. Unchanged rows, store errors, and summaries have no event charge. This is designed to beat tools that charge $1–$5 per 1,000 full observations when the customer only needs changes. Configure pricing only after cloud cost tests.

The Actor stops delivering rows when the customer's maximum charge is reached. Monitor state advances only for rows already delivered, so unpaid changes are not silently lost.

### Limits

- Public Shopify and WooCommerce endpoints only.
- A store may disable or restrict its public catalog endpoint.
- WooCommerce variations depend on what the public Store API exposes.
- This Actor does not bypass access controls or guarantee that public storefront data is complete.

### Local verification

```sh
npm install
npm test
```

# Changelog

This Actor's version history is a separate document: https://apify.com/rikayushi/catalog-change-tracker-shopify-woocommerce/changelog.md

# Actor input Schema

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

Public Shopify or WooCommerce store homepages. One URL per item.

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

Auto tries Shopify first, then WooCommerce.

## `monitorName` (type: `string`):

Reuse the same name on scheduled runs to compare with the previous complete snapshot.

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

A hard cost and runtime ceiling. Removals are suppressed when this cap truncates a catalog.

## `includeBaseline` (type: `boolean`):

Disable for a silent baseline that only stores state.

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

Usually leave this off so scheduled runs stay compact.

## Actor input object example

```json
{
  "storeUrls": [
    "https://www.allbirds.com"
  ],
  "platform": "auto",
  "monitorName": "my-catalog-monitor",
  "maxProductsPerStore": 1000,
  "includeBaseline": true,
  "includeUnchanged": false
}
```

# Actor output Schema

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

Baseline, new, updated, removed, unchanged, error, and summary records.

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

// Run the Actor and wait for it to finish
const run = await client.actor("rikayushi/catalog-change-tracker-shopify-woocommerce").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"] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rikayushi/catalog-change-tracker-shopify-woocommerce"
        }
    }
}
```

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/qZtHk9eQlMVEDtQcU/builds/7phcL0YMhAZP9PJJM/openapi.json