One product serves many tasks.
Order entry, search, payment, approval, customer accounts, printing, and service modes share one system.
Work 04 · Core platform
Point of
Sale
I built responsive rules for the screens that move a restaurant from login to payment.
Read the case study ↓
My roleProduct and UX design
Responsive rules, workflows, handoff, and release review
ProductVolanté POS
Restaurant order entry and service
Period2023 to 2026
Work with design, product, engineering, and quality assurance
Scale1,064 active POS terminals
Plus 84 active Cloud POS devices on September 14, 2026
Product at scale
The shared POS system reached production and now supports a large active footprint.
1,064Active POS terminals
84Active Cloud POS devices
17,773,950POS transactions
50.4%Of Volanté transaction volume
Volanté Product Specialist data from January 1 to September 14, 2026. The active footprint covers 422 live locations.
Project value
Make fast restaurant work stay clear across screens, modes, and input devices.
What the design needed to achieve
- ✓
Scale type, spacing, popups, and controls across three terminal sizes.
- ✓
Use one keyboard and keypad across login, search, payment, and approval.
- ✓
Organize each workflow around its ticket, states, behavior, and prototype.
Every exception costs time.
Different layouts and input behavior slow staff during busy service and create more training work.
Turn patterns into a system.
Responsive guidance and shared components reduce repeated decisions across product and engineering.
Design decisions
Build reusable rules before adjusting individual screens.
01Start from real terminal sizes
Responsive foundation
The 26-page responsive file covers 1366 by 768, 1366 by 1024, and 1024 by 768 terminals.
Intended impact
Each layout decision has a clear reference size and manual device check.
02Research search behavior
Pattern study
A 142-participant placement study guided search position, button behavior, and suggestions.
Intended impact
Staff find search where they expect it and understand how results will respond.
03Share one keyboard
Common input
The Bar Tabs keyboard became the shared POS input for search, cash payment, manager override, and login in GA13.
Intended impact
Staff reuse the same input pattern across devices and tasks.
04Design for physical inputs
Device behavior
Touch, keyboards, scanners, cards, drawers, printers, scales, and payment devices all need clear ownership and recovery.
Intended impact
Disconnected, delayed, duplicate, and retry states become part of the workflow.
Product proof
The design system grew from guidelines into shipped platform patterns.
2,508 frames
The 26-page guidelines cover sizes, gutters, popups, keyboards, keypads, and shared behavior.
6,474 frames
The 36-page Quick Menu file holds ticket-based work across orders, customers, transactions, discounts, gift cards, and printing.
Login and home
The Bar Tabs redesign became the POS login and home across service modes in February 2026.
Result
The shared system reached production and now supports a large active footprint.
GA13 keyboard
One responsive keyboard replaced the legacy pattern across major POS input tasks.
Three terminal sizes
The released guidance covers 1366 by 768, 1366 by 1024, and 1024 by 768 terminals.
142 participants
The placement study guided search position, button behavior, and suggestions.