Trigo is a storewide loss prevention layer that runs on the cameras a store already has and integrates with the till. Switching is rarely about the cameras, then: it is about whether checkout loss stays its own vendor or becomes one agent among safety, operations and perimeter ones on the same feeds. Here is the plan, phase by phase.
Both platforms read the cameras a store already owns, so the switch changes what sits behind them and what happens once something is spotted. Both rows describe what each vendor publishes.
Four moments when retail teams running a checkout-focused loss tool start this conversation. If none of them are true, staying put is a reasonable answer.
Trigo's published set is checkout-shaped: hidden products, self-checkout non-scan, checkout skipping, manned checkout monitoring and Scan and Go losses. That is a precise answer to a precise problem. When the loss shifts to the stockroom door, the delivery bay or an after-hours entry, none of it is in scope and the answer is another vendor on the same cameras.
Trigo documents staff receiving instant notifications with clear video evidence for intervention. That is the right design when the store is staffed and someone can walk over. It does the least on a thin shift, at a self-checkout bank with one attendant or after closing. If your worst events happen when nobody is free to respond, the gap is in what happens next.
No safety, operations or perimeter detection set appears on Trigo's site. So the moment EHS asks about spills and blocked exits, or operations asks why the morning open runs long, that is a second platform reading the same feeds. Two vendors on one camera estate is a workable answer. It is worth pricing against one platform that covers both before you commit to it.
Renewal is the cheapest moment to compare, because a platform decision is already open and nobody has to manufacture a reason to look. Ask both vendors to quote the identical store list, broken out into software, any on-site hardware, installation and integration work, then to state plainly what is still not covered afterwards.
The structural differences that decide whether a switch is worth starting.
Swipe the table sideways to see every column.
Trigo data comes from Trigo's own public loss prevention, technology and IMPACT pages, read August 2026. Where Trigo publishes nothing, this table says so rather than guessing.
A rollout that keeps coverage live throughout. Most sites go live inside six weeks.
Map what Trigo is actually watching per store: which cameras feed it, which checkout lanes and self-checkout banks are in scope and what the on-site workstation is connected to. Then map the integration work separately, because the point of sale and self-checkout links are the part with real effort behind them and they are a separate conversation from the video. Finish with the open cases that still need footage.
Run one store on both at once for a fortnight. Trigo keeps notifying while Spot AI reads the same feeds, so the comparison happens on your own floor rather than in a demo. Pick a store with a real self-checkout problem and extend the pilot cameras past the lanes to the stockroom door and the delivery bay, because the difference between a checkout tool and a storewide platform only shows up where the checkout tool was never pointed.
Move store by store rather than chain-wide, keeping Trigo live at each store until its replacement has run a full week. Cameras do not move and cabling does not change, so a store cutover is a configuration change plus an IVR. Retire the on-site workstation only after that store has signed off, and sequence the point of sale integration ahead of the video cutover rather than alongside it, because it is the piece most likely to need a vendor on a call.
Once checkout coverage is stable, the work moves to what the old scope excluded. Add the safety and operations agents on the same feeds, build an Iris detection for something specific to your format and decide what should fire on site after closing rather than waiting for a member of staff to read a notification that nobody is there to act on.
The six that come up in every one of these conversations.
Most switches start before the contract ends, because assess and pilot cost little and the comparison is more honest with both live. Run the pilot on one store during the overlap and time the chain-wide cutover to the renewal date rather than paying twice across every location.
No, and the plan makes that structural rather than a promise. Trigo keeps notifying at each store until its replacement has run a full week, the cameras never move and stores cut over one at a time. If a store fails its sign-off test, that store stays where it is while the others proceed.
That work is real and it is worth sequencing around rather than repeating in a rush. Treat the transaction link as its own workstream in the assess phase, land it before the video cutover at each store and keep the old integration live until the new one has matched it on the same lanes for a week.
Camera reuse is common ground, so it is not the reason to move. What changes is scope and response: checkout loss becomes one agent among safety, operations and perimeter ones on the same feeds, and something can happen on site at the moment of a detection without a member of staff being free to walk over.
Trigo does not publish where video is processed or stored, or for how long, so that answer has to come from your account team in writing rather than from a website. Ask for it during assess, export what open cases need before the contract lapses and confirm the format the investigation records come out in.
Anyone answering without two quotes is guessing. The structural difference is what the money buys: a checkout-shaped detection set against a platform that also covers safety, operations and the perimeter on the same feeds. Quote both on the identical store list, and count the vendors still needed afterwards on each side.
Bring a camera list and we will tell you what works as it is.
Customer-reported outcomes from named Spot AI customers.
Staccato went from first conversation to full deployment across an 800-acre campus in seven weeks, on the camera infrastructure it already had.
Bridge33 Capital standardized video across 25 plus properties, each acquisition arriving with a different camera system, and cut footage search from hours to minutes.
The YMCA of Greater Richmond deployed 17 locations in two weeks and standardized retention across the estate.
"Within four minutes of the alarm going off, Spot AI gave us video footage of the incident on the responding officers' phones. We had five recoveries within the hour."
No. Trigo states universal compatibility with any camera system regardless of brand, and Spot AI is camera agnostic in the same way: any IP camera speaking ONVIF or RTSP works as it is, with legacy analog coming in through the Intelligent Video Recorder. Nothing on the wall moves and no coax is pulled.
Most estates are live inside six weeks: a week to assess, a fortnight of pilot on one store, then store-by-store cutover. Trigo publishes its own deployments as typically two weeks, so the two are comparable in shape, and the timeline scales with store count rather than camera count.
Trigo lists a single small on-premise workstation per store in its typical requirements. It stays in place through the pilot and comes out only once that store has passed sign-off. Spot AI does not need it: the Intelligent Video Recorder connects to the existing camera network directly.
Yes, and the plan depends on it. The pilot phase runs one store on both at once so detection quality and what happens after a detection can be compared on identical footage. Trigo keeps running at every store until that store's replacement has passed a full week of sign-off.
Scope and response. Trigo detects checkout-shaped loss and sends staff a notification with video evidence. Spot AI runs 15+ pre-trained agents spanning security, safety and operations on the same feeds, with AI Talk Down, strobes and horns through standard speakers already on site and full-resolution video staying on the Intelligent Video Recorder.