# Shopify Price Change Monitor (`zinin/shopify-price-change-monitor`) Actor

Watch a list of Shopify stores and get alerted when their price range, catalog size, or estimated revenue band shifts since your last check — competitor price-positioning monitoring, not per-SKU tracking. Unofficial, independent tool — not affiliated with, endorsed by, or sponsored by Shopify.

- **URL**: https://apify.com/zinin/shopify-price-change-monitor.md
- **Developed by:** [Tim Zinin](https://apify.com/zinin) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.50 / 1,000 change founds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Shopify Price Change Monitor

Watch a list of Shopify stores and get alerted when their price range, catalog size,
or estimated revenue band shifts since your last check — competitor price-positioning
monitoring at the store level, not per-SKU tracking. Runs on our own live Shopify
store-intelligence engine under the hood.

### What you get

- A named "watch" (a list of store URLs) that remembers each store's last-seen price
  range, catalog size, and revenue band.
- Every scheduled run reports ONLY what changed — a store newly added to the watch, or
  an already-tracked store's price range / product count / revenue band shifting.
- Add or drop stores from your watch at any time — a new store gets its own "just
  started tracking this one" moment, and a dropped store gets an honest (free) notice,
  never billed.
- Runs on Apify: schedule it, monitor it, call it from the API, export to
  JSON/CSV/Excel or push straight into your own pipeline.

### How to run it

1. Click **Try for free** — no card needed on the free plan.
2. Paste the store URLs you want watched into **Websites**, optionally a name for this
   watch.
3. Hit **Start**. Schedule it to run again (daily or weekly) to get a stream of only
   the CHANGES each time.

### Pricing

Pay-per-event: **$0.005 per run start + $0.01 per new/changed store /
first-time tracked**. A store DROPPED from your watch list is reported for visibility
but never charged — it's your own choice to stop tracking it, not new information about
the store. The "no changes" notice on a quiet run and any error/notice row are also
never charged. 10 new/changed stores cost about $0.11 (the one-time start fee plus 10 billed rows).

### Input

| Field | Required | What it does |
|---|---|---|
| `websites` | yes | Store URLs to watch, e.g. `"allbirds.com"`. Up to 100. |
| `baseline_key` | no | Name for this watch, so you can run several independent watches. |
| `max_items` | no | Max new/changed-store rows delivered (and charged) per run (1-200, default 20). |

```json
{
    "websites": ["allbirds.com", "gymshark.com"],
    "baseline_key": "dtc-competitors"
}
```

### Output

New-store row (real output, live run 30.07.2026):

```json
{
    "baselineKey": "selftest-shopify-1",
    "found": true,
    "changeType": "new-store",
    "url": "https://www.allbirds.com/",
    "isShopify": true,
    "priceMin": 3,
    "priceMax": 160,
    "currency": "USD",
    "productCount": 750,
    "revenueBand": "$10M+",
    "error": "",
    "summary": "\"https://www.allbirds.com/\" added to watch \"selftest-shopify-1\" — Shopify store, 750 product(s), price range USD3–160."
}
```

Changed-store row (real output, live run 30.07.2026 — reflects a real detected shift
back to the store's true price range after a synthetic test mutation):

```json
{
    "baselineKey": "selftest-shopify-1",
    "found": true,
    "changeType": "changed-store",
    "url": "https://www.allbirds.com/",
    "isShopify": true,
    "priceMin": 3,
    "priceMax": 160,
    "currency": "USD",
    "productCount": 750,
    "revenueBand": "$10M+",
    "error": "",
    "summary": "\"https://www.allbirds.com/\" changed for watch \"selftest-shopify-1\": priceMax 99999 -> 160."
}
```

| Field | Meaning |
|---|---|
| `baselineKey` | Which watch this row belongs to. |
| `found` | `true` for a real result row (new or changed store); `false` for a notice/error row. |
| `changeType` | `"new-store"`, `"changed-store"`, or `null` for a notice row. |
| `url`, `isShopify`, `priceMin`, `priceMax`, `currency`, `productCount`, `revenueBand` | The store's own tracked fields. |
| `error` | Empty string when the check completed cleanly (including "nothing changed" and "a store was dropped"); non-empty only on a real problem. |
| `summary` | Human-readable one-liner. |

### Other tools we built

#### Related tools

Related tools for adjacent workflows in e-commerce.

| Actor | What it does |
|---|---|
| [Zid Store Products Scraper](https://apify.com/zinin/zid-store-products) | Pair it in the e-commerce workflow: Pull live product catalogs (name, price, sale price, category, image) straight from Zid storefronts — a... |
| [Chotot Vietnam Listings Scraper](https://apify.com/zinin/chotot-listings) | Pair it in the e-commerce workflow: Pull live classified ad listings (real estate, vehicles, electronics, jobs and more) straight from... |
| [Shopify Store Intelligence](https://apify.com/zinin/shopify-store-intelligence) | Pair it in the e-commerce workflow: Confirm a site runs on Shopify and pull store intelligence from its public feeds — product count, price... |

### FAQ / Limitations

**Does this track individual product prices?** No — this tracks store-level signals
(price RANGE across the catalog, product count, a rough revenue band), not per-SKU
price history. If you need per-product tracking, this is not that tool.

**What happens if I change my `websites` list?** A newly added store gets its own
"first time tracked" moment; a removed store gets an honest, free notice and stops
being compared going forward.

**What this is NOT.** The revenue band is a rough heuristic from catalog size and
average price, not real sales data — Shopify's public keyless feeds don't expose
actual revenue. Treat it as a qualification signal, not a forecast.

Found a bug or need per-SKU tracking? Issues on the Actor's page.

# Actor input Schema

## `websites` (type: `array`):

Shopify (or possibly-Shopify) store URLs to watch, e.g. "allbirds.com". Every scheduled run re-checks these same sites and reports ONLY what changed since a previous run of this watch: a store newly added to the watch, or an already-tracked store's price range / catalog size / estimated revenue band shifting.

## `baseline_key` (type: `string`):

A name for THIS watch, so you can run several independent store watches from one Actor (e.g. "dtc-competitors", "my-portfolio") without one overwriting another's memory of what's already been seen. Each name is scoped to YOUR OWN Apify account. The prefilled value is only there so this Actor's own daily test run has a stable, obviously-a-test name; replace it with your own watch name.

## `max_items` (type: `integer`):

Caps how many new-store / changed-store rows a single run will deliver and charge for, even if more were found.

## Actor input object example

```json
{
  "websites": [
    "allbirds.com"
  ],
  "baseline_key": "apify-daily-test",
  "max_items": 20
}
```

# Actor output Schema

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

API URL for the default dataset items produced by 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 = {
    "websites": [
        "allbirds.com"
    ],
    "baseline_key": "apify-daily-test"
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinin/shopify-price-change-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 = {
    "websites": ["allbirds.com"],
    "baseline_key": "apify-daily-test",
}

# Run the Actor and wait for it to finish
run = client.actor("zinin/shopify-price-change-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "websites": [
    "allbirds.com"
  ],
  "baseline_key": "apify-daily-test"
}' |
apify call zinin/shopify-price-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=zinin/shopify-price-change-monitor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/VSsGDsO5VxUTm7TNM/builds/fiyHegsT8rKrlN9Nc/openapi.json