Most shopping centre teams already own the data they need. The problem is where it lives. Footfall sits in one dashboard, lease and unit data in a property management system, HVAC and washroom sensors in a facilities tool, and tenant sales in a spreadsheet that arrives monthly. When a duty manager asks "what is happening on Level 2 right now?", the honest answer usually requires four logins and a mental map of the building. The Mappedin Vemco integration removes that translation step: Vemco Group has built Mappedin's indoor mapping directly into the Vemco platform, so footfall, sales, property management and IoT data now render on an interactive 3D model of your actual centre.
Dashboards are built for analysts. Maps are built for people who run buildings. A table showing "Zone 14: occupancy 78% of threshold" means nothing to a security lead on shift three who joined last month. A 3D view of the centre with Zone 14 glowing amber next to the food court entrance means everything, instantly. Spatial context is not decoration — it changes who in your organisation can act on data without an analyst interpreting it first.
This matters most at the speed Vemco operates. Occupancy data appears in the platform roughly two seconds after a person crosses a counting line. At that latency, the data is operational, not historical — but only if the person watching can locate the event in the building faster than they can walk to it. Every Mappedin/Vemco customer now gets exactly that: live counts, occupancy states and alerts rendered on the map, in the place they occur.
The integration is not a screenshot of a floor plan with numbers pasted on top. It is the Vemco data engine — currently processing more than 85 million counts per day for 2,000+ customers across 95+ countries — feeding a live Mappedin 3D model. In practice, four layers matter to a centre operator:
The compounding effect comes from seeing these together. A unit with strong passing footfall, weak sales density and a lease expiring in nine months is a remerchandising conversation. On separate systems, that pattern takes a quarterly review to surface. On one map, a portfolio director spots it in a walkthrough of the model.
Vemco's live alerts already travel over app push, email, WhatsApp, SMS, webhook and MQTT — which means they slot into whatever your teams and building systems already use, from a security guard's phone to a BMS integration. What is new is that those alerts can now be visualised in map context. An occupancy threshold breach does not just say a zone number; it lights up on the 3D model. For control rooms, that shortens the gap between "alert received" and "person dispatched" because nobody has to translate a zone code into a physical location.
Facility managers get a parallel benefit on the IoT layer: a CO₂ or temperature alert shown on the map tells a technician which plant area or tenancy to check before they leave the workshop, not after they arrive at the wrong riser.
This is the question every operations team asks first, so here is the direct answer: Vemco is sensor-agnostic. Xovis, Milesight, Elsys, Hikvision, Axis and Irisys hardware all feed the same platform and the same map. If your centre has a mixed estate — Xovis at the main entrances from a 2018 project, Axis cameras added during a refurbishment, Elsys environmental sensors in the washrooms — that mix is normal, not a blocker. The integration consolidates the outputs rather than forcing a hardware refresh.
On accuracy, be sceptical of vendors quoting a single flat number. Counting accuracy depends on lighting, ceiling heights, entrance layout and how visitors behave — groups, prams, trolleys, people lingering under sensors. Vemco commits to a contractual minimum of 96%, and in practice achieves 98–99% where conditions allow. That distinction between guaranteed and typical is exactly what you should press any counting provider on before signing.
A practitioner note worth more than any feature list: the quality of a mapped-data deployment is decided by zone naming and unit mapping discipline, not by the technology. If your counting zones were named by an installer in 2019 ("Line 07-B") and your PMS knows the same space as "Unit 214, Anchor Wing", someone has to reconcile those before the map means anything. Centres that assign a single owner — usually an operations manager — to maintain the zone-to-unit mapping as tenants churn get lasting value. Centres that treat it as a one-off project task watch the map drift out of sync within a leasing cycle. Budget a few days for this reconciliation up front and a standing responsibility afterwards; it is the cheapest line item in the project and the one that determines whether the rest pays off.
Vemco Group has been building retail measurement since 2005, and this Danish pragmatism shows in the integration: no rip-and-replace, no new hardware mandate, no separate mapping login. Your existing data, on a 3D model of your actual property, updating in seconds.
If you want to see your own centre rendered this way — your zones, your tenants, your sensor estate on a live Mappedin model — contact Vemco Group at vemcogroup.com/contact-us and ask for a demo of the Mappedin integration using a floor plan of one of your properties. Bring your zone list and your unit schedule; the conversation gets specific fast.