Case study
QikServe Kiosk
Brand-specific, accessible self-service ordering that holds up under real operational pressure in 42 countries.
- Client
- QikServe / Access Group
- Role
- Head of Product Design
- Timeframe
- 2020–2026
- Sector
- Hospitality technology
- venue growth during my tenure
- 800 → 8,000+
- countries
- 42
- integrations
- 100+
- processed annually
- $1bn+
Context
QikServe builds the self-service ordering layer for hospitality. The kiosk is the most demanding surface in that estate: a single product deployed across thousands of venues, dozens of brands and dozens of countries, each with its own menu logic, payment setup and operational habits.
The platform it sits within grew from around 800 venues to more than 8,000 locations across 42 countries during my tenure, with over 100 integrations and more than a billion dollars processed annually. The kiosk is a configurable product that has to behave correctly for a global coffee chain and an independent operator from the same codebase. I joined when it was a promising product with a small team; by the end it was the flagship of an enterprise platform, and the design team had grown from one to five across the UK and Brazil.
Problem
White-label kiosks tend to fail in one of two directions. They either collapse into a generic template no brand wants to put its name on, or they fragment into bespoke builds that can't be maintained. Neither scales, and both fail the people standing in front of the screen.
The kiosk also carries an unusually high trust burden. It takes payment, handles allergen and dietary information, verifies age for alcohol, and does it all without a member of staff present. Any ambiguity in the interface becomes an operational problem at the worst possible moment, with a queue building behind the screen.
Constraints
Every decision had to hold up against real operations: legacy POS integrations, peripheral hardware, intermittent connectivity, accessibility legislation across regions, and brand guidelines that ranged from a loose steer to a strict system. A kiosk that works beautifully on a designer's monitor and falls over against a fifteen-year-old POS has not been designed; it has been drawn.
Accessibility was a hard requirement, not a finishing pass. The kiosk had to meet ADA and WCAG expectations as a physical and digital product at once, which shapes everything from reach and contrast to focus order and error recovery.
The structural model
The answer was to treat the kiosk as a system of configurable behaviours rather than a fixed screen. Each behaviour was modelled as a component an operator could turn on, restyle and arrange without touching code:
- Menu architecture and modifier trees, deep enough for a fully customised coffee or a built-from-scratch pizza
- Basket logic, cross-sell and upsell patterns at item and basket level
- Payment, loyalty, tipping and charity donation flows
- Age verification for alcohol, designed to work without a staff member hovering
- Attract screens in portrait and landscape, templated so brand teams could own them
Brand expression was scoped deliberately. Operators control styling, imagery and tone within a structure that guarantees the journey still works.
The system flexes on surface and holds firm on flow.
Designing for a queue
A kiosk user is not a website user. They're standing up, often holding something, often with someone waiting behind them, and they did not choose this interface; it was put between them and their lunch. That context drove the core interaction decisions: a menu structure legible at arm's length, predictable basket behaviour with no surprise states, and error recovery that never strands a guest mid-order.
The attract screen earned particular attention. It's the only moment the kiosk gets to sell itself, and the difference between a screen that invites a first-time user and one that intimidates them shows up directly in adoption. We built a template system for it so brand teams could produce their own without breaking the journey underneath.
The sharp edges
Complex cases were handled as first-class parts of the design, not afterthoughts. Coffee customisation, pizza builds, alcohol verification, tipping and charity prompts each had a defined pattern, so adding them to a deployment did not break the rest of the experience. Alcohol was the sharpest: an unattended surface selling an age-restricted product, across jurisdictions with different rules, has no room for an ambiguous state.
Accessibility as a physical product
A kiosk is hardware and software at once, so accessibility spans both: reach ranges and mounting heights on the physical side; contrast, focus order, target sizes and timeout behaviour on the digital side. We treated WCAG 2.1 AA and ADA expectations as the floor, and the work raised the accessibility standard across the wider product estate. Participation became a design default rather than a retrofit, and it turned up later in sales conversations as a genuine differentiator.
The kiosk as a transformation practice
The kiosk was also the front door to a professional services practice. Enterprise deployments came with brand consultation and digital-transformation work attached: translating brand guidelines into kiosk systems, advising operators on menu structure and attract-screen strategy, and carrying estates through go-live. I worked as a senior brand and digital-transformation partner to enterprise clients including Burger King, Starbucks, Costa, Krispy Kreme and Avolta, shaping journeys that delivered on brand promise and contributed directly to revenue growth.
Outcomes
The kiosk became the flagship surface of a platform operating across 8,000+ locations and 42 countries, deployed by major global brands alongside independents from the same configurable base. The work showed that white-label can still mean brand-specific: a well-structured system let QikServe sell distinctive experiences at scale without taking on bespoke maintenance, which is a commercial position as much as a design one.
Team and credits
Nothing at this scale is designed alone. I led design as Head of Product Design, and the credit belongs across the team:
- The QikServe and Access product design team, who owned whole surfaces of this work
- Platform engineering, who made configurable behaviours real against 100+ integrations
- Product management and customer success, who carried operator reality into every prioritisation call
- The operators and their floor staff, who stress-tested every release on a live shop floor and told us the truth about it
Stack and approach
- Figma with a token-driven theming model
- a component library built for operator configuration
- attract-screen template systems in portrait and landscape
- WCAG 2.1 AA and ADA conformance work
- and integration design across POS
- payment and loyalty providers
What I'd do differently
Instrument earlier. The system thinking was right, but we earned our outcome data slowly, and the case for several design decisions would have been cheaper to make with completion-rate and time-to-order numbers from day one. That lesson now travels with me into every product.