· 00
Every alert: what, when and from where
Know exactly when the system tells you things, and when it does not.
Reviewed 2026-09-05
Everything ToolFlux can notify you about, in one place: where it comes from, exactly when, and what triggers it. The chapters describe each alert where it appears in the flow; this is the whole.
Three things to know before the table
Scheduled alerts
Sent from the server, at fixed times on Romanian time, whether or not anybody opens the app. The server comes looking for you.
07:30 — Stock rules
Where · Daily, server. Only if you have defined stock rules.
- Stock threshold reached — An item has dropped to the minimum quantity set for a location. The notification goes out even if you switched automatic request creation off — the person has to know the threshold was hit, even if they decide what to order themselves.
An hour and a half before the others, deliberately: goods are ordered before the day starts.Pro
09:00 — The morning round
Where · Daily, server. One pass over the assets, four counts.
- Overdue — Items past their return date.
- Long overdue — Those more than 14 days past. A separate alert; it does not replace the first.
- Service due — Scheduled services that have come due.
- Late back from service — Tools still at a service provider past their date.
09:45 — Documents with deadlines
Where · Daily, server. Vehicles, warehouses and sites alike.
It fires on exact days, not across a window:
- Document expiring — Exactly 30 and exactly 7 days before expiry.
- Document expiring today — On the expiry day.
- Document expired — At 1, 3, 7 and 30 days after.
It covers the free-form document list on every type of location, plus the four legacy vehicle fields (ITP, RCA, road tax, CASCO) for vans not yet migrated.
Event alerts
Sent the moment somebody does something, not at a fixed time.
Asset movements
Where · On any change to an item.
- Assigned to an employee — The name of the person who took the item is in the message.
- Returned by an employee — The item is back in the store.
- Status changed — The item's status or visual condition changed. Not sent if an assignment alert already went out in the same write — one notification per change.
- Sent to service — The item went to a service provider.
- Back from service — The item came back from service.
Transfers
Where · On creating a transfer.
- Goods sent to you — A push transfer: somebody started a delivery to you.
- Goods asked of you — A pull transfer: somebody wants something that sits with you.
The two directions have different notifications because they need different actions: one is accepted, the other fulfilled. See chapter 09.
Supply and stock
Where · On creating a request, or when a stock falls.
- Supply request — A new request was created. Sent only for new, pending requests — not on every state change.
- Consumable allocated — A quantity of a consumable was given out.
- Stock below threshold — A stock has just fallen below its reorder threshold.
Alerts from inside the app
Calculated locally, appearing when the app is running. The app waits for you. They do not replace the server alerts; they cover the gap between milestone days.
- Documents with deadlines — One alert anywhere in the last 30 days, then milestones at 0, 1, 3, 7 and 30 days after expiry. After 60 days it goes quiet — a document two months expired is not solved by one more notification.
- Pending transfers — The banners on the home screen, updated live.
What does not notify
Worth knowing as much as what does:
- The console sends no notifications and receives no push. The bell in its header reads the same data, but only while it is open.
- An item with no return date can never become overdue. The date is optional at handover, and without it the whole 09:00 mechanism stays silent for that item.
- An item with no price does not enter the value-at-risk figures, so it does not appear in value-based alerts.
- Deletions do not notify. They stay in the history but announce nothing.
Language
All server alerts go out in the company's language, not each user's — one setting, made by the administrator. The interface stays in whatever language each person chose. See chapter 15.