Routes
The actual path of a person, basket or order and its deviation from the optimum
Automarket – high-precision tracking and analytics for physical operations
We show how staff, customers and equipment move indoors. Precise data and AI analytics help reduce losses, optimise routes and order picking, and improve staff efficiency and customer experience
Automarket Visualiser
Realtime
Not just coordinates
Automarket captures movement inside a site and turns it into routes, idle time, zone dwell, load peaks, heatmaps and reports for operational decisions
How Automarket works
Tags
Trackers on staff, baskets, orders or equipment
Anchors
Typically 3–15 points per site form the positioning infrastructure
Algorithms
UWB + IMU fusion, outlier filtering, signal quality scoring, trajectory recovery and smoothing
Visualiser
Realtime and DVR, site map, history, roles, objects and orders
Analytics
Routes, stops, zones, peaks, heatmaps, reports and export
Decision
Improvement hypotheses, before/after comparison, rollout across the network
What the system shows
Compare shifts and scenarios, find extra walking and waiting, test layout changes and export results in a clear format
Idle time
When an object stopped, how long the pause lasted and in which zone it happened
Zone dwell
Dwell time in the kitchen, buffer, aisles, checkouts and merchandising zones
Load peaks
When and where process density rises — the basis for reallocating staff
Order picking
Path length, picking time, pick points, product search, pauses and extra passes
Heatmaps
Movement density, bottlenecks, unused areas and overloaded aisles
Customer journey
With trackers on baskets: shopper routes, areas of interest, abandoned baskets
Before/after
The effect of a change in layout, process or staffing
Export and reports
XLSX, CSV, PNG and MP4 — data flows into BI and internal systems
Integrations
WMS, ERP, timesheets, receipts, orders and API — to fit the client's scenario
Swipe the cards sideways
Demo: real Visualiser screens
Three screens of the web platform that pilot analytics is built on
Heatmap and zone traffic
- On screen
- Activity by zone over the day, the most and least visited zones, average time in zones and hourly dynamics
- What you get
- Bottlenecks and unused zones become the basis for moving shelves and staff
Real-time store plan
- On screen
- Customers, baskets and staff on the floor plan, visitors by zone and a feed of recent events
- What you get
- You see where people and baskets are now, which zone is peaking and where customers lack staff
Customer route
- On screen
- A customer’s path across the floor: zones in order, time in each, stops at products and the visit outcome
- What you get
- You understand how a customer moves through the store, where they linger and whether they reach the checkout
1 / 3
Technology
UWB + IMU is why the data can be trusted. Figures are design values and depend on the site configuration
- Technology
- UWB + IMU
- Accuracy
- 5–8 cm
- Update rate
- up to 10 Hz
- Anchors
- typically 3–15 per site
- Range
- up to 100 m, depending on conditions
- Deployment
- installation in 4 to 7 days, tuning 1–2 weeks
- Export
- XLSX, CSV, PNG, MP4
- Integrations
- WMS, ERP, timesheets, orders, receipts, API
Process data, not surveillance
The core stack runs on UWB and IMU — no cameras, face recognition or biometrics. Data access is role-based, and analytics can run on depersonalised tags. Video analytics can be added separately if the project needs it
Integrations
Automarket can link movement data with orders, WMS/ERP, timesheets, POS data and the client's BI stack
- WMS
- ERP
- Timesheets
- Orders
- Receipts
- BI
- API
- CSV / XLSX
Where Automarket works
Several operational scenarios — from dark stores to manufacturing and beyond
Dark stores
Order picking: routes, pauses, zone dwell time and SLA
View use caseStores
Sales floor: staff, customer path and zone load
View use caseDCs and warehouses
Pallets, loading, people and vehicle movement, bottlenecks
View use caseIndustry
Material flows, staff and equipment between stages
View use casePilots and deployments with partners
Every project is shown with its actual status. Click a card to open a detailed case breakdown
Yandex LavkaYandex Lavka
Up to 20% faster picking
Optimised routes for pickers
Yandex MarketYandex Market
Up to ₽1M per month per sort centre
Monitoring pallet placement in storage and loading zones
Magnit KosmetikMagnit Kosmetik
Optimising sales floor operations
Staff efficiency and service quality
How we run a pilot
One site, KPIs agreed before the start, scaling only after the impact is confirmed
- Quick diagnosticsSite map, processes and KPIs
- Pilot from two weeks to 2 monthsTags, anchors and data collection
- ROI and analytics reportBefore/after comparison
- RolloutNew zones and sites
Pilot FAQ
Briefly about timing, data and integrations. Click a question to see the answer
How long does a pilot take?
A pilot lasts from two weeks to 2 months. The exact timing depends on the site, the map, the number of trackers and integrations
What can be tracked?
Staff, baskets, orders, equipment and any other objects a tag can be attached to
Do we need cameras?
No. The core Automarket stack runs on UWB/IMU and doesn't need face recognition. Video can be used separately as an extra source if the project needs it
Can it integrate with our systems?
Yes. The architecture supports data export and integrations with WMS/ERP, orders, timesheets, receipts and your BI stack
What do we get after the pilot?
A map of actual routes and zones, a set of operational metrics, exports and conclusions on improvement hypotheses
Can the analytics be adapted to our process?
Yes. Zones, events, reports and integrations are configured for the specific pilot task
Partners
Companies we develop the technology and projects with
- Magnit
VkusVill- Yandex Lavka
X5 Group- Yandex Market