Zero on Hand Is Not Low Stock
A service has nothing on hand, so by any arithmetic it is at or below its reorder point, every day, forever. That is why the first night after a team adds services to a stock system is usually the noisiest night it has ever had.
Low-stock alerting is one comparison: is what you have on hand at or below the point where you should reorder? For a stock item it is the most useful question an inventory system asks. For a service it is meaningless, and it always answers yes.
Zero on hand, a reorder point of zero. Zero is at or below zero. Every service is low stock.
Where that comparison is made
Not in one place. A stock system asks "is this low?" from a surprising number of directions, and each is a separate opportunity to get it wrong:
| Surface | What a service would have done |
|---|---|
| The low-stock alert email | Listed every service, every day |
| Low-stock reminders | Repeated the list on schedule |
| Low-stock workflows | Fired an approval or a notification per service |
| Smart alerts on the dashboard | Ranked services as the most urgent shortages |
| Reorder suggestions | Proposed buying hours of consulting by the box |
| The dashboard summary | Counted services in the low-stock tile |
| The replenishment list in the API | Handed the mobile app services to reorder |
| The nightly reorder recalculation | Rewrote each service's reorder point from its sales |
Every one of those now looks at stock items only. A service is left out of all eight before the comparison is made, rather than filtered from the result afterwards, so it cannot reappear in a total, a count or a chart.
An alert that is always on is an alert that is always ignored, and it takes the real shortages down with it.
Why the noise is worse than it looks
The cost of a false alert is not the false alert. It is what happens to the true ones. A buyer who opens a low-stock email with forty service names at the top learns, within a week, to stop opening it. The shortage of a real product that arrives on day eight is in the same email, and nobody reads it.
The nightly recalculation is the quieter version of the same problem. Reorder points are rewritten from usage, so a service that sells a lot would acquire a large reorder point, and the next alert run would then flag it more urgently. The number you typed is recalculated explains how that job works for stock; it now skips services entirely.
What a service has instead
Nothing to reorder. A service carries no reorder point, no safety stock and no warehouse, so there is no field for anyone to set by mistake. If you buy a service from a supplier, that goes through a request and a purchase order, as buying a service you cannot count describes, not through a reorder trigger.
For how reorder points work on the items that do have them, reorder point and safety stock is the reference.
Check the morning after
Open the low-stock alert the day after adding services.
What you should see
The same list as the day before.
If you see otherwise
A service is still a stock item. Check its type.
Open reorder suggestions.
What you should see
Products only.
If you see otherwise
The suggestion is reading an item marked as stock.
Look at the low-stock tile on the dashboard.
What you should see
Unchanged.
If you see otherwise
Same as above: look for an item with the wrong type.
In one line
Services are left out of every low-stock alert, reminder, workflow, suggestion, dashboard count and nightly recalculation, so adding them does not add a single line of noise to the alerts your buyers rely on.
What AWRA OpsHub does today
- Services left out of low-stock alerts and reminders.
- Services left out of low-stock workflows, smart alerts and the dashboard count.
- Services left out of reorder suggestions and the replenishment list in the API.
- Services skipped by the nightly reorder recalculation.
More we can add to your workspace
- Stock measures in the custom report builder that leave services out automatically, rather than relying on a type filter you add.
- A capacity alert for services, warning when booked hours exceed the people available to deliver them.
Where we point you to a specialist
- We will not give a service a pretend reorder point to make it fit a stock alert. If you need to plan capacity for services, that is a different measure and we would build it as one.
Both items in the middle column can be scoped for your workspace.
Alerting that fits services
Stock alerts are now quiet about services. If you want services to have alerts of their own, they look different.
Capacity warnings
Compare booked service hours against the people available to deliver them.
Stock-only report measures
Stock totals in custom reports that exclude services without an extra filter.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your workspace and maintained with the product.
Talk to us about alertsAdd your services without the noise
The feature page shows where services appear and where they do not.
See how service items workFrequently asked questions
Will services appear in low-stock alerts?
No. Services are left out of low-stock alerts, reminders, workflows, smart alerts, reorder suggestions and the dashboard low-stock count.
Does the nightly reorder point recalculation touch services?
No. It recalculates stock items only.
Can I set a reorder point on a service?
No. A service carries no reorder point, safety stock or warehouse.
