Product Stock Monitor

Product Stock Monitor extracts conservative availability snapshots from public product pages using structured product data when available or explicit CSS selectors when a source needs custom targeting. It is built for recurring stock checks where a stable dataset is more useful than repeatedly inspecting pages by hand.

What it does

The Actor crawls configured product URLs, resolves supported availability information, normalizes the result, and writes a structured snapshot to the default Apify dataset. Structured product metadata is preferred where possible, while selector-based extraction provides a controlled fallback for sites that do not expose reliable availability markup.

Typical use cases include:

• monitoring when selected products return to stock;
• tracking public availability across retailers;
• feeding stock status into alerts or dashboards;
• recording availability snapshots over time;
• scheduling recurring checks in Apify.

Quick start

1. Add one or more public product URLs to the Actor input.
2. Run a small test using conservative request and result limits.
3. Inspect the dataset and verify that the reported availability matches the page.
4. If structured data is not sufficient, configure the supported selector options for that target.
5. Once the source is verified, schedule recurring runs or call the Actor through the Apify API.

The Input tab also includes common crawler settings such as retries, request limits, concurrency, timeouts, and proxy configuration.

Output

Each dataset item represents a normalized stock/availability snapshot together with source and scrape metadata. The exact field contract is defined by the Actor's dataset schema. Results can be exported as JSON, CSV, or Excel or consumed through the Apify dataset API.

Scheduling and integrations

Use an Apify schedule for periodic stock checks and connect the resulting dataset to webhooks, Make, Zapier, notification services, databases, or other Actors. Choose a schedule that is reasonable for the retailer and the urgency of the monitoring task.

Limitations

Availability displayed on product pages can depend on location, product variant, store selection, account state, cookies, or delivery method. Structured markup may also be stale, and CSS selectors can break after a site redesign. This Actor monitors public page data and should not be treated as a guaranteed inventory reservation system.

Pricing

The active pricing model and current rates are shown in the Actor's Apify Store Pricing tab. Platform cost depends on page count, frequency, retries, proxy use, and target complexity. Test a small representative set before enabling frequent recurring runs.