How to Monitor Product Availability on Any Website

You're trying to buy something that keeps selling out. Or you're a reseller chasing restocks across 30 SKUs. Or you're tracking a supplier's inventory page to catch supply-chain blips before they hit your operations. The setup is the same. This is the practical version.

Step 1: Identify the right element to monitor

Open the product page in your browser and figure out what flips when the item is in stock versus out of stock. There are four common patterns:

• A button text change — "Notify me" → "Add to cart". The button text itself is the signal.
• A stock chip or badge — "Out of stock" / "Available now" / "Only 3 left". A small label, usually near the buy button.
• An entire button appearing or disappearing — the "Add to cart" button only renders when stock is positive.
• A structured data field — some sites expose stock state in invisible schema.org Product metadata. Power users can target that.

Whichever pattern the site uses, that's what you target. Don't monitor the whole page — banners, reviews, and recommendations rotate constantly and you'll get false alerts.

Step 2: Set up a monitor with a CSS selector

Use a monitoring tool that supports CSS selector targeting (PageChange, Distill, and Visualping all do). Walking through PageChange:

1. Paste the product URL into a new monitor.
2. Switch the scope from "Whole page" to "Selector".
3. Use the visual selector picker to click on the stock element you identified in step 1.
4. Confirm the baseline snapshot shows the right text (run a manual "Check now" if you're not sure).

Step 3: Pick a cadence that fits your urgency and quota

• 15 minutes — for hot drops and contested SKUs where minutes matter.
• Hourly — for products that restock once or twice a day.
• Every 4–6 hours — for supplier inventory pages that change infrequently.
• Daily — for slow-moving niches or pages you check more out of habit than urgency.

Faster cadence eats more of your monthly check quota. At 15 minutes, one monitor consumes ~3,000 checks per month. The Starter plan's 100,000 checks has enough quota for about 33 monitors at that cadence, but the plan itself is capped at 25 monitors. Hourly checks leave far more quota headroom.

Step 4: Route alerts to a loud channel

For restock monitoring specifically, push notifications matter. Email alone is usually too slow. Best choices:

• Slack or Discord with a direct mention — phone push within seconds for most users.
• Telegram — reliable mobile push, easy setup once you have a bot token.
• Webhook into your own bot or notification service if you want SMS or phone calls.

Common pitfalls

• Monitoring the whole page. You'll get an alert every time the site changes a banner. Always narrow to a selector.
• Selector targets the wrong element. A wrapper that includes price, reviews, and the buy button will trigger on every price update. Use the selector picker carefully or write a more specific CSS selector by hand.
• Bot protection blocks the checks. Big-box retailers (Walmart, Best Buy, some sneaker sites) use aggressive bot detection that may return the wrong page or block automated checks. Shopify, Magento, and most independent retailers usually work fine.
• Geo-restricted inventory. Some retailers show different stock by region. If you're in Europe checking US stock, you may see the wrong status. Look at the baseline snapshot to confirm.
• Forgetting to test. Always trigger a manual check after setup. The selector picks the wrong element more often than you'd think.

What about retailer-specific tools?

Tools like Keepa (Amazon) or NowInStock (a few specific products) are great when you only need one retailer. They handle that retailer's quirks better than a general-purpose tool can. The downside is you end up running 4–5 different tools to cover the sites you actually care about. A general-purpose monitor like PageChange isn't optimized for any single retailer but works on whatever public product page you point it at.

Should I worry about getting blocked?

For most non-enterprise retailers, no — PageChange uses realistic browser headers and standard request rates. For aggressively protected sites (sneakers, GPUs at MSRP, ticket sites during onsales), you'll have a harder time. The best signal is the first snapshot: if it captured what you expected, you'll likely keep getting clean checks.

Where to go from here

Pick the one product you most want to be alerted about — the GPU, the concert ticket, the supplier's component page. Set up a monitor at 15-minute cadence, route it to Slack or Telegram, and run it. Add more once you see the alert path actually work.

The stock availability alerts use case covers the same workflow in more product-focused detail. Or start with PageChange free if you want to skip to setup — 3 monitors and 5,000 checks per month, no credit card.