For brunch spots, third-wave coffee shops, weekend pastry rushes
Café waitlist app — free queue tool for brunch and coffee.
Saturday-morning brunch queues. The pastry shop with a 9am rush. The third-wave espresso bar with limited bench seating. The List is a free café waitlist that runs in any phone browser — customers join the queue, you focus on pulling shots.
Save the queue from your front door.
Customers can wait at the patisserie down the road and watch their position from their phone. Your front door doesn't need to be a holding pen.
QR self-check-in for the queue
Customer scans the QR on the door, types their name and how many people they're with, gets a queue position. No staff intervention.
Party size matched to bench / table size
Two people for the window seat, four for the corner banquette. The dashboard shows every party's size — your barista picks the right party for the table that opens.
Customers can wander while they wait
Phone capture is optional — text them when their table's ready. They go to the bookshop next door, come back when they're up.
No app to download
Walk-in regulars and Saturday tourists alike just scan the QR. Pure browser flow, no install friction.
Free forever
No monthly fee, no card on signup, no per-customer charges. The cost of running it is whatever a free QR poster costs to print.
GDPR-friendly auto-delete
Names and phone numbers auto-delete 48h after the queue closes. No long-term customer database to manage or worry about.
The café-queue problem is specifically a weekend problem. Tuesday at 11am, plenty of seats. Saturday at 10am, a 30-minute queue snaking around the block, the host losing track of who's actually waiting and who just popped in to ask if there's a queue. The clipboard works at low volume. At weekend brunch volume the clipboard becomes the bottleneck — a barista pulled away from the espresso machine to take names is a barista not pulling shots.
The List moves the queue off the front door. Customers scan the QR — printed on a window sticker or on the menu board — and join a queue from their own phones. They can wait inside if there's room, or wander to the patisserie across the street, or sit on a bench in the park, and watch their queue position update live on the page they're already on. When their table's ready, the host taps Done on the previous party and the next party gets a visual cue (or a text, if they entered a phone number).
It works for the spectrum of café formats. Third-wave espresso bars with limited bench seating where the queue is part of the brand. Brunch spots where parties of 4 take the corner table and parties of 2 take the window. Pastry shops with a 9am rush before they sell out of the cinnamon buns. Independent coffee shops in tourist areas where the front-of-house is overwhelmed with walk-in traffic from people who don't speak the local language but can scan a QR fine. The product doesn't care which format — the underlying mechanic is the same.
Free forever for cafés. No monthly fee, no per-customer charge, no tier you'd hit at busy weekends. Optional pay-per-SMS bolt-on (~$0.10/text) for cafés that want to text customers when their table's ready, which is roughly $3-8 across a busy Saturday brunch — vs $89-299/month for the equivalent feature in Yelp Waitlist or Waitwhile.
Saturday brunch — 25-cover indie café, the actual flow
Typical run-of-show
- 1QR poster on the front door + tucked into the menu.
- 29:30am: queue forms. Customers scan QR, type name + party size.
- 3Barista runs admin URL on their phone behind the counter.
- 4Table opens — barista glances at queue, taps Done on next-best-fit party.
- 5Customer sees their position update; if they gave a phone number, optional SMS.
- 611:30am: queue tapers. Close browser. £0 spent on software.
Café-specific use cases we've watched in the wild
The pastry-rush problem: weekend cafés with limited pastry stock often see customers queue specifically for the pastries, not for a table. Use The List as a pastry-pickup queue — first 30 names get the kouign-amann, after that you're tomorrow's customer. Eliminates the "is this still going to be here when I get to the front" dread that makes queues toxic.
The reading-bench café: a popular indie café with a single big communal table that turns over every 90 minutes. Walk-ins want the table for an hour of laptop work. The List handles party-of-1 / party-of-2 / party-of-4 differently because the corner is a 4-person space. Host glances at queue, picks the next 1 when a single seat opens, picks the next 4 when the corner clears.
The brunch-and-wander spot: a café where the standard customer behavior is to put their name down, walk to the bakery, buy bread, walk to the bookshop, browse, and come back when their phone says it's ready. The List automates the "come back when ready" part without a tablet at the door.
Café vs restaurant — when to pick which page
If you serve hot food at table service with seated guests, the /restaurant-waitlist page is closer to your use case. If you primarily serve coffee + pastries + light lunch with a quicker turnover, this page captures the workflow more accurately. The underlying tool is the same — both pages just frame the use case differently for SEO and onboarding clarity.
If you do both (a café that runs a brunch service Saturday and a coffee bar Tuesday-Friday), pick whichever framing your audience searches for and use the same tool for both shifts.
Questions hosts ask
Will my regulars actually scan the QR or will they just queue at the counter?+
Regulars usually do both — they queue at the counter, the staff member writes their name into the queue dashboard for them. The QR is for new customers and the Saturday rush. The dashboard handles staff-added entries identically to QR self-signups.
Does this work with a single-employee Saturday morning shift?+
Yes — that's actually the easiest case. The barista runs everything: makes coffee, glances at the dashboard between drinks, taps Done as tables open. The QR self-check-in means the barista isn't pulled away from the machine to take names.
What if the customer doesn't have a phone or won't scan?+
Staff can manually add a name to the queue from the same admin dashboard. The QR is the path of least resistance, not the only path. The system doesn't care how the name got into the queue.
Can I show customers a wait estimate?+
Position number, yes. Time estimate, no — wait time depends on table-turn rate which we'd have to track over multiple sessions, and we delete data after 48h. Most café customers prefer the position number anyway because it's accurate ("you're 3rd") rather than aspirational ("about 12 minutes").
Does this integrate with my coffee shop POS / loyalty program?+
No, deliberately. The List is narrowly scoped to walk-in queue management. Use Square / Toast / iZettle for POS and loyalty — those tools do their job well, and we don't try to compete with them.
Is there a way to print a daily customer count for accounting?+
Not in v1. We delete customer names after 48h on purpose — the privacy default is more important than the analytics. If you want daily customer counts, your POS already records them via transactions.
Ready in 10 seconds.
Tap the button. Share the QR. That's it.
Running something else?