Product availability monitoring watches public web pages on a schedule and notifies you when something becomes available to buy, book, or register for. ScoutPing uses Page Scouts — one URL, one plain-language condition, scheduled checks, deduplicated email Pings — to replace manual refreshing across retail, tickets, appointments, courses, and any page where availability text changes.
This is the pillar guide for the Price & Availability monitoring category. Whether you are waiting for a sold-out GPU, concert tickets, a passport appointment, or an open course seat, the underlying pattern is identical. This article explains that pattern end to end: what to monitor, how to set it up, which intervals to choose, where it breaks, and how to troubleshoot.
The core pattern: URL + condition + schedule
Every availability watch follows three steps:
- URL — the exact public page where availability status is visible
- Condition — plain-language description of when the item is available
- Schedule — how often ScoutPing fetches and evaluates
ScoutPing fetches public HTML, extracts readable text, evaluates your condition with deterministic and semantic checks, fingerprints logical events, deduplicates notifications, and sends email Pings with evidence.
No store integration. No browser extension. No visual monitoring. Public HTML only.
For restock-specific setup, start with how to get notified back in stock. For hands-on steps, see track product availability.
What counts as "availability"
Availability monitoring detects when you can take action on a page:
| Domain | Unavailable signal | Available signal |
|---|---|---|
| Retail products | Sold out, Out of stock | Add to cart, Buy now |
| Tickets | Sold out, Not on sale | Buy tickets, On sale |
| Appointments | No slots, Fully booked | Book now, Schedule |
| Courses | Course full, Registration closed | Enroll now, Seats available |
| Preorders | Coming soon | Preorder now |
The vocabulary changes. The monitoring mechanics do not.
Page Scouts: the building block
ScoutPing availability monitoring uses Page Scouts — monitors tied to a single public URL and one described condition.
Each Scout has:
- A URL to fetch on schedule
- A parsed availability or keyword condition
- A check interval (daily Free; 60–1440 min Pro)
- Deduplication so one logical event produces one Ping
- Email notification with evidence and source link
Create Scouts via the product availability monitor flow for general availability, or back-in-stock alert for restock-focused setup.
Web Scouts Pro exist for broader search-based monitoring, but single-page availability watches are the most common pattern in this category.
Condition types for availability
Positive signals
Watch for text that means you can act:
- "Add to cart" / "Buy now" / "In stock"
- "Buy tickets" / "On sale now"
- "Book appointment" / "Enroll now"
- "Preorder now"
Negative signal disappearance
Watch for unavailable text going away:
- "Sold out" disappears
- "No appointments available" disappears
- "Course full" disappears
- "Coming soon" disappears
Variant-scoped conditions
When one page lists multiple sizes, tiers, or sections:
- "Tell me when size 11 is available"
- "Notify me when VIP tickets are on sale"
See track size variant availability.
Semantic evaluation
When stores use unusual phrasing, ScoutPing uses structured AI to interpret whether the page satisfies your natural-language condition. Deterministic text matching is tried first. Read exact match vs semantic monitoring.
Check intervals: choosing the right frequency
| Interval | Best for |
|---|---|
| Daily (Free) | Slow restocks, seasonal items, patient waits |
| 1440 min (Pro) | Same as daily with Pro features |
| 720 min | Moderate urgency |
| 360 min | Periodic restocks, appointment cancellations |
| 180 min | Competitive tickets, popular courses |
| 60 min | Limited drops, flickering inventory, on-sale events |
ScoutPing uses a cron-driven scheduler with bounded concurrency. Checks run in the cloud regardless of whether your computer is on.
Use the monitoring frequency calculator to think through tradeoffs.
Use case library
Retail and e-commerce
Sold-out products, limited editions, size variants, preorders, marketplace listings. The most common availability category.
Tickets and events
Concert, sports, and festival tickets. Monitor official pages for on-sale openings and cancellation returns.
Appointments and booking
Passport offices, medical specialists, DMV slots, service providers. Monitor public booking pages for cancellation-driven openings.
Courses and enrollment
University sections, certifications, workshops, camps. Monitor enrollment pages for open seats and registration windows.
Preorders and launches
Hardware, games, books. Monitor for preorder language and coming-soon-to-available transitions.
Availability vs price monitoring
These are separate questions requiring separate Scouts:
- Availability: Can I buy or book this now?
- Price: Is this at or below my target price?
Do not combine them in one Scout. A product can be in stock but too expensive, or cheap but sold out. Each condition deserves its own Page Scout.
For price monitoring, see track SaaS pricing changes and price drop alerts.
ScoutPing capabilities and hard limits
What ScoutPing does
- Fetches public HTML on a schedule
- Evaluates plain-language conditions
- Sends email Pings with evidence
- Deduplicates logical events
- Runs checks in the cloud (Free daily; Pro 60–1440 min)
What ScoutPing does not do
- Execute JavaScript or render SPAs
- Access login-required or CAPTCHA-protected pages
- Visual or screenshot monitoring
- Browser automation or button clicking
- SMS or push notifications
- Real-time sub-minute streaming
For eligible websites, see what websites can be monitored.
Deduplication: why you get one Ping per event
ScoutPing fingerprints logical availability events. A restock is one event. A ticket on-sale opening is one event. Subsequent checks that still show available do not generate repeat Pings.
This prevents inbox spam. It also means:
- You will not get daily "still in stock" emails
- A new sold-out-to-available cycle triggers a new Ping
- Paused Scouts do not check until resumed
Understand the pipeline in how back-in-stock alerts work.
Troubleshooting availability monitoring
When alerts fail or behave unexpectedly:
- Verify the exact public URL
- Check availability text in page source
- Tighten the condition to availability-specific language
- Increase check frequency for brief inventory windows
- Accept JS-only and bot-protected page limitations
Full diagnosis: restock alert failures.
Multi-page monitoring
Watching several products, tickets, or appointments? Create one Scout per URL. Each has independent scheduling, conditions, and deduplication.
For portfolio management, see monitor multiple websites.
Getting started checklist
- Identify the public URL where availability status changes
- Confirm availability text appears in server-rendered HTML
- Choose the right landing flow: product availability monitor or back-in-stock alert
- Describe the condition in plain language
- Pick daily or Pro interval based on urgency
- Confirm ScoutPing understood your condition
- Wait for deduplicated email Pings
- Act quickly when notified — availability windows are often short
Product availability monitoring turns any public "sold out" or "fully booked" page into a background watch. Set your Scouts, choose your intervals, and let ScoutPing handle the refreshing.