AI SYSTEMS • GUEST FLOW DESIGN • OPERATIONAL STRATEGY
AI Self-Checkout System Design for The Nest
Led system selection, checkout flow design, and implementation planning for a
new high-volume restaurant concept at a mountain resort. By evaluating guest flow patterns,
throughput data, and staffing models, I determined that Mashgin’s AI self-checkout system
was the best fit for the concept and operational constraints.
Location
The Nest – Snowbird
Timeline
Feb 2025 – Feb 2026
Technology
Mashgin AI Self-Checkout
Stations
4 checkout devices
Overview
Project Overview
Context
High volume, limited space - rethinking the checkout model
A high-volume restaurant concept at a mountain resort needed a checkout system that could handle large guest volumes within a limited physical footprint.
As the systems lead, I evaluated checkout technologies and designed a guest flow that prioritized speed, throughput, and operational efficiency.
Early analysis showed that a traditional POS setup would create bottlenecks and limit throughput, making it difficult to meet demand within the available space.
Decision drivers
Why the problem mattered
Speed of service was critical in a high-volume environment
Limited space restricted traditional checkout setups
Guest flow needed to remain efficient during peak periods
Labor efficiency was a key operational priority
The project served as a pilot for a scalable checkout model
The Problem
Traditional checkout would not fit the concept
01
Space constraints
The layout limited the number of traditional checkout stations without disrupting guest flow.
02
Volume pressure
Peak service required significantly higher checkout capacity than standard setups could support.
03
Labor efficiency
The solution needed to maintain throughput while adhering to labor guidelines.
Research
How I evaluated the options
Data-driven evaluation
Throughput and guest flow shaped the decision
Analyzed transaction volume, peak rush windows, and service patterns from two other
on-mountain restaurants to estimate what checkout capacity The Nest would need. I also
evaluated how different systems would affect staffing needs and guest flow.
Comparable data
Used transaction and volume data from two similar on-mountain operations
Checkout options
Compared traditional Square setups against self-checkout alternatives
Guest flow
Studied how line movement and station placement would affect throughput
Labor model
Measured the staffing implications of each checkout approach
Capacity planning
Determined that the space and volume required four Mashgin devices
Decision criteria
Focused on speed, footprint, labor savings, and operational fit
System Selection
Why Mashgin was the right fit
Decision summary
Traditional checkout would not support the space or volume
Early planning focused on whether a standard Square-based checkout setup could support The Nest.
After reviewing guest flow, physical space, and transaction data from comparable on-mountain outlets,
it became clear that a traditional staffed checkout model would create bottlenecks and require more
labor than the concept allowed.
Space: Traditional lanes would take up too much room within the restaurant footprint.
Flow: Guest movement would bottleneck during peak service windows.
Staffing: Four Mashgin devices could replace three employees.
Fit: Mashgin was better aligned with the speed and layout The Nest required.
Pilot Strategy
Pilot Deployment Strategy
Pilot value
More than a one-location install
The restaurant served as a pilot environment for evaluating AI self-checkout in a high-volume
hospitality setting. The project was designed not only to support the new concept but also to
generate operational insights for future implementations.
The pilot allowed the team to collect real-world performance data, observe guest adoption,
and evaluate whether AI-powered checkout could support long-term operational efficiency.
What the pilot proved
Confidence before opening
Confirmed the approach could work at scale
Created data and learnings for future implementations
Allowed the team to understand the operational realities of AI checkout
Showed how guests interacted with the system
Operational Design
Translating system needs into physical space
Checkout flow
Placement and station layout
Register placement
Positioned checkout devices within the guest flow
Queue movement
Designed to minimize congestion and keep traffic moving
Tray flow
Mapped how guests approach, scan, pay, and exit
Operational fit
Aligned the checkout flow with real layout constraints
Counter design
Physical requirements
Counter dimensions
Defined required measurements for checkout stations
Equipment clearance
Allocated space for hardware and supporting equipment
Design input
Informed counter design and functionalityn
Operational decisions
Determined the setup that best supports F&B operations
Implementation
What I owned
Project lead
Operational lead for the system
As the operational lead for F&B systems, I owned the core system decisions around
checkout selection, guest flow, station requirements, and operational fit.
System research
Researched available checkout approaches and evaluated operational fit
Data analysis
Used historical transaction data to estimate required throughput
Vendor engagement
Worked with Mashgin after the first round of research and layout evaluation
Flow design
Defined where devices should go and how guests would move through checkout
Counter requirements
Provided measurements and physical requirements for the final build
Decision leadership
Served as the primary operational decision-maker for the system
Outcome
What the project delivered
Operational outcomes
A checkout model designed for the concept
The final system gave The Nest a checkout experience that better matched its space,
projected volume, and labor goals than a traditional staffed POS model would have.
Four Mashgin devices sized to support projected restaurant volume
Reduced labor needs by replacing three staffed positions
Opened The Nest in December 2025 with the new checkout model in place
Created a pilot use case for future Powdr self-checkout decisions
Unique on-mountain checkout experience
Built a model for future rollout
Key Takeaway
What this project reinforced
Technology decisions in hospitality are rarely just software decisions. They are space,
labor, flow, and guest-experience decisions. This project showed how data analysis,
operational design, and vendor evaluation can come together to shape a better system.
The final system aligned checkout with the restaurant’s space, volume, and labor constraints,
resulting in a model that performed under real operating conditions.