Here is a scene most asset managers will recognise: the quarterly review deck says footfall is up 4%, the leasing team says three anchor-adjacent units are underperforming, and the tenant in unit B-14 insists their weak sales are the center's fault because "nobody walks past anymore." Three claims, three separate data sources, and no shared reference point. The meeting ends with everyone agreeing to "look into it," which means nothing happens until the next quarterly review, when the same conversation repeats.
A shopping center KPI dashboard exists to end that meeting. Not to produce prettier charts — to establish a single, agreed version of the truth that owner, operator, leasing team, and tenant can all argue from rather than argue about. That distinction is where most dashboard projects succeed or quietly die.
If you have read the generic articles, you know the standard list: footfall, sales per square metre, dwell time. Fine. But at enterprise level, the useful question is not "what should we measure" — it is "which metric triggers which decision, and who owns that decision." Structure your dashboard around decisions, not data availability.
Notice what is missing: raw entrance counts as a headline number. They belong on the dashboard, but as a denominator, not a trophy.
Every sales-per-square-metre figure, every OCR calculation, every turnover-rent reconciliation depends on tenant revenue data. And in most centers, that data arrives late, in inconsistent formats, keyed manually by a junior accountant, or not at all. It is the single largest source of dashboard failure — not the sensors, not the software, but the monthly chase for tenant numbers.
This is worth solving structurally rather than administratively. Vemco's pairing of VemCount and VemTenant addresses exactly this joint: traffic measurement on one side, automated tenant revenue collection on the other, feeding one benchmarking layer that compares conversion, sales, and engagement across tenants. When revenue reporting is automated into the same system that counts the traffic, the sales-per-visitor and capture-rate figures stop being quarterly estimates and become operational metrics you can act on within the month.
One practical note for leasing teams: automated revenue collection also changes the turnover-rent dynamic. Tenants who self-report have an incentive to report conservatively. Tenants whose reporting is systematised — and who can see their own benchmarked performance in return — tend to treat the data as a management tool rather than a rent liability. Give tenants access to their own dashboard view. The centers that share data get better data back.
Anyone who has deployed counting infrastructure across a multi-entrance center knows this: the dashboard is only as credible as the entrance nobody calibrated. One sensor above a service corridor double-counting staff, or a mall entrance where a promotional stand pushes visitor flow outside the detection zone, and your total-traffic figure develops a permanent bias that tenants will eventually notice — usually at the worst possible moment, in a rent dispute. Budget for a calibration walk-through after every significant layout change, not just at installation. This is a recurring operational task, not a one-time project line item.
Accuracy claims deserve the same scepticism you would apply to a tenant's sales forecast. A credible vendor commits contractually — Vemco's contractual minimum is 96%, with typical performance at 98–99% when lighting, layout, and visitor behaviour allow. Anyone quoting a flat guaranteed figure regardless of site conditions has not walked enough malls. Ask for the contractual floor in writing and ask how accuracy is audited after go-live, because a number nobody re-verifies is a number nobody should trust in an OCR negotiation.
A single dashboard that tries to serve everyone serves no one. The enterprise approach is one data foundation, four views:
The benchmark layer matters more as scale grows. A platform processing millions of precise data points daily across global sites can tell you not only how corridor C performs against corridor D, but how your center's conversion pattern compares with comparable assets — context a single-site spreadsheet can never provide.
Do not scope a dashboard project by listing every metric you could theoretically display. Pick one recurring argument — the turnover-rent reconciliation, the "nobody walks past my unit" complaint, the marketing team's unproven event ROI — and build the data foundation that settles it definitively. Prove the model on one dispute, then expand. Dashboards fail when they are built as reporting furniture; they succeed when they retire specific arguments, one at a time.
If your center is still reconciling tenant sales in spreadsheets while traffic data sits in a separate system, that gap is costing you leasing arguments you should be winning. Talk to Vemco Group about building a shopping center KPI dashboard on unified traffic and tenant revenue data — contact us here and bring your hardest tenant dispute; that is the best place to start.