Aggregator platforms take 20-35% of every order and own your customer relationship, while ERPNext out of the box gives you a solid POS, an Item master and Sales Order engine but no public-facing ordering website that customers can actually place orders on. Restaurants end up either paying the commission or bolting a disconnected Shopify/WooCommerce store onto the side, then re-keying orders into ERPNext by hand. Both paths leak margin, introduce order-entry errors at the busiest hour, and break the single source of truth that made you choose ERPNext in the first place.

ECOSIRE builds a proper Frappe app (a versioned, bench get-app-installable module — not a pile of one-off customizations) that adds a branded ordering storefront on top of your existing ERPNext site. The public menu is rendered from your ERPNext Item and Item Group records, so the site is never out of sync with what your kitchen actually sells. Custom DocTypes model the pieces ERPNext lacks — Ordering Menu, Menu Modifier and Modifier Group (for options like size, spice level and add-ons), Combo/Meal Deal, and Online Order with a linked child table for line items and selected modifiers. Fulfilment type (pickup, delivery, or a scheduled future slot), delivery address, and time-window are captured at checkout and validated server-side. When an order is confirmed, a hooks.py doc_events handler and whitelisted server-side methods create the corresponding ERPNext POS Invoice/Sales Order against the configured POS Profile and Customer, so the order lands in the same POS queue, stock ledger and accounting your staff already use — no re-keying, no separate reconciliation.

The storefront is a headless-friendly build: it talks to ERPNext over the Frappe REST API and app-specific whitelisted methods (@frappe.whitelist()), with a guest-cart flow and optional customer login mapped to ERPNext Customer/Contact. Online payment is wired through your chosen gateway via the Frappe payments integration (Stripe, Razorpay, or a regional PSP), with cash-on-delivery as a first-class option; payment status flips the Online Order state through hooks.py events. Menu availability, sold-out flags and store open/close hours are driven by scheduler events (scheduler_events cron/hourly hooks) and a Store Settings single DocType, and customers get live order-status tracking (received → preparing → ready/out-for-delivery → completed) rendered from the Online Order status field, updated by staff from ERPNext or from a lightweight ops screen. Access is governed by proper Frappe role profiles and permission rules so the public site, kitchen staff and managers each see only what they should. The app targets Frappe/ERPNext v15 and the v16 line, and is delivered as clean source you own, respecting Frappe upgrade conventions so it survives bench update.

Because this is build-to-order, nothing is a generic template drop. We start with a scoping call to map your menu structure, modifier logic, fulfilment zones, payment gateway and branding, then build against a staging bench, run UAT with you, and cut over to production. Typical delivery is one working week from confirmed scope. You receive the full Git repository, install and configuration on your environment, technical and user documentation, a training session for your team, and a post-go-live support window. Request a quotation and we will size it to your restaurant.