Vemco and Yardi: Connecting Property Management with Physical-Space Analytics

Here is a pattern most portfolio operators recognise but rarely say out loud: the tenant record in Yardi and the tenant record in the analytics platform drift apart within weeks of go-live. A store rebrands, a unit gets split, a tenant expands by 200 square meters — and someone forgets to update the second system. Six months later, your sales-per-square-meter report is comparing footfall against floor areas that no longer exist. The problem is not the software on either side. It is the gap between them, usually filled by a spreadsheet and one overworked analyst.

This is exactly the gap a proper Yardi footfall integration closes. Yardi, headquartered in the USA, is one of the world's leading providers of high-performance software for the real estate industry, and for most portfolios it is — rightly — the system of record for tenants, leases and units. Vemco Group, a Danish company with more than 20 years of experience, runs a sensor-agnostic analytics platform that counts more than 60 million people every day across 55,000+ installations in 98+ countries. The integration connects Yardi with VemTenant, Vemco Group's tenant sales reporting product, and moves data in both directions. It is set up per customer with a customer-specific file format, so it is not automatically available to every Yardi customer.

Direction one: Yardi stays the master, VemTenant imports the tenant data

In the Yardi-to-Vemco direction, VemTenant imports tenant and location details, area, opening date, status and contacts from Yardi. A new tenant, a changed trading name or adjusted square meters is maintained in Yardi and reaches VemTenant with the import, together with the opening date and the status of the unit. Your teams change data once, in the system where they already work, and the analytics side takes it over from there.

Why does this matter beyond convenience? Because every KPI that leasing teams actually use — sales per square meter, conversion by unit, footfall capture rate per corridor — depends on tenant metadata being correct on the analytics side. If the square meters are stale, the density metric is wrong. If a closed store still shows as trading, your vacancy-adjusted footfall benchmark is polluted. Anyone who has run a portfolio-wide reporting cycle knows that data hygiene, not dashboard design, is where these projects live or die.

Direction two: daily tenant turnover exported to Yardi

The return direction is where turnover-based leases get interesting. VemTenant, Vemco's tenant revenue management product, exports the daily turnover for the previous month to Yardi, with property and lease codes, sales type and date. For operators running percentage rent or turnover-linked lease clauses, this replaces manually keying the figures into Yardi before the rent run.

A practical note: a common source of friction in turnover-rent reporting is not technology, it is tenant compliance — small-format tenants who report late, report gross instead of net, or report at brand level rather than unit level. Turnover reported per day through VemTenant changes the dynamic. An odd figure can be questioned while it is still fresh instead of at quarter-end, and the conversation with the tenant shifts from "you owe us a declaration" to "your Tuesday figure looks off, can you check the till export." That is a materially easier conversation, and it protects the percentage-rent revenue line.

What one source of truth actually changes in leasing

When property data, tenant sales and footfall live in one connected environment, several decisions get sharper:

• Rent negotiations with evidence. A tenant claiming poor performance because "the mall is quiet" can be shown their unit's footfall capture against corridor traffic. Sometimes the mall is quiet. Sometimes the corridor is busy and the store is not converting — and the negotiation changes accordingly.
• Re-leasing and remixing decisions. Sales per tenant combined with footfall per zone shows which categories over- or under-index in specific locations, so leasing teams place the next tenant where the traffic profile fits.
• Turnover-rent audit readiness. Turnover reported per day in VemTenant gives a consistent record rather than a folder of tenant-submitted files of varying quality.
• Portfolio benchmarking. With tenant details and areas imported from Yardi, comparisons across assets use the same unit definitions and areas everywhere — no more debating whose square-meter figure is correct.

On the footfall side, accuracy claims deserve honesty because they underpin every downstream number. Vemco contracts a minimum of 96% counting accuracy, and in practice sites typically achieve 98–99% where conditions such as lighting, store layout and visitor behaviour allow. That distinction matters: a vendor promising a flat guaranteed 99% across every entrance and every lighting condition is telling you something about their sales process, not their sensors. Because the platform is sensor-agnostic and built on open data principles, existing counting hardware can often be kept, which shortens deployment and protects prior capital spend.

The budget question: what does consolidation save?

Integration projects usually get justified on efficiency, but the harder-edged case is license consolidation. Your stack will differ, but the pattern is common: a CRM bent into service as a tenant-sales collector, a BI tool stitching it together, and staff time reconciling both. When VemTenant handles sales collection and the Yardi import supplies the tenant data, part of that work can go — including analyst hours spent on manual re-entry, which rarely appear on any budget line but are very real.

The strategic point is worth stating plainly: this is not a rip-and-replace pitch. Yardi remains your property management system of record. Vemco adds value to the Yardi investment you have already made by connecting it to what happens in the physical space — the footfall, the conversions, the daily tenant turnover — so your data stops living in separate systems that disagree with each other.

What to check before you start

Three practical items shorten these projects considerably. First, audit tenant naming and unit numbering in Yardi before connecting anything — the import will faithfully reproduce whatever is there, including the mess. Second, map which leases actually contain turnover clauses so the turnover export is prioritised where it drives rent. Third, decide who owns tenant metadata changes going forward; the whole value of one-way mastering collapses if two teams keep editing in two places out of habit.

Already running your portfolio on Yardi? Connect it with Vemco and combine your property data with footfall, tenant sales and occupancy analytics — one source of truth, turnover exported to Yardi, less double entry. Talk to us at vemcogroup.com/contact-us and we will walk through how the Yardi integration would be set up for your specific asset list and lease structures.