Zeplo Admin - restaurant reservation and table booking dashboard built with React, TypeScript and Firebase

A real operator console for your Zeplo booking app

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.

Live demo: zeplo-admin.webkodingtheme.com/app
Landing page: zeplo-admin.webkodingtheme.com
Demo operators: owner@fera.demo / Owner2024! – also manager@fera.demo / Manager2024! and host@fera.demo / Host2024!
Sign in as the Host to watch the navigation and the available actions shrink to that role.

Which app does it work with

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.

Ten operator screens - reservations diary, waitlist, door check-in, floor maps, reports, staff roles

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.

Firestore security rules enforce the operator role matrix field by field

Security you can actually point at

Zeplo Admin is a browser client. Anything a browser client enforces can be bypassed, so the interface permissions exist only to hide what a role cannot do – the authority is the Firestore security rules, included and documented in the package.

A guest’s booking arrives as pending with the price the app quoted, and only venue staff can write confirmed – an operator reviews it before the table is promised. A host can check a guest in and nothing else. A guest can only cancel their own booking – no self-confirming, no zeroing the total from the customer app. Ownership and venue are immutable, so a reservation cannot be reassigned or moved. Every update is checked against a key whitelist, so no unexpected field can be injected. An owner cannot demote, suspend or delete their own access, which means the venue can never lock itself out. The audit trail is append-only.

Beyond the role matrix: suspending an operator revokes access instantly without deleting their history; the CSV export neutralises spreadsheet formula injection, because guest names arrive from a public booking app; the nginx configuration ships with HSTS, a Content-Security-Policy, Referrer-Policy and Permissions-Policy already set, including on static assets; and password reset never reveals whether an address is on the staff list.

Operators reset their own passwords from the sign-in screen. The demo credential cards on the preview only render on a demo build – a buyer deployment shows a plain sign-in screen, and no demo password exists anywhere in the source. The rules ship with an emulator test suite that signs in as each role and checks every promise above.

What is included - full React and TypeScript source, Firestore rules, documentation, nginx config

Firebase is required, and that is the honest version

Zeplo Admin is a Firebase client. It has no other production data layer: no REST adapter, no Supabase, no custom server, and none is planned. You need a Firebase project with Email/Password authentication and Cloud Firestore, and you deploy the included rules to it.

Disclaimer – third-party services and costs. Firebase Authentication and Cloud Firestore are external services operated by Google, not included in this purchase and not operated by us. They are billed to your own Google account and may incur additional costs: the free Spark plan usually covers a single venue, and usage beyond its quotas is charged by Google at their published rates. The panel bounds its own reads with a configurable history window, but your Firebase bill is yours. Review firebase.google.com/pricing before going live.

It is an operator console for a Firestore database in the Zeplo schema, so you also need a customer-facing app writing the same collections. That is either Zeplo | Multi-Sector Booking App, a separate CodeCanyon item under its own licence, or an app you build yourself against the documented schema.

The mock mode included in the package is for evaluating the interface offline – it stores nothing and must not be sold to a venue as a product. The seed script in the download populates a fresh Firebase project with the venue, its tables and a month of realistic reservations, so you can run and demo the dashboard end to end before deciding whether you also want the mobile app.

Requirements

Node.js 20 or newer, for the build only – the output is static files
A Firebase project on any plan, with Authentication and Cloud Firestore enabled
Any static host: nginx, Apache, Netlify, Vercel, Firebase Hosting, S3
An evergreen browser. QR check-in needs a camera and HTTPS
A customer-facing app on the same Firestore schema – either Zeplo | Multi-Sector Booking App (separate item, separate licence) or your own

What is in the download

Complete React 19 and TypeScript source – readable, nothing minified, no pre-built bundle
Hardened Firestore security rules, composite indexes and an emulator test suite for the rules
Mock data layer so you can evaluate the interface without Firebase
nginx virtual host and a security-header snippet
Demo seed scripts for a fresh Firebase project
Full buyer documentation with a plain-language user guide and a visual branding guide

Open the Zeplo Admin live demo and sign in as owner, manager or host

Roadmap

A drag-and-drop floor map builder with draft and published states; a staff email invite flow; table-turn timers on the map; and internationalisation if buyers ask for it. Guest email and SMS notifications need Cloud Functions – a static panel cannot send mail, so this is a documented non-goal until that piece exists rather than a promise on a listing.

Support

Support covers installation, configuration and defects in the item as supplied. It does not cover customisation of your own code, third-party services, or your Firebase billing. When you write in, please include your version, browser, whether you are in mock or Firebase mode, and the exact error text from the browser console.

License

Regular License – Use the item in one end product that end users are not charged for. Suitable for a venue running its own dashboard.

Extended License – Use the item in one end product that end users may be charged for. Required if you resell access to the dashboard as a service.

A licence for Zeplo Admin covers this item only. The Zeplo mobile app is a separate purchase with its own licence.

For full terms see Envato Standard Licenses.

Changelog

v1.0.0
– Initial release

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