Custom software, from understanding the problem to a system in operation.
Routines that stop causing rework, and AI that says where every number comes from: measured, inferred or predicted.
Mission: Turn technology into solutions that make businesses flow. Vision: Be known for technology solutions that make a real difference to businesses.
First solution in development · next step: a pilot in a partner store
From idea to a system in operation: development, automation and artificial intelligence, with measured data and privacy by design. A company built for more than one solution.
Afluxion is not a one-product company. We start from a real problem, measure before we promise and deliver in phases, with discipline. The first solution already has a name.
Web systems and links between the programs the business already uses, tested before going live.
Custom management and operations systems, from discovery to support.
Routines and processes that flow without rework, with a record of what was done.
Automatic reading of images and data, always saying where each number comes from: measured, inferred, predicted or simulated.
Footage from the cameras a store already has becomes flow indicators, a 3D Digital Twin and layout scenarios. All in totals, identifying no one, with the origin of every number recorded.
In development · the pilot is the next milestoneExplore the productEvery new solution starts from a real problem and follows the same rules: the right number first, then the screen; privacy from the start; and always saying what is measured and what is an estimate.
About the companyThe store exports clips from its camera recorder (DVR or NVR). No new camera, no sensor, no construction work.
Each person in the footage becomes a per-camera trajectory, classified as customer, employee or unknown. No face, no identity.
Each camera is fitted to the store floor plan: what appears in the image becomes a position in metres inside the real store.
Produce, bakery, checkouts: each department becomes an area on the plan, and each crossing into it becomes a record with entry and exit times.
Totals by hour, day and department become dashboards, the day replay and the 3D model of the store, the Digital Twin.
Dwell, density and routes over the store floor plan, never over people. Tap the points to see a department.
Illustrative data, to demonstrate the interface
Every number says which period it came from, who was counted and how it was calculated, and carries a seal: measured (counted on video), inferred (estimated by a model), predicted (projection ahead) or simulated (test scenario). When data is missing it shows as partial. Indicators arrive in phases, starting with counting.
How many people crossed a line marked on the entrance cameras, in each direction.
Visits classified as customer, in 5, 15 or 60 minute periods.
Period in which flow or occupancy reached the defined level.
Time between entering and leaving a department, with a minimum-stay rule.
Mean, median and the range most customers fall in, because a mean alone misleads.
Share of visits that passed through each department.
People per period, by department and main camera.
People per usable area, computed on the floor plan, not in pixels.
A score combining crowding, slowness and standing time.
Most common department sequences in a period.
Which department people come from and which they go to.
Complete once the system can follow the same path from one camera to the next; partial until then.
Estimated flow and crowding for the coming hours or days.
Deviations from the expected pattern for the day and hour.
Today's store compared with a layout change on the Digital Twin, always marked as simulation.
No facial recognition, no representation of faces, no attempt to find out who someone is.
Before going to more stores: one store, a defined period and agreed targets. What is not measured does not make the report. The numbers below are pilot targets, not guarantees.
One pilot store with the cameras already in place, after an approved technical visit.
Paid pilot with a fixed term. A meeting every two weeks with whoever owns the pilot on the retailer's side, and a monthly report.
Maximum difference between the system count and a manual count, at agreed times.
Findings recorded and confirmed by the store, and at least one decision tested with data.
Tell us about the operation, the process or the store. We reply within two business days with next steps, no commitment.