Rowomat Research · Note 01

Managing a barbershop queue under variable walk-in demand.

An analysis of queue control when arrival time is unknown, service duration varies and available capacity changes throughout the day.

Author: Rowomat operations teamEditorial review: 28 August 2026Basis: the Rowomat operating model and the cited primary research in queueing and service operations.

Executive summary

A queue must be an operating system, not a list of people.

Walk-in service does not mean service without rules. It means demand arrives without a reserved time. That makes order, capacity and customer information more important than in a system that schedules every arrival in advance.

During quiet periods, the queue can exist in staff memory and among the people in the room. Under load, that model fails: different versions of order appear, wait estimates are given without enough evidence, and staff interrupt service to explain the line. The problem is no longer only a long wait. It is the loss of a reliable operating record.

A digital queue is useful only if it becomes the sole source of order. Public link, kiosk, Staff application, customer phone and TV must not maintain separate lists. Every surface must read the same branch, ticket and service lifecycle state.

Research basis

Four facts a reliable queue system must respect.

Little's Law links the average number of units in a stable system, throughput and average time in the system. For a salon, the implication is direct: if people enter faster than available staff can complete service, waiting must grow. A virtual queue can remove people from the waiting area, but it cannot repeal the flow constraint.

Kingman's heavy-traffic work explains why planning for nearly 100% utilisation is not evidence of an efficient operation. When arrivals and service times vary, small disturbances in a near-full system create disproportionately larger waits. Capacity reserve is not automatically waste; it is often the only room the operation has to absorb variation.

Maister's analysis separates objective waiting time from the way a wait is experienced. Uncertain, unexplained or apparently unfair waits feel longer. A ticket number is therefore not enough: the customer needs to understand position, what can change an estimate and whether order is being applied consistently.

A field experiment by Yu, Zhang and Zhou covering more than 1.4 million virtual waits found that initial delay information and update frequency affected abandonment even though actual wait did not vary between groups. The study was not conducted in salons, but it establishes an important warning: ETA is not decorative copy. Its calculation and update policy form part of the operating promise.

Operating flow

Admission through completion requires one continuous record.

1. Admission

The customer selects a real branch and service. Before issuing a ticket, the system checks opening hours, channel policy, available services and projected completion of existing work.

2. Preserve order

The issued ticket is the durable record of place in line. A later estimate change must not silently change order or turn an estimate into an appointment promise.

3. Wait and return

The customer follows ticket and position away from the shop. Messaging must distinguish confirmed position from estimated time because they have different levels of certainty.

4. Execute service

Staff call next, start, pause and finish service from one operating view. Other surfaces display the consequence of those decisions; they do not maintain their own queue.

5. Record exceptions

No-show, cancellation, work interruption and sudden capacity loss must be explicit states. An unrecorded exception leaves the queue formally ordered but operationally false.

Control model

What the system must know and who may change state.

Queue unit
One issued ticket for one branch, service and customer language.
Source of order
Canonical queue position; not an estimate and not the order shown on one device.
Source of capacity
Staff actually on duty, the services they provide, breaks and branch opening hours.
Source of duration
Defined service duration corrected by actual flow, rather than one average for the whole shop.
Decision owner
The local Staff flow changes ticket state; public link, kiosk and TV expose permitted views only.

Measurement

Measure system behaviour, not only tickets issued.

Throughput
Completed services per hour and per staff member, separated by service type.
Waiting
Median and 90th percentile from ticket issue to service start; the mean alone hides peak failures.
Abandonment
Cancelled, expired and no-show share, including the point at which customers left the flow.
Estimate error
Difference between displayed estimate and actual service start across the full distribution.
Utilisation
Service time against available time without concealing breaks or unavailable staff.
Record quality
Share of tickets with start, finish and a reason for every exception recorded correctly.

Common model failures

Digitising a weak process only distributes its errors faster.

Parallel lists

Paper, verbal agreement and the digital queue produce three answers to who is next.

False capacity

Staff who are absent or cannot perform the selected service must not increase available capacity.

One duration for every service

Haircut, beard and complex work cannot share a generic duration when they load the queue differently.

ETA as a promise

An estimate without visible uncertainty becomes an appointment promise a walk-in operation may not keep.

Mean without the tail

Average wait can look acceptable while some customers wait several times longer. Percentiles are essential.

Evidence boundary

What research supports and what must still be measured in a salon.

This study combines Rowomat's functional model with general findings from queueing and service-operations research. The sources support principles of flow, heavy traffic, waiting experience and information effects. They do not establish a business outcome for a named barbershop using Rowomat.

Findings from healthcare and transport are transferred only at the level of a shared operating mechanism: uncertain arrivals, variable service duration, limited servers and possible abandonment. Their effect sizes are not presented as expected salon results.

A customer case study requires a defined baseline, a sufficiently long post-adoption period, stable measurement and permission to publish. Until those conditions are met, this document remains a research-backed operating study, not a testimonial.

References

Primary work behind the operating analysis.

Sources are provided so every research claim can be checked. Interpretation and application to walk-in salons are original to this study.

  1. A Proof for the Queuing Formula: L = λWJohn D. C. Little · Operations Research 9(3) · 1961

    The fundamental relationship between average units in a stable system, throughput and time in the system.

  2. On Queues in Heavy TrafficJ. F. C. Kingman · Journal of the Royal Statistical Society, Series B 24(2) · 1962

    Analysis of queue behaviour when load is very close to available service capacity.

  3. The Psychology of Waiting LinesDavid H. Maister · The Psychology of Waiting Lines · 1985 / 2005 edition

    A classic operating framework for objective wait and the way customers experience it.

  4. Delay Information in Virtual QueuesQiuping Yu, Yiming Zhang and Yong-Pin Zhou · Management Science 68(8) · 2022

    A randomised field experiment on initial estimates, update frequency and abandonment in a virtual queue.

  5. Managing Appointment-Based Services in the Presence of Walk-in CustomersShan Wang, Nan Liu and Guohua Wan · Management Science 66(2) · 2020

    Shows that walk-in arrivals add distinct uncertainty that capacity planning must address explicitly.

Assess whether this operating model fits your shop.