Why Discounts and Voids in CrescendPOS Require Manager Approval

The Feature Nobody Asks For (Until They Need It)

No one opens a cafe and thinks: "I can't wait to add approval steps to my cashier workflow." Approvals feel bureaucratic. They slow things down. They imply you don't trust your team.

And yet, manager approval for discounts and voids is one of the features we hear the most positive feedback about — usually from owners who initially resisted it. The reason is simple: it solves a problem that's invisible until it costs you real money.

The Problem: What Happens Without Gates

When any cashier can apply any discount and void any order without oversight, three things tend to happen:

The "friend" discount. A cashier's friend comes in, and the cashier applies a 20% discount. Then another friend. Then a regular they're friendly with. None of these are authorized, but each one individually looks small. Over a month, it adds up.

The cover-up void. A cashier makes a mistake — charges the wrong item, double-charges a customer, or messes up a payment split. Instead of calling a manager, they void the order and redo it. The mistake is fixed, but the original error disappears from the record. If this happens repeatedly with the same cashier, you'd want to know — but without an audit trail, you can't.

The theft pattern. This is the one nobody wants to talk about, but it's real. A cashier completes a cash order, then voids it and pockets the cash. On paper, the order never happened. In practice, you're missing revenue you'll never notice because there's no record.

We're not saying your cashiers are doing any of these things. But if you have no system to detect them, you also have no way to confirm they're not happening. And as your business grows and you add more cashiers, "I trust everyone" becomes harder to maintain.

How the Approval Flow Works

In CrescendPOS, certain actions require a manager PIN before they can proceed:

• Applying a discount — the cashier selects the discount type and amount, but it doesn't apply until a manager enters their PIN on the same device.
• Voiding an order that has already been sent to the kitchen — the cashier initiates the void and provides a reason, but it only goes through after a manager PIN.
• Closing a shift with significant cash variance — if the cash in the drawer doesn't match what the system expects (beyond a small threshold), manager approval is required to close.

The flow is designed to be fast: the cashier taps the action, the manager walks over and enters their 4-digit PIN on the numpad, and it's done. In practice, this takes about 5 seconds.

The Trade-Off: Speed vs Visibility

Let's be honest about the trade-off. Every approval step is friction. During a rush, that 5 seconds matters. If the manager is in the back doing prep, the cashier has to wait or call them over.

We thought hard about this. Here's why we landed where we did:

Discounts and voids are rare relative to total transactions. In a typical shift, a cashier might process 50-100 orders but only need to apply 1-3 discounts or voids. The approval step affects a tiny fraction of transactions, not every one.

The cost of one undetected issue outweighs hundreds of 5-second delays. A single cashier quietly voiding one cash order per shift costs you much more per month than the cumulative time spent on PIN entries.

The PIN isn't about blocking — it's about recording. The goal isn't to prevent managers from approving discounts. It's to ensure that every discount and void has a named manager who approved it, a timestamp, and a reason. The approval almost always goes through. But now there's a record.

What the Audit Trail Reveals

Once you have approval data flowing, patterns emerge that you couldn't see before:

Discount frequency by cashier. If one cashier applies three times more discounts than others working the same shift, that's a conversation worth having. Maybe they're too generous. Maybe they're handling a customer segment that expects discounts. Either way, you want to know.

Void timing. Voids that happen right after a cash payment — and before the next customer — look different from voids that happen because a customer changed their order. The pattern tells the story.

Manager approval patterns. If one manager approves everything without question and another actually reviews the reason before approving, that difference shows up in the data. You can coach accordingly.

Discount ROI. If you're giving discounts to drive repeat visits, the data tells you whether those discounted customers actually come back. Without tracking who approved what and why, you're flying blind on whether your discounts are investments or just losses.

Why "Just Trust Your Cashiers" Doesn't Scale

When you have one cashier and you're standing right there, trust is sufficient. You see everything. You know when a discount is given and why.

But the moment you have two cashiers, or you're not always on the floor, or you open a second location — trust alone isn't enough. Not because your people are dishonest, but because you physically can't observe everything anymore.

Systems aren't a substitute for trust — they're a complement to it. The best teams have both: mutual trust AND transparent systems. The system isn't there because you suspect wrongdoing. It's there so that when nothing is wrong, you can see that nothing is wrong.

How We Balanced It

We made several design choices to keep the approval step as lightweight as possible:

• PIN, not password. A 4-digit PIN on a numpad is much faster than typing a password. The manager doesn't need to log in — just enter their PIN and go.
• Same device. The manager enters their PIN on the cashier's tablet. No need to switch to a different device or screen.
• Reason is required but brief. The cashier provides a short reason ("customer complaint", "wrong item", "loyalty discount") — enough for the audit trail without slowing things down.
• Only for high-risk actions. Adding items, taking payments, opening the cash drawer for a sale — these don't need approval. We only gate the actions that have actual financial risk.

What Owners Tell Us

The most common feedback we get, from owners who've been using the approval flow for a while: "I didn't think I needed it, but now I'd never go back."

It's not about catching bad behavior — though it does that too. It's about the peace of mind that comes from knowing your discount and void activity is visible, recorded, and attributable. When you review your shift reports and see exactly which discounts were given, by whom, approved by whom, and for what reason — that's a level of operational clarity that changes how you manage your business.

Five seconds per approval. Complete visibility in return. That's the trade-off, and we think it's worth it.