Service counter needs review
Under review- Site
- Riverside
- Zone
- Service desk
- Time
- Evidence
- Clip attached
Illustrative alert — sample data
Platform
A structured approach to retail video intelligence — from compatible cameras and site-specific detection to event review, reporting and operational workflows.
Illustrative interface — layout concept with sample values; it is not a customer deployment or a performance claim
The short version
The architecture below is the same journey at engineering resolution. Start here.
Assess which cameras can be reached, and how.
Choose the zones and rules that matter per site.
See events with time, place and evidence attached.
Compare before and after, site by site.
See what a camera view actually reports — zone by zone, with the boundary stated.

Architecture
Each stage hands something concrete to the next. The last stage is always a human decision, recorded so it can be reviewed later.
Compatible existing cameras, assessed for stream access and placement.
Video reached by a validated method - direct IP, encoder, or NVR/VMS access.
Object and event models applied to the zones you have defined.
Your thresholds, schedules, exceptions and escalation conditions.
Timestamp, camera, zone and review status, with evidence attached.
Routed to an authorised reviewer, or rolled into a trend report.
A person decides, records the action taken, and the trail is kept.
Roles and least privilege, retention periods, auditability, your own configuration, and a defined support process - applied across every stage above, not bolted on at the end.
Conceptual architecture — final deployment varies by site, camera estate and agreed scope
How it is built
IP cameras, encoders, and NVR or VMS access by validated methods. There is no promise of universal plug-and-play compatibility, because that promise would not survive contact with a real camera estate.
Object and event models, the regions and zones you define, and the frame and event logic that connects them. Solution-specific availability is disclosed only once it has been tested.
Your operational thresholds, schedules, exceptions and escalation conditions. The rules are yours; we do not impose a default definition of what counts as a problem.
Timestamp, camera and zone, confidence or review status, and safe access to approved snippets where that has been deployed. An event without evidence is just an assertion.
Store and site comparison, operational trend interpretation, human review, and reporting you can configure. This is the layer an operator actually lives in.
Roles and least privilege, data retention, auditability, your own configuration, and a defined support process. Applied across every layer above.
Modules
A feature grid with every row ticked tells you nothing. This lists the same modules with their actual status, including the ones that need validating on your sites first.
Service counter needs review
Under reviewIllustrative alert — sample data
Event Review
Authorised teams review a defined event with its timestamp, camera and context, record the action taken, and keep an audit trail.
Confirmed for your sites during a scoped pilot before it informs decisions.
Location Dashboard
Compare locations on consistent definitions where data is sufficient. Role permissions and tenant separation are configured as part of the deployment.
Confirmed for your sites during a scoped pilot before it informs decisions.
Configurable Alerts
Event rules can raise a timestamped alert to an authorised reviewer. End-to-end timing is measured for your site during a pilot.
Confirmed for your sites during a scoped pilot before it informs decisions.
Trend Reports
Visit and occupancy counting where the camera view supports it. Accuracy is benchmarked against a manually reviewed sample before any number is used for decisions.
Confirmed for your sites during a scoped pilot before it informs decisions.
Integration Readiness
A specific POS connection is reviewed for compatibility and documented in the deployment scope. Sightora does not claim universal POS support.
Confirmed for your sites during a scoped pilot before it informs decisions.
Pilot Measurement
Queue events against a defined threshold, where camera geometry allows the queue to be seen. Start and end logic is agreed with you in writing.
Confirmed for your sites during a scoped pilot before it informs decisions.
Governance
Roles and least privilege are configured for your organisation, not assumed. Retention periods are set deliberately and are part of the deployment agreement rather than a default nobody chose.
Access and review activity are auditable, which matters when an incident decision is questioned months later. The support process and escalation path are defined before go-live.
A technical assessment is the honest first step. It establishes what your existing cameras can and cannot support before anyone discusses scope.
Book a Demo