Barbershop Booking and Business Tracking
Follow bookings and the walk-in queue in a calendar with a column per barber. Send a booking link to customers on WhatsApp; your phone alerts you to each new booking.
Demo with sample dataIn a barbershop several customers want the same hour, and some walk in and wait their turn, so the records must carry both the barber-specific booking and the queue. This page uses the sample-data barbershop demo to gather what to settle before a project.
The calendar shows a column per barber, and the same barber cannot be booked twice for the same time. In the panel a barber sees only their own calendar; the manager sees everything, and reception works with bookings, customers and payments.
The waiting list is a page of its own, apart from the calendar: it does not write to the calendar or delete lines, and it warns when the chosen barber has an appointment coming up. Booked customers and people in the queue are not shown on the same screen. There is no automatic barber assignment, no priority by service and no wait-time prediction; these can be scoped separately.
When booking on the internet a customer can tick an extra service such as a beard shave next to the haircut (up to three); the minutes and prices are added up and it lands in the barber’s calendar as one booking. A booking entered in the panel is a single service; a frequent pairing such as “haircut and beard” can also be defined as a service of its own. The note on the customer card carries the detail of short jobs (“Sakal: makine 3 numara, ense düz.”, i.e. beard: clipper guard 3, flat neckline).
Each barber has a commission percentage of their own, calculated only from service revenue; product sales such as beard oil do not earn it. Separate percentages can be entered for master, journeyman or apprentice; there is no seat-based revenue.
A product such as beard oil sold on the ticket leaves the stock; a minimum level is set per product and the stock page warns about low items.
A package is sold from the customer card and each visit uses up a session; whether it works as a monthly subscription has to be tried separately.
These use sample data and are not customer references. Price, installation, migration, hosting, maintenance and support are agreed separately in written scope.
The product page walks through the app’s real screens step by step, the waiting-list screens included. The delivery and sales status are written there.
Follow bookings and the walk-in queue in a calendar with a column per barber. Send a booking link to customers on WhatsApp; your phone alerts you to each new booking.
Demo with sample dataThese parts of the barbershop product page answer the questions here with shop screens.
A record flow for keeping barber-specific bookings, phone bookings and the walk-in queue apart without mixing them up.
Read the guide →Put short jobs on tickets with their barber, tie the queue’s payments to tickets, keep the till apart and check each barber’s monthly commission.
Read the guide →Yes. The shop adds a phone booking from the calendar: the saved customer, the barber, the service and the time are chosen, and the program lists that barber’s free times.
No. A customer without an appointment goes on a waiting list apart from the calendar; the list shows the arrival order and the waiting time, and the shop chooses the barber when it takes the person in.
No. The reminder list opens a prepared WhatsApp message for confirmed bookings; the shop sends it from its own line, and no service sends messages by itself.
Not at the moment: the barbershop application has not been delivered to a client and has not passed a sales acceptance. Your shop’s needs and a possible route are discussed in a first conversation; the public demo runs on sample data only.
I can visit clients at their workplace in Bursa for in-person requirements discussions. We first identify existing records and workflows, then agree on features and delivery scope.
Do you run a hair salon? → · All guides · Custom software: web and desktop tools
Describe your requirements