Shopper intelligence
How to Analyze Shopper Behaviour in Physical Stores
To analyze shopper behaviour in physical stores, you need to decide which behaviours matter, pick a source that can actually observe each one, and read the result by store and week rather than as one network average. Most customer behaviour analytics in retail stops at movement: counts, paths, dwell. The behaviours that decide revenue are spoken: what the shopper asked for, what they compared, what they objected to, and whether they left a number. This guide covers both kinds, and a method for measuring them without turning the store into a surveillance site.
The behaviours worth measuring
- Arrival: when they come, alone or in groups, and to which zone first.
- Attention: which displays hold them and for how long.
- Engagement: whether an advisor reached them, and how long that took.
- Intent: what they said they came for, in their words, and how firm it was.
- Comparison: which rival product or store they named, and what price they had been quoted.
- Objection: what stopped them, and whether it was answered.
- Decision: bought, left, or left a number and a reason to call.
- Return: whether the follow-up happened and whether they came back.
Five sources and what each misses
| Source | Observes | Misses | Cost of setup |
|---|---|---|---|
| POS data | What sold, when, basket size | Everyone who did not buy | Already there |
| Door counters | Entries by hour | Everything after the door | Low |
| CCTV analytics | Paths, dwell, queues, groups | Any reason; cannot hear | Medium; cameras usually exist |
| Staff observation and CRM entries | The advisor's summary after the fact | The customer's actual words; biased to the advisor's story | Low, but low trust |
| Consented conversation capture | Intent, comparison, objection, decision, in the customer's words | What happened before the advisor arrived | Consent design plus an app on the advisor's phone |
A step-by-step method
- Write down the three questions you want answered. For most Indian assisted-retail networks they are: why do walk-ins leave, what do they compare us to, and what did they want that we did not have.
- Choose the source that can observe each. All three live in the conversation, so start there. Put consent signage at the entrance and counter, and capture on the advisor's phone with a disclosure line.
- Run for two weeks in five to ten stores across two regions. Track coverage first: conversations captured as a share of walk-ins. Below half, fix advisor trust before reading anything else.
- Read the objections and unmet requests by store, ranked by frequency, with the transcript line behind each. This is the first real picture of behaviour most networks have ever had.
- Add movement where a question needs it. If the objection list is short but conversion is low, the problem may be before the conversation: wait time, unattended visits. That is where camera events, on the Borentis roadmap as ShopperDNA, would answer.
- Cluster. Once there are a few hundred conversations, ShopperPersonas groups them into the customer types that actually walk in, each with its questions, objections and closers.
- Act on one thing per store per fortnight, then re-read. Behaviour analysis that does not change a display, a script or a stock order is a report.
Reading the result
Read by store, not by network. A network average of objections hides the fact that one store hears price and another hears delivery time. Read by week, so a rising rival mention is a trend and not an anecdote. Read with coverage next to every number, so a quiet store's score is known to rest on twelve conversations, not two hundred.
Read non-buyers separately from buyers. Buyer behaviour is the story the till already tells. Non-buyer behaviour is where the recoverable revenue sits, and the guide on why walk-ins do not convert goes deeper on that.
Mistakes that waste the effort
- Starting with heatmaps. They are the easiest thing to buy and the hardest to act on, because a hot display tells you where people stood and not what they thought.
- Trusting the CRM's lost reason. It is chosen from a dropdown by the advisor after the customer has gone.
- Analysing a national sample once a quarter. Behaviour changes with the scheme, the launch and the rival's offer; the read has to be weekly.
- Identifying people. Facial recognition, age and gender estimates and emotion detection add legal risk and no decision a store manager can act on. Count events; hear consented conversations; identify nobody who did not ask to be called.
- Building dashboards before deciding who acts. Every behaviour metric should have an owner: the trainer, the buyer, the store manager, or the area manager.
Frequently asked questions
What is the best way to analyze customer behaviour in a retail store?
Start with the behaviour that decides revenue: what the customer said. Capture consented conversations, read objections and requests by store and week, then add movement data where a question needs it. Movement-first programmes learn where shoppers stood and not why they left.
Can CCTV alone analyze shopper behaviour?
It can count entries, time dwell and see queues and groups. It cannot hear a reason, a comparison or an objection, which is most of what a store can act on.
How many conversations are needed before the analysis means anything?
A store's weekly read should rest on dozens of conversations. Persona clustering needs a few hundred across the network. Coverage should be reported next to every number.
Is shopper behaviour analysis allowed under India's DPDP Act?
Yes, when done as consented conversation capture with audio deleted after transcription and customers anonymous in reports, and as camera event counting without identifying anyone.
Related reading
- Why walk-ins do not convert
- How to measure the customer journey inside a store
- ShopperPersonas
- Voice of customer in retail stores, methods compared
Where Borentis applies this
- Unmet Demand Signals: Demand for what you did not have.
- Objection Intelligence: The reason they did not buy, in their own words.
- Competitor Defence: Hear the rival the moment your customer names them.
- Walk-in Recovery: The customer who left is still yours.
Borentis is the Agentic Operating System for Customer Interactions, built for Indian retail floors: consented one-tap capture on the advisor's phone, every conversation scored against your playbook with the evidence behind every number, leads created when a number is heard, and coaching from your own best conversations.