Why We Built a Notification Center (and What We Learned)

If you've ever used any SaaS application, you're familiar with the bell icon in the top right corner. Notification center. A feature that seems "basic" — until you don't have one and realize how much you needed it.

This is the story of why we decided to build a notification center in CrescendPOS, what we learned in the process, and why it turned out to be more than just "a bell with a red badge."

The Problem We Were Trying to Solve

In a single-cashier operation, communication is simple — all information lives in one person's head. But once you have more than one cashier, more than one shift, and a manager who isn't always on-site, information starts falling through the cracks.

Real situations we observed:

• Manager approves a void from home, but the cashier doesn't know if it's been approved yet. They send a message. Manager replies late. Customer waits.
• Morning shift closes with a cash discrepancy. Afternoon shift only finds out when they close their own shift and the numbers don't match — but the discrepancy was from the previous shift.
• Owner invites a new manager via email. Email goes to spam. Manager never joins. Owner thinks they're not interested.

All of these are problems of information not reaching the right person at the right time.

Why Not Just Use WhatsApp?

Fair question. Many F&B businesses run 100% of their internal communication through chat groups. And it works — until it doesn't.

Problems with messaging apps for operational notifications:

• Noise. Group chats mix everything: operational info, small talk, memes, complaints — important information gets buried.
• Not actionable. "Manager, there's a void request" in a chat doesn't have an approve button. You have to open another app, find the transaction, then approve.
• No clean audit trail. Who got what notification, when, and whether it was acted on — impossible to track in a messaging app.
• Personal boundaries. Messaging apps are personal tools. Work notifications coming through at 11 PM is invasive.

We're not anti-messaging. But operational notifications that need action and require an audit trail need a dedicated channel.

Three Channels, Three Purposes

We ended up building the notification center with three complementary channels:

1. In-App (The Bell)

Notifications that appear inside the CrescendPOS application. Bell icon with a red badge number — classic, and there's a reason every app uses this pattern: people already understand how to interact with it.

When used: Information that needs to be seen when the user opens the app. Approval requests, status updates, system announcements.

What we learned: In-app notifications only work if the user opens the app. For cashiers who are in front of the tablet all day, this is perfect. But for managers or owners who only open the app occasionally, in-app alone isn't enough.

2. Web Push Notifications

Browser push notifications that appear on the tablet or laptop, even when the app isn't in the foreground.

When used: Time-sensitive information that needs immediate attention. "A void request is waiting for approval" — this can't wait until the manager happens to open the app.

What we learned: Push notifications are powerful but must be very selective. Too frequent, and people disable them. We had to define a hierarchy: what's important enough for push, and what's fine as in-app only.

3. Email Digest

Periodic summaries sent via email.

When used: Information that's not urgent but needs to be known. Shift summaries, weekly reports, invitation reminders.

What we learned: Email is the most "patient" channel — people read it when they want to. But precisely because of that, emails need to be well-structured. Walls of text won't get read. Bullet points, clear sections, and one call-to-action per email — that's what we optimized for.

Non-Obvious Design Decisions

Grouping, Not Flooding

Initially, every event generated one notification. Predictably, if there were 10 transactions in the morning shift, the manager got 10 notifications. Annoying.

We switched to grouping: similar notifications are bundled into one. "3 void requests waiting for approval" is more useful than three separate notifications saying the same thing.

Read/Unread That Means Something

This sounds trivial but it isn't. In many notification centers, "read" just means "the user clicked on it." But in an operational context, "seen" and "acted on" are two different things.

We ended up making actionable notifications (like approval requests) stay prominent until they're actually resolved — not just clicked.

Per-User Preferences

Not everyone needs every notification. A cashier doesn't need to know about subscription billing. An owner might not need push notifications for every order — but definitely wants to know about a significant cash discrepancy.

We built a preference system that lets each user configure which channels they want for which types of notifications.

What Changed After Launch

Before the notification center, a lot of operational information traveled through informal channels — messaging apps, verbal communication, or even sticky notes at the register. The problem wasn't that these channels are bad, but that there's no record and nothing is trackable.

After the notification center went live:

• Approval workflows got faster. Void requests, cash drawer adjustments, and actions requiring manager approval now have a dedicated channel with push notifications. No more back-and-forth messaging.
• Cross-shift information became more reliable. End-of-shift notifications ensure the next shift knows the previous state.
• Off-site owners maintained visibility. Without having to ask via chat, notifications come in as configured.

What's Not Perfect Yet

Honestly, our notification center isn't perfect. Some things we're still iterating on:

• Noise calibration. Finding the sweet spot between "informative" and "annoying" is an ongoing process. Too many notifications = ignored. Too few = important info missed.
• Mobile experience. Web push notifications on Android tablets sometimes have their own quirks. This is an area we're still polishing.

Takeaway for F&B Businesses

If you run an F&B business with more than one cashier or more than one shift, how information flows through your team is just as important as how money flows. Information that's late, lost, or doesn't reach the right person — that's an invisible but real operational cost.

Our notification center was built from real problems we observed in F&B operations. Not because every app needs a bell icon, but because multi-cashier businesses need an operational communication channel that's reliable, trackable, and not invasive.