Restaurant Table Reservation System with Floor Plan Booking

Most small and mid-size restaurants still manage tables on a paper register, a whiteboard, or the manager's memory. That breaks down on busy evenings: double bookings, forgotten phone reservations, tables held for guests who never arrive, and no record of which slots actually make money. This project replaces that chaos with a proper reservation system. The centrepiece is a live floor plan — every table shown with its real-time status (available, reserved, occupied) — so staff can seat and book without walking the floor. Reservations carry guest details, party size, time slot and status; confirmations go out by SMS or email; and the manager gets occupancy and no-show reports. The design is deliberately scoped to one outlet done well: roles for staff and manager, validation that prevents over-seating a table, and a clean relational schema a student can fully explain in a viva.

1. The manager sets up the outlet once: tables with seat counts grouped into zones (main hall, terrace, cabins) on the floor plan.
2. Staff take a booking by phone, walk-in or web form; the app suggests tables that fit the party size and are free in the chosen slot.
3. The reservation is stored with a unique ID, and a confirmation is sent to the guest via the configured SMS/email gateway.
4. On arrival, staff mark the guest seated; the table flips to occupied on the floor plan for everyone to see.
5. When the party leaves, the table is marked free and the reservation moves to completed, feeding the occupancy reports.
6. Cancellations and no-shows are recorded with one click, freeing the table and updating the guest's history.
7. The manager reviews covers, turnover and no-show trends on the reports dashboard at close of service.

Tech stack:

• HTML5 · CSS3 · JavaScript (ES6)
• Node.js · Express
• MySQL · relational schema design
• REST API architecture
• Responsive mobile-first UI
• Canvas/SVG chart rendering
• Git · version control

• [Live floor-plan booking] Visual floor plan with every table's real-time status — available, reserved or occupied. Clicking a free table opens the booking form pre-filled with that table.
• [Reservation management] Create, edit, cancel and reassign reservations with guest name, phone, party size, date and time slot, all validated against table capacity.
• [Guest notifications] Booking confirmations and reminders through SMS/email gateway hooks (Twilio/MSG91-ready), with console logging in test mode.
• [Table status tracking] One-click transitions as guests arrive, are seated and leave, keeping the floor plan truthful through the whole service.
• [Search & filters] Instant search across guest name, phone and table, plus status filters (confirmed, seated, completed, cancelled).
• [Occupancy reports] Covers by day, table turnover and booking-channel split rendered as charts for the manager's weekly review.
• [No-show tracking] Flags guests who miss reservations so repeat no-shows can be spotted and policies applied.
• [Walk-in handling] Seats walk-in parties directly from the floor plan without a prior reservation, keeping one system of record.

• Complete source code: frontend, backend API and database schema
• Database migration scripts with realistic seed data
• Setup and deployment guide (local + shared hosting/VPS)
• User manual written for restaurant staff
• Project report PDF (problem, design, schema, testing)
• PPT presentation for final review
• Viva Q&A preparation document

• Scoped to a single restaurant outlet; multi-branch management is future scope.
• SMS delivery needs the buyer's own paid gateway account; test mode logs messages to the console instead.
• Reservations are confirmation-only — no online advance payment or table-hold deposits.
• The floor plan is a 2D schematic for operations, not a CAD-accurate architectural layout.
• Real-time status assumes a stable internet connection; there is no offline mode.
• Reports are only as complete as the reservations staff enter — garbage in, garbage out.