Waiter Ordering App for ERPNext

ECOSIRE builds a proper Frappe app (waiter_ordering) that installs into your existing ERPNext site rather than bolting on a disconnected third-party system. Servers open a mobile-first interface on a phone or tablet, pick a table from the floor map, and capture items straight against your live ERPNext Item master and Item Price / Price List — so what they tap is exactly what you sell, at the price ERPNext already knows. Orders are held in dedicated DocTypes (a Waiter Order header with Waiter Order Item child rows carrying seat number, course, modifiers, and special instructions) so nothing is lost between capture and the kitchen. A whitelisted REST method fires the order to the kitchen the instant the server hits send; hooks.py doc events and Frappe realtime (frappe.publish_realtime) push each item's status — new, preparing, ready, served — back to the handheld so the server knows what to run without walking to the pass.

Technically the app is grounded in ERPNext's own primitives. It reads Items, variants, and Price Lists directly; it maps completed orders onto POS Invoice / Sales Order so revenue, tax templates, and stock ledger stay in ERPNext with no reconciliation. Modifiers and course logic are enforced with server scripts and validation on the child table; a role profile and permission rules scope what waiters, kitchen staff, and managers can see and do. A scheduler event sweeps stale or abandoned orders, and the kitchen display is driven off the same realtime channel so KDS/KOT and handheld never drift apart. Everything targets Frappe/ERPNext v15 and v16, respects your existing customizations, and is delivered as clean, reviewable source in a git repository — no obfuscated blobs.

Because this is build-to-order, there is no instant download. We start with a short scoping call to confirm your floor layout, menu structure, modifier rules, KDS/printer setup, and ERPNext version, then hand you a fixed scope and quotation. Typical delivery is 2-4 weeks from confirmed scope. We build on a staging copy of your site, run UAT with your team, keep a documented rollback plan, and only then install into production — followed by a post-go-live support window while your floor staff settle into it.