A shopping centre with 180 tenants issues a tender for tenant revenue analytics. Four vendors respond. All four demos look identical: dashboards, conversion rates, sales-per-square-metre heatmaps. Eighteen months later, one of those centres is still chasing 40 tenants who never submit sales data, another discovered its turnover rent calculations were built on unverified figures, and a third is paying change-request fees every time a lease structure changes. The demo told them nothing about any of this. The tender documents could have — if they had asked the right questions.
This guide covers what to specify, what to score, and where vendors quietly differentiate themselves in a tenant revenue analytics tender — the parts that rarely appear in a features comparison matrix.
Tenant revenue analytics lives or dies on two data streams: verified tenant sales figures and reliable footfall. Most tender documents spend 80% of their requirements on reporting features and 20% on data acquisition. Reverse that ratio.
On the sales side, require vendors to describe — in detail, not as a bullet point — how they handle each tenant category: national chains with central POS systems that can push automated feeds, franchisees running three different POS platforms, and the independent café that reports monthly by email if reminded twice. A vendor whose answer assumes 100% API-connected tenants has never operated in a real centre. Ask specifically:
That last point matters more than buyers expect. If turnover rent is calculated from these figures, your finance team will treat the platform as a system of record. Vendors built for marketing analytics often lack immutable audit logs, and retrofitting them is expensive.
Footfall data is the denominator in every conversion and capture-rate metric the platform will produce. If counting accuracy drifts, every downstream benchmark is wrong, and tenants will notice before you do — usually when they dispute a performance review based on your figures.
The evaluation trap here is that vendors quote their best-case number. The correct tender requirement is a contractually guaranteed minimum accuracy, with a defined validation method and remedy. As a reference point: Vemco Group commits to a contractual minimum of 96% counting accuracy, with typical performance at 98–99% where lighting, entrance layout and visitor behaviour allow. The precise number matters less than the structure — a vendor willing to put a floor in the contract, define how it is measured (manual count validation over an agreed sample period), and accept consequences for breaching it is making a fundamentally different commitment than one quoting "up to 99%" in a slide deck. Score the contractual structure, not the headline percentage.
Counting hardware in a large centre represents significant capital and installation disruption — ceiling access, tenant coordination, sometimes night work. If your analytics platform only works with the vendor's own sensors, replacing the software later means replacing the hardware too, which in practice means never replacing either. Public sector buyers should note this creates exactly the kind of dependency that procurement rules exist to prevent.
Require sensor-agnostic architecture explicitly, and test the claim: ask which third-party sensor brands are running in production at reference sites today, not which ones are "supported on the roadmap." A device-independent platform also lets you mix technologies — 3D stereo at main entrances, lower-cost sensors at service corridors — and absorb sensors already installed by previous vendors rather than writing them off.
Tenant revenue data is only useful when it reaches the systems where decisions happen: the leasing team's CRM, the finance team's ERP for turnover rent invoicing, the asset manager's BI environment for portfolio benchmarking. Vendors handle this in one of two ways — a genuine integration layer (Vemco's VemFusion is an example, connecting POS, BI, ERP and CRM systems) or bespoke point-to-point connectors built per project. The second approach demos fine and then generates a change request every time your ERP is upgraded or a tenant switches POS provider.
System integrators evaluating on behalf of a client should demand API documentation during the tender phase, not after award, and check whether data export is complete and machine-readable. If you cannot extract every raw count and every tenant sales record on exit, your exit clause is decorative.
Based on where these projects actually go wrong, a defensible scoring split looks like this:
Note what is missing: dashboard aesthetics. Every shortlisted vendor will clear that bar.
Here is the observation that separates experienced buyers: the hardest month of any tenant revenue analytics rollout is not installation — it is the first month tenants see their own numbers benchmarked against category averages. Underperforming tenants will attack the data before they accept the conclusion. They will question the footfall counts, the zone boundaries, the category definitions. If your vendor cannot produce validation evidence and a clear methodology document at that moment, the entire programme loses tenant trust, and adoption collapses regardless of how good the software is. Ask every bidder: what materials and support do you provide when a tenant disputes the data? The quality of that answer predicts project success better than any feature list.
Skip the vendor-arranged reference call script. Ask reference sites three things: how long tenant onboarding actually took versus the plan, how many change requests were invoiced in year two, and whether turnover rent has ever been invoiced directly from the platform's figures without manual reconciliation. Vendors with genuine multi-site, multi-country delivery experience will connect you with references who can answer all three without hesitation.
If you are preparing a tenant revenue analytics tender and want to pressure-test your requirements — including how a contractual accuracy guarantee, sensor-agnostic architecture and ERP integration should be specified before the RFP goes out — talk to the Vemco Group team at vemcogroup.com/contact-us. We will walk you through real tender language and reference cases relevant to your portfolio.