Why most low-stock alerts get ignored
An online store sets a low-stock alert on its best-selling candle. It fires on a Tuesday into a shared inbox with forty other notifications. Everyone sees it, so nobody owns it. By Friday the candle shows "sold out," the ads are still running, and the supplier needs two weeks to ship more.
The alert worked; the process behind it did not. A useful low-stock alert answers two questions when it fires: who is responsible, and what should that person do next.
TwoQM has already written about keeping online and in-store inventory numbers in sync, which covers making the count itself trustworthy. This piece starts after the count is right: what happens when a trustworthy number gets low. It also differs from handling order-status questions, which covers customers asking about orders already placed.
Here is an original illustration, not a TwoQM client and not a measured result. A three-person online shop sells roughly 400 products across its own store and one marketplace. The ecommerce platform sends an email whenever any item drops below five units. Most are about slow sellers that will sit at four units for months. The owner filters them into a folder. Then the one alert that mattered, a fast seller with a long supplier lead time, sits unread in that folder.
The usual problems:
One threshold for everything. Five units means a crisis for an item that sells ten a day and nothing for an item that sells one a month.
No named owner. Alerts go to "the team," a shared inbox, or a group chat where silence looks like agreement.
No next action. The alert says "low stock" but not whether to reorder, transfer, pause promotion, or let the item run out on purpose.
No closure. Nobody marks an alert as handled, so handled and forgotten look the same.
Set the threshold from lead time, not a round number
A reorder point should reflect how fast an item sells and how long it takes to replace: typical units sold per day, multiplied by the supplier's usual lead time in days, plus a buffer you choose for slow shipments or busy seasons. Your own sales history supplies the inputs; no outside benchmark can.
Keep the inputs on the product record, not in someone's head:
Sales rate. Recent average units per day or week, recalculated on a schedule.
Supplier and lead time. The vendor, the usual days from order to receipt, and any minimum order quantity.
Buffer. Extra units for uncertainty, adjusted before peak seasons.
Lifecycle status. Core item, seasonal, clearance, or discontinued. A discontinued item should never trigger a reorder alert.
With those fields in place, each item gets its own reorder point, and the folder full of noise shrinks.
Give every alert a named owner
Decide ownership before the alert fires. Common ways to assign it:
By supplier. Whoever manages a vendor relationship owns every alert for that vendor's products.
By category. One person owns apparel, another owns home goods.
By channel. Marketplace-only products belong to whoever manages that listing.
Store the rule with the product or supplier record, let the alert carry the owner's name, and include a backup owner for days off. The alert goes to a person, not a mailbox.
Attach a next action to the alert
The alert should suggest the expected action from the item's status, so the owner confirms or changes it instead of starting from scratch:
Reorder. Core item, supplier available: start a purchase order draft for review.
Transfer. Stock exists in another location or warehouse: request a move.
Pause promotion. Ads or emails push an item that cannot be restocked in time: flag it for the marketing owner.
Mark backorder. The store allows it and the supplier date is known: update the listing after review.
Let it sell out. Seasonal or discontinued: confirm, hide the item at zero, and close the alert.
Each alert then gets a status (open, acknowledged, action taken, closed) with a date and the owner's name. If an alert sits unacknowledged past a window you choose, it escalates to the backup owner or manager, so important alerts do not die quietly.
Where AI helps, and where it stops
Ordinary business automation carries most of this: recalculate reorder points on a schedule, route alerts to the named owner, escalate when an alert is not acknowledged, and send a short daily list of open alerts.
AI can help with drafts a person reviews: a purchase order or supplier email from the product record, a summary of open alerts on promoted items, or a short backorder note in English and Spanish. A person reviews and approves every draft. AI does not place orders, change prices, pause ads, or edit listings on its own.
Connect the alert to the tools you already use
Many stores keep sales in the platform, supplier details in a spreadsheet, and purchase orders in email. Connected systems can pull sales rates, lead times, and promotion status into one alert, so the owner sees everything needed to decide. If no off-the-shelf tool fits, custom software can be scoped around your catalog.
Where to start this week
Pick your twenty best-selling products. For each, write down the supplier, the usual lead time, a rough sales rate, and who should own the reorder decision. Then review your last low-stock alerts: did anyone act, and how would you know? The gaps show which rules to write first.
TwoQM builds business automation, connected systems, and custom software for retail and ecommerce businesses. If your low-stock alerts land in a folder nobody opens, TwoQM can scope an alert workflow with owners, next actions, and escalation around the platform you already use. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Low-Stock Alert Workflow · Explore TwoQM business automation