The Pavement Ledger: How a Data Co-op Could Even the Score for Small Shops
Photo: independent retailers meeting on a British high street, via wallpapers.com
On a damp Tuesday in a Midlands market town, the owner of a independent hardware shop knows roughly how many people walk past her window. She knows it's fewer than last year, and more than the week the road was closed. What she doesn't know is how her street compares with the one over the river, whether the new coffee shop two doors down is stealing her morning trade, or whether the council's plan to move the bus stop will help or hurt. The out-of-town retail park has dashboards for all of this. The online giants have more. She has a notebook and a feeling.
That gap—between the data a high street generates and the data its businesses can actually use—isn't an accident. It's a market failure dressed up as a technology problem. And it's fixable with a model that looks a lot like the mutuals that built Britain's retail co-ops in the first place.
The asymmetry isn't accidental
Footfall data already exists. Councils commission pedestrian counts for parking strategy and transport bids. Business Improvement Districts buy it to justify Christmas lights and late-night opening. Card processors and mobile network operators sell aggregated spend and movement data to anyone with a budget. The problem is that the small shop at the end of the row is usually a data donor, not a data owner: its card terminal, its Wi-Fi, its very presence contribute to somebody else's model, and the resulting insight is sold back to landlords or used to set business rates.
Meanwhile the independent retailer makes decisions on gut feel. That's not a criticism—gut feel is often excellent—but it's no match for a competitor that can see the whole board.
A different kind of utility
The proposal is a high street data cooperative: a member-owned, not-for-profit entity that collects, anonymises and shares three things—footfall counts, dwell time and spend bands. Members would include independent retailers, the local council, the BID, and perhaps community groups or libraries. Governance would be deliberately mixed: one member, one vote for retailer members; a seat or two for the council and BID; and a hard cap on any single member's influence. No chain should be able to outvote the row.
Data would come from sources that already exist—pedestrian counters, anonymised card aggregators, opt-in Wi-Fi counts that discard device identifiers immediately, manual clicker tallies by staff, event attendance, car park ticket machines. The co-op's job is to blend them into a single local dashboard, updated weekly, that any member can query without a data science degree.
Who pays, and who governs
Nothing about this is free, but it needn't be expensive. A typical town-centre co-op could be seeded with £30,000–£60,000 from the council's high street or economic development budget—roughly the cost of a single consultancy report that nobody reads. Ongoing costs would come from three places: a top-slice of the BID levy where one exists, membership fees scaled to rateable value with a cap for the smallest shops, and tightly controlled data licensing to permitted users such as transport planners, researchers or property owners. That last one needs a community benefit clause and a veto for members. No sale to hedge funds. No advertising. No passing the data to a landlord who wants to regear leases.
Safeguards: the boring bits that matter
The fastest way to kill this idea is to get the privacy wrong. A credible co-op would start in the Information Commissioner's Office sandbox, adopt k-anonymity thresholds (no cell published with fewer than ten observations), ban re-identification outright, and maintain a public register of every data use. Members would have a veto on new purposes. Algorithms would be open source. An independent annual audit would publish its findings in plain English. And there would be a sunset review every three years—if the thing isn't working, it winds up.
That may sound like a lot of governance for a footfall counter. It isn't. Trust is the product.
What small shops could actually do with it
Here's the practical bit. A bookseller could compare her conversion rate—people who come in versus people who buy—with the street average, then test a new window display for a fortnight. A café could show the council that late-night opening draws 40 more people into the town centre on Thursdays, making a case for cheaper evening parking. A group of retailers could negotiate rents with evidence of street-level footfall rather than a landlord's optimistic brochure. A BID could apply for grant funding with hard numbers instead of anecdotes. And a council could see, in near real time, whether its pedestrianisation trial is working.
None of that requires tracking individuals. It requires counting feet and sharing the count.
Where it could go wrong
Plenty of ways. Free-riding—shops that take the dashboard but won't contribute counts—is the classic co-op problem, best solved with a low membership fee and a clear reciprocity rule. Data quality can be patchy, especially in towns with no existing counters. Governance can be captured by the biggest retailer or the most vocal BID manager. Surveillance creep is a real risk: someone will always ask to add facial recognition or loyalty-card linkage. The answer is a constitution that says no.
And there's the digital exclusion problem. Not every independent retailer wants a dashboard. The co-op should offer a printed monthly summary and a phone call, not just a login.
A small idea with long legs
This won't save the high street on its own. Nothing will. But data is infrastructure now, as much as a bus shelter or a broadband cabinet. If independent shops are going to compete with businesses that can see around corners, they need a ledger of their own—one that belongs to the people who walk the pavement, not the people who sell the map. A local data co-op is a modest, practical way to build it. And it starts with counting what's already there.