Notifications
What Kassly alerts you about, who gets each alert, and the one setting that changes when they fire.
5 min read · Updated 26 Sep 2026
On this page
Kassly tells you when something needs your attention — stock running out, a shift closed, a cashier asking to void a sale. This page lists every alert it sends, who receives it, and what makes it fire.
There is no notification preferences screen. Alerts are not individually switchable, and there is no per-user opt-out. Kassly decides who gets what from your role and your branch. If an alert is noisy, the fix is in the underlying data — a reorder point set too high, for example — not in a preferences page.
Where notifications appear
The bell in the top bar. It shows an unread count and lists your 20 most recent notifications. Tapping one marks it read; Mark all read clears the count.
New notifications arrive live, without a page refresh, as long as you have an internet connection.
On your phone. If you have signed in to the Kassly app on a phone or tablet, the same alerts arrive as push notifications, so they reach you when the app is closed. Nothing to set up — the app registers the device when you sign in. Sign out and that device stops receiving them.
Who gets what
Alerts go to owners and managers, never to cashiers or staff. The split is:
- Owners get everything for the whole store, across all branches.
- Managers get alerts for the branches they are assigned to.
- The person who caused an alert does not get pinged by it. A cashier's void request notifies the managers, not the cashier; the cashier who closes a shift does not get their own shift-closed alert.
Every alert Kassly sends
| Alert | Fires when |
|---|---|
| Low Stock Alert | A product with a reorder point set falls to or below it — after a sale, or after a stock movement |
| Stock Oversold | A sale takes an item below zero, or below what confirmed sales orders have reserved. One notification per request lists up to five items; an offline batch syncing at once sends one. An item already below zero doesn't notify again. See When stock goes below zero |
| Large Transaction | A single sale totals ₱10,000 or more |
| Shift Closed | A cashier ends a shift, with the sales total in the message |
| Expiry Alert | A daily 8:00am check finds product batches expiring within 7 days |
| Sale needs attention | A synced sale's payments do not cover its total, so it has no receipt and is missing from your reports |
| Void approval requested | A cashier asks to void a sale and cannot do it themselves |
| Approval approved / rejected / changes requested | Someone acts on a request you filed |
| Cheque due | A post-dated cheque is due for deposit, or is overdue. Checked daily at 8:00am. |
| Production order filed / ready | A commissary production order is filed, or a sales order's production is ready |
| Membership | A membership lapses on the daily stale-membership sweep |
| Billing | Something happens to your subscription — a trial ending, a renewal, a failed payment |
Some of these only exist if you have the relevant add-on. Expiry alerts need batch tracking, cheque reminders need receivables, commissary alerts need warehouse and commissary. See Plans and add-ons.
What controls the low-stock alert
The alert fires off each product's own reorder point, compared against that branch's quantity on hand. Two consequences worth knowing:
- A product with no reorder point never raises a low-stock alert. However low it gets. If you are not getting alerts, this is almost always why.
- The right reorder point differs wildly per product. A store selling 200 sachets a day and two cases of soft drinks a week should not use the same number for both.
Set them per product — see Stock levels.
Settings → Store Settings → Operational Settings also carries a Low Stock Threshold field, defaulting to 10. It is a store-wide default figure; it does not substitute for a missing reorder point, so do not rely on it to start your alerts.
Large Transaction fires at ₱10,000 and that figure is fixed. If most of your sales are above it, expect the alert most of the day.
Emails Kassly sends you
Notifications are in-app. Kassly also sends email, and email is used for a different set of things:
| When | |
|---|---|
| Verify your email address | At signup |
| Add-on or bundle subscription confirmed | When you subscribe |
| Renewal invoice | Before a renewal falls due |
| Trial expiring / trial expired | Near the end of an add-on or bundle trial |
| Cancellation confirmed | When you cancel an add-on |
| Report subscription | On the schedule you set — see Exporting reports |
| Order confirmation and one-time codes | To your customers, for online-store orders |
Billing and trial emails go to the store owner. You cannot switch these off — they are the record of what you are being charged for.
If notifications stop arriving
Work down this list:
- Check your role. Cashiers and staff never receive notifications. Managers and owners do.
- Check your branch. A manager only gets alerts for their assigned branches — see Users and roles.
- Check your connection. Live delivery needs internet. The alerts are still stored, so they appear in the bell the next time you are online.
- Check the phone. Push notifications need the app's notification permission granted in the phone's own settings, and they only go to devices that are still signed in.
- Reload the back office. The live channel reconnects on page load.
Nothing is lost if delivery fails — every notification is written to your inbox first and pushed second.