Cloud-kitchen operators typically run four, six, or a dozen virtual brands out of one back-of-house — and stock ERPNext has no concept of a "brand" that owns its own menu, pricing, tax profile, and P&L. You end up modelling each brand as a separate Company (which fragments your one shared inventory) or crushing everything into a single price list and item group, at which point you can no longer answer the only question that matters: which brand actually makes money after aggregator commission and food cost? Sales Orders arriving from Talabat, Deliveroo, Careem, Uber Eats or your own web checkout all land in the same Sales Order list with nothing that routes, tags, or reconciles them by brand and channel. That is exactly where ERPNext core runs out of road for this business model.

We build a proper Frappe app (its own module, git repo, and hooks.py) that adds first-class multi-brand structure on top of ERPNext instead of fighting it. A Virtual Brand DocType owns each brand's menu (linked ERPNext Items via a child table), its own Price List and Item Tax Template, its logo/branding, and its target margin. A Kitchen Channel DocType maps each delivery aggregator or direct channel to its commission percentage, prep-station, and default warehouse. Incoming orders — whether pushed via the Frappe REST API / a whitelisted ingest method or entered at POS — are stamped with virtual_brand and channel custom fields, and a doc_events hook on Sales Order before_save/on_submit applies the brand's price list and tax template, injects the channel commission as a deduction line, and routes the ticket to the correct prep station via a Kitchen Display screen (a Frappe Page / Portal view backed by realtime frappe.publish_realtime).

Under the hood the shared pantry stays shared: all brands deduct from the same ERPNext Warehouse and Stock Ledger, so a kilo of chicken consumed by three different brand menus draws down one real inventory balance and triggers one reorder — no double-counting, no per-company silos. Server Scripts and scheduled jobs (scheduler_events — hourly/daily) roll up a per-brand P&L: revenue, aggregator commission, theoretical food cost from linked BOMs/recipes, and contribution margin, surfaced through a Query Report and dashboard chart filtered by virtual_brand. Client Scripts add brand-aware validation and one-click brand switching on the order form, and a Role Profile ("Brand Manager") plus User Permissions scope each operator to only their own brands' orders and reports.

This is build-to-order, not a marketplace download — there is no instant install. After a short scoping call we confirm which aggregators, brands, tax jurisdictions and reporting cuts you need, then build and hand over an installable Frappe app tested against ERPNext v15/v16. Typical delivery is 2–4 weeks from confirmed scope. You receive the source, a UAT pass on a staging bench with a rollback plan, training, and a post-go-live support window — installed and maintained by ECOSIRE.