BITO

The connectivity gap in age verification is a compliance risk retailers can no longer ignore

AgeAI

Nicolas Sierro, Product Manager, Privately SA

A convenience store in the UK over the weekend is a busy place. You will find staff managing queues, restocking shelves, handling cash, fielding questions and checking IDs. This is often taking all at the same time. Somewhere in that pressure sits a growing compliance burden: age verification is getting harder, and the tools most retailers rely on have not kept pace.

The regulatory picture has changed significantly in a short space of time. Retailers already navigate different age thresholds depending on the product at the till. It’s 18-plus for tobacco and vapes, Challenge 25 for alcohol, and potentially a 16-plus requirement for energy drinks, still under discussion. 

The UK Tobacco and Vapes Bill, expected to come into force in 2027, adds further complexity, with its generational ban requiring retailers to assess not just whether a customer appears old enough, but when they were born. All this, applied consistently across a busy store with variable staffing and high turnover, is a major operational challenge.

Yet the dominant response in most convenience stores remains the same as it has been for years: a member of staff makes a judgment call. This is understandable – familiar, low-cost – but not sustainable in modern times. It’s highly inconsistent and leaves a retailer vulnerable. The answer is automation.

Three problems most solutions ignore

Automated age verification is not a new idea. Cloud-connected systems have been available for some time. But conversations with retailers reveal a consistent set of objections that have slowed adoption. They tend to cluster around three issues: privacy, speed, and connectivity.

Privacy – we live in an era when privacy is protected more than ever. Customers are increasingly aware of how facial data can be collected and misused. There is a meaningful and important distinction between facial recognition and facial age estimation, which asks a single yes-or-no question and discards everything used to answer it. The privacy architecture of any system matters as much as its accuracy.

Speed – a check that adds meaningful seconds to a transaction in a busy store is not a viable solution. Facial age estimation that completes in under a second changes that calculation. So does the question of who is actually doing the work: if a majority of customers complete the check themselves without cashier involvement, the system is running in parallel with the transaction rather than interrupting it.

Connectivity – this is perhaps the least-discussed of the three, but it may be the most practically significant. Cloud-dependent age verification systems sound compelling in a product demonstration. They tend to perform less well on a busy Saturday afternoon in a rural forecourt or in an older retail premises where network infrastructure has not been updated in years. The failure mode is not minor: a system that relies on a live connection to process an age check will either stall the queue or default to letting the transaction through when connectivity drops. Neither outcome is acceptable from a compliance standpoint.

This is the gap that on-device processing addresses. When everything takes place on the device itself – no image transmitted, no server queried, no biometric data leaving the premises – network availability is irrelevant. The system performs the same whether the store has full 5G coverage or a patchy rural signal. 

The staffing element

There is another element to this that does not always surface in the technology conversation: what it is like to be the staff member making the call. Asking a customer their age, or refusing a sale, is not a neutral act. It can be confrontational. For younger employees especially, it can feel genuinely uncomfortable. 

Having a system that makes an objective determination, and escalates to a human only when it cannot, removes the social pressure from the individual at the till. That matters for compliance too. Inconsistency in age checks is rarely deliberate. It tends to be a product of discomfort, time pressure, or uncertainty about the rules. 

A system that handles the determination consistently and produces an auditable log of every check and its outcome gives retailers a far stronger position than staff memory in the event of a compliance query.

Getting ahead of the regulation curve

It’s a true challenge, but the good news is that the technology has matured to the point where implementation does not require major capital investment or disruption to store workflow. 

An Android device near the till, integrated with existing EPOS systems to trigger checks automatically on restricted products, is a low-friction starting point. As the regulatory pressure is not going away, the better question is not whether to act, but whether to act now or wait until the compliance stakes are even higher.

Dorotape