Your low-stock threshold is a purchasing policy in disguise

If every item in your list has a low-stock threshold of 5, you don't have a threshold. You have a guess.

Clover lets you set that number per item, and when the count hits it, someone gets told. The feature works. The purchasing policy hiding inside the number is the part most operators never write down.

What Clover actually does with low-stock alerts

Clover's help center is short on this point, and that's useful. You can manage item stock counts and set a low-stock alert threshold for each item. When an item's stock count is equal to or less than that threshold, "the system automatically sends alerts through email and push notification to the business owner." Clover also says you can select how to be notified.

Two things follow from that wording. First, the alert is per item: a slow-moving jar and a daily sell-out can carry different thresholds. Second, the documented recipients are the business owner, by email and push. If you expect a manager, buyer, or the whole staff list to get the same ping, that isn't what this help article describes. Build your reorder habit around who Clover says is notified, or add your own handoff.

Stock tracking has to be on for the count to mean anything

A threshold only fires against a count that moves. Clover's stock-tracking settings live under Settings → View all settings → Inventory. After you enter an initial stock count, Clover can automatically adjust that count after each sale. The same page lets you turn on Track stock (counts in the Inventory app, shown in Register), Automatically update item counts, and optionally Allow negative stock counts when more units sell than you have on hand.

If you manage counts in a third-party app instead, Clover says to turn off Automatically update item counts. Either path is fine. Mixing them—Clover auto-decrementing while another system also writes counts—is how you get alerts that fire late, early, or against a number nobody trusts. Pick one system of record for the quantity the threshold watches.

One caveat Clover surfaces directly: allowing negative stock counts means the on-hand figure can drop below zero when you oversell. Useful for not blocking a sale. Less useful as a clean reorder signal. Know which mode you're in before you treat the alert as gospel.

A threshold is lead time wearing a round number

Here's the purchasing math the POS field doesn't show you. A workable low-stock number is roughly supplier lead time in days, times how many units you sell per day, plus a safety buffer for late trucks and busy weekends. The alert should fire while you still have cover to reorder—not after you're empty.

Example (hypothetical round numbers, not a benchmark): an item that sells about 4 units a day, from a supplier that takes 5 days to deliver, needs roughly 20 units of cover for the lead time alone. Add a small buffer—say another 8 units for a couple of busy days—and a threshold near 28 is a policy. A threshold of 5 on that same item is a hope that someone notices early.

Flip it for the slow mover. An item that sells one unit a week doesn't need a threshold of 20. That number isn't caution; it's a standing order to keep cash on the shelf. Set thresholds by velocity and lead time, even if you only tighten the top sellers first.

The cash cost of padding every SKU the same way

Uniform padding feels safe. Every threshold of 15 "just in case" means you reorder earlier and hold more units across the whole list. On a cheap napkin that's noise. On a specialty product at, say, $12 a unit (example number), raising the floor by 10 units parks $120 per SKU that could have stayed in checking. Multiply across dozens of items and the "safe" default is a working-capital decision you never voted on.

The honest tradeoff: stockouts cost sales and goodwill; overstock costs cash and, for anything perishable or seasonal, markdown risk. Clover's alert won't make that tradeoff for you. It will only tell the business owner that a number you chose has been crossed.

A checklist that turns the guess into a policy

None of this needs new software. It needs numbers you already have:

• Confirm stock tracking: Settings → View all settings → Inventory—Track stock on, and Automatic updates either on (Clover as system of record) or off (third-party app owns the count).
• For your top 20 sellers, estimate daily sell-through and supplier lead time; set each low-stock threshold near lead time × daily rate plus a small buffer.
• Leave catch-all thresholds (every item = 5 or 10) only on items you haven't reviewed yet, and shrink that leftover list.
• Make sure the business owner actually sees the email and push alerts—Clover sends them there—and decide who acts when they arrive.
• After a week of alerts, spot-check a few: did the count match the shelf, and did the reorder land before you stocked out?

When the threshold matches how you buy, the alert stops being noise. It becomes the purchasing policy you meant to write.

If you'd like a second set of eyes on how inventory, cash, and your Clover setup line up with your books, Gameplan Financials pairs bookkeeping and tax strategy with AI systems work: schedule a conversation.