Salonier

Complete SaaS for beauty salon management

SaaS platform with online booking, financial control, client and staff management. Available as a desktop web application and as a mobile app for clients and staff.

Platforms
SaaS · Web · Mobile
Year
2026
Status
In production
Role
Full stack — API, web and app
Visit website Play Store · closed testing

Your salon booking appointments while you work. Salonier brings together a 24-hour online booking link, a per-professional schedule, client records, cash control and WhatsApp. Clients book on their own; the salon just confirms.

It is a multi-tenant SaaS: every salon is isolated from the others and every person signs in with their own login, as admin, front desk or professional. The same Vue 3 and Quasar front end runs in the browser and becomes an Android app through Capacitor, published on the Play Store. It serves hair salons, barbershops, aesthetics studios and nail designers, each with their own services, durations and prices.

What the system does

  1. 24-hour booking link

    Each salon gets its own address for the Instagram bio, WhatsApp status and Google. Clients pick the service, the professional (or "anyone") and the time, with no app, sign-up or password, and get a booking code and receipt.

  2. The whole day on one screen

    Four views of the same schedule: day, per professional, week and list. The current-time line moves by itself, statuses change with the clock and the grid never lets you book over another appointment.

  3. Chemical processing time becomes bookable

    Coloring, highlights and keratin treatments have waiting time in the middle. Salonier splits the appointment into two blocks and frees the gap for a quick fit-in, without overlapping anyone.

  4. Clients who don't disappear

    Each record shows how much the person has spent, the average ticket and how often they come back. Overdue clients show up on the list, with an automatic VIP badge and this week's birthdays on the dashboard.

  5. Cash closed every day

    Income, expenses, cash withdrawals and payment methods set by the salon. Every paid appointment lands in the cash register with client and service, prints a receipt and every cancellation leaves a trail.

  6. Which service pays the bills

    Reports of income, expenses, balance and average ticket for any period, with daily flow, top 10 services by revenue and the split between PIX, card and cash.

  7. WhatsApp in one click

    Confirmation, reminder, come-back and birthday templates written once with tags (client, service, date, price). When sending, the system fills in the real data and opens WhatsApp.

  8. Revenue only for those who should see it

    Admins see everything; the front desk sees schedule, clients and the day's cash; professionals see only their own appointments. For staff, the cash register simply doesn't exist.

How it was built

Frontend
Vue 3Quasar 2PiniaVue Routervue-i18nChart.js
Mobile
Capacitor 8Android
Backend
Laravel 12PHP 8.2SanctumLaravel AuditingLaravel ExcelDomPDF
Data
PostgreSQL

Technical challenges

  1. A schedule that understands breaks

    An appointment with a break takes two blocks with a free gap in between. Conflict validation, the grid and the public booking slots must treat that gap as available time without ever overlapping the start or the end of the service.

  2. Truly free slots on the public link

    Offered times account for lunch, blocked days, each service's duration and what other professionals already have booked. With "any professional", the salon decides who attends when confirming.

  3. Encrypted yet searchable sensitive data

    Phone, tax ID, address and notes are encrypted in the database. To recognize returning clients on the public link without decrypting the whole base, they are looked up by a hash of the normalized phone number.

  4. Isolation by salon and by role

    All data is scoped by salon through a global scope. Staff routes take no id in the URL: the scope comes from the authenticated user, so reaching a colleague's data is impossible by construction.

  5. Every change traced, nothing lost

    Every change is audited with author and date, and deletions can be reversed. If money vanished from the cash register you can find where it went; if a client was deleted by mistake, they come back.

Need something
like this?

Tell me the idea or the problem. I help shape the solution and build it from the API to the app.

Let's talk