Monitor Voids and Discounts Across Every Franchise Location

Voids, comps, and discount overrides are the primary mechanisms of transactional theft in franchise operations. They're also normal business occurrences—which is why they're so easy to hide in aggregate. Ezra doesn't flag every void. It flags the patterns: the employee whose void rate is 3x their peers, the shift where discount percentages consistently spike, the location where cash variance tracks with manager override volume.

Why Voids and Discounts Are the Primary Theft Vectors

Transactional theft in service businesses most commonly operates through voids (reversing paid transactions and pocketing the cash), unauthorized comps (giving free service in exchange for cash payments outside the system), and discount abuse (applying unauthorized discounts to friends or family). All three leave traces in transaction data. Ezra finds them.

Pattern Detection vs. Individual Flag Review

Reviewing individual void transactions is inefficient and ineffective. A manager who voids three transactions on a busy Saturday is probably correcting errors. A manager whose void rate is 4x the network average across 30 shifts is a different signal. Ezra's anomaly detection operates on patterns, not individual transactions—surfacing the meaningful signals without burying operators in noise.

Six Detection Surfaces for Transactional Anomalies

Ezra monitors voids, manager overrides, comps, discount percentages, cash variance, and productivity anomalies. Each surface is tracked against location-specific baselines with configurable thresholds. Anomalies are surfaced as a triaged feed—the highest-risk flags first—with direct links to the source POS record for investigation.

From Flag to Investigation Without Spreadsheets

Traditional exception reporting requires pulling a report, exporting it, filtering it, and then locating the relevant transactions in the POS for investigation. Ezra shortcuts this entire process: each flag links directly to the source POS record. Investigation starts the moment the flag appears.

Configurable Thresholds Reduce Alert Fatigue

Not every void is theft. Ezra's thresholds are operator-validated and configurable per location—so the void rate that triggers a flag at a low-volume boutique location is different from the threshold at a high-volume flagship. Alert fatigue is the enemy of operator trust; meaningful thresholds are the solution.

Frequently Asked Questions

Does Ezra flag every void, or only unusual patterns?: Ezra flags patterns, not individual transactions. A single void is not a flag. A void rate that significantly exceeds a specific employee's or location's historical baseline is a flag.
Can I configure how sensitive the void monitoring is?: Yes. All thresholds are configurable per location and detection surface. High-volume locations can have higher void-rate thresholds that still reflect meaningful anomalies for their operating context.
Does Ezra connect to the POS record when it flags a void?: Yes. Every anomaly flag links directly to the source POS record—no spreadsheet forensics required to investigate.
What is the difference between a comp and an unauthorized void?: Comps (complimentary services or products) are a legitimate business practice. Unauthorized comps—those given outside normal authorization parameters or at unusually high rates—are a theft signal. Ezra monitors comp patterns alongside void patterns.
Is void and discount monitoring live today?: Yes. Ezra Loss Prevention (Module 01) is live in production on Zenoti, including void, discount, and override monitoring.

Find the Discount and Void Patterns Before They Compound

Ezra Loss Prevention is live today. Let us show you the anomaly feed from your locations in the first two weeks.

See Ezra in Action Talk to the team →