Price Alerts vs Automated Buys: Why Alerts Don't Get Filled
Every tracker offers them: set a target price, get a ping when it hits. It feels like automation. It isn't. An alert is a notification about an opportunity; a fill is the opportunity captured. The distance between those two things is measured in hours of your life and listings you never got.
The lifecycle of an alert
Here's the sequence nobody draws on the marketing page. The price of a case you want dips under your target at 3:12am — dips are disproportionately off-hours events, since that's when sellers in other time zones are active and buyers in yours aren't. The alert fires. Your phone is on do-not-disturb, as it should be. You see the notification at 7:40 over coffee, open the marketplace, and one of three things is true:
- The cheap listings are gone, taken by buyers — often bots — who don't sleep;
- The price has drifted back above your target, and now you're staring at a "should I chase it?" decision the alert was supposed to eliminate;
- The listing is still there — and now you do the manual checkout dance anyway: log in, top up, confirm, all before someone else clicks first.
Only the third case ends in a fill, and it's the rarest, because the whole reason the alert fired is that the price was attractive — and attractive prices are exactly the ones that don't wait four hours. This is the same latency problem that creates cross-market price lag, viewed from the losing side.
Alerts optimize the wrong bottleneck
Manual buying has two costs: knowing when to act and acting. Alerts fully solve the first and leave the second untouched — and the second is the expensive one. Acting means being awake, near a device, logged in, funded on the right marketplace, and decisive within minutes. Multiply that by every dip across every item you track, and an "automated" alert system quietly becomes an on-call rotation with you as the only engineer. The accounting is done in the hidden time cost of manual trading, and it's brutal for anyone with a job.
There's a psychological cost too. Alerts are FOMO delivery devices: each missed one is a small documented failure — you now know, with a timestamp, exactly which price you failed to get. Watchers of dashboards end up chasing entries out of frustration, the pattern automation-as-FOMO-insurance exists to break.
A standing cap is an alert that also buys
Flip the design. Instead of "tell me when it's under $0.80," the instruction becomes "buy it whenever you can at or under $0.80, up to my daily budget." That's a price ceiling attached to a schedule — a standing order. Structurally it's the same watchfulness as the alert, with the execution step welded on:
- It never sleeps through the dip, because there's no human in the loop at decision time — you made the decision when you set the cap, calmly, in advance. The design logic is laid out in max-price lines.
- It never chases, because a cap is a hard line, not a mood. Expensive morning? The buy skips, the report says why, and the budget rolls forward per your rules.
- It's already funded and already logged in — the boring operational readiness that human buyers reconstruct from scratch at every ping.
A scheduled buyer with caps won't catch a fleeting 2am mispricing that lives for ninety seconds; that's sniper territory, a different tool entirely. What it catches is everything slower: the soft dips, the weekend drifts, the venue that's a few percent cheaper this morning. For an accumulator, that's most of the available edge — as the manual-versus-automated numbers suggest, the wins come from never missing ordinary opportunities, not from heroically catching rare ones.
The math of missed fills
It's worth putting a rough shape on the cost, even hedged. Suppose an item you want dips below your target a handful of times a month, and — being honest about sleep, work, and reaction time — you convert perhaps one dip in four into an actual purchase. A standing cap converts nearly all of them, because the only dips it misses are the ones shorter than its run cadence. Over a year of accumulation, the alert-driven buyer fills a fraction of the opportunities at, on average, worse prices (the dips they catch are the slow, shallow ones — the sharp ones are gone by the time a human arrives). The gap between those two fill rates, compounded across every item and every month, is the quiet fee you pay for keeping a human in the execution loop.
Where alerts still earn their keep
None of this makes alerts useless — it makes them a research tool rather than an execution tool. They're good for items you're still deciding about, for sell-side awareness on positions you hold, and for learning an item's rhythm before committing a cap to it. The honest division of labor: alerts for things you're watching, standing caps for things you're accumulating. Trouble starts only when the first is asked to do the second's job.
One more practical note: an executing system deserves a rehearsal step that a pinging system doesn't need. Before real money moves, you want to see exactly what would have been bought, where, at what price — which is why dry-run-by-default is the right default for any tool that holds your caps. cs2stack works this way: plans preview with real prices and fake money until you flip the switch, and once live, every fill or skip lands in an emailed report with the reason attached. The alert you actually want, it turns out, is the one that arrives after the buy — a receipt.