WooCommerce Catalog & Price Monitor - Diffs & Low-Stock Alerts

catalog-snapshot

One store's catalog was fetched in full and stored as a snapshot, so the next run can tell exactly what changed. Charged once per store, only after the snapshot is written — a store that is unreachable, excluded by robots.txt, has no WooCommerce Store API, or returns an empty catalog is never charged.

change-alert

One detected change — price drop, price increase, back in stock, out of stock, new product or removed product — was written to the dataset and included in the Slack and webhook summary. Charged per event, after the event is stored. The first run per store is a baseline and emits none. Low-stock events are charged under low-stock-alert instead, never both.

variant-exported

A block of up to 1,000 catalog records was exported to the dataset, each with price, regular/sale price, currency, stock availability, stock count, SKU, categories, tags, brands, attributes, images, weight and dimensions. Charged per 1,000 records, rounded up, once for the whole run — and only when "Export the full catalog" is switched on.

low-stock-alert

A product's remaining units crossed into the configured low-stock threshold, or fell further while below it. Derived from the store's own low_stock_remaining field where published, otherwise from the unit count parsed out of its stock-availability text and tracked across runs. Charged instead of change-alert for these events, never in addition.

request-served

One HTTP request to the actor running in Standby mode was answered with a completed run. Charged on top of the events that run produced, so resident compute is never running at a loss. The /health endpoint is never charged.