To track size and variant availability, create a Page Scout on the specific variant URL — or describe your size in plain language — and set an availability condition that fires when that variant becomes purchasable. ScoutPing checks public HTML on a schedule and emails you once when your size, colour, or SKU is available to buy.
Apparel, footwear, and configurable products rarely restock all variants at once. Your size might stay sold out while others return. Watching the parent product page without scoping the variant means false hope — or missed Pings when the wrong size restocks. Variant-aware monitoring fixes that.
Why variant-level monitoring matters
Product pages often show mixed availability:
- Size 8: In stock
- Size 9: Sold out
- Size 10: Sold out
- Size 11: Notify me
A generic "back in stock" alert on the parent URL might fire when any size returns. You click through and find your size still unavailable. Variant-scoped conditions prevent that frustration.
Two reliable patterns:
- URL-encoded variants — the address bar includes size, colour, or SKU parameters
- Condition-scoped variants — you describe "notify me when size 11 is available" and ScoutPing evaluates semantic evidence
For the general availability workflow, see track product availability. For limited drops where variants sell out fast, read limited edition restock alerts.
Step-by-step: size restock alert
1. Identify how the store encodes variants
Open the product page and select your size. Watch the URL:
| Store behaviour | What to do |
|---|---|
| URL changes with size param | Copy that exact URL into ScoutPing |
| URL stays the same | Describe your size in the condition |
| Separate SKU pages per variant | Use the SKU-specific URL |
When the URL encodes the variant, prefer that URL. It narrows what ScoutPing fetches and reduces ambiguity.
2. Write a variant-specific condition
Examples:
- "Tell me when size 11 is available"
- "Alert me when the black colourway is in stock"
- "Notify me when the 512GB option can be added to cart"
Pair positive signals (Add to cart for my size) with negative signals disappearing (Sold out next to size 11 goes away). Semantic evaluation helps when stores phrase variant availability inconsistently.
3. Create one Scout per variant you need
If you watch sizes 10 and 11, create two Scouts. Each has its own URL, condition, schedule, and deduplication. This keeps every Ping actionable — you know exactly which variant restocked.
4. Choose an appropriate interval
Footwear and streetwear restocks often happen in small batches. If your size competes with high demand, consider Pro intervals at 60 or 180 minutes. Slow-moving catalogue sizes may be fine on daily Free checks.
URL-encoded variants: best case
When selecting size 10 changes the URL to include ?size=10 or /size-10/, copy that link. ScoutPing fetches that specific representation. Your condition can be simpler — "tell me when this product is available" — because the URL already scopes the variant.
Test by opening the URL in a private browser window. Confirm the correct size is selected and availability text matches what you expect.
Same-URL variants: semantic scoping
Many Shopify and custom storefronts keep one URL for all sizes. Availability appears in a size selector or variant table. ScoutPing reads the full HTML response and evaluates whether your variant is purchasable.
Tips for reliable conditions:
- Name the exact size or colour in plain language
- Reference how the page shows unavailability ("Sold out" next to the size)
- Avoid conditions that would pass when a different variant restocks
Read exact match vs semantic monitoring to understand when literal text matching vs AI interpretation applies.
Real-world examples
Running shoes in a rare width
Standard widths restock weekly. Your wide width stays sold out for months. Scout with the width-specific URL if available, or describe "notify me when size 10 wide is available."
Streetwear with colourway drops
A hoodie releases in three colours. You want the olive colourway. Monitor the colourway URL or condition scoped to olive availability — not the parent product that might show black in stock.
Furniture with fabric options
A sofa page lists six fabrics. Three show "Made to order — 8 weeks." Three show "In stock." Watch the fabric variant you want, not the page-level headline.
PC components with model variants
GPUs ship in multiple SKUs (founders edition vs partner models). Each has a distinct product URL. Monitor the exact SKU page.
Variant monitoring vs parent-page monitoring
| Approach | Fires when | Risk |
|---|---|---|
| Parent URL, generic condition | Any variant restocks | False positives for your variant |
| Variant URL, generic condition | That URL's availability changes | Low — preferred when URL encodes variant |
| Parent URL, scoped condition | Your variant specifically | Good when URL does not change |
| Multiple Scouts | Each variant independently | Best for watching several sizes |
ScoutPing limits for variants
ScoutPing fetches public HTML without executing JavaScript. If variant availability loads only after client-side scripts run — common on some SPAs — monitoring may be unreliable. If the server-rendered HTML includes variant state in text or data attributes, monitoring works well.
ScoutPing does not click size selectors or interact with the page. It reads what the server returns. Test your URL and inspect whether availability text for your variant appears in the initial HTML.
For broader context, see what websites can be monitored.
Pairing with limited edition workflows
Limited drops amplify variant competition. Your size may sell out in seconds while other sizes linger. Combine variant-scoped Scouts with faster Pro intervals. See limited edition restock alerts for drop-specific strategy.
For general restock mechanics, how to get notified back in stock covers the full setup flow via back-in-stock alert.
Checklist: track size variant availability
- Select your size on the product page and note whether the URL changes
- Copy the variant-specific URL or plan a size-scoped condition
- Create a Page Scout via product availability monitor
- Describe availability for your specific variant
- Use one Scout per variant you are watching
- Choose daily or Pro interval based on demand
- Act quickly when the Ping arrives — popular sizes resell fast
Variant-aware monitoring is the difference between "something restocked" and "your size restocked." Scope the Scout to the variant you actually want to buy.
Testing your variant Scout before launch day
Before a high-demand drop, confirm ScoutPing interprets your variant condition correctly. Set the Scout, review how the condition is parsed, and wait for at least one scheduled check while your size is still sold out. If the check completes without false positives, you are ready for restock day.
Marketplace and multi-seller variant pages
Third-party marketplaces sometimes show variant availability per seller. Monitor the specific seller listing URL, not the parent product search. Describe availability for that seller explicitly — for example, when this listing shows as available to purchase from Seller XYZ.
ScoutPing plans and variant monitoring
Free daily checks suit slow-moving variant restocks — specialty sizes, rare colourways, seasonal fabrics. Pro intervals help when your variant competes on limited drops where inventory flickers. Use the monitoring frequency calculator to compare interval tradeoffs for your specific product category.
When to create a new Scout after a successful purchase
After you buy the item, pause or delete the Scout to avoid unnecessary checks. If you might want the same variant again — seasonal items, consumables — keep the Scout paused and resume next season instead of rebuilding from scratch.