Barbershop Walk-In Queue and Payment App: Running a Saturday Without Losing Track

Saturday, 11 a.m. Six people in the chairs and on the bench. Two of them want Marcus specifically and will wait. One has been there twenty minutes and is starting to look at the door. Someone walked out ten minutes ago and you are not sure who or whether they were next.

That is the problem a walk-in queue app solves. Not scheduling — scheduling is the easy half.

What a real walk-in queue has to handle

Check-in in under ten seconds. Name, phone, service. If it takes longer than that, the person at the front desk stops doing it during the rush, which is exactly when it matters.

"I'll wait for Marcus." A queue that is strictly first-in-first-out is wrong for a barbershop. Clients request specific barbers, and the request has to travel with the entry so Marcus's line and the next-available line coexist.

An honest wait estimate. Every service has a duration. Sum the queue ahead of you, divide by the barbers who can take it, and you can tell someone "about forty minutes" instead of "not long." People will wait forty minutes. They will not wait "not long."

Priority, without a fight. The client who called ahead, the regular who has been coming for eleven years, the kid who needs to get to a game. You need a priority flag that is used occasionally and visibly, not a hidden reordering.

The exits. People leave. Entries need to end as completed, cancelled, or no-show, because the difference between those three is the difference between a good day and a day you should study.

A path to payment that is not re-typing. The queue entry already knows the client, the service, and the barber. Sending that to the register should be one action.

How Dokani does it

Dokani's queue entry carries the customer (or just a name and phone for someone new), the service, an estimated duration, the requested barber, a priority flag, party size for the parents bringing two kids, and free-text notes. Status moves waiting → serving → completed, with cancelled and no-show as real endpoints rather than deletions.

Because a queue entry already holds the service and the barber, closing it hands the register a ticket that is already correct — right service, right price, right person credited. That last part is what makes the commission and tip reports work at the end of the week without anyone reconstructing who cut what.

The queue and the appointment calendar are the same day. Pre-booked clients and walk-ins appear against the same barbers and the same customer list, so your regulars are not duplicated across two systems.

The payment half

In person. Cash, card, and split tenders are recorded on the ticket. Card payments go through the terminal you already have, and get recorded as a card tender so your tender summary and your payouts stay correct. Dokani does not tap the card itself today — tap-to-pay on Android is in development and we will say so plainly until it ships.

Tips, per barber. Tips are recorded against the worker who earned them, cash or card. Pooled tips get expanded into per-worker rows on a stated basis. Payout is a separate recorded event, so "what do I owe out of the drawer" is a report, not a memory test.

Online, before they arrive. Your booking page can take a deposit or full prepayment through Stripe (US). For a shop with a no-show problem, a deposit on the highest-demand slots does more than any reminder.

Reminders. WhatsApp and email reminders are included on every tier, SMS as a paid add-on. The cheapest queue-management technique is the client who shows up on time.

Why offline matters more here than anywhere else

Your queue is at its most valuable during the rush, and the rush is when the shop Wi-Fi is loaded with six phones streaming. A cloud-only queue that stalls at 11 a.m. on a Saturday is worse than a whiteboard, because a whiteboard never spins.

Dokani runs against a local database on the device. The queue, the register and the reports keep working with the internet off; cloud sync catches up when it returns, and syncs in real time when you are online. If you run two stations, they sync over your own LAN — the front desk and the back station see the same queue without a round-trip to a data center.

What to look at before you pick anything

1. Can a walk-in be checked in without creating a fake appointment?
2. Does the queue survive an internet outage?
3. Does a completed queue entry become a ticket, or do you re-type it?
4. Is a specific-barber request a first-class concept or a note field?
5. Are no-shows counted, or just deleted?
6. Does the tip land on the barber who earned it, automatically?

Most tools pass one to three. The last three are where the money leaks.

FAQ

Do I need appointments if I am 90 % walk-in? Keep them available but do not build around them. What you need is a fast queue and a clean path to payment; appointments are for the regulars who ask.

Can clients see the queue from their phone? Dokani's queue is staff-facing today, with online booking for appointments. If self-service check-in is a hard requirement, verify it before you switch.

How do I handle two barbers on one head — a cut and a beard? Put both lines on the ticket, each attached to its barber. Commission and tips then follow the work rather than the ticket.

What hardware do I need? A Windows PC or an Android tablet or phone. Receipt printing is supported. There is no iOS app today.

---

Dokani runs a walk-in queue, an appointment calendar and a register in one offline-first app. Download it or see pricing.