Full-service restaurants live and die by their floor. ERPNext gives you POS, items, customers and accounting, but out of the box it has no concept of a physical table, a reservation held for 7:30pm, a party waiting at the door, or the turn-time that decides whether you seat two covers or four on a Friday night. Hosts end up managing all of that in a paper book or a disconnected SaaS tool, so walk-ins, no-shows and covers never reconcile against the sales and customer data already sitting in ERPNext. That gap is exactly where the native platform runs out of road.

We build a proper Frappe app — table_reservation — that installs cleanly onto your existing ERPNext v15 or v16 site and adds first-class DocTypes for the restaurant floor: Restaurant Table (capacity, min/max covers, zone, merge-able flag, status), Floor Plan (a JSON layout consumed by a drag-and-drop editor built as a Frappe Page + client script), Table Reservation (party size, requested time, deposit, source, linked Customer), and Waitlist Entry. Reservation state transitions (Requested → Confirmed → Seated → Completed / No-Show / Cancelled) are driven by hooks.py doc events (validate, on_update, on_submit) and server-side Python so double-bookings and capacity overflows are rejected at the source, not just hidden in the UI. A client script renders the live floor: drag a table to move it, tap it to seat a party, and colour reflects real-time status pulled over the Frappe REST API.

Online reservations come in through a whitelisted method (@frappe.whitelist(allow_guest=True)) that backs a lightweight booking widget you embed on your website or Frappe Website page; it checks availability against confirmed reservations and turn-time rules before it will create a Table Reservation, and can require a deposit or prepayment that posts against ERPNext accounting. Waitlist entries are SMS/WhatsApp-notification-ready via ERPNext's Notification framework and a queued background job, so a "your table is ready" message fires without blocking the host. A scheduler_events hook sweeps for expired holds and no-shows on an interval, and every table-turn and dwell-time metric is captured so a Query/Script Report can show you average turn time by zone, peak-hour utilisation and no-show rates. Role profiles and permissions are configured so hosts, managers and servers each see only what they should.

Because this is build-to-order, nothing is a black-box download. After a short scoping call we confirm your exact floor zones, turn-time rules, deposit policy and notification channels, then build against a staging copy of your site. You get the installable app source for your version, install and configuration on your environment, UAT on staging with a rollback plan, a training session for your hosts and managers, and a post-go-live support window. Typical delivery is 2–4 weeks from confirmed scope. Everything is handed over as a git repository you own, tested on Frappe/ERPNext v15/v16, so you are never locked to us.