Inventory Visibility
Part of In-store customer analytics
Footfall counts versus identified customer journeys
Understand the difference between store entry counts, observed paths and journeys linked to customer records before choosing a measure.
Use footfall counts for decisions about visits through a doorway. Use observed paths for movement between measured areas. Link a path to a customer record only when the decision requires identity and the collection can be justified. These records answer different questions.
Separate counts, paths and identity
| Record | What it can show | Main limit |
|---|---|---|
| Entrance count | Crossings or visits under a stated rule | It cannot distinguish every repeat visitor. |
| Observed path | Movement linked across covered areas during a visit | It may be incomplete and need not identify a person by name. |
| Identified journey | Events joined to a customer record through a specified link | Matching errors and privacy risks increase. |
A system may track a temporary path without knowing who the shopper is. A loyalty transaction may identify a buyer without showing which aisles they visited. Neither record should be called a complete journey unless its coverage supports that description.
Choose the detail the decision needs
For shift planning, compare eligible entries by period with service demand; recognising returning individuals is unnecessary for that decision. For a layout question, define the relevant zones and ask whether the system can follow movement between them. Where coverage breaks, report separate zone events rather than a continuous route.
An identified journey needs a specific linking event. Ask what connects a path to a customer record, how a wrong match is detected, what happens when several people shop together, and how unmatched visits appear. Joining doorway counts and POS transactions by store and hour supports aggregate analysis. It does not identify which entrant bought.
Keep denominators visible
State whether “traffic” means crossings, visits or distinct people. A shopper who leaves and returns may make two entries; a group can enter together and pay in one transaction. Staff and deliveries can also affect counts. Record the exclusions used.
A transaction-to-visit ratio uses qualifying transactions and eligible visits for the same store and period. A zone-reach ratio requires a compatible count of visits that reached the zone, counted under a stated repeat-visit rule, and eligible store visits.
Repeated zone crossings cannot silently stand in for distinct visiting sessions. Do not compare a sampled path population with all transactions as if they described the same people.
Key Metrics and Their Definitions in Retail Footfall Analysis
- Transaction-to-Visit Ratio
- Qualifying transactions ÷ Eligible visits (same store, same period)
- Zone-Reach Ratio
- Visits reaching a zone ÷ Eligible store visits (under repeat-visit rule)
Check the cost of linking records
If a proposed link involves personal information, check the applicable OAIC guidance on collection. Ask for the fields and join keys in the proposed configuration. If a count or short-lived path answers the question, establish what further decision a persistent identity link would support.
