Product feature
Owners and dashboard operators
Notifications
A real-time owner notification system for important business events, unread state, deep links, settings, browser push, and bell previews.
Overview
Notifications keep the owner aware of what is happening inside the business. In a system where AI can reply, customers can place orders, and operators may be away from the dashboard, important events need a reliable path back to the person responsible for the business.
The released notification surface includes a full notifications page, a topbar bell preview, unread counts, mark-read controls, live socket updates, notification settings, and browser push subscription support. It is designed to work both while the owner is inside the dashboard and when the owner needs an offline browser push.
How It Works
The notifications route is business-scoped and guarded by the NOTIFICATIONS feature flag. Both the full page and the dashboard bell read the same owner notification cache for the active business. Marking a single notification as read or marking all as read updates the shared state.
Live notification frames are mounted once in the dashboard shell. New frames are validated, deduplicated, prepended to the cache, and surfaced through toast and sound feedback. Because the page and bell share the same cache, both update together.
Notification settings live under the settings area. Owners can enable or disable notifications, control per-kind preferences, subscribe the current browser for push delivery, and test push delivery.
Components
Notification Feed
The feed presents unread and read notifications in one place. Each row can deep-link to the relevant order, customer, or business path after marking the notification read.
Dashboard Bell
The bell gives a compact preview in the persistent dashboard shell. It uses the same data as the full feed, which keeps unread state consistent across the product.
Live Updates
The notification socket patches the RTK Query cache as new frames arrive. Duplicate or malformed frames are ignored, while valid new frames increase the unread count and trigger local feedback.
Push Settings
Push subscription support lets the server deliver notifications when the dashboard is not actively open. The browser subscription is registered through the service worker and stored through the push API.
Operating Proof
The operating proof is event visibility. Important activity moves into the feed, dashboard bell, unread state, and push settings so the owner can notice work without keeping every module open.
Related Pages
- Feature: Order Management
- Feature: Customer Management
- Feature: Dashboard Analytics