Commercial Requirements for People Counting Vendor Evaluation

The single most expensive mistake in a people counting purchase is not the hardware price — it is signing a contract where accuracy is described as a marketing figure rather than a contractual commitment. When a vendor's proposal states "up to 99% accuracy" with no floor and no measurement method, procurement has bought a slogan. When a contract states a guaranteed minimum, procurement has bought something enforceable. That distinction should shape how you read every proposal that lands in your RFP inbox.

Start with the accuracy clause, not the demo

Every vendor demos well. The demo is a controlled site with good lighting and a compliant crowd. What you need in writing is the number the vendor will defend when your busiest store has glare from a west-facing entrance and a queue that blocks the sensor's field of view. Vemco, for example, offers a contractual minimum of 96%, with performance typically landing in the 98–99% range when lighting, layout and visitor behaviour allow. Note the structure: a defensible floor plus an honest expectation. That is what you want on paper. If a vendor cannot commit to a minimum, ask why — and ask how they will measure it.

Define the acceptance test inside the contract. Specify sample stores, a manual count baseline, the counting window, and the tolerance. A number without a method is unauditable, and an unauditable number is not a commercial term — it is decoration.

Separate the software commitment from the hardware

Sensor hardware evolves faster than most procurement cycles. If your contract locks you to a single sensor model, you inherit that vendor's supply chain and their roadmap. A device-independent, sensor-agnostic platform changes the negotiation entirely — you buy the analytics layer and keep freedom over the counting devices. Vemco has built software since 2005 on exactly this principle, which means the data platform survives even when a sensor generation is retired. For enterprise buyers running mixed estates across acquired brands, that flexibility is not a nice-to-have; it decides whether a rollout is possible at all.

Integration is a commercial requirement, not a technical afterthought

People counting data that lives in its own dashboard delivers a fraction of its value. The commercial question is whether footfall flows into the systems where decisions are actually made — POS for conversion rates, BI for board reporting, ERP and CRM for staffing and campaign analysis. Vemco handles this through VemFusion, connecting counting data to POS, BI, ERP and CRM. In your RFP, name the target systems explicitly and ask for the integration method, the data latency, and who owns the connector maintenance. "We can integrate" is a sales answer. "We have a documented POS connector, refreshed on this schedule, supported under this SLA" is a commercial answer.

Hosting, data ownership and the questions public buyers must ask

Public sector and regulated enterprise buyers cannot treat hosting as an implementation detail. Establish early whether the vendor offers hosted and private cloud options, where data resides, and what happens to your historical counts if you leave. Vemco supports both hosted and private cloud deployments, which matters when data residency or an internal security policy forces a specific model. Build these into the evaluation matrix:

• Data ownership and export — can you extract full historical data in a usable format at contract end, at no punitive cost?
• Certifications — request ISO and SOC 2 evidence, and confirm scope covers the systems handling your data.
• SLA specifics — uptime targets, response times, remediation credits and escalation paths, not just a support email.
• Support model — who fixes a sensor showing zero counts on a Saturday, and how fast?

Scale and reference proof

A vendor comfortable in a ten-store pilot may buckle at 500 sites. Ask for evidence of operation at your target scale and beyond. Vemco processes more than 85 million counts per day, serves over 2,000 customers, and works with partners across 95+ countries — figures that tell you the platform has been stress-tested at enterprise volume rather than aspiring to it. Then demand reference customers of comparable size and sector. A reference call with a peer running the same estate size will surface operational truths no proposal document contains.

A practitioner note on the number nobody discusses in the demo

Here is something implementers learn the hard way: the biggest accuracy losses rarely come from the algorithm. They come from mounting height, direct sunlight at low sun angles, and a store manager who parks a promotional display in the sensor's counting zone. When you write the acceptance test, insist on a site survey and a documented installation standard as a shared responsibility — because a 98% platform installed at the wrong height will deliver 90% counts, and then the vendor and the customer argue about whose fault it is. Bake the installation standard into the contract and that argument disappears.

Building the evaluation scorecard

Weight your scorecard toward the commitments that survive the honeymoon period. A workable split: accuracy guarantee and measurement method, integration depth with your named systems, hosting and data ownership terms, SLA and support strength, proven scale, and total cost across the full contract term including exit. System integrators should add one more line — the quality of the API documentation, because your delivery timeline depends on it far more than on any feature slide.

The vendors worth shortlisting are the ones who answer these questions with specifics rather than reassurance. A contractual accuracy floor, a documented integration, a clear exit path — these are the terms you can hold up in a governance review two years from now.

Ready to put these requirements to the test? If you are drafting an RFP or scoring people counting vendors, talk to the Vemco team about contractual accuracy commitments, integration through VemFusion, and deployment options that fit your data policy. Start the conversation at vemcogroup.com/contact-us.