SentrixShield
Home Platform Solutions Pricing Trust Company Contact Book a scan
Home/Solutions
Solutions

The same engine. Nine sectors. Completely different questions.

We do not sell a retail product and a restaurant product. We sell one platform and a starting set of watches per sector — because a twin makes a new question nearly free, the vertical is a configuration, not a codebase.

Sector 01

Retail, kirana & supermarkets

The money leaks where the owner is not standing.

In a shop the constraint is almost never demand — it is the twenty minutes a day when the queue outruns the counter and people put things down and leave. That is invisible from behind the till and obvious from above.

Start with these four

A retail checkout counter with a till

The billing counter is the whole business

Queue depth, coverage gaps and abandonment all live in one three-metre region.

QueueDepth & wait at the till
ShelfStock-out & refill latency
FunnelEnter → reach → transact
LayoutDisplay engagement A/B
Sector 02

Restaurants, cafés & QSR

Everyone blames the kitchen. It is usually the fifteen minutes after the bill.

Table turn is the single number that decides a busy evening's revenue, and it decomposes into three intervals that nobody measures: seated-to-first-contact, dining, and bill-to-vacated. Two of the three are service problems, not cooking problems.

Start with these four

A restaurant dining room with laid tables

Turn time is three intervals, not one

Only one of them happens in the kitchen.

TurnTable cycle by section
LatencySeated → first service
PassTicket → plate collected
HygieneCompliance at the pass
Sector 03

Schools, colleges & hostels

Configured conservatively by default, and we will not budge on it.

Education is the sector where our privacy position stops being marketing and starts being the reason a deployment is permissible at all. Campus sites ship with aggregate-only counting, no demographic estimation, a fourteen-day retention default, and a parent-notice pack you can send home before the first camera is connected.

Start with these four

A school classroom with students

Counting, never identifying

Aggregate headcount, congestion and after-hours presence. No recognition of any individual.

Education defaults

Demographic estimationDisabled
Default retention14 days
Clip attachmentOff unless enabled per watch
Parent-notice packIncluded
Also deployed in

Six more places a twin pays for itself

Pharmacy shelving stocked with medicines

Pharmacies & clinics

Waiting-room dignity and controlled-substance discipline, without watching patients.

  • Waiting-room dwell and consultation start latency
  • Restricted-cabinet access outside permitted hours
  • Counter coverage during the evening rush
  • Occupancy against seating capacity
Gym floor with exercise equipment

Gyms & studios

Equipment utilisation is the only honest input to a capex decision.

  • Utilisation per machine zone, by hour
  • Peak-hour floor density against capacity
  • Unattended weight-floor alerts after hours
  • Class-studio occupancy versus bookings
Warehouse interior with racking

Warehousing & light manufacturing

Small units, no WMS, and a dock that is either empty or chaos.

  • Dock dwell and vehicle turnaround time
  • Aisle obstruction and forklift-path conflict
  • PPE compliance in designated zones
  • Bay occupancy and put-away latency
Interior of a small salon with styling chairs and a mirrored wall

Showrooms & salons

Long consideration cycles, few walk-ins, every one of them expensive.

  • Time-to-greet after a customer enters
  • Dwell per product zone and per display
  • Chair or bay utilisation through the day
  • Walk-in to consultation conversion
A restaurant rendered as a point-cloud twin

Hotels & banquet halls

Front desk, lobby and function space, measured rather than guessed.

  • Check-in queue depth at arrival peaks
  • Lobby dwell and seating utilisation
  • Banquet turnaround between functions
  • Service-corridor obstruction alerts
A campus corridor rendered as a point-cloud twin

Multi-site operators

Every site gets its own twin. Watches are templated and pushed across the estate.

  • Estate rollup ranked on any metric
  • Outlier detection — which branch is different, and how
  • One watch definition, deployed everywhere at once
  • Per-site and per-region access control
At a glance

Which watches matter where

SectorPrimary watchSecond watchUsual first alertTypical cameras
Retail & kiranaQueue depth at billingEntry-to-purchase funnelCounter unstaffed 5 min4–8
Restaurants & QSRTable turn by sectionSeated → first servicePlate held 4 min at pass6–12
Schools & collegesGate headcountCorridor congestionAfter-hours block entry8–24
Pharmacies & clinicsWaiting-room dwellCounter coverageRestricted cabinet access3–6
Gyms & studiosZone utilisationPeak floor densityLone user after hours4–10
WarehousingDock dwellAisle obstructionPPE non-compliance6–16
Showrooms & salonsTime-to-greetZone dwellWalk-in unattended 3 min3–8
HotelsCheck-in queueLobby utilisationService corridor blocked8–20

Camera counts are the range we typically see at single-site deployments; they are not a requirement. The platform runs from a single camera upward.

Not sure which four watches to start with?

Tell us what kind of site you run and what is annoying you. We will tell you what we would watch first — before you commit to anything.