Notification centre
The bell in the header is the history of everything StorePilot has told you — across every site you can see, in one place.
This is not the same thing as notification channels. Those decide where an alert is delivered — Slack, Telegram, email, a webhook. The notification centre is what the platform recorded, and it is written whether or not you have configured any channel at all.
That distinction is deliberate. If the feed only held what was delivered, a site with no Slack and no email would have an empty bell forever — which looks exactly like a site where nothing has happened.
What lands there
| Notice | When |
|---|---|
| New error | The first time a fault is seen, or when a fixed one comes back |
| Error spike | Errors in one hour rise far above the site's own trailing average |
| Site down / back up | The uptime monitor opens or closes an incident |
| New lead | A form submission is captured |
| Order paid | A checkout completes and the money arrives |
| Approaching the plan limit | Usage crosses a warning threshold for the month |
| Scheduled export ready | A generated file is available to download |
| Support replied | Someone from StorePilot answered your request |
Silenced errors are the one exception: if you mute an issue, or snooze it until a date, it stops appearing here too. Muting is a statement about the news itself, not about a channel.
Reading it
- The badge counts what you have not read. Read state is per person — a colleague opening a notice does not mark it read for you.
- The bell's panel shows only what is unread. It is your queue, not the history: once you have read a notice it leaves the panel, and when nothing is left the panel says so rather than showing you notices you have already dealt with. Everything read is still on the account page.
- Opening a notification marks it read and takes you to the thing it is about.
- It works the other way round too. Opening the issue, the lead, the abandoned cart or the chat itself also clears the notice about it — you never have to read the same thing twice, once on the page and once in the bell.
- That link runs one way only. Marking a row unread again in a list is about your own triage queue and does not bring the notice back; and Mark all read here clears the bell without touching the unread dots on your lists.
- A paid-order notice points at the checkout it came from, so it is the cart that clears it — the same place the notice itself links to.
- Mark all read clears the current view — in the bell that empties the panel. If there are more than the server will do in one press, it says so and you can press again.
- The full history is at Notifications in the account area, where you can filter by site or show only unread.
How long it is kept
Notifications are kept for 90 days. The thing a notice points at — the error, the incident, the lead — keeps its own, longer retention; the notice is only the pointer.