# Shopify & WooCommerce Product Tracker (`descriptive_orbit/store-product-tracker`) Actor

Track competitor Shopify and WooCommerce stores: full catalog with prices, discounts, stock, SKUs and images, plus what changed since the last run (new products, price drops and increases, back in stock, out of stock, removed). Public product feeds only, no login.

- **URL**: https://apify.com/descriptive_orbit/store-product-tracker.md
- **Developed by:** [Orbit Data Tools](https://apify.com/descriptive_orbit) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 product rows

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 & WooCommerce Product Tracker

Give this Actor the URL of any Shopify or WooCommerce store. It returns the store's products with prices, compare-at prices, discounts, stock status, SKUs, brands, categories, images and dates. Run it again (or schedule it) and every row tells you **what changed since the last run**: new products, price drops, price increases, items back in stock, items that sold out, and products that were removed.

It reads the public product feeds that these platforms publish for every storefront (Shopify's `/products.json` and the WooCommerce Store API). There is no login, no browser and no API key, so runs are fast and cheap: a 100-product store takes about 1–2 seconds.

### What you can use it for

- **Competitor price monitoring.** Schedule a daily run on your competitors and get only the rows where a price went up or down, with the old price and the % change.
- **New-arrival alerts.** See every product a store adds, the day it appears (`changeType: "new"`, `firstSeenAt`).
- **Stock-outs and restocks.** Know when a competitor's best seller sells out (`out_of_stock`) or comes back (`back_in_stock`). Turn on variant mode to track stock per size or colour.
- **Discount and sale tracking.** `compareAtPrice` and `discountPct` show what is on sale and how deep the cut is.
- **Catalog export.** Download a full catalog as CSV, Excel, JSON or XML from the dataset, or send it to Google Sheets with Apify's integrations.
- **Product research for dropshipping.** Compare vendors, price ranges and product types across many stores in one table.
- **Feeding AI agents.** Every row has the same fields, with a single `changeType` to filter on, so an agent can call the Actor (through the Apify API or MCP server) and reason over clean JSON.

### How to use it

1. Paste one or more store URLs into **Store or collection URLs**. You can mix Shopify and WooCommerce stores; the platform is detected for each URL.
2. Set **Max products per store** (default 1,000).
3. Start the run. The first run marks every product as `new`, because there is nothing to compare with yet.
4. Run it again later, or create a schedule. From now on each row says what changed.

Accepted URL types:

| URL | What is read |
|---|---|
| `https://www.allbirds.com` | The whole Shopify or WooCommerce catalog |
| `https://store.com/collections/sale` | One Shopify collection |
| `https://store.com/product-category/shoes/` | One WooCommerce category |

### How change tracking works

After each run the Actor saves a small snapshot of every store (price, stock, title, URL and a few other fields per product) in a named key-value store in your Apify account, `store-product-tracker-state` by default. The next run compares the live catalog with that snapshot and sets `changeType` on each row:

| changeType | Meaning |
|---|---|
| `new` | Not in the previous snapshot (always the case on the first run) |
| `price_drop` | Price is lower than last time. `previousPrice` and `priceChangePct` show by how much |
| `price_increase` | Price is higher than last time |
| `back_in_stock` | Was unavailable last time, available now |
| `out_of_stock` | Was available last time, unavailable now |
| `removed` | Was in the previous snapshot and is gone from the store now |
| `unchanged` | Same price and same stock status |
| `error` | The store could not be read. The `error` field explains why. Error rows are free |

When a product has more than one change (for example it is back in stock at a higher price), `changeType` shows the stock change and the `changes` array lists all of them: `["back_in_stock", "price_increase"]`.

Turn on **Output only changes** to drop the `unchanged` rows. On a scheduled run that usually leaves a handful of rows, and you only pay for those.

Some details worth knowing:

- Product mode and variant mode keep separate snapshots, so you can run both on the same store.
- `removed` is only reported when the run read the whole catalog or collection. If a store has more products than **Max products per store**, the Actor cannot tell a removed product from one that is beyond the limit, so it skips removal checks for that store (the run log says so). Set the limit above the store's size if you need removals.
- If a run stops early because it reached your maximum charge, that store's snapshot is not updated, so the next run reports the same changes again instead of losing them.
- To start a fresh baseline, change **Snapshot store name**, or delete the store's record from the `store-product-tracker-state` key-value store in Apify Console.

### Input example

```json
{
    "startUrls": [
        { "url": "https://www.allbirds.com" },
        { "url": "https://www.taylorstitch.com/collections/mens-shirts" },
        { "url": "https://barefootbuttons.com" }
    ],
    "maxProductsPerStore": 1000,
    "includeVariants": false,
    "trackChanges": true,
    "onlyChanges": true
}
```

| Field | Default | Description |
|---|---|---|
| `startUrls` | (required) | Store, Shopify collection or WooCommerce category URLs |
| `maxProductsPerStore` | 1000 | Product limit per URL |
| `includeVariants` | false | One row per variant (size, colour) instead of one row per product |
| `trackChanges` | true | Save a snapshot and compare with the previous run |
| `onlyChanges` | false | Output only rows whose `changeType` is not `unchanged` |
| `stateStoreName` | `store-product-tracker-state` | Key-value store that holds the snapshots |
| `proxyConfiguration` | no proxy | Only needed if a store blocks requests |

### Output example

Real rows from a test run. The first is a Shopify product on sale. The second came from a second run on a WooCommerce store after a price change (to test the tracking, the saved snapshot was edited to an older price before that run). `tags` is shortened here.

```json
[
  {
    "platform": "shopify",
    "storeUrl": "https://www.allbirds.com",
    "sourceUrl": "https://www.allbirds.com",
    "productId": "7340901859408",
    "variantId": null,
    "title": "Women's Allbirds Flip Flop - Dusty Pink",
    "variantTitle": null,
    "handle": "womens-allbirds-flip-flop-dusty-pink",
    "url": "https://www.allbirds.com/products/womens-allbirds-flip-flop-dusty-pink",
    "vendor": "Allbirds",
    "productType": "Shoes",
    "categories": ["Shoes"],
    "tags": ["allbirds::edition => limited", "allbirds::gender => womens"],
    "sku": null,
    "price": 25.0,
    "maxPrice": 25.0,
    "compareAtPrice": 50.0,
    "discountPct": 50.0,
    "currency": "USD",
    "available": true,
    "variantCount": 7,
    "image": "https://cdn.shopify.com/s/files/1/1104/4168/files/A12513_26Q2_Allbirds-Flip-Flop-Dusty-Pink_PDP_LEFT.png?v=1774646345",
    "createdAt": "2026-03-27T14:03:50-07:00",
    "updatedAt": "2026-10-21T07:37:30-07:00",
    "publishedAt": "2026-09-25T16:58:13-07:00",
    "changeType": "new",
    "changes": ["new"],
    "previousPrice": null,
    "priceChangePct": null,
    "previousAvailable": null,
    "firstSeenAt": "2026-10-21T14:37:31Z",
    "scrapedAt": "2026-10-21T14:37:31Z",
    "error": null
  },
  {
    "platform": "woocommerce",
    "storeUrl": "https://barefootbuttons.com",
    "sourceUrl": "https://barefootbuttons.com",
    "productId": "1298",
    "variantId": null,
    "title": "Spacers- Pack of 4",
    "variantTitle": null,
    "handle": "spacers-pack-of-4",
    "url": "https://barefootbuttons.com/product/spacers-pack-of-4/",
    "vendor": null,
    "productType": "Accessories",
    "categories": ["Accessories"],
    "tags": [],
    "sku": "18-AC-NS-01",
    "price": 1.95,
    "maxPrice": 1.95,
    "compareAtPrice": null,
    "discountPct": null,
    "currency": "USD",
    "available": true,
    "variantCount": 1,
    "image": "https://barefootbuttons.com/wp-content/uploads/2026/04/spcaer-2.png",
    "createdAt": null,
    "updatedAt": null,
    "publishedAt": null,
    "changeType": "price_drop",
    "changes": ["price_drop"],
    "previousPrice": 3.95,
    "priceChangePct": -50.63,
    "previousAvailable": true,
    "firstSeenAt": "2026-10-21T14:37:33Z",
    "scrapedAt": "2026-10-21T14:38:26Z",
    "error": null
  }
]
```

#### Output fields

| Field | Description |
|---|---|
| `platform` | `shopify` or `woocommerce` |
| `storeUrl`, `sourceUrl` | The store's address, and the URL you entered |
| `productId`, `variantId` | Platform IDs as strings (`variantId` is filled in variant mode) |
| `title`, `variantTitle`, `handle`, `url` | Product name, variant name (e.g. "Size: L"), URL slug and product link |
| `vendor` | Brand or vendor (WooCommerce: product brands, when the store uses them) |
| `productType`, `categories`, `tags` | Shopify product type, or WooCommerce categories; tags |
| `sku` | SKU (in product mode only when the product has one variant) |
| `price`, `maxPrice` | Lowest and highest price across variants (equal in variant mode) |
| `compareAtPrice`, `discountPct` | Original price when on sale, and the discount in % |
| `currency` | Store currency (WooCommerce from the API; Shopify from the store's settings) |
| `available` | `true` if it can be bought (in product mode: any variant in stock) |
| `variantCount`, `image` | Number of variants and main image URL |
| `createdAt`, `updatedAt`, `publishedAt` | Shopify timestamps (WooCommerce's public API does not expose them) |
| `changeType`, `changes` | Main change and the list of all changes since the last run |
| `previousPrice`, `priceChangePct`, `previousAvailable` | Values from the previous run |
| `firstSeenAt`, `scrapedAt` | When the Actor first saw this product, and when this row was read |
| `error` | Only filled on error rows |

The run's default key-value store also gets an `OUTPUT` record with a per-store summary: platform, product count, rows saved, change counts, whether the full catalog was read, and timing.

### Pricing

This Actor uses pay-per-event pricing: **you pay per product row saved to the dataset**, plus a small fee per run start. Error rows are free. Apify platform usage is included in the event price.

See the price per row on the Pricing tab. As a worked example, assuming $0.80 per 1,000 rows:

- **One-off catalog export** of a 2,500-product store: 2,500 rows, about $2.00.
- **Daily monitoring of 5 competitors** with about 800 products each, with **Output only changes** on:
  - First run: 4,000 `new` rows, about $3.20.
  - Each day after that: if 2% of products change price or stock, that's about 80 rows a day, $0.064 a day, or about $1.90 a month.
- The same monitoring with Output only changes off would save all 4,000 rows every day (about $96 a month), so turn it on for schedules.

You can cap any run with Apify's "Maximum cost per run" setting. When the cap is reached, the Actor stops cleanly, keeps what it has saved, and leaves the snapshot untouched so the next run picks up the same changes.

### Scheduling tip

Create a task with your store list and **Output only changes** on, then add a schedule (for example daily at 06:00). Add a webhook, or the Slack, email, Zapier or Make integration, to get the changed rows as soon as each run finishes. Keep the same task and the same **Snapshot store name** so each run compares with the one before it.

### FAQ

**Can an AI agent use it?** Yes. Add this Actor to Apify's MCP server (mcp.apify.com) and it becomes a tool for Claude, Cursor and other MCP clients. An agent can then ask for a store's price drops or new products and get clean JSON rows back. You can also call it from code with the Apify API or any Apify client.

**Do I need a Shopify or WooCommerce account or API key?**
No. The Actor reads the same public product data that the store's own website loads.

**Why did a store return an error row?**
The error text says what happened. Common causes: the site is not on Shopify or WooCommerce; a Shopify store uses a custom headless front end that does not serve `/products.json` (some large brands return HTTP 403); the store is password-protected; the WooCommerce Store API is disabled; or the site blocks datacenter IP addresses. For the last case, try the proxy setting with Apify Proxy's residential group. The other stores in the run are not affected.

**Why are `createdAt` and `updatedAt` empty for WooCommerce stores?**
WooCommerce's public Store API does not include those dates. `firstSeenAt` tells you when the Actor first saw each product.

**Which currency are Shopify prices in?**
The store's main currency, read from the store itself. Stores that sell in several currencies may show local prices to visitors; this Actor reports the base prices from the product feed.

**How fast is it?**
It sends about one request per second to each store, to stay polite, and reads up to 5 stores at the same time. Shopify returns 250 products per request and WooCommerce 100, so a 1,000-product Shopify store takes about 5 seconds.

**Will it report a product as new just because it moved into the first 1,000?**
It can, when a store has more products than your limit and the order of its feed changes. For exact new/removed reporting, set **Max products per store** above the store's size, or track a single collection or category.

**Can I track the same store in product mode and variant mode?**
Yes. Each mode keeps its own snapshot.

### Public data only

The Actor reads public catalog data that stores publish for their own websites: product names, prices, stock status and images. It does not log in, it does not collect personal data (no customer, reviewer or staff information), and it limits itself to about one request per second per store. You are responsible for using the data in line with each website's terms and the laws that apply to you.

# Actor input Schema

## `startUrls` (type: `array`):

Shopify or WooCommerce store home pages (e.g. https://www.allbirds.com), Shopify collection pages (https://store.com/collections/sale) or WooCommerce category pages (https://store.com/product-category/shoes/). The platform is detected automatically. A URL that is neither platform produces one error row and the run carries on with the other stores.

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

Stop after this many products per URL. With variants on, all variants of these products are returned. Products that are removed from a store are only detected when the whole catalog fits under this limit.

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

Off: one row per product with the lowest price (price) and highest price (maxPrice), and available = true if any variant is in stock. On: one row per variant (size, colour...) with its own price, SKU and stock. Variant mode keeps a separate change-tracking snapshot.

## `trackChanges` (type: `boolean`):

Saves a snapshot of each store after the run in a named key-value store, so the next run can mark every row as new, price_drop, price_increase, back_in_stock, out_of_stock, removed or unchanged, with previousPrice and priceChangePct. The first run for a store marks everything as new.

## `onlyChanges` (type: `boolean`):

Only output rows whose changeType is not unchanged, so you pay only for new products, price changes, stock changes and removals. Ideal for scheduled monitoring. Needs change tracking (it is switched on automatically).

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

Name of the key-value store that keeps the snapshots between runs. Use a different name to run separate monitors of the same store, or to start a fresh baseline.

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

Usually not needed: Shopify and WooCommerce product feeds are public. If a store blocks requests (HTTP 403 or 429 in the error row), try Apify Proxy, residential group.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.allbirds.com"
    },
    {
      "url": "https://barefootbuttons.com"
    }
  ],
  "maxProductsPerStore": 100,
  "includeVariants": false,
  "trackChanges": true,
  "onlyChanges": false,
  "stateStoreName": "store-product-tracker-state",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One row per product with what changed since the previous run (price, stock, new, removed).

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

Totals per store and per change type for this run.

# 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 = {
    "startUrls": [
        {
            "url": "https://www.allbirds.com"
        },
        {
            "url": "https://barefootbuttons.com"
        }
    ],
    "maxProductsPerStore": 100,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("descriptive_orbit/store-product-tracker").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 = {
    "startUrls": [
        { "url": "https://www.allbirds.com" },
        { "url": "https://barefootbuttons.com" },
    ],
    "maxProductsPerStore": 100,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("descriptive_orbit/store-product-tracker").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.allbirds.com"
    },
    {
      "url": "https://barefootbuttons.com"
    }
  ],
  "maxProductsPerStore": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call descriptive_orbit/store-product-tracker --silent --output-dataset

```

## MCP server setup

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

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/1q8Fqk3yYkkgrhN5r/builds/GDjZTmtMKCh6VXVV5/openapi.json