Industry News
Enterprise People Counting Without the IT Project (2026)
Fleet-wide foot traffic rollouts used to take quarters. Dor's new analysis shows how anonymous, wireless sensors cut enterprise people counting deployments to weeks — with no cameras and no PII.
7 min read ·
Key Takeaways
- Enterprise retailers measure e-commerce to the pixel but go dark in-store — traffic is the largest unmeasured variable across a store fleet.
- Typical retail analytics rollouts run 4–6 months mid-scale and 8–12+ months at full enterprise scale; the counting is easy, the deployment is what stalls.
- Camera and Wi-Fi based counters add site surveys, cabling, network access, and privacy reviews at every single door.
- Anonymous infrared sensors collect no images or personal data, which shortens legal and security review under GDPR, CCPA, and the EU AI Act.
- Wireless, cellular, peel-and-stick hardware turns a multi-quarter construction project into a shipping-and-mounting exercise measurable in weeks.
- Counting only pays off when it is joined to POS, labor, marketing, and weather data — and pushed into the BI tools teams already use.
Dor published a piece on 15 September 2026 titled Enterprise People Counting Without the IT Project, and it names the thing most multi-site retailers quietly accept: the reason large chains still do not measure in-store traffic has almost nothing to do with the counting technology, and almost everything to do with how painful it is to deploy across hundreds of doors. We read it, checked it against what we see in vendor deployments, and it holds up.
The Enterprise Blind Spot
A large retailer can recite its online funnel from memory — sessions, add-to-cart rate, checkout conversion, cost per acquisition. Then a shopper walks into a physical store and the telemetry stops. The point-of-sale system is excellent at reporting what sold and completely silent on what did not: the visitor who came in, waited, could not find help, and left empty-handed.
Without an entry count you cannot calculate conversion rate, which is the single metric that separates a traffic problem from an execution problem. You cannot tell whether a campaign pulled people through the door or simply coincided with good weather. And you cannot benchmark locations honestly, because raw sales flatter high-traffic stores and hide the ones converting at a fraction of their potential. For one shop that is a missed opportunity. Across a fleet it is a reporting gap that touches operations, marketing, merchandising, real estate, and finance simultaneously.
Why Rollouts Stall at Scale
Dor cites implementation guidance putting a mid-scale retail analytics rollout at four to six months, and a full enterprise programme with real-time data and governance at eight to twelve months or more. The delays are not mathematical. They come from integrating with legacy POS and ERP systems, cleaning up data quality, and the change management needed to pull teams off spreadsheets.
Then there is hardware. Traditional camera and Wi-Fi counters are not peel-and-stick. Each door typically needs a site survey, mounted hardware, power cabling, a network connection, router configuration, and a security review. Once, that is an afternoon. Across two hundred locations — each with its own contractor scheduling, landlord approvals, and IT tickets — it becomes a programme measured in quarters. Momentum dies, only part of the fleet gets instrumented, and the data that does arrive is late and incomplete.
| Deployment step | Camera / Wi-Fi counter | Anonymous wireless sensor |
|---|---|---|
| Site survey | Usually required per door | Not required |
| Power & cabling | Electrical work, contractor visit | Battery powered |
| Network access | Store LAN / Wi-Fi provisioning | Own cellular link |
| Security review | Common before go-live | Rarely triggered |
| Privacy / notice process | Often required | No personal data collected |
| Realistic fleet timeline | Months to quarters | Weeks |
Privacy as a Deployment Cost
The point we think enterprise buyers most often underrate: privacy review is not only an ethics question, it is a schedule line item. Even when a camera vendor processes anonymously at the edge, a lens at the doorway still raises questions a legal or security team must answer — what is captured, where it is processed, how it is secured, whether local rules require signage. Under GDPR, CCPA, and the widening patchwork of US state privacy laws, systems capable of biometric identification also land in the higher-risk tiers of frameworks like the EU AI Act.
An anonymous infrared sensor registers that a person crossed a threshold and nothing else. No images, no faces, no identifiable data. There is nothing to anonymise, no footage to secure, and no employee notification to negotiate. "We collect no personal data" is a dramatically shorter review than explaining how personal data will be handled — and at fleet scale you avoid repeating that review in every jurisdiction you operate in. Our sensor technology comparison covers the accuracy trade-offs that come with that choice.
Weeks, Not Quarters
Strip out the cabling, the network dependency, and the privacy review and the deployment maths changes. Dor's sensor is battery powered and peel-and-stick, mounts on any doorway without wiring or a contractor, and connects over its own cellular link — so it never touches the store network or waits on IT to provision access. A store manager can mount it and have it counting the same day.
Across a fleet that converts a multi-quarter hardware project into a shipping-and-mounting exercise you can run in parallel. No per-site construction to schedule, no reason to instrument stores one painful batch at a time, and a region can go live in weeks — which is the entire point of instrumenting a fleet rather than a pilot handful of stores.
Anonymous wireless sensors at enterprise scale
Pros
- No cameras, no PII, shorter legal and security review
- No cabling, contractors, or landlord construction approvals
- Cellular connectivity bypasses store IT entirely
- Parallel rollout — whole regions live in weeks
- API access pushes traffic and conversion into existing BI tools
Cons
- Doorway counting only — no in-store zone or dwell heatmaps
- No demographics or staff-exclusion via video analytics
- Battery replacement becomes a light recurring task across large fleets
- Very wide or unusual entrances may need multiple units
What the Data Unlocks
Counting is the foundation, not the finish line. A traffic number alone says a store was busy; it does not say why, or whether busy became revenue. Paired with POS data you get conversion rate, revenue per visitor, transactions, and average transaction value per store and fleet-wide. That is the difference between "traffic dipped 8% last week" and "traffic held steady but conversion fell in twelve stores, all of which cut weekend staff."
- Operations staff to real traffic curves instead of gut feel, protecting conversion during peak hours.
- Marketing attributes campaigns to in-store lift rather than assuming it.
- Merchandising and real estate benchmark locations on conversion, not just raw sales.
- Finance quantifies the revenue attached to conversion swings before rolling changes fleet-wide.
The last mile matters as much as the sensor. If the numbers live in yet another login nobody opens, adoption dies. An API that feeds foot traffic and conversion into the warehouse and dashboards analysts already use is what keeps an analytics programme alive past month three.
Our Take
Dor has an obvious interest in this argument — it sells the wireless, anonymous sensor the piece describes. That said, the underlying claim matches what we hear repeatedly from multi-site buyers: enterprise people counting projects rarely fail on accuracy, they fail on rollout friction. Any evaluation of a fleet-wide deployment should score installation effort, network dependency, and privacy review load alongside the accuracy spec, because those are the variables that decide whether store number forty ever gets instrumented.
Read the original on getdor.com. To weigh it against other options, see our Dor vendor profile, put it head to head in the vendor comparison tool, check real budgets in the cost guide, or run the 2-minute recommender quiz if you are still narrowing the field.