Appearance
Multi-location booking for a salon, in Laravel
A salon opens a second place across town. It is the same business: the same name, the same prices, the same clients, and some of the same people. Mira does colour on Linden Street from Monday to Wednesday and in Osborne Village on Fridays and Saturdays. Now the booking page has three new ways to go wrong. A client books Mira for a Friday at the wrong address, because the page does not know where she is that day. The floor in Osborne Village is redone on a Wednesday, and closing that day closes Linden Street too. The confirmation says "see you at the salon", and the client goes to the one they know.
The usual fix is a second account in the booking system, with a second client list and a second calendar, and the staff in both. kitloom/bookings now keeps several locations on one site instead: one client base, one price list, one team, and every visit at a place.
A site with one address sees nothing new
Until the first location is made, nothing changes. A salon at one address books as it always did, and no form, email or screen asks where.
Making the locations
Bookings → Locations → Make the first location from the settings turns the salon as it is into its first location. The address, the phone, the opening hours and Also notify move from Settings into it. Every staff member, every booking and every wish on the waitlist is put there, in one go. From then on the hours, the address and the phone belong to each location, and Settings says where they went.
A New location has:
- the name clients know it by, and a slug made from it;
- the address, a line each, and its phone;
- the Front desk's email, which hears of every booking there besides the staff member;
- its Opening hours (a new one starts from the salon's);
- its Days closed;
- a picture and a page of the site;
- Services done here: nothing chosen means every service;
- Takes bookings.
A service done in one place only says so on its own form, under Where: the hot towel shave needs the barber's chair, which is on Linden Street. A location is never deleted. Takes bookings off closes it to new visits, and its past visits keep saying where they were. That is refused while visits ahead, waitlist wishes or staff members' homes are still there, with how many of each.
Staff at two locations
Each staff member has a Home location. They work there unless a row of their Hours names another Location. Mira's Monday to Wednesday rows stay empty (her home, Linden Street); her Friday and Saturday rows say Osborne Village. A day at both places is a row at each, 10:00–14:00 in one and 15:00–19:00 in the other, and the two may not overlap. Their bookings make them busy wherever they are, and their time off counts everywhere.
Closing one location for a day
A holiday at one address, or a repair, goes into that location's Days closed, with the reason. That location takes no visits then, and its staff can still work at the other one. A day closed for the whole business still closes them all, as before. Visits already booked on a closed day stay where they are, so the desk moves them to another day or to the other location, or tells the clients.
What the client sees
Once two or more locations take bookings, Book asks Where first: a card for each, with its address. There is no "anywhere": a booking needs a location. After the choice, the client sees only that location's services done by people who work there, and their free times there.
The day strip tells the days apart. Closed is a day that location is shut. Away is a day the chosen person is not in, because they are at the other location or off. Full is a day when every time is taken. A link with ?location=osborne- opens Book with the place already chosen. A location's own page shows its address, hours and team under the owner's text, with Book here.
A client who moves their visit stays at its location, with a colleague who works there then. Only the salon moves a visit to another location, and the client is told as of any move.
The salon themes Atelier and Solace and the groomer's theme Fetch draw all of this, and show each location with its address, hours and phone. The kitloom app asks Where first in the same way, once the site has two locations.
Every message says where
The confirmation, the reminder and its text, the calendar file, the visit's page, the visit in the account, the series and waitlist emails, and the Google Calendar event carry the visit's location: its name, address and phone. The front desk that hears of a booking is that location's.
At the desk
The reception calendar has Every location and a chip for each one. One location's day has a column for whoever works there that day, and Book here books there. A closed day is said above the calendar, Osborne Village is closed all day · Floor repair, and the hours there are striped. New booking asks the Location first. All Bookings has a Location column and filter, and a manager can change a booking's location, which counts as a move. Nova's calendar has the same switch on its week.
The waitlist and repeat visits keep their place. A wish names its location, or Any location when the desk leaves it so, and a time freed at one location is offered only to the wishes for it. A series of repeat visits stays at the first visit's location, and a date that location is closed is skipped and reported.
Ask the agent
With kitloom/ai connected, an agent sees each open location's hours by its name in describe_, and bookings_ says whose each closure is. "Book Nora with Mira on Friday at ten" (bookings_) books where Mira works then. The agent's tools do not name a location yet, and a location's days closed are set on its form, not by the agent.
What is not there yet
- A price per location. A service costs the same everywhere: its own price, or the staff member's.
- A manager of one location. Whoever manages the bookings sees and runs every location.
- The till by location. kitloom/booking-checkouts keeps one day's takings for the whole business.
- A one-day shift elsewhere. Only the weekly hours say where someone works.
Salons of different owners or brands are not locations: each is a site of its own, on kitloom/multisite.
For a Laravel developer
Locations are a table of the module's own, booking_, with booking_ for the services a location does not do. location_ sits on staff, their hours, time off, bookings and waitlist wishes, and stays null on a site without locations. Location writes them with the acting user and has no delete. Availability takes an optional location, and with none it answers as it always did.
For a theme or an app: GET / lists the open ones with their hours. services, staff, slots, bookings, bookings/ and waitlist take location, a slug or an id. A booking without one, where several take bookings, is a 422 booking_. The site's API at / has location_ and location. The locations themselves are not a resource of it yet.
Watch it
Try it
- See it live: atelier.kitloom.dev is a hair salon on Linden Street and in Osborne Village, and grooming.kitloom.dev a dog and cat groomer in Riverside and Westbrook. Open Book and choose where.
- Have us build it: the salon solution or the grooming solution.
Locations come with kitloom/bookings, for either admin:
bash
composer require kitloom/bookings kitloom/bookings-filament
php artisan migrateOn a Nova site, the second package is kitloom/. Every detail, from the desk to the routes, is in the Bookings guide.