Restaurant / Café / Bar

The Restaurant base is built for hospitality. Your customers are Guests, bookings are Reservations, and the dashboard leads with what’s on the books tonight.

Who this is for

Vertical	Navigation
Restaurant	Full set — Reservations, Floor, KDS, Clients, Invoices, Tickets, Activity
Café / Coffee	Lean set — Reservations, Clients, Invoices, Activity (no floor map or KDS)
Bar / Nightclub	Full set, same as Restaurant

A full Restaurant account’s sidebar:

Dashboard — reservations today, unpaid tabs, active guests
Reservations — tonight’s bookings
Floor — the floor map / table layout
KDS — the kitchen display system, where tickets flow to the line
Clients (your Guests)
Invoices — open tabs
Tickets — service issues
Activity

A Café runs a stripped-down version — just Reservations, Clients, Invoices, and Activity — since most cafés don’t seat by table or run a kitchen display.

Your dashboard

The Restaurant dashboard leads with today’s reservations, then three tiles:

Reservations today — covers booked
Unpaid tabs — outstanding amount and open count
Active guests — guests in your system

Quick links jump to Reservations, Clients (guest profiles), and Invoices (open tickets).

The restaurant-specific screens

Three screens only appear on this base:

Floor — a visual table map for seating and managing covers.
KDS (Kitchen Display System) — the line-side ticket display.
Reservations — booking management tuned for covers, not generic appointments.

Terminology follows suit: in restaurant mode the generic “record” noun renders as Table / Covers, and “appointment” becomes Reservation everywhere it appears.

How a typical night runs

Guests book — through the booking widget on your site, a phone call, or walk-ins you add to Reservations.
You seat them from the Floor map and track covers.
Orders flow to the KDS for the kitchen.
The tab closes out as an invoice; guest history builds in Clients.