AisleWatch AI

AisleWatch AI / How it works

How AisleWatch runs on the cameras a store already has.

AisleWatch reads your CCTV on a server in the store or in the cloud. It alerts store teams as things happen, and it keeps the cases, audit packs and footfall reports.

  1. Cameras

    Your CCTV, NVR or VMS streams over RTSP or ONVIF.

  2. On-site server or hosted

    On the on-site server, detection keeps running and alerting when the store internet drops.

  3. Alerts to the right person

    Each alert goes to the store team first, then the store manager and the area manager.

  4. Cases and reports

    A person approves each case record, audit pack and footfall report.

Deployment

Each retailer chooses where footage is processed, store by store.

On-site server

With the on-site server, footage is processed and stored in your store. The server sits in the store comms room or your data centre, sized to the camera count.

Hosted

Hosting suits stores with a steady internet link. Stores with a weak link use the on-site server, so alerts keep running offline.

Pilot and rollout

An AisleWatch pilot runs for 8 weeks on up to 10 cameras in one or two stores. The fee is fixed up front and credited if you roll out. The go or no-go call is made in writing against measures agreed at the start.

Download the pilot scorecard template (PDF)

Integrations

Alerts go where store teams already work. Links are by API unless named, and each till event is matched to the video.

Cameras, NVR and VMSLive and recorded streams over RTSP or ONVIF; events back to the VMS by API
POSSales, refunds, voids and no-sale opens, by API or export
Workforce and task appsTasks, rosters and staffing levels, by API
Alarm receiving centresAfter-hours alerts with the clip, by API
Microsoft Teams, SMS and emailAlerts to a person or a store channel, and reports
Mobile app pushAlerts with the clip, as an option
BI toolsFootfall, conversion and dwell data, by API or export

Data and security

Deployments are set up in line with Singapore's PDPA, Saudi Arabia's PDPL and UAE data protection law.

Where footage is processed

Hosting is on Microsoft Azure in the Singapore region. Saudi and UAE customers can host in-country or on site. Only alert clips and chosen events reach the dashboard.

Pilot footage

Pilot footage is covered by an NDA and a data processing agreement. It is deleted at the end of the agreed review period.

People and watchlists

Faces are blurred in every shared clip by default. The optional watchlist is switched on only by the retailer, and it stays off in the EU and Australia.

Integrators and partners

Security integrators and facility managers can run AisleWatch on the cameras they look after for retail and mall clients. Partner pilots follow the same terms as direct pilots. In the Gulf, AisleWatch is delivered with local partners.

hello@aislewatch.ai

Which cameras does AisleWatch work with?

AisleWatch works with most IP cameras, NVRs and VMS platforms that provide RTSP or ONVIF streams. Each stream is checked in the first review, and any camera to move or add is named before the pilot.

What happens when the store internet drops?

On the on-site server, detection and alerts keep running, and the store dashboard keeps working on the local network. The central dashboard catches up when the link returns.

Is store footage used to train models?

Store footage is used to train models only with the retailer's written agreement. Without it, footage is used for alerts, cases and reports only.

How is face recognition handled?

Face recognition is off by default, and only the retailer can turn on the watchlist.

Who can see the footage?

Access is set by role, and every view and export is logged.

See a sample store report from one day of your own footage.

AisleWatch returns the alerts one day of your footage would have raised.