Norwegian Energy Drink Vending Machine Age Verification

When someone fails at a vending machine, it looks like a user error. In reality it is a funnel problem. A vending machine is a high-intent moment with low patience. People are standing in public, they want the purchase to be quick, and they are not in the mood to troubleshoot.

Age verification adds a hard constraint. The flow must be compliant, but it also has to work for the actual audience at the machine. In Norway, that audience often includes tourists and international students who may not have local IDs or may not expect the machine to assume them.

The product goal in this setting is simple. Verify age quickly without excluding legitimate buyers or creating a confusing stop sign that feels like a dead end.

This case started from observing repeated failures at machines rather than reading a specification. The same moments happened often enough to form a pattern:

• High intent did not translate into completion. People approached the machine ready to buy, then dropped out once verification became unclear or felt impossible.
• Local ID assumptions blocked legitimate buyers. Tourists and international students were more likely to fail because the flow implicitly expected a Norwegian identity setup.
• Vending contexts punish slow flows. Extra steps, unclear instructions, or switching to a phone-based flow increased abandonment quickly.

The key insight was that this problem is not about education. It is about flow design in a low-attention, high-friction environment.

The requirement is compliance, but the product problem is conversion under constraint. The verification flow must satisfy legal requirements and still feel fast and inclusive for the real population using the machine.

I framed the solution as a two-path strategy:

• A fast local path for people with Norwegian identity rails, optimised for minimum steps and near-instant completion.
• A visitor-friendly path for everyone else, designed to verify age without requiring a local ID assumption or forcing account creation.

The decision logic is simple. Do not make every buyer pay the cost of the hardest verification method. Route users into the fastest compliant path they qualify for.

• BankID-only Fast for locals, but excludes visitors and international students. Exclusion becomes lost revenue and poor user trust.
• App account as the default Too slow for vending. Creating an account is not a vending moment behaviour.
• Document scan flows High friction and high failure risk in public settings. Lighting, camera quality, and error handling all increase abandonment.
• Improving copy only Helpful but insufficient. If the structure assumes a local identity system, better wording does not remove the block.

Build a two-path verification flow that keeps the local experience fast while providing a visitor-friendly option that does not require becoming a user.

• Local path: one-tap identity verification designed for speed and near-zero confusion
• Visitor path: a compliant method that works without local ID assumptions and has clear failure recovery
• Instrument the funnel: measure completion time and drop-off reasons for each step

The MVP is successful if verification time drops, completion rises, and the visitor path reduces hard stops while remaining compliant.

• Conversion rate at the machine Measures how many purchase attempts result in a successful vend. This is the primary signal that the verification flow is working in the real environment.
• Verification completion time Measures speed under constraint. In vending contexts, seconds matter, so this validates whether the flow is fast enough to keep high-intent buyers.
• Drop-off reasons Measures why users abandon. Categorizing drop-off (timeout, verification failure, user cancellation, unclear instructions) tells you what to fix first.
• Differences by location type Measures audience fit. Tourist-heavy areas and campuses should show higher benefit from a visitor-friendly path if the hypothesis is correct.

AI helped structure the decision matrix, generate interview scripts, and draft alternative flow options. The real value in this case came from observation, funnel framing, and choosing a strategy that can be measured quickly in the field.

• Turn this into a thought piece with a clear funnel diagram and the conversion problem framing
• Decision matrix artifact comparing verification methods by speed, inclusivity, compliance, and failure rate
• Two example flows showing the local path and visitor path with step-by-step screens
• Field test plan covering pilot locations, instrumentation, and success thresholds