Existing but unmet customer, guest, or order demand. It disappears without leaving any trace in the system.
Unmet interestUnmet product demand
Decision: When to increase capacity and stock
PLATFORM
The layer that turns observation into decision
ODAQ combines footage from your existing cameras with your business data (POS, ERP, shift) to turn it into events that drive operational decisions. Footage is processed on-site throughout this process; it never moves to the center.
Request a demoHOW IT WORKS
The camera observes the event, business data gives it meaning
The edge device produces structured events from footage; these events are correlated with business data (POS, ERP, shift) and tied to one of four loss families, turning into a decision. Signal details are covered in the technical fit conversation.
The time between demand and service, vehicle and service, material and the line. The longer it stretches, the more it turns into loss.
Service delayService wait time
Decision: Which step needs extra staff or a process change
The point where flow gets stuck: a queue, a checkout, a dock, a line. One point slows the entire operation.
QueueLine stoppage
Decision: Where to route resources (staff, checkout, dock)
The unused capacity of space, team, and time. Invisible, but billed every month.
Space utilizationTable turnover
Decision: Which area or shift to shrink or redesign
ARCHITECTURE
Footage is processed on-site; only the event goes to the center.
Camera streams and business systems (POS, ERP, shift, WMS) converge at the on-site ODAQ Edge. Footage is processed there and never leaves the site; only structured event data reaches the central platform.
ARCHITECTURE
ON-SITE↓ ↓
Existing cameras / NVRRTSP stream
Business systemsPOS · ERP · shift · WMS
ODAQ EdgeFootage is processed here and never leaves the site; the event is correlated with business data at this stage
only structured event data ↓
CENTER
ODAQ PlatformAnalysis, action, reporting
raw footage: noneALERT FATIGUE
Not every event is a notification
The system doesn't forward every event it observes to the team. Repeated and non-priority events are evaluated in the background; only situations that require action reach the team as a notification. The details of the suppression and prioritization logic are covered in the technical fit conversation.
Event flowDEMO DATA
- Observed eventbackground
- Repeated / non-prioritysuppressed
- Requires actionsent to team
OPERATING CONDITIONS
What we measure, what we don't
Every measurement system has a limit. What sets us apart isn't hiding the limit — it's saying exactly where it is and what we do at that point.
- 01Measurement accuracy depends on camera angle. Before installation, we determine what each camera can measure, signal by signal; if the angle isn't suitable, we either recommend repositioning or state in writing that we don't measure that signal on that camera.
- 02Accuracy drops in low light. We don't hide this: when light falls below the threshold, the affected signal is marked “not measured” and no estimate is produced.
- 03In dense crowds, distinguishing overlapping people becomes harder. As density increases, flow measurement takes precedence over counting; which measurement is valid at which threshold is set during installation.
- 04Not every camera can produce every signal. During the site survey, we evaluate your existing cameras signal by signal and state in writing what each one can measure.
- 05A new location requires a short calibration period. References are established during this period; the system does not update its own reference on its own.
- 06Outdoors, weather conditions affect visibility. Data from the affected camera during that period is excluded from the report.
- 07The camera doesn't hear. Verbal requests are not measured directly; they are derived from the intersection of behavioral signal and business data.
- 08Results are probabilistic. ODAQ produces a measurable estimate, not certainty.
COMPARISON
Different approaches, different visibility
A comparison by approach category, not specific products.
| Store/space analytics platforms | Analytics add-on on top of VMS | Embedded on-camera analytics | ODAQ | |
|---|---|---|---|---|
| Setup time and complexity | Medium — usually requires its own hardware and integration | Medium — depends on the existing VMS; requires licensing and configuration | Fast — per-camera, no central integration required | Medium — works with existing cameras, requires business-data integration |
| Real-time visibility | Usually available, in a dashboard | Depends on the add-on | Per camera, no central view | Continuous, event-based |
| Correlation with business data | Rare — requires platform-specific integration | None | None | Yes — POS, ERP, shift data |
| Action recommendation | Limited — mostly reporting, not action recommendation | None | None | Yes |
| Works with existing camera infrastructure | Usually requires its own hardware | Depends on the existing VMS | Only with supported camera models | Works with existing cameras |
| Raw footage leaving the site | Depends on provider, mostly cloud | Usually stays local | Stays on the camera | None — only event data |
| Multi-location comparison | Yes — a strength of most platforms | Limited | None — isolated per camera | Yes |
| Evidence and reporting | Dashboard report | Add-on report | Per-camera log | Structured report |
Turn focus into the right action.
ODAQ tracks events, explains the cause of loss, and triggers the right action. Operations improve; sales and efficiency increase.
Request a demo