Salon Booking System Pro stores every reservation as a row in sln_reservations with a status column whose values are pending, confirmed, paid, cancelled, or no-show. The default admin lists those reservations as a flat table sorted by start time with the status as a small column per row, which is fine for a one-chair salon and breaks down for a multi-stylist studio with a full appointment book.

SleekView Kanban reads the same sln_reservations table and treats the status column as the natural axis to group by. Each card surfaces the client name, the service, the assistant or stylist, the start datetime, and the price. Columns mirror your real Salon Booking System statuses, so the pending stack and the paid stack each read as a single number rather than as labels scattered across rows.

Drag a card from Pending to Confirmed and SleekView calls the same Salon Booking System update path the admin uses, which fires the confirmation email, sends the SMS through the configured gateway, and pushes the appointment to the assistant's Google Calendar. Drag to Cancelled and the refund and notification flows run through Salon Booking System so any payment gateway integration handles the money side consistently.

A salon sells time, not products, and time runs out whether you act on it or not. Salon Booking System Pro captures reservations cleanly in sln_reservations, but the default admin lists them in start-time order, which works for a one-chair shop and falls apart the moment two stylists, three services, and a phone all want attention. The board view fixes this by making the only state that matters, the reservation status, the primary axis of the screen.

You can see at a glance how many requests still need a confirmation, how many of yesterday's confirmed slots actually completed, and how many no-shows need a recovery call. Cards make individual reservations legible at the level of client, service, assistant, start time, and money, which is exactly what a busy salon needs to plan a day. Drag is the natural verb for moving a reservation from one stage to the next, and because SleekView writes through Salon Booking System's own functions, every drag still triggers the confirmation emails, the SMS messages, the calendar pushes, and the deposit captures you already configured.

List view and board view become two reading surfaces over the same data instead of a tradeoff.