Retail / wholesale park
Expo Market Doraly
Afumati, Ilfov · retail and wholesale park
AI Video Analytics for Retail
Retail environments generate valuable information every day — customer movement inside the store, vehicles in the car park, queues at the checkout. Much of it is never measured consistently. Metrici turns IP camera feeds into operational data you can act on: count visitors, see how they move, track queues and occupancy, manage parking spaces and automate vehicle access.
Built for shopping malls and retail parks, supermarkets and stores, and retail chains that need consistent reporting across locations.
Illustrative overlays. Panels show the kind of information each application reports.
A retail operator manages footfall, staffing, service levels, parking capacity and vehicle movements at the same site — usually with data sources that were never designed to work together. The result is decisions taken from estimates, sampled counts and memory of last Saturday.
Door counters and manual samples give rough totals for one entrance on one day. There is no consistent record of how visitors move between zones, which areas they pass without stopping, or how long they stay. Marketing and leasing decisions end up based on assumptions rather than measurement.
Checkout wait times are usually discovered by customers, or by a supervisor walking the floor. By then the transaction is lost. Without a measured queue length per lane, staffing adjustments are reactive and cannot be compared across shifts, days or locations.
Which corridor carries traffic, which gallery is being bypassed, which layout change actually improved activity — these questions are difficult to answer retrospectively when no zone-level activity history was recorded. Layout and tenant-mix decisions are therefore hard to justify.
In a large multi-level car park, occupancy is often known only as a barrier counter — a total, not a per-level or per-zone figure. Drivers waste time searching, congest internal lanes, and guidance displays either do not exist or show numbers nobody trusts.
Supplier and tenant vehicles are admitted by guards checking lists, badges or phone calls. Each access event is a manual decision, records are paper or spreadsheet based, and misuse of reserved or tenant-only areas is discovered late, if at all.
A retail site typically already runs dozens of IP cameras for security. Their output is reviewed after an incident, never turned into operational data. The infrastructure is paid for and the analytical value is unused.
Metrici analyses video from compatible IP cameras and turns it into structured events, counters and records. The same platform covers customer flow inside the store and vehicle movements outside it, so operations, marketing, facilities and security work from one data source instead of five separate tools.
Retail applications are modules on the same analytics engines, managed through the Metrici Interface. Adding queue monitoring to a site that already counts visitors is a configuration and licensing step, not a second vendor and a second console.
Each approach answers a different question. Video analytics is not a replacement for a POS system or a Wi-Fi sensor; it measures what happens in the physical space, which those systems cannot see.
| What you need to know | AI video analytics (Metrici) | Manual counting | Wi-Fi / Bluetooth sensing | POS transaction data |
|---|---|---|---|---|
| People entering, continuous and unattended | Yes — 24/7, per entrance or line | Sampled, staff-dependent | Estimated, opt-in dependent | Only people who bought |
| Movement and activity by zone inside the store | Yes — zones defined on the camera view | Not practical | Coarse, requires many sensors | No |
| Queue length and wait-time pressure per lane | Yes — with configured thresholds and alerts | Spot checks only | No | Retrospective only |
| Free or occupied state of each parking space | Yes — per space, per level | Patrol-based, not continuous | No | No |
| Vehicle identity for access control | Yes — plate recognition and rule lists | Guard checks, manual | No | Payment ticket only, not identity |
| Uses cameras you already operate | Yes, where cameras meet application requirements | Not applicable | Requires new sensor hardware | Not applicable |
| Measures sales conversion | No — combine with your own POS data | No | No | Yes — within its own scope |
The last row is deliberate. Metrici reports how many people entered a space and how they used it. Turning that into a conversion rate means joining it with your own transaction data — a reporting task on your side, not a metric the cameras produce.
Deployments usually start with one application and add others on the same cameras and servers, where technically suitable. The six groups below describe what Metrici is configured to measure and what it can then do with that information.
Entrance and zone footfall, multi-level car park guidance, tenant and delivery access, reserved-bay monitoring across large sites with thousands of spaces.
Entrance counting, queue length per lane, occupancy of defined areas, self-checkout support and trolley or asset presence in the sales area.
Consistent counters and reports across locations, employee access by plate, loading-area and yard control, supplier and contractor vehicle management.
How many people come, through which entrance, and how do they move through the space?
Where is service degrading right now, and by how much?
Which space is free, on which level, right now?
Who is allowed in, and how do they get through without stopping?
Are docks and yard areas moving, and who used them?
What should someone look at now, rather than after the fact?
What these applications do not do. Metrici does not identify individual shoppers and does not build personal profiles. It does not measure conversion rate — that requires joining visitor counts to your own transaction data. It does not issue fines on its own: parking and access applications support monitoring and documentation, while any sanction remains a human and procedural decision under the rules of the site and the applicable law. Predictive features, where configured, extrapolate from recorded history; they are not a forecast of demand.
Fuel retail has its own set of requirements — forecourt lane events, pump-area activity and canopy-environment cameras. Those are covered on a dedicated page.
Where a site needs space-by-space records and vehicle images to support its own parking administration process, see the dedicated parking application page for what is captured and how it is handled.
Four stages, in the order a retail deployment actually happens. Each stage is scoped per site, because camera suitability and the actions you want depend on the environment.
Compatible IP cameras already installed on site — or added where coverage gaps exist — provide the video feed. Resolution, framing, mounting height and lighting are assessed per camera against the requirements of each application.
Metrici analytics engines process the streams and produce structured events: people crossing a line, occupancy in a zone, a space becoming occupied, a recognised plate. Processing runs on your own infrastructure, inside your network.
The Metrici Interface presents counters, occupancy, alarms, plate records and reports. Users see only the sites, cameras and records their role and tenant scope allows. Thresholds and rules are configured here.
Events drive connected barriers, LED displays and controllers directly, and are published to access control, payment, reporting or BI systems through documented interfaces where an interface exists.
Camera suitability is confirmed before licensing, camera by camera. An existing camera that cannot deliver the image quality an application needs will be identified at this stage rather than discovered after go-live.
Analytics engines run on customer-supplied servers, on customer virtualisation, or on Metrici supplied hardware such as the Metrici Racksys series. Video does not have to leave your network to be analysed, which simplifies both security review and connectivity at large sites.
Events, counters and plate records are exposed through documented interfaces so they can be consumed by access control, parking payment, ticketing, ERP or reporting platforms. Integration work is scoped per project against the interfaces that actually exist on the third-party side.
Most retail projects start with a single measurable application on a limited camera set, verify the results against what staff observe, then add further applications or locations on the same platform.
The value is not the analytics itself. It is having a continuous, comparable record of how your retail space and its car park are actually used, so decisions can be defended afterwards.
Visitor counts, occupancy and space state are recorded around the clock, in the same way every day. Seasonal patterns and the effect of a layout or promotion change become visible as a data series rather than an opinion.
Queue length per lane and measured peak periods give supervisors a basis for opening lanes and scheduling shifts, and a record of whether the change improved the situation.
Per-space and per-level availability feeds guidance displays that drivers believe. Less internal congestion, shorter search time, and a better first and last impression of the site.
Tenant, employee and supplier vehicles recognised by plate pass on configured rules. Guard time is freed, entry records are consistent, and exceptions are logged with a plate and a timestamp.
The same cameras that serve security also produce operational data. Retail analytics becomes an additional use of existing infrastructure rather than a parallel system with its own sensors and console.
Footfall, queues, parking and access are configured and reported together. Operations, marketing, facilities and security look at one set of records instead of reconciling four tools.
Retail chains and multi-site operators apply the same definitions of a counted entrance or a monitored zone across sites, so locations are comparable rather than each measuring differently.
Processing and event storage can remain on infrastructure you control, with permissions scoped by role, site and tenant. The retail operator sets retention and access; Metrici provides the controls to enforce those decisions.
A note on results. This page does not quote percentage improvements in sales, conversion or dwell time. Outcomes depend on your site, camera coverage and, above all, what your teams do with the data. The verified deployments below show what was installed and measured; all case studies are listed separately.
Three verified Metrici deployments, described by what was installed and what the system now records. They are not identical to every mall or store — a retail park with 26 pavilions and a business campus solve different problems — but they show the platform working at retail scale.
Retail / wholesale park
Afumati, Ilfov · retail and wholesale park
Commercial campus
Bucharest · office and commercial campus (not a retail site, shown for tenant access management)
Commercial car park
Bucharest · paid car park with additional vehicle services
Rather than a generic promotional clip, we prefer to walk your own environment: which camera views answer which question, and what the interface shows for them. Ask for recorded footage of people counting, occupancy alerts, space detection and plate-based access, or for a session against your camera specifications.
If your environment is closer to a logistics or truck park than a shopping centre — gated lorry spaces, driver check-in, long-stay monitoring — that deployment pattern is documented separately.
A retail deployment combines one or more analytics modules with the control hardware and interfaces the site needs. Licensing is per application and per camera, scoped during the project.
| Metrici component | What it does in a retail deployment | Typical applications |
|---|---|---|
| Area Counter | Counts people in defined areas and zones, tracks activity and occupancy over time, and raises alarms on configured conditions. | Footfall and flow analysis, zone activity, occupancy and queue monitoring, situational awareness |
| Line Counter | Counts people or vehicles crossing a defined line, with direction, producing entrance and corridor totals. | Entrance counting, store front traffic, corridor and zone boundary totals |
| Parking Place Detector | Determines whether each individual parking space is free or occupied, per level and zone, and tracks session duration per space. | Car park guidance, availability displays, reserved-bay monitoring, turnover analysis |
| Metrici LPR | Recognises vehicle number plates and applies whitelist or blacklist rules, producing a time-stamped record of every read. | Vehicle access control, tenant and employee parking, delivery gate control, session billing |
| LPR Parking | Combines plate recognition with parking session logic for controlled entry and exit and duration-based records. | Paid retail car parks, tenant parking, multi-service sites |
| Metrici MultiController | Interfaces multiple cameras and devices into one control point, coordinating counters and outputs across an area. | Multi-entrance counting, multi-lane checkout areas, gates with several cameras |
| Metrici LAN Controller | Drives barriers, boom gates, traffic lights and displays over LAN and I/O connections when an event condition is met. | Barrier release on plate match, LED guidance output, gate and dock control |
| Metrici Display | Presents live availability, counter or status information on LED totems and screens for drivers, staff or visitors. | Car park availability guidance, queue or status information at entrances |
| Metrici Custom | Applies custom rules and reports when the required logic is not covered by a standard module. | Site-specific visitor reports, unusual zone definitions, bespoke alarm logic |
| Custom applications | Engineering work for requirements outside the standard catalogue, including bespoke integrations and reporting. | Chain-wide reporting definitions, proprietary business system integration, unusual camera geometry |
Works with compatible IP cameras meeting the resolution, framing and lighting requirements of the chosen application. Camera suitability is verified per camera before licensing, and cameras can be added where coverage is missing.
Connected boom gates, traffic lights, LED totems and I/O devices are driven directly by event rules, so recognised vehicles and availability figures act without an operator in the loop.
Events, counters and records are published through documented interfaces so third-party access control, parking payment, ERP or reporting platforms can consume them where an interface exists.
Retail environments are public spaces, so how a system is deployed and governed matters as much as what it measures. These are the questions procurement and legal teams actually ask, answered plainly.
In many cases yes. Metrici works with compatible IP cameras that meet the image quality, resolution, framing and positioning requirements of the selected application. Suitability is assessed camera by camera during deployment planning, before licensing, so a camera that cannot support an application is identified early.
Yes. Analytics engines run on server hardware on the customer's premises, on customer virtualisation, or on Metrici supplied servers. Video processing and the event database can stay inside the retail operator's own network, with no requirement to send video to an external cloud service.
Metrici exposes events and records through documented interfaces and can drive connected barriers, displays and controllers directly. Integration with third-party access control, payment and business systems is possible where a documented interface exists, and is scoped as integration work during the project.
The Metrici Interface supports named users, role-based permissions and hierarchical tenant or site scoping, so a tenant or store manager sees only the locations, cameras and records assigned to them. Plate events, corrections and exports are recorded, producing an audit trail of who accessed or changed what.
Retention is configured by the retail operator. Analytics events, counter totals and occupancy records are stored as structured data; video and vehicle images follow the retention period set in the recording systems. What is retained, for how long and who may access it are project decisions, documented before go-live.
Retail applications are configured to count and monitor activity in defined areas. They are not configured to identify individual shoppers, follow a person between visits or build personal profiles. Configuration choices that would move a deployment towards personal data must be assessed by the operator before they are enabled.
Access to live views, records and exports is granted per role and per site or tenant group. In multi-tenant retail and campus environments this lets each tenant administer its own vehicle list without seeing other tenants' data.
Alerts and records support an operator's decision. Where a site uses parking or access records in an administrative process, the decision and any sanction remain with the responsible person under the site's rules and applicable law — the system documents, it does not adjudicate.
Responsibility for compliance stays with the operator. Deploying Metrici does not by itself make a site compliant with GDPR or any other regulation. Lawful basis, notices and signage, data protection impact assessment, access policies, retention periods and cross-border transfers remain the responsibility of the data controller. Metrici provides technical capabilities — scoped permissions, structured event data, on-premises processing, configurable retention — that support a compliant deployment, and our approach to personal data handling is documented separately. Contractual terms are agreed per project.
Start with the operation that costs you the most uncertainty today — footfall you cannot prove, queues you learn about too late, a car park nobody can guide, or a gate that needs a guard. We will map it to camera views and show you what the interface returns.
Or write to us directly: sales@metrici.ro
Site layout or floor plan, your camera inventory with models and positions, and the two or three operational questions you want answered. That is enough to scope which applications fit.
A view of which camera positions support which measurements, the applications that apply, and what the Metrici Interface would show your teams for each one.