Once a restaurant or retail brand grows past a handful of ERPNext POS locations, the native model starts fighting you. A stock POS Profile and its Item Price lists are managed per company and per profile, so a menu change or a promotion has to be repeated by hand at every store; there is no first-class notion of a franchisee who should see their own outlet but nothing else; and royalty or management fees end up reconstructed in a spreadsheet at month-end from raw POS Invoice and Sales Invoice data. ERPNext gives you a solid single-store POS — it does not give you a head-office console that treats "all my outlets" as one governed system.

The Multi-Outlet / Franchise POS Console is a proper Frappe app (its own module, DocTypes, and hooks.py) installed onto your existing ERPNext v15/v16 site. At its core is a set of new DocTypes — typically Outlet (linked to Company, Cost Center, and Warehouse), Menu Version / Price Book, Promotion Plan, and Franchise Royalty Agreement — plus a child-table mapping that records which outlets are subscribed to which menu and price set. A whitelisted publish_menu method fans a Menu Version out to every subscribed outlet, writing the correct Item Price and POS Profile rows in a single controlled transaction, with an audit record of what was pushed, when, and by whom. Outlet-level exceptions are honored: an outlet can carry a pricing or tax override (a different Sales Taxes and Charges Template or a delta on specific items) that the central push respects instead of stamping over.

On top of that we build the head-office reporting and money flows. A consolidated sales dashboard aggregates POS Invoice / Sales Invoice data across all outlets — by day, outlet, item group, and franchisee — using ERPNext Query/Script Reports and Number Cards rather than a bolted-on BI tool, so it stays inside your permission model. A nightly scheduler event (registered in scheduler_events) reads each Franchise Royalty Agreement and computes royalties and fixed fees from actual net sales, producing draft Journal Entries or Sales Invoices against the franchisee for review. Access is governed with Frappe Role Profiles and User Permissions keyed on Outlet, so a franchise manager logging into the same ERPNext site sees only their locations, while head office sees the whole network. hooks.py doc_events validate overrides and keep the audit trail current, client scripts drive the console UI, and everything is reachable over the standard Frappe REST API and whitelisted methods for any external app or mobile client you run.

Because this is build-to-order, nothing ships as an instant download. We start with a short scoping call to confirm your outlet structure, menu/price governance rules, tax handling, and royalty formulas, then ECOSIRE builds the app against your ERPNext version, tests it on a staging copy of your site, and installs it into production with your team. Typical delivery is one working week from confirmed scope depending on how many override and royalty rules you need. You receive the full source, documentation, a training session, and a post-go-live support window — and the git repository is handed to you so you are never locked in.