A build-to-order Frappe app that gives franchise and multi-outlet chains a single control tower over ERPNext POS locations — central menu and price pushes, per-outlet overrides, consolidated sales, and automated royalty billing. ECOSIRE scopes, builds, installs, and supports it for you. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $799.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that gives franchise and multi-outlet chains a single control tower over ERPNext POS locations — central menu and price pushes, per-outlet overrides, consolidated sales, and automated royalty billing. ECOSIRE scopes, builds, installs, and supports it for you.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
New `Outlet` DocType linking each store to its ERPNext Company, Cost Center, Warehouse, and `POS Profile`, so the whole network is modeled as first-class data
Central `Menu Version` / `Price Book` DocType with a whitelisted `publish_menu` method that fans item and price changes out to every subscribed outlet in one controlled transaction
Per-outlet price and tax overrides that survive central pushes — an outlet keeps its local `Sales Taxes and Charges Template` or item-level price delta instead of being overwritten
Promotion Plan DocType with start/end effective dates that schedules `Pricing Rule` records into targeted outlets and auto-expires them via a scheduler event
`Franchise Royalty Agreement` DocType supporting percentage-of-net-sales, tiered, and fixed-fee models per franchisee
Nightly `scheduler_events` job that computes royalties from actual `POS Invoice` / `Sales Invoice` net sales and drafts Journal Entries or Sales Invoices for review
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 2–4 weeks 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.
Runs a multi-brand or multi-region franchise network on ERPNext and needs to push menu, price, and promotion changes to dozens of outlets without touching each store, while keeping an auditable record of what changed.
Operates several company-owned and franchised locations and wants one dashboard for consolidated daily sales plus automated, defensible royalty and management-fee billing instead of month-end spreadsheets.
Owns royalty accuracy and inter-company money flows; needs royalties computed from real POS net sales, drafted as reviewable Journal Entries, with per-outlet permissions so franchisees only see their own numbers.
Maintains the Frappe site and needs a clean, upgrade-safe app (proper DocTypes, hooks, `bench migrate` compatible on v15/v16) rather than brittle customizations scattered across POS Profiles.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Multi-Outlet / Franchise POS Console for ERPNext 应用程序 ZIP。
将 ZIP 解压到您的 bench 的 apps 文件夹中,或者使用解压缩的应用程序的路径运行“bench get-app”。
运行 `bench --site SITE_NAME install-app APP_NAME`,然后运行 `bench migrate` 以安装 Multi-Outlet / Franchise POS Console for ERPNext 并应用其架构。
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Central menu/price push to all outlets | One `publish_menu` action fans changes to every subscribed outlet with audit log | Possible, but you design and build the fan-out and audit yourself | Often single-store focused; bulk push rarely first-class | |
| Per-outlet price & tax overrides | Overrides modeled as data and respected on every central push | Depends entirely on your build effort and testing | Limited or all-or-nothing override support | |
| Consolidated multi-store dashboard | Query/Script Reports + Number Cards across all outlets and franchisees | Build reports and cards from scratch | Usually per-store views only | |
| Franchise royalty & fee automation | Scheduler job drafts royalties from real net sales for review | You write the formula engine and scheduler yourself | Rarely franchise-aware; no royalty engine | |
| Per-outlet permissions | Role Profiles + User Permissions keyed on Outlet, franchisee-scoped | Configurable but you own the design | Generic roles, not outlet-scoped by default | |
| ERPNext v15/v16 upgrade safety | Proper Frappe app, `bench migrate` compatible, version-targeted | Quality varies with the developer | Compatibility depends on maintainer's release cadence | |
| Ownership & lock-in | Full source + git repo handover, no lock-in | You own it, but carry all build risk | Licensed; source often closed | |
| Time to value | 2–4 weeks from confirmed scope, built and installed for you | Months of in-house design, build, and QA | Fast to install but may not fit your model |
No. It is build-to-order. ECOSIRE scopes your outlet structure, pricing rules, and royalty formulas, then builds the Frappe app against your ERPNext version and installs it with your team. There is no instant-download version because the override and royalty logic is tailored to how your network actually operates.
Typical delivery is 2–4 weeks from confirmed scope. Simple networks with straightforward percentage royalties land at the shorter end; more outlets, complex tax overrides, or tiered/multi-formula royalty agreements push toward the longer end. We give you a firm timeline after the scoping call, before any build starts.
Frappe/ERPNext v15 and v16. The app is packaged as a standard Frappe app that installs with `bench get-app` / `bench install-app` and upgrades cleanly through `bench migrate`, so it stays compatible when you patch your site.
Each outlet can carry its own price deltas and tax template as an override. When head office publishes a Menu Version or Price Book, the `publish_menu` method applies the central set everywhere but respects any outlet-level override, so a store keeps its local pricing or `Sales Taxes and Charges Template` instead of being overwritten.
A `Franchise Royalty Agreement` DocType holds each franchisee's terms — percentage of net sales, tiered rates, or fixed fees. A nightly scheduler event reads actual submitted POS/Sales Invoice net sales per outlet and drafts Journal Entries or Sales Invoices for your finance team to review and post. Nothing is auto-posted without review.
No. Access is enforced with Frappe Role Profiles and `User Permission` records keyed on `Outlet`. A franchise manager logging into the same ERPNext site sees only their own outlets and reports, while head office sees the whole network. It is governed by ERPNext's own permission model, not a separate layer.
Every engagement includes a post-go-live support window for bug fixes and adjustments. Because you receive the full source and the git repository, your own team can also maintain and extend the app. We offer ongoing support and enhancement retainers separately if you would rather ECOSIRE keep evolving it.
A build-to-order Frappe app that gives franchise and multi-outlet chains a single control tower over ERPNext POS locations — central menu and price pushes, per-outlet overrides, consolidated sales, and automated royalty billing. ECOSIRE scopes, builds, installs, and supports it for you.