Restaurants and cloud kitchens running ERPNext POS take orders cleanly, but the moment the ticket needs to reach the line it falls back to printed KOTs or shouted callouts. ERPNext core has no live kitchen screen: there is no POS Invoice fan-out to a cook display, no prep-timer state, no per-station routing, and no "order ready" acknowledgement flowing back into the system. As soon as you run more than one prep station, or a cloud kitchen with several brands sharing a pass, paper tickets stall, items get re-fired, and expo has no view of what is actually late. That gap is exactly where a purpose-built KDS earns its place.

ECOSIRE builds a proper Frappe app (for example ecosire_kds) installed into your ERPNext bench, not a bolt-on iframe. The core is a set of DocTypes — a KDS Ticket and child KDS Ticket Item that mirror each POS Invoice/POS Order, plus a KDS Station DocType defining each screen and the item groups it owns. A hooks.py doc_events handler on POS Invoice (on_submit, on_update) creates and updates tickets, and a server script applies your routing rules so a burger line, a fryer, and a drinks station each see only their own items. The screen itself is a Frappe-served page (or Frappe UI/Vue app) that subscribes over the realtime socket (frappe.realtime/websocket) so new orders appear instantly with color-coded prep timers that shift green→amber→red against your target times.

On the line, cooks drive the board with a physical bump bar or touchscreen: bump an item, bump a whole ticket, recall an accidental bump, and fire an "order ready" that writes back to the ticket status and can notify the pass or front-of-house. Modifiers and allergen notes are highlighted so nothing gets missed, and a scheduler event (a scheduler_events cron entry) reconciles any tickets whose POS document changed out-of-band, so the screen never drifts from ERPNext. State changes are exposed through whitelisted methods over the Frappe REST API, and every action is permission-gated with dedicated role profiles (Kitchen Staff, Expeditor, Kitchen Manager) so only the right people can void or recall. If a screen or the network drops, an optional KOT printing fallback keeps the line moving.

Because this is build-to-order, we start from your real kitchen: how many stations, which item groups route where, your target prep times, whether you run one brand or several under a cloud-kitchen pass. After a short scoping call ECOSIRE writes the app against Frappe/ERPNext v15 or v16, tests it on a staging copy of your site, runs UAT with your team, and then installs it on production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source in a git repository, so nothing about the system is locked away from you.