How Much Does Retail Loss Prevention Software Cost in 2026?
$90,000 to $600,000 spans the category, with $90,000 to $180,000 buying a first release in 14 to 20 weeks and $250,000 to $600,000 buying a full platform phased across 9 to 15 months.
On this page
$90,000 to $600,000 spans the category, with $90,000 to $180,000 buying a first release in 14 to 20 weeks and $250,000 to $600,000 buying a full platform phased across 9 to 15 months. The single largest cost variable is how many distinct video platforms sit in your estate, because each one is a separate integration measured in weeks and some older recorders expose no usable interface at all, which turns an integration into a hardware conversation. One modern video platform across the chain might add $25,000. Three platforms inherited from acquisitions will add closer to $80,000 and are the main reason video correlation belongs in phase two rather than phase one.
The bands a loss prevention build falls into
Below $90,000 you are buying exception reporting rather than building it, and for a chain under about 40 stores that is unambiguously the right decision. Agilence or Appriss Retail plus a disciplined store audit calendar will surface more than your team can work.
The first band, $90,000 to $180,000 over 14 to 20 weeks, buys a system investigators work inside daily rather than a dashboard they check. Exception rules written against your own point of sale (POS), returns and fulfilment data with your own override reason codes. A real case file with an evidence chain, file hashing at ingest, append only evidence entries and immutable access logging. Entity resolution linking suspects, vehicles, phone numbers and loyalty accounts across stores.
The second band, $250,000 to $600,000 phased over 9 to 15 months, adds video correlation with clock drift handling, electronic article surveillance and self checkout vision events on the same timeline, civil recovery and restitution tracking, store audit workflows, and shrink attribution reporting that separates theft from process loss.
Above $600,000 you are describing a chain past a thousand stores where the data volume itself becomes an engineering problem, or a multi banner group where two asset protection organisations have to share one platform without sharing their cases.
What drives a loss prevention build up
Video platform count. Each platform is a distinct integration with its own export mechanism, its own retention behaviour and its own clock. Milestone and Genetec expose usable interfaces. A proprietary recorder from a chain you acquired in 2019 may expose nothing documented, and the honest answer there is replacement or manual export.
Point of sale heterogeneity. Two journal formats means two parsers and two sets of rules that must produce comparable exceptions. An Oracle Retail Xstore journal is a different problem from an NCR or Toshiba one, and a quote that says integrations without naming the vendor and version is not a quote.
Data volume. A 500 store chain generates a transaction line volume that forces a columnar store rather than a general purpose database, and that architectural decision has a real cost attached that only appears above a certain scale.
Legal review. Retention and access design is not optional when the records are discoverable. Your counsel needs to be in the design conversation, and their time is a project cost.
Fulfilment event integration. Joining order management pick, pack and handoff events to point of sale and returns is what lets you write the omnichannel rules that actually matter, and it is a separate system with a separate owner.
What keeps the number down
Start with returns and refund abuse at your worst 30 stores. It is usually the fastest recoverable money, it proves the case model before anyone spends on video, and it gives your investigators a working tool inside four months.
Defer video correlation to phase two without exception. Video is the feature everybody asks for first and the one with the most integration risk, and a case file with clean evidence handling is worth more than a correlated clip in a system nobody trusts.
Parse one point of sale journal format in release one, even if you run two. The second parser is far cheaper once the rule engine and case model exist, and you learn what your rules actually need from the first.
Bring legal counsel into the first design session rather than the final review. Retention rules and access policy shape the data model, and discovering a retention requirement after the storage design is settled is expensive rework.
Keep the executive attribution reporting for later. It is the feature that wins the next budget argument, and it depends on receiving variance and damage coding that you probably are not capturing yet, so it belongs after the operational system is running.
A worked example that adds up
A 340 store chain with two point of sale journal formats following an acquisition, three video platforms in the estate, an order management system handling buy online pick up in store, and investigators currently assembling case packages by hand. Here is a first release.
- Discovery plus retention and access design with your counsel: $11,000
- Point of sale and returns ingestion, two journal parsers: $30,000
- Exception rule engine written against your own policy fields and override reason codes: $26,000
- Case file with evidence chain, hashing at ingest, append only entries and immutable access logging: $34,000
- Entity resolution across suspects, vehicles, phone numbers, addresses and loyalty accounts: $24,000
- Fulfilment event join from order management for omnichannel refund rules: $18,000
- Deployment, role based access, retention policy enforcement: $9,000
That totals $152,000 across 18 weeks. The case file and entity resolution lines together are more than a third of the build, which is the correct shape, because those are the two features that turn scattered incidents into a case a prosecutor will accept.
Phase two adds video correlation with clock drift handling across three platforms at $78,000, electronic article surveillance and self checkout vision event ingestion at $26,000, civil recovery and restitution tracking at $30,000, store audit workflows at $28,000, shrink attribution reporting at $44,000 and a columnar analytics store for the transaction volume at $32,000. That is $238,000 more, taking the chain to $390,000 over roughly thirteen months.
How the spend phases
Pay against cases, not against screens. Fifteen percent at kickoff for discovery and the legal design work. Then three delivery points: exception rules producing flags your investigators agree are worth working, a case file holding a real organised retail crime case end to end with evidence that survives review, and entity resolution linking incidents across at least two districts that nobody had previously connected.
Hold the last 10 percent until the first case package assembled entirely in the system has been reviewed by your counsel or a prosecutor contact. That is the only acceptance test that matters in this category, because the whole purpose of the build is a package that holds up.
Phase the video work separately with its own contract and its own milestone per platform. Video integrations fail for reasons outside anyone's control, usually an undocumented recorder, and you should not have your core build hostage to that.
The ongoing costs nobody quotes
Hosting and storage is the unusual line here. Transaction data is large and evidence is larger, and evidence retention periods are set by legal requirement rather than by convenience. Expect $800 to $3,500 a month for a chain of a few hundred stores once video clips attached to cases are being retained, and understand that this number grows as cases accumulate rather than staying flat.
Maintenance at 15 to 20 percent of build cost is $23,000 to $30,000 a year on a $152,000 first release. That covers security patching, rule tuning and the steady stream of changes from investigators using the system.
Then the category specific costs. Every point of sale upgrade risks a journal format change, which breaks parsers. Every new video platform, whether from an acquisition or a refresh, is a fresh integration. Legal review recurs whenever retention law or your own policy changes. And rule maintenance is continuous: your fraud patterns move when your policies move, so somebody has to own the rule set the way somebody owns a pricing file.
Budget investigator time for exception review as well. The system finds more than the old process did, which is the point, and finding more means working more.
Comparing a build against your current renewal
Use your own contracted figure. Exception reporting platforms price against store count and transaction volume and are negotiated, so a published number would tell you nothing about your position.
Add four things. Annual platform licensing. The professional services you buy to tune rules. The investigator hours spent assembling case packages by hand, which in the teams we have built for runs six to twelve hours per organised retail crime package. And the cases lost entirely, whether to recorder overwrite before a clip was pulled or to an evidence chain nobody was willing to take forward.
That last item is the one that changes the arithmetic and the one nobody counts. A chain that loses a handful of significant cases a year to preservation failures is carrying a cost that no reporting subscription addresses.
Suppose licensing plus services plus investigator assembly time comes to $120,000 a year. Over five years that is $600,000 against a $152,000 build plus $27,000 a year, so $287,000. The build wins and you own the evidence. At $40,000 a year with a small team and a modern single vendor estate, buying wins clearly and we would say so.
When buying beats building
Buy if you are under roughly 40 stores. Agilence or Appriss Retail plus a store audit programme will surface more exceptions than your team can act on, and a build would be spending capital to avoid a subscription. Appriss Retail is particularly strong on return behaviour because it sees a consortium view you cannot replicate at any budget, which is a genuine reason to keep it even alongside a build.
Buy if your shrink is concentrated in receiving and damages rather than theft, because your fix is a process and a scale at the back door, not software. Buy if your video estate is a single modern platform and your point of sale is one vendor across the chain, since the integration pain that justifies a build is largely absent.
Build when two or more of these hold: investigators assemble case packages by hand and cases are being lost to recorder overwrite, you run more than one journal format or more than two video platforms, your loss is organised rather than opportunistic and needs cross store linking, your return policy has enough exceptions that vendor rules cannot express it, or a prosecutor has asked you for something you could not produce. That last one is the moment most chains we work with pick up the phone.
If you want that decision made properly rather than quickly, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- Criteo's Global Commerce Review found retail apps convert at 18% versus 4% on mobile web (roughly 4.5x), and travel apps convert at 20% versus 6% on mobile web (about 3.3x). Source: Criteo (2017) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
Frequently asked questions
What is the total cost of custom loss prevention software for a 300 store chain?
A first release with exception rules against your own point of sale and returns data plus a real case file and evidence chain runs $90,000 to $180,000 over 14 to 20 weeks in Digital Heroes delivery experience. A full platform adding video correlation, cross store organised retail crime linking and restitution tracking runs $250,000 to $600,000 phased over 9 to 15 months.
A representative 340 store chain with two journal formats and three video platforms lands near $152,000 for the first release and around $390,000 for the full platform. Video platform count is the largest single variable at that size.
What does it cost to run each year?
Hosting and storage is the unusual line: $800 to $3,500 a month for a few hundred stores once evidence clips attached to open cases are retained, and it grows as cases accumulate rather than staying flat. Maintenance at 15 to 20 percent of build cost is $23,000 to $30,000 a year on a $152,000 build.
Rule maintenance is continuous and belongs in the budget as staff time. Your fraud patterns move when your policies move, so the rule set needs an owner the way a pricing file needs an owner. Point of sale upgrades also break journal parsers on someone else's release schedule.
How long does it take to build a loss prevention case management system?
Fourteen to twenty weeks for a working first release covering exception rules, case files and the evidence chain. Video correlation adds meaningfully and should be a separate phase with its own milestone per platform, because each integration is real weeks and older recorders sometimes have no usable interface at all.
The fastest projects start with returns and refund abuse at the worst thirty stores. That proves the case model before anyone spends on integrations and puts a working tool in investigators' hands inside four months.
Is Agilence or Appriss Retail cheaper than building?
Under roughly 40 stores, clearly yes, and we would tell you so before quoting. Appriss Retail is also worth keeping alongside a build at any size because it sees a consortium view of return behaviour that you cannot replicate at any budget.
The comparison shifts when you count investigator hours. Assembling a single organised retail crime package by hand runs six to twelve hours in the teams we have built for, and cases lost to recorder overwrite before a clip was pulled cost more than any subscription. Run the arithmetic on your own contracted figure plus those two items.
Why does video correlation cost so much?
Because the unglamorous parts are the work. Measuring and correcting clock drift per device, mapping cameras to registers so a transaction resolves to the right lane view without a human choosing, retrieving clips by transaction rather than by timestamp, and automatically pulling and retaining clips attached to open cases before the recorder overwrites them.
One modern platform across the chain might add $25,000. Three platforms inherited from acquisitions will add closer to $80,000, and a proprietary recorder with no documented interface may not be integrable at all, in which case the honest options are replacement or manual export.
Can we cut cost by using our existing exception reporting alongside a build?
Yes, and it is often the right structure. Keep Appriss Retail scoring returns, because the consortium view is genuinely unavailable elsewhere, and build the case management, entity resolution and evidence chain that no exception reporting tool owns.
That splits the spend sensibly: the subscription buys you scoring you could not replicate, and the build buys you the case object your investigators actually work. It also removes the pressure to rebuild rules that are already working, which is where a lot of budget gets wasted in this category.
What does the evidence chain add to the build cost?
Roughly $30,000 to $40,000 in a typical first release, and it is the line you should refuse to cut. Hashing every file at ingest, append only evidence entries, immutable access logging showing who viewed what and when, and retention policy enforced per record type are what make a package survive a defence attorney reading it.
Involve your counsel in that design from the first session rather than the final review, because retention and access requirements shape the data model. Discovering a requirement after the storage design is settled turns a design decision into rework across everything.
How much does shrink attribution reporting cost, and is it worth it?
Around $40,000 to $50,000 as a phase two component, and it depends on capturing receiving variance at the door against the advance ship notice plus coded damage and markdown events with a photo and an employee attached. Without that upstream capture there is nothing to attribute.
It is worth it when your budget conversations keep stalling on how much of shrink is actually theft. Once the number decomposes by cause, store, category and shift, the investment argument changes from more guards everywhere to a specific intervention at specific sites.
Who owns the code and the evidence if an agency builds this?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm, in the contract before kickoff. At Digital Heroes the client owns the code from the first commit.
This matters more here than almost anywhere else, because the system holds evidence and access logs you may need to produce in court. A developer who wants to keep the repository or host it under their own accounts is asking you to accept a dependency inside your chain of custody, and that is not a negotiable point.
When is it time to move from Excel reports to an actual dashboard?
The reliable signal is when someone spends more than a few hours a week copying data between spreadsheets, or when two teams arrive at a meeting with different numbers for the same metric. At that point the spreadsheet is acting as an unversioned, single-person database, and a costly error is a matter of time. A first dashboard that automates those recurring reports typically pays for itself in recovered hours within the first year.
Is Tableau worth $75 per user per month, or should we build our own dashboard?
If you have analysts who explore data visually all day, Tableau Creator at $75 per user per month earns its price, and Viewer seats at $15 keep the total reasonable for a small team. The math flips once you have hundreds of viewers or need dashboards inside a customer-facing product, because per-seat pricing scales with your audience while a custom build does not. Run the 3-year seat cost before deciding; that horizon usually makes the answer obvious.
What should the first version of a dashboard include, and what can wait?
Version one should answer 5 to 7 questions your team already asks every week, pull from your 2 or 3 most important data sources, and refresh daily. Real-time data, custom report builders, scheduled email exports, and write-back features can all wait for version two. Across our projects, teams that launch a narrow version one reach a dashboard people actually use roughly twice as fast as teams that try to cover every department at once.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
How much does a custom BI dashboard cost for a small business?
For a small business, a focused first dashboard typically runs $25,000 to $60,000 when it covers 2 or 3 data sources, daily refresh, and 5 to 7 core metrics. Across 2,000+ Digital Heroes projects, budgets climb past that only when real-time data, complex permissions, or customer-facing access enters the scope. If a quote for a simple internal dashboard exceeds $75,000, ask exactly which of those three is pushing it there.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other business intelligence dashboards companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
