The Friday Afternoon Surprise
Every warehouse has lived some version of this story. Friday, late afternoon, a good customer calls for the order that ships Monday, and somebody walks the aisle and finds an empty bin where the product was supposed to be. The system knew. The system had known for a week, sitting quietly on a report nobody ran, holding its tongue like a polite butler while the building walked face-first into a wall. That silence is not an SAP problem. SAP Business One will happily shout. Somebody just has to tell it what to shout about, and then somebody has to actually listen.
That is the difference between an alert and a report. A report waits for you to come ask. An alert comes and finds you. Most small businesses run their entire operation on reports, which means they run on luck and memory, and then they wonder why every problem arrives as an emergency instead of a warning.
How Alerts Work in SAP Business One
The machinery is simpler than people expect. Under Administration, in Alerts Management, you build alerts that run on a schedule you choose: every few minutes, hourly, daily, whatever fits the thing being watched. Each alert is powered by a saved query, which means the alert fires only when the query finds something. No rows, no noise. You pick who receives it, and it lands in their Messages and Alerts inbox right inside B1, with the option to push it out to email as well. The recipient can drill straight from the alert into the document or the item that triggered it.
Two things matter in that design. First, because alerts are query-driven, an alert can watch for almost anything the data knows: stock falling below a minimum, a sales order past its delivery date, an invoice drifting past due, a purchase order nobody has confirmed. Second, because it lands inside the system where people already work, it does not depend on somebody remembering to open a dashboard. The warning shows up in the room where the work happens.
This is a different tool from approval procedures, which stop a document until someone signs off. Approvals are a gate. Alerts are a heads-up. You want gates on spending. You want heads-ups on everything that quietly goes bad while nobody is looking.
If your SAP Business One setup needs a tune-up, here is how I help SAP Business One customers.
The First Five Alerts I Set Up
I always start with five, because five is a number a team will actually read. One: minimum stock breaches on your A-items, the products that pay the rent, so purchasing hears about it while there is still time to order. Two: sales orders past their committed delivery date and not yet delivered, because that list is tomorrow's angry phone calls in writing. Three: open customer invoices past due beyond whatever grace window you honestly give, so collections starts as a nudge instead of an ambush. Four: purchase orders sent but never confirmed by the vendor, because an unconfirmed PO is a rumor, not a delivery. Five: negative or zero stock attempts on fast movers, which usually means a counting or receiving problem wearing a disguise.
Notice what those five have in common. Every one of them points at a specific human action: order it, ship it, call them, confirm it, go count it. An alert that does not end in a verb is decoration. When you set yours up, read each one and ask, "and then who does what?" If there is no answer, delete the alert and save everybody the eye roll.
Why Alert Systems Die
Alert setups rarely fail on technology. They fail on volume and on ownership. Somebody gets excited, turns on thirty alerts, and by the second week the inbox is a slot machine of red flags that everybody mutes. The fix is boring: fewer alerts, each with a named owner. An alert that belongs to everyone belongs to no one, and it will die ignored in a crowded inbox like every company-wide email ever sent.
The other killer is stale thresholds. A minimum level set two years ago for a product that now sells twice as fast is not a warning system, it is a false sense of security. Put a recurring fifteen minutes on the calendar each quarter to review the list: kill what nobody acts on, tighten what fires too late, add what burned you since last time. The goal is a short list of alerts so trustworthy that when one fires, people move. Trust is the whole product. An alert system people believe in is worth more than a dashboard with forty charts, because the alert shows up on the one day nobody would have thought to look.
Your ERP already knows most of what is about to go wrong in your building. The data is sitting there right now, patient as anything. Set up the five alerts, give each one an owner, and let the system do the worrying at 2 a.m. so you do not have to.
More from me on the Dead Brands blog, new posts every weekday.
Frequently Asked Questions
Where do I find alerts in SAP Business One?
Alerts are built in Administration under Alerts Management. You write or pick a saved query, set how often it runs, choose the recipients, and decide whether it stays inside B1's Messages and Alerts inbox or also goes out by email. Recipients can open the underlying document straight from the alert.
How many alerts should a small company run?
Start with about five, each watching something that ends in a clear action and each owned by a named person. Add more only after the first set has earned the team's trust. An inbox flooded with alerts trains people to ignore all of them, including the one that mattered.
What is the difference between an alert and an approval procedure?
An approval procedure is a gate: the document stops until an approver releases it. An alert is a notification: nothing stops, but the right person gets told while there is still time to act. Use approvals to control commitments like spending, and alerts to catch drift like low stock, late orders, and overdue invoices.
Can alerts watch for things besides low stock?
Yes. Because alerts run on saved queries, they can watch for anything the data can express: overdue deliveries, unconfirmed purchase orders, invoices past due, items received without a purchase order, margins below a floor on a quote, and plenty more. If you can write it as a question about your data, you can probably make it an alert.
