Your stock alerts trained you to ignore them

There's a folder in my inbox called "stock." For about a year it was where low-stock alerts went to die. The rule was simple: anything from the inventory system, skip the inbox, file it. I told myself I'd review the folder every morning with coffee. I reviewed it maybe once every couple of weeks, and only when something had already gone wrong.

Then one Tuesday a customer asked why their order had been sitting unfulfilled for nine days. The SKU had hit zero the previous Wednesday. The alert had fired. It was in the folder, the 41st unread message that week, wedged between a slow-mover that was one unit under buffer and a seasonal line I'd already ordered twice over. I'd built a system that warned me about everything, which is the same as a system that warns me about nothing.

That's the trap with stock alerts. They fire reliably enough. The trouble is they fire so often, for things that don't need a decision, that you train yourself to look away. And the day you most need one to land, it's camouflaged by the forty that didn't matter.

Why the folder fills up

Most alerting works on a threshold and nothing else. Stock drops below the minimum, an email goes out. Drop, email. Drop, email. There are four reasons that turns into a flood, and only one of them is about you having too many SKUs.

The first is that the rule fires on a state, not a change. "Below buffer" is a state a SKU can sit in for three weeks. If the alert re-checks every cycle and re-sends whenever the condition is still true, you get the same warning Monday, Tuesday, Wednesday, for a SKU you looked at on Monday and decided to leave. Nothing new happened. You get told anyway.

The second is that it has no idea what you've already done about it. You saw the bestseller getting low last week. You raised a purchase order. Stock is on the way. The system doesn't know that, so it keeps screaming "low stock" at a SKU where the decision is made and the units are in transit. This is the single biggest source of noise I've seen, and it's the easiest one to kill.

Third, every alert carries the same weight. A craft-ribbon SKU that sells four units a month, sitting one unit under its buffer, generates the exact same email as your top seller at a hard zero in your peak week. One of those is a shrug. The other is revenue walking out the door and a fulfillment backlog forming behind it. If they look identical in your inbox, you'll treat them identically, which means you'll treat the urgent one like a shrug.

Fourth, the alerts land somewhere you don't live. A 6 a.m. email per SKU, into an inbox you triage for customer and supplier mail first. By the time you've cleared the real mail, the stock alerts are below the fold and out of mind.

What an alert is actually for

Here's the rule I wish I'd started with.

An alert should represent a decision you haven't made yet.

If a SKU is low and you've already ordered more, there's no decision left. Suppress it. If a SKU is low and you haven't acted, that's a live decision, and it should reach you. If a SKU is at zero right now, that's not a "soon" problem, it's a "today" problem, and it should reach you even if you've got stock on the way, because inbound stock three days out doesn't help the customer whose order is stuck today.

That last one matters more than it looks. The tidy version of "don't alert me about SKUs I've already ordered" quietly swallows the worst case. You ordered more two weeks ago, the supplier slipped, and now you're at zero with a PO that says everything's handled. Suppress that and you've muted the exact alarm you needed. So the line I draw is: an open purchase order suppresses a reorder nudge, never an out-of-stock one. Running out now is urgent regardless of what's on a truck somewhere.

How I'd wire it today

Four changes, roughly in order of how much noise they kill.

Suppress reorder alerts for SKUs with an open PO. If you've raised an order, the system should stop nagging you to raise an order. This alone cut my alert volume by more than half. Stocura does this out of the box: a SKU with stock on the way drops out of the reorder alerts automatically, because you've already actioned it.

But let true out-of-stock through anyway. Keep the out-of-stock alert firing even when a PO is open. A reorder reminder is "you'll want to act soon." An out-of-stock alert is "a customer can't buy this right now." Those are different events and they should never share a mute switch. Stocura splits them deliberately: open POs quiet the reorder reminders, and never the out-of-stock ones.

Rank by urgency, not alphabetically. Group what needs attention into buckets that mean something. Out of stock now. Order this week. Worth a look. Stocura's reorder queue sorts into exactly those three so the zero-stock bestseller sits at the top and the one-unit-under ribbon sits where it belongs, near the bottom. A list that's sorted by how much it costs you is a list you'll actually work top to bottom.

Send one digest, to where you work. Not forty emails. One daily summary, in your timezone, to whoever needs it, listing what changed and what's urgent. If your team lives in Slack or Google Chat, send it there instead of email. Stocura does a single per-timezone digest to multiple recipients, with Slack and Google Chat webhooks if that's where your day happens.

One more, less obvious: make sure a failed alert retries. Early on I had a stretch where alerts that failed to send still counted as "sent" for deduplication, so a SKU that genuinely needed me went quiet for a day because the first attempt bounced off a rate limit. The fix is to only mark an alert handled once it's actually delivered. Worth checking whatever you run on.

The test for any alert you keep

Before you leave an alert rule switched on, ask one thing: when this fires, is there a decision I need to make that I haven't already made? If yes, keep it. If the honest answer is "no, I'd glance at it and move on," that alert is training you to ignore the next one. Turn it off.

I deleted about two-thirds of my alert rules the week I worked this out. The folder still exists. I just don't need it anymore, because the alerts that reach me now are the ones I'd have wanted at the top of my inbox all along.