Exception Based Reporting for Loss Prevention: A Guide for Multi-Unit Operators
Savi
If you run more than a handful of locations, you already know the problem: your cameras are recording everything, but nobody has time to watch any of it. That's exactly the gap exception based reporting loss prevention software is built to close. Instead of asking a manager or loss prevention analyst to scrub through hours of footage hoping to spot something wrong, exception based reporting flags the transactions and moments that actually look suspicious, so your team spends its time investigating, not searching.
For operators managing shrink, food cost, and internal theft across a growing footprint, this shift matters more than it sounds. The math of watching video doesn't scale past a few sites. The math of reviewing a short list of flagged exceptions does.
How Exception Based Reporting Works
At its core, exception based reporting loss prevention software looks for the transactions and behaviors that fall outside a location's normal pattern: excessive voids, no-sale drawer opens, discounts stacked on discounts, cash drawer activity at odd hours, or a register that behaves differently than every other register in the same daypart. Instead of a flat video feed, you get a list. That list is the exception report, and it's the difference between "watch everything" and "look at this."
The best systems pair that transaction-level signal with the video itself, so a flagged exception isn't just a line in a spreadsheet, it's a clip you can pull up and confirm in seconds. That pairing is what turns a data anomaly into an actionable, defensible finding, rather than a hunch.
This is where the loss prevention audience overlaps with operations and IT. The same event that surfaces internal loss also tells an ops leader something about training or process, and it tells IT that one connected system, not five disconnected ones, produced the answer.
Why Reviewing Every Frame of Video Doesn't Scale
Think about the math at even a modest multi-unit brand. Ten locations, each running twelve or more hours a day, produce more footage in a week than any regional LP manager could review in a month. Add more sites and the gap widens, not narrows. Manual review isn't just slow, it's reactive: by the time someone finally watches the tape, the loss has already happened dozens more times.
Exception based reporting loss prevention software flips that order of operations. It surfaces the moments worth watching before a human ever presses play. That's the same principle Savi customers use in the field today. FiiZ Drinks used video paired with Event Search to uncover $3,250 in internal loss in its first 90 days on the platform, not by reviewing footage end to end, but by following the transactions that didn't look right. Scooter's Coffee franchisee Craig Schroeder caught $3,500 in internal theft in a similar 90-day window and added 1.41% back to gross sales, prompting his own verdict: "This system pays for itself."
Those aren't abstract savings. They're the direct result of turning a review problem into a search problem, at a scale a manager can actually act on.
What Good Exception Based Reporting Looks Like Across Locations
Single-site loss prevention is one thing. Multi-unit loss prevention is a different problem entirely, because the real signal often isn't inside one store, it's in the comparison across stores. A void rate that looks normal at one location might be an outlier when benchmarked against 40 sister locations running the same daypart and menu. That cross-location visibility is exactly what a fragmented, on-premise camera setup can't deliver, and it's exactly what a cloud platform is built for.
This is also where IT stakeholders get pulled into a conversation that started in loss prevention. A Burger King franchisee found that consolidating onto a single cloud platform eliminated an IT bottleneck and gave GMs and DMs org-wide video access, described by the franchisee as "essentially a Google Search for our operations." When exception based reporting sits on top of that kind of consolidated architecture, an LP lead isn't waiting on IT to pull footage from a DVR at a random site. The exception, the clip, and the context are already in one place.
Marco's Pizza took a similar consolidation approach for a different reason, rolling cloud video out to more than 1,000 locations in under six months and saving $500K in equipment, labor, and deployment costs in the process. The lesson for loss prevention leaders is the same one IT and operations learned: the platform decision underneath exception based reporting matters as much as the reporting itself.
The Platform Behind the Exceptions
Exception based reporting is only as good as the data feeding it, and that data comes from the same cloud video foundation that powers everything else a multi-unit brand needs from its cameras. Savi's edge device syncs footage and transaction data from every site to the cloud, which means the dataset that flags a suspicious void today is the same dataset that can support drive-thru speed analytics, brand compliance checks, or training review tomorrow, without adding new hardware or re-wiring a single site. Loss prevention, operations, IT, and training all draw from that same source. As computer vision and AI capabilities continue to advance, that shared foundation is what lets a brand adopt new detection and insight tools without ripping out what's already on the wall. It's a foundation decision, not a point solution.
Key Takeaways
Exception based reporting loss prevention software flags suspicious transactions and behaviors automatically, so teams review a short list instead of hours of raw footage.
Pairing transaction exceptions with matching video clips turns anomalies into evidence a manager can confirm in seconds.
Real customer results back this up: FiiZ Drinks found $3,250 in internal loss and Scooter's Coffee caught $3,500 in theft, both within 90 days.
Cross-location benchmarking, not just single-site review, is where multi-unit loss prevention finds its sharpest signals.
A cloud video foundation, like the one behind Marco's Pizza's 1,000+ location rollout and a Burger King franchisee's consolidated IT setup, is what makes exception based reporting scale across a growing brand.
Ready to see what exception based reporting could surface at your locations? See how Savi works, request a demo.
