Loading
Loading
CheckIn is multi-location first: one account owns every shop, each location keeps its own branding, hours and data, and the whole business rolls up into one view.
All locations
LiveWhen you open a second nail salon or spa, the tools built for a single shop start to fight you. You end up with a separate login per location, separate billing, and no honest way to compare last week across the group. Owners juggle a folder of bookmarks and four sets of credentials just to see how the business is doing.
Worse, the data is rarely kept properly apart. Many platforms simply hide other locations in the menu while every record still lives in one shared pile. One wrong filter and a manager at one shop is looking at another shop’s clients, staff hours, or revenue. That is a privacy problem and a trust problem.
CheckIn was built for the multi-location case from day one, not patched in later. The architecture every other feature sits on assumes you might run many shops, so adding a location is a normal step, not a migration.
Your business is a single account (the tenant). Under it you add as many shops as you run. Every client, booking, staff member and report belongs to a specific business and a specific location, always.
Data separation is enforced in the database itself, not just hidden in the interface. A query scoped to one shop physically cannot return another shop’s rows, so a manager only ever sees the location they are allowed to see.
An owner or multi-shop manager picks a location from a switcher and the whole app re-scopes to it. No second password, no second app, no signing out and back in to move between shops.
Set branding, working hours, queue rules and kiosk settings per location. Your downtown spa can open late and look one way while the suburban salon runs different hours and offers, all under one account.
The org-wide overview pulls every location into a single dashboard, so you can compare shops side by side on visits, revenue and wait times without exporting anything by hand.
Each shop gets a clean, readable web address with alias support, so an old or renamed link redirects to the right place instead of breaking.
A single business account owns every location you operate. Add a shop when you open one; there is no separate purchase or migration to start a new site.
Every record carries which business and which location it belongs to, and isolation is enforced at the database level. Locations cannot read each other’s clients, bookings, staff or revenue.
Move between locations from a built-in switcher. The queue, bookings, CRM and reports re-scope instantly to the shop you picked, with no second login.
Give each shop its own logo, working hours, queue rules and kiosk display, so every location can look and operate the way that suits it.
See the whole business in one overview: visits, revenue and wait times across every location, with subscription context, so head office never flies blind.
Each location gets a readable web address with alias support and clean redirects, so renaming a shop or merging links never sends clients to a dead page.
One client identity follows a person across all your shops, and a staff member can be assigned to several locations, while activity stays tracked per shop.
CheckIn sells per location, not per chair or per staff member, so hiring more techs or adding more seats never raises your bill for doing well.
Owners running two to fifty nail salons, head spas, day spas or hair salons who want one account, one bill, and one place to compare every site.
Operators who need each location to keep its own branding and hours while head office keeps a clean, group-wide picture and central control.
A one-location salon that wants software that will not need replacing the day a second shop opens. Start with one, add the rest when you are ready.
Yes. CheckIn is multi-location first. One account owns every shop, and an owner or multi-shop manager switches between locations from a built-in switcher without logging out or installing a second app.
Yes, and strictly. Every record knows which business and which location it belongs to, and isolation is enforced at the database level, not just hidden in the interface. One location cannot read another location’s clients, bookings, staff or revenue.
Yes. Branding, working hours, queue rules and kiosk settings are set per location, so each shop can look and operate differently while still living under one account.
Yes. An org-wide overview rolls every location up into a single dashboard covering visits, revenue and wait times, so you can compare shops side by side without exporting anything by hand.
CheckIn is sold per location, not per chair or per staff member. Adding more techs or more seats at a shop does not raise your bill, so growth is never penalized.
Yes. Each location has a clean, readable web address with alias support and clean redirects, so an old or renamed link sends clients to the right place instead of breaking.
Book a 20-minute demo and we’ll show you the queue, kiosk and loyalty running on a setup like yours.