If you run a GCC restaurant or dark store on noon Food, your day is spent re-keying platform orders into ERPNext, manually toggling item availability when you run out of stock, and reconciling a monthly settlement statement against a pile of individual orders. ERPNext gives you excellent native Sales Order, Item, Stock, and Payment Entry DocTypes, but out of the box it has no knowledge of the noon vendor portal — there is no built-in poller for incoming orders, no push of your menu and prices to the platform, and no automatic pause when an item goes out of stock. That gap is where margin leaks: missed orders, oversells on sold-out items, and settlement disputes nobody has time to trace.

ECOSIRE builds a proper Frappe application — installed on your own bench as an app alongside erpnext — that closes that gap. We model the integration as first-class DocTypes (for example Noon Vendor Config, Noon Order, Noon Menu Item Map, and Noon Settlement) so every platform interaction is a queryable, permissioned record inside your ERPNext, not a black box. Incoming vendor orders are pulled on a scheduler_events cron (or received via webhook where the platform supports it), validated, and converted into native ERPNext Sales Orders with the correct customer, item mapping, tax template, and delivery details. hooks.py doc_events fire on Item and Bin changes so that when stock crosses zero the connector auto-pauses the corresponding menu item on noon, and re-enables it when you restock — no more selling what you can't cook or pick.

Technically, the connector is built the way a maintainable Frappe app should be: menu and availability push, order status transitions, and rider/dispatch updates run through server-side whitelisted methods (@frappe.whitelist()) and background jobs (frappe.enqueue) so the UI never blocks; API credentials live in a Single DocType or Frappe's encrypted site config, never hard-coded; and access is controlled with dedicated Role Profiles and DocType permissions so kitchen staff, store managers, and finance each see only what they should. Where you need on-screen behavior — a "Sync now" button, a live order board, availability toggles — we add Client Scripts and a lightweight workspace. Settlement reconciliation matches each platform payout line back to its Noon Order and the corresponding ERPNext Sales Invoice, flags commission and short-payments, and drafts the Payment Entries so finance reviews exceptions instead of typing every line. The app targets Frappe/ERPNext v15 and is forward-compatible with v16, and we pin it to your exact version at build time.

Because this is build-to-order, nothing ships until we understand your setup. We start with a short scoping call to confirm your noon vendor account structure, ERPNext version and hosting (Frappe Cloud, self-hosted, or ECOSIRE-managed), item/menu mapping rules, tax treatment, and which flows matter most to you. We then build against your requirements, deliver installable source for your version, and run UAT on a staging bench with a documented rollback plan before we touch production. Typical delivery is one working week from confirmed scope, depending on how many flows and edge cases (multi-branch, multi-brand, combos/modifiers) you need. You receive the git repository, technical and user documentation, a training session, and a post-go-live support window — no fabricated dashboards, just a working connector your team actually uses.