WooCommerce Catalog Radar

What does WooCommerce Catalog Radar do?

Export prices and stock availability from a public WooCommerce Store API. Optionally compare the result with a previous snapshot to identify price changes and stock transitions for the same product IDs.

Use it to check a supplier's selected products, prepare a price comparison spreadsheet, or feed catalog observations into your own backend. Apify provides API access, dataset exports, scheduling and integrations; previous snapshots must be passed explicitly between runs.

How to use it

1. Enter the public Store API URL in the Input tab. The WordPress merchandise endpoint below is a working technical example.
2. Choose 1–100 products and start a run.
3. Download the dataset as JSON, CSV or Excel. Save the OUTPUT JSON if you want to compare a later observation.
4. For the next run, paste that JSON into previousSnapshot and use the same URL and filters.

Input

{
  "apiUrl": "https://mercantile.wordpress.org/wp-json/wc/store/v1/products",
  "maxProducts": 8
}

Use ?include=123,456 to follow specific product IDs. The API must be publicly accessible without login or API keys. Each run requests at most 100 products with bounded pagination. It does not scrape arbitrary web pages or bypass access restrictions.

Results

The default dataset contains one row per observed product and can be exported using Apify's dataset export options. Each row contains product ID, SKU, name, product link, integer minor-unit prices, currency, currency unit, price type, stock availability, observation time, comparison status and a list of changes.

For example, price_minor: 2600, currency: "BRL", currency_minor_unit: 2 means BRL 26.00. Variable products may have a price range. Unknown values remain null. Stock availability does not indicate inventory quantity. Prices depend on the source and may vary by location; shipping and taxes are not included.

The default key-value store's OUTPUT record contains the snapshot and a summary. To compare two runs, copy the earlier OUTPUT JSON into the next run's previousSnapshot input, keeping the same API URL and filters. No previous customer run is looked up automatically. Without this input, all rows are marked baseline and no changes are reported.

Missing products are reported in notSeenProductIds, without claiming deletion or unavailability. A newly observed ID is marked not_in_previous_sample, without claiming the source just added the product. Currency and decimal-unit changes are separate from price changes. HTTP 401, 403 or 429 stops the run. Source failures do not produce a successful partial snapshot.

Field	Meaning
product_id, sku, name, url	Product identity and source link
price_minor, price_max_minor	Price or range in integer minor units
currency, currency_minor_unit	Currency code and decimal places
in_stock	Availability, or null if unknown
comparison_status, changes	Comparison with your supplied snapshot

Illustrative output fields (not a live price):

{"product_id":"123","sku":"EXAMPLE","price_minor":2600,"currency":"BRL","currency_minor_unit":2,"in_stock":true,"comparison_status":"baseline","changes":[]}

Pricing

The pilot price is US$1 per 1,000 saved product snapshots (US$0.001 each), plus US$0.00005 per Actor start at the supported 128–256 MB memory. Platform usage is included for customers running the published Actor. A run saving 8 products costs US$0.00805; 100 products cost US$0.10005. Each observation is charged, including unchanged products. The start event can still apply if the source is empty or a run fails.

Consult the live Pricing tab for the authoritative current price. Set a maximum cost per run; if it limits dataset delivery, OUTPUT includes only the delivered rows, marks truncatedByChargeLimit, and does not report missing IDs from that truncated sample. If the platform stops a run before OUTPUT is saved, use the already saved dataset rows.

Scope and current status

This is an early pilot, limited to the public WooCommerce Store API v1. The WordPress merchandise store is a technical example, not a recommended supplier or a resale opportunity. This Actor is not affiliated with WooCommerce or WordPress.

One run collects one snapshot and exits. Scheduling, downstream delivery and forwarding the previous snapshot must be configured separately. No email or messaging service is included. Use public endpoints you are authorized to access and respect the source's terms. For errors, supported-source questions or a custom workflow request, open an Issue.