Zeplo Admin | Restaurant Reservation and Table Booking Dashboard With React and Firebase

Zeplo Admin is a browser dashboard for the people running the room. It reads and writes the same Firebase project as the Zeplo mobile app, so a booking taken on a phone appears on every open dashboard within a second – and a walk-in taken at the counter appears in the app.

It is not a template with placeholder screens. Every screen is wired to Firestore: the reservations diary, the walk-in waitlist, QR door check-in, the live floor map, reports with period-over-period comparison, venue settings and staff roles.

Your guests book on Zeplo | Multi-Sector Booking App – the Flutter app that covers restaurants, cinemas, theatres, parking, beach clubs and coworking spaces from one codebase. Zeplo Admin is the console your staff run that business from. Point both at the same Firebase project and they are two halves of one system: a booking taken in the app lands in the diary, a walk-in taken at the counter appears in the app.

These are two separate items, sold separately, each with its own licence. Buying Zeplo Admin does not include the mobile app, and buying the mobile app does not include Zeplo Admin. If you want both halves you purchase both items. You are also free to use Zeplo Admin on its own with a customer app you build yourself, as long as it writes the same Firestore collections – the schema is documented in the package.

Built around the shift, not around a demo

Reservations diary – Today, this week or everything. List view and a 7-day calendar with a day panel. Search by guest, table or reference (press the slash key), filter by status, sort, paginate, multi-select to confirm or cancel in one batched write, export CSV, or print a paper service run sheet with the guest notes on it.

Reservation detail – Guest contact and notes, payment, the full status flow, guest history matched on email or phone, and a timeline. Managers can edit the time, table, party size, price and notes in place. Cancelling asks what was actually refunded and records it on the booking instead of pretending money moved.

Walk-in waitlist – The queue at the door, shared live across every device on the floor. Quoted wait against the real wait, with parties past their quote highlighted. Seat them, mark them as left, or turn the walk-in into a real reservation with the guest details carried across.

Door check-in – Camera QR scanning with jsQR, loaded on demand so the rest of the panel stays light. A host at the door usually has a name rather than a reference, so the same box searches by guest name and phone. Recent check-ins stay listed with an undo.

Live floor maps – Zones drawn from your Firestore units, painted with who is seated now and who arrives in the next two hours. Not “has a booking somewhere today”, which is true of every table during a full service and tells a host nothing.

Reports – Revenue, covers, average per cover and no-show rate, each with its change against the previous period of the same length. Busiest hours, channel mix, top tables, and a shared operator audit trail stored in Firestore rather than one browser’s local storage.

Venue settings and staff – Profile, currency, service fee, cancellation window, opening hours and closed days, with an unsaved-changes guard. Staff are added by Firebase UID, and an owner can change a role, suspend an operator who has left, or remove them entirely.