Store Footfall Logger: Record Every Walk-In Enquiry, Not Just the Bills

How most shops do it today

In most independent stores the record of a day is the bill book. Anyone who bought something exists. Anyone who walked in, asked for a model, heard the price and left does not. Some shops keep a paper register near the counter, and it works for about three weeks, until a busy Saturday breaks the habit.

The job is narrow: capture every enquiry as it happens, in a fixed structure, with enough detail to act on the same evening. The monthly report is a by-product. The real output is that at 7pm one person holds a list of eleven names, each with a number and a reason.

These are the columns to build, in the order they are easiest to fill at a counter. The first six are mandatory; the rest are completed during follow-up.

• Visit date and time — stamped automatically, so you see which hours produce enquiries, not just traffic.
• Branch code — pointless with one shop, essential from the second onward.
• Greeted by — the staff member who handled the enquiry, not the one who raised the bill.
• Source — walk-past, WhatsApp offer, Google Maps, referral, advertisement, repeat customer. Six options, no more.
• Category and model asked for — the specific request, in the words your own stock list uses.
• Outcome code — bought, quoted, still deciding, out of stock, price objection, wrong specification, only browsing.
• Mobile number and consent — the number, plus a yes or no on being messaged later.
• Party size — a single decider behaves differently from a family of four.
• Budget band — a range, never an exact figure, because customers state ranges.
• Buying timeline — today, this week, this month, undecided.
• Next follow-up date and owner — the two fields that make the log operational rather than historical.
• Bill number and value — filled when the sale closes, whether that is today or eleven days later.

The table below is an illustrative example, not data from a real store. It shows what a properly filled log looks like.

A single shop can do this in a spreadsheet. What breaks is scale. With four branches you get four files, four naming conventions, and no way to answer which branch converts walk-past traffic best. And a date typed in a cell never rings anyone.

Inside a CRM the same field list becomes a form on the counter phone, the follow-up column becomes a task queue with an owner, the consent flag becomes a segment you can message, and the out-of-stock rows become a purchase report.

Free-text outcomes. If staff can type anything they will, and the column stops being countable within a month. Use seven fixed codes.

Logging only serious enquiries. The definition of serious drifts, and it drifts towards a better conversion number. Log browsers too and filter later.

Numbers without consent. A register of numbers that cannot be messaged is a liability.

No owner on the follow-up. A due date without a name belongs to nobody. Assign it while the customer is still in the shop.

Continue with lead management software, CRM versus Excel, WhatsApp CRM, the built-in dialer, CRM for small business, and the full tools library.