Beauty Salon Management System

Booking a salon appointment involves more than setting aside a time. The customer's remaining package sessions, the specialist, the room and payment after the service all belong to the same job. The project began with these details scattered across notebooks, separate payment slips and remembered session counts. We treated the workflow as a chain of records running from the appointment to the end of the day. Daily tasks shaped the panel before the number of screens did. The product has a Turkish interface and is designed for salons in Türkiye.

When a customer calls, reception needs the calendar, the specialist needs the history, and the person taking payment needs the outstanding balance. We placed the shared customer record at the centre of these handovers. Visits, packages and payments are linked, while staff responsibilities remain distinct. Showing available times and records needing attention in the daily panel connects record keeping with choosing the next task. You can plan the day using related records rather than gathering information about the same customer from separate lists.

One panel does not mean every employee performs the same actions. Role permissions, individual additions and removals, and the company's enabled features are evaluated together. Reception booking an appointment and accounts reviewing a cancelled payment have different responsibilities. We carried this distinction into navigation and server actions. Permissions and company status are refreshed from the database during each request; the available options reflect the employee's responsibilities.

We also chose separate record models for packages and the cash register. A change to package entitlement creates an entry in the session ledger. Cash is calculated from movements linked to an open register session, rather than from the date alone. This lets different activities retain their own rules within the same panel. You can inspect a payment's register link or a package usage entry's appointment link. Reversing entries to correct the history became a shared development approach.

Reducing package entitlement as soon as an appointment is booked would mix planned work with completed work. We linked usage to completion instead. Completing an appointment writes a usage entry to the session ledger; reversing completion creates a refund entry. Keeping the original usage entry makes it possible to trace why entitlement changed. On-screen session counters are updated alongside this ledger. A sold package retains its name and session values as they were at the time of sale.

Payment handling prevents the same appointment from being charged twice, and services covered by a package are not charged again. Cash belongs to the open register session; card payments and bank transfers do not increase the cash in the drawer. Once the count is entered in the closing dialogue, the expected amount and difference are shown. An absolute difference of 50 ₺ or more requires an explanation. Freezing the expected amount, count and difference at closing makes the end of day a record in its own right, rather than a total recalculated later.

We used a CSV preview to migrate basic customer details. Saving an Excel list as CSV UTF-8 gives the transfer a defined file format. The flow supports up to 5,000 rows. The preview separates duplicates within the file, existing phone numbers, invalid rows and records to be added. Branch selection is part of this assessment. You can review how each row will be handled before importing; the data is checked again during the transfer.

Importing the customer list and setting up the working arrangements are separate steps. Service durations, required resources, staff skills and working hours feed the availability calculation. We connected the initial assessment to a sample flow from customer record to appointment, completion, payment and register closing. Migration of past appointments, financial records and session history is discussed separately. The basic customer preview makes it clear which records are ready and which areas need further consideration.

The Beauty Salon Management System is in live use. This case study explains our development approach through appointment availability, session entries, register sessions and company scope. Turning records such as remaining package entitlement, overdue visits and pending online requests into daily tasks continues the same approach. Each follow-up row shows why it needs attention, and the outcome of the conversation is marked in the panel. When a prepared message opens in an external app, you retain control over reviewing and sending it.

We can assess the next scope together through your salon's daily tasks. Enabled company features determine the available areas; team roles and branch arrangements guide that choice. When discussing a new need, we examine where its record originates, which action changes it and how its history can be traced. The product page provides more detail on screens and usage. Sharing your appointment, package and closing workflow helps us connect the next development decision to a concrete working scenario.