Enterprise FAQ for Shopping Mall Analytics

The questions that stall a mall analytics rollout are almost never about the technology. In our experience across enterprise deployments, the sticking points are contractual accuracy language, who owns tenant data, and whether the operations team will actually open the dashboard after week three. This FAQ answers the questions we hear from procurement teams, tenant coordinators, IT departments and mall managers once they have moved past the introductory articles and started negotiating real budgets.

What accuracy should we demand in the contract?

Insist on a written, contractual minimum — not a marketing number. Vemco commits to a contractual minimum of 96% counting accuracy, and in practice delivers 98–99% when conditions allow: adequate lighting, sensible sensor placement relative to the entrance layout, and typical visitor behaviour. Be suspicious of any vendor quoting a flat 99% guarantee with no conditions attached; entrances with revolving doors, strong backlighting from glass façades, or trolleys and pushchairs will affect any sensor. The right question is not "what accuracy do you claim?" but "what accuracy will you sign for, and how is it audited?" A proper audit uses manual verification counts against sensor data over agreed time windows, documented and repeatable.

Why do our tenant traffic numbers and our mall totals never match?

This is the single most common support ticket in mall analytics, and it is usually not an error. Mall entrance counts measure unique building entries; the sum of tenant store entries will always be higher because one visitor enters multiple stores. If a shopper visits four stores, the tenant total records four entries against one mall entry. Support teams should build this explanation into onboarding material, because tenants raise it constantly. The useful metric is the ratio itself — store entries divided by mall entries gives you a capture rate per tenant, which is far more actionable than either raw number alone.

How does tenant revenue collection actually work at scale?

Manually chasing monthly sales declarations from 150 tenants is where most turnover-rent models quietly break down. Late submissions, spreadsheet formats that change every quarter, and figures that mysteriously arrive rounded — every mall finance team knows this pain. This is exactly what VemTenant automates alongside VemCount: traffic counting and tenant revenue management run in one system, so turnover rent calculations, sales-per-square-metre reporting and conversion figures are generated from the same data pipeline rather than reconciled by hand. For enterprise portfolios, the practical benefit is that leasing, finance and operations stop arguing about whose spreadsheet is correct.

Can we benchmark tenants against each other fairly?

Yes, if you compare the right things. Raw sales comparisons between a jeweller and a fast-fashion anchor are meaningless. Benchmarking becomes fair when you compare conversion, sales and engagement within peer groups: same category, similar floor position, comparable frontage. Vemco's benchmarking does this across tenants, and mature mall operators use it in lease renewal conversations. A tenant with strong footfall but weak conversion has an in-store execution problem; a tenant with weak footfall but high conversion may deserve a better location or reduced rent pressure. That distinction is worth real money in negotiations, and you cannot make it with sales data alone.

What should IT ask before signing?

• Data residency and GDPR: Confirm sensors count anonymously without storing identifiable images, and confirm where processed data is hosted.
• API access: Your BI team will eventually want raw data in Power BI or your data warehouse. Confirm the API is documented, versioned and included in the licence, not sold separately later.
• Network requirements: Sensors need PoE and outbound connectivity. Agree early whether they sit on a segregated VLAN — retrofitting this after installation is expensive.
• Sensor health monitoring: Ask how offline sensors are detected and how data gaps are backfilled or flagged. Silent sensor failure is worse than obvious failure.

How do we know the platform will scale across our portfolio?

Ask for evidence of production volume, not architecture diagrams. Vemco has operated since 2005, serves more than 2,000 customers across 95+ countries, and processes over 85 million counts per day — millions of precise data points daily across global sites. For a multi-property owner, the relevant scaling questions are organisational: can you set portfolio-wide KPI definitions so "conversion" means the same thing in every mall, can regional managers see only their properties, and can head office roll everything up without exporting to Excel? Get a live demo of the permission model with your own org chart, not a sample account.

What does implementation really involve?

Here is the observation every experienced implementer will confirm: the sensor installation is the easy part; the entrance mapping workshop is where projects succeed or fail. Before a single sensor goes up, someone who knows the building must walk every entrance and decide what counts as "inside" — the loading dock staff use as a shortcut, the cinema entrance open two hours after retail closes, the connecting corridor to the car park. Skip that workshop and you will spend six months explaining anomalies in your data instead of acting on it. Budget a proper site survey, agree the counting logic in writing, and run a two-week validation period comparing manual counts against sensor output before declaring go-live.

How do we prove ROI to the budget owner?

Tie the business case to three concrete levers. First, turnover rent accuracy: automated tenant revenue reporting closes the gap between declared and actual sales. Second, marketing accountability: entrance-level traffic data shows whether a campaign moved footfall or just shifted it between doors. Third, operational staffing: security, cleaning and parking rosters aligned to real hourly traffic curves rather than assumptions. Most buyers find the tenant revenue lever alone justifies the licence, because turnover rent discrepancies compound across a full tenant roster year after year.

Who should own the platform internally?

Not IT. IT maintains the infrastructure, but ownership should sit with whoever answers for commercial performance — typically the mall manager or portfolio asset manager. Give tenants their own logins showing their store data plus anonymised category benchmarks. Tenants who see their own numbers become allies rather than sceptics, and your leasing conversations shift from opinion to evidence.

If your questions go deeper than this FAQ — sensor placement for a tricky atrium, integrating tenant POS feeds, or structuring accuracy clauses in your next RFP — talk to the team that has been answering them since 2005. Contact Vemco Group at vemcogroup.com/contact-us for a mall-specific walkthrough of VemCount and VemTenant using your own entrance layouts and tenant mix.