Outlet-Wise P&L for Restaurants: A 2026 Operator's Playbook
An outlet-wise P&L is a profit and loss statement built for a single restaurant location: channel-level revenue net of aggregator commissions, COGS tied to that kitchen's stock movement, and shared costs allocated by a documented rule. Almost no Indian multi-outlet chain has one that refreshes faster than month-end. This playbook lays out the 6-line stack that works, the four ways operators try to build it, and how to make the report deliver weekly operating decisions instead of monthly post-mortems.
If you run 4 outlets or 400, this is for you. You will leave with the report structure to demand from finance, a comparison of the four build paths, the FireAI feature map for each pain point, and a 5-question weekly review checklist.
What is an outlet-wise P&L, and why don't most chains have one?
An outlet-wise P&L scopes profitability to a single restaurant location. Revenue splits by channel (dine-in, takeaway, Swiggy, Zomato, ONDC, own app) and reports net of aggregator commissions — not gross. Cost of goods sold matches that outlet's purchases plus commissary transfers minus closing stock. Variable opex (packaging, gas, electricity) carries the outlet code at booking. Fixed and shared costs (commissary overhead, brand marketing, head-office payroll) are allocated through a published rule. The output is one number that an outlet manager can defend or be judged by: outlet EBITDA.
Most Indian chains do not produce this. Their consolidated P&L lives in Tally. Their sales sit in Petpooja or Posist. Their commissions sit in Swiggy and Zomato partner dashboards (15–30% per order in 2026, per current rate cards). Their payroll sits in Keka or RazorpayX Payroll. Each system is internally clean. None of them line up.
The constraint isn't software. Every Indian QSR has a finance analyst maintaining a master spreadsheet that could be an outlet P&L. The problem is that the file takes 3–5 working days per month to refresh, the data is 30+ days stale by the time it lands in a review meeting, and a new outlet opening or an aggregator slab change breaks the model.
The result, in our experience across Indian QSR and casual-dining chains: a brand with a healthy 11% consolidated EBITDA frequently contains 2–4 outlets running negative EBITDA. The healthy outlets fund the sick ones until the lease comes up for renewal. By then, the easy fixes are gone.
The 6-line outlet P&L stack every restaurant chain should run
Build the report in this exact order. Each line ties to a system of record, so finance can audit it. Each line ties to a unit metric (per cover, per order, per square foot), so operators can act on it.
| # | Line | What it measures | Source system | Audit rule |
|---|---|---|---|---|
| 1 | Gross sales by channel | Order value across dine-in, takeaway, Swiggy, Zomato, ONDC, own app | Petpooja / Posist + aggregator partner portals | Ties to POS sales register and aggregator settlement files |
| 2 | Net revenue | Gross minus aggregator commission, payment gateway, GST collected as agent, outlet-funded discounts | POS + Swiggy/Zomato settlements | Recompute commission against published slabs; flag mismatches |
| 3 | COGS | F&B cost tied to outlet stock movement and commissary transfers | Inventory / commissary IMS | Opening + purchases + transfers in − closing − transfers out |
| 4 | Outlet variable opex | Packaging, rider fees if self-delivered, gas, electricity, water, consumables | Tally outlet tag + sub-ledger | Every invoice carries the outlet code at booking |
| 5 | Outlet fixed opex | Rent, manager and kitchen payroll, AMC, internet, security | Payroll + Tally | Payroll attribution via employee→outlet master |
| 6 | Allocated shared cost | Commissary overhead, regional manager, brand marketing, head office | Allocation rule | Rule is documented, dated, signed off by CFO |
Outlet EBITDA = Line 2 − (Lines 3 + 4 + 5 + 6).
Two rules separate a credible outlet P&L from a vanity one. First, every shared cost needs a written allocation rule the franchisee or outlet manager has signed off on. Without that, the report becomes a political instrument and gets ignored. Second, every line has to roll up exactly to the consolidated P&L in Tally. If the outlet-wise total doesn't equal the chain total, finance loses trust and reverts to spreadsheets.
Where outlet-wise P&L breaks down: the five-stack problem
The reason this report is hard is not arithmetic. It is data plumbing. Indian restaurant chains run on five disconnected stacks at once.
The POS layer (Petpooja, Posist, Dotpe, Restro PoS). Strong at operations, weak at finance. Outlet-tagged sales, item-level mix, order count by hour. Most POS reports won't net out aggregator commissions or reconcile to settlement files.
The aggregator layer (Swiggy, Zomato, ONDC). Commissions, ads, restaurant-funded discounts, and platform-side adjustments all live here. Settlement files arrive on T+7 to T+14 with a different SKU code than the POS uses for the same item.
The accounting layer (Tally, Zoho Books, QuickBooks). Holds the audited P&L. Typically without an outlet dimension on every voucher. Shared invoices (commissary purchases, central marketing) get booked without a clean outlet tag.
The payroll layer (Keka, GreytHR, RazorpayX Payroll). Salaries are tagged to employees, not outlets. Transfers and dual-outlet roles break attribution unless someone maintains the employee-to-outlet master every payroll cycle.
The commissary and inventory layer. Central kitchens usually sit on a separate IMS. Transfer-out values to outlets are often booked at internal transfer pricing, which inflates outlet COGS unless you correct for it.
Reconciling these five by hand is what kills outlet-wise P&L projects. The data exists. The pipes don't.
Outlet-wise P&L tools compared: four build paths
There are four routes operators take. Each has a ceiling.
| Approach | What you get | What breaks | Realistic time-to-decision |
|---|---|---|---|
| Tally outlet tags + Excel pivots | Month-end legal P&L by outlet, eventually | Aggregator nets, payroll attribution, weekly cadence | 30–45 days after month close |
| POS reports (Petpooja, Posist multi-outlet) | Sales, item mix, basic margin by outlet | Commissions, shared cost allocation, no audit trail to Tally | Daily on sales; never on full P&L |
| Restaurant accounting platforms (Restaurant365, MarginEdge, Gofrugal) | Outlet P&L if you migrate accounting onto their platform | Heavy implementation, India stack (Tally, Swiggy, Zomato) not always native | 3–6 months to roll out across a chain |
| Decision intelligence layer (FireAI) | Outlet P&L on top of existing Petpooja, Tally, Swiggy, Zomato — no migration | Requires up-front mapping; quality depends on source data hygiene | 2–4 weeks from connect to first signed-off report |
The accounting-platform route works for chains willing to re-platform. Most established Indian operators won't, because Tally is the system of record their CA audits and Petpooja is what their captains already use. That's the case for a connect-and-model layer rather than a full replacement.
How FireAI builds outlet-wise P&L on the stack you already run
FireAI is the decision intelligence layer that sits above Petpooja or Posist, Tally, Swiggy and Zomato partner data, payroll, and the commissary IMS. It does not replace any of them. It pulls each source on a schedule, reconciles to the outlet master, and produces one P&L every outlet manager and the CFO read the same way.
Five capabilities matter for outlet-wise P&L specifically:
1. 250+ source connectors. Petpooja, Posist, Tally, Swiggy and Zomato partner data, Keka, RazorpayX, and the common SQL stores that hold commissary inventory all plug in out of the box. New outlets appear automatically once they're tagged in the master.
2. Configurable allocation rules. Shared costs (commissary overhead, regional manager salaries, brand marketing) allocate by rules you write once: revenue share, order count, cover count, square footage, or fixed monthly. Every rule is versioned, dated, and printed on the report. Finance and franchisees argue with the rule, not with the number.
3. Ask FireAI. Outlet managers don't open BI tools. They ask questions. "Which outlet had the biggest drop in EBITDA last week?" or "Why did Indiranagar's COGS spike on Saturday?" Ask FireAI returns the answer with the underlying drill-down, in plain English (or 20+ Indian languages), with no SQL.
4. Causal Chain. When an outlet's EBITDA drops, FireAI walks every P&L line to find the one that moved most: aggregator commission rate, COGS spike, payroll over-run, restaurant-funded promo. That's the difference between "your margin fell 180 bps" and "your margin fell 180 bps because the Swiggy lunch-combo discount cost ₹74,000 over the week and ads didn't recover it."
5. Data Guard (role-based row access). Franchisees see only their own P&L. Regional managers see their cluster. The CFO sees everything. Access is enforced at the row level, so one dashboard can serve a 200-outlet chain without anyone seeing data they shouldn't.
The first signed-off outlet P&L typically lands 2–4 weeks after sources are connected. The work in that window is mapping, not modelling: agreeing on the outlet master, agreeing on the allocation rules, and validating that the FireAI total ties to Tally's consolidated number to the rupee.
What outlet-wise P&L unlocks: three real chain decisions
The 9-outlet QSR that found 4 loss-making outlets behind an 11% margin
A QSR brand with 9 outlets across two cities ran an 11% consolidated EBITDA and assumed the chain was healthy. The first outlet-wise P&L told a different story: three outlets at 18–24% margin, two at 4–6%, four between -9% and -3%. The healthy three were funding the sick four.
The Causal Chain pulled out why: the loss-making outlets were over-indexed on aggregator delivery — 62–78% of revenue, against a 41% chain average. At that mix, Swiggy and Zomato commissions were eating margin faster than dine-in could replace it. The decision wasn't to close the four outlets. It was to renegotiate the aggregator rate card, kill outlet-funded discounts on the lunch combo, and shift the promo budget to dine-in recovery in those four locations. Outlet EBITDA on the worst-performing site moved from -7% to +6% in 11 weeks.
The franchise dispute settled by data, not lawyers
A 14-outlet franchise chain had a six-month standoff with two franchisees over commissary pricing. The franchisees claimed the central kitchen was overcharging. The brand claimed labour costs in those outlets were above the agreement.
With outlet-wise P&L on FireAI, both sides looked at the same rules and the same numbers. The commissary's blended margin came in at 9%, not the 12% the franchisees believed. Labour cost as a percentage of revenue was 4.2 points higher in the two outlets than the chain average, driven by overstaffing in the slow afternoon window. The brand rolled out a volume-based commissary discount; the franchisees re-rostered. The dispute closed in three weeks.
The dark-kitchen brand that re-cut a 16-outlet expansion
A delivery-only brand with 11 dark kitchens was raising a Series A and pitching a 16-outlet roll-out. The first outlet-wise P&L showed that the four most profitable kitchens cleared 22% EBITDA. The seven newer ones averaged 3%. Same menu, same supplier, same head office. The Causal Chain isolated the gap: the seven newer kitchens sat in zones where Swiggy and Zomato's surge and long-distance rider fees ate the unit margin.
The brand cut the roll-out plan to 7 kitchens, retargeted to high-density zones with sub-2-km delivery radii, and went back to the investor with revised unit economics. The round closed on stronger terms a month later.
Your weekly outlet review: 5 questions to ask
The report is not the point. The weekly conversation it enables is. Use these five questions in every outlet review.
- Which outlet moved most against last week, and which P&L line caused it? If you can't answer in 60 seconds, your data is too slow or too aggregated.
- Where is the channel mix drifting? A 10-point swing toward Swiggy or Zomato in a week is a margin event, not a topline event.
- Is COGS percentage tracking the menu mix, or moving independently? Independent movement usually means wastage, theft, or recipe drift.
- Which outlets are over- or under-staffed against cover count? Labour percentage is the second-biggest movable cost after COGS.
- Is the allocation rule still fair? Re-test shared-cost allocation every quarter. Outlet mixes change; rules don't update themselves.
If the current report can't answer 4 of the 5 in real time, the report isn't doing its job.
Benchmarks: what good looks like in 2026
Use these as floors, not targets. Most chains we work with are 200–500 bps below them on at least one line.
- Prime cost (COGS + labour) as % of net revenue. 55–60% for QSR, 60–65% for casual dining. Higher signals menu engineering or roster discipline issues.
- Aggregator commission cost as % of delivery revenue. 18–28% blended (Swiggy + Zomato), depending on city and ads spend. Anything above 30% means the promo mix is broken.
- Outlet EBITDA spread. The best outlet in your chain should be no more than 15 points ahead of the worst. Larger spreads mean either location-mix failure or unenforced operating standards.
- Same-store EBITDA growth. Track this alongside same-store sales growth. Sales growth without EBITDA growth means the chain is buying revenue from aggregators.
FAQs
What is outlet-wise P&L for a restaurant?
An outlet-wise P&L is a profit and loss statement built for a single restaurant location. It shows channel-level revenue net of aggregator commissions, location-specific COGS, variable and fixed opex booked to that outlet, and an auditable allocation of shared costs. The output is outlet EBITDA — the number used to decide which locations to invest in, fix, or close.
Why don't Petpooja or Posist already produce outlet-wise P&L?
Petpooja and Posist are point-of-sale platforms. They report sales, item mix, and basic margin by outlet, but they don't hold accounting ledger, payroll, or commissary inventory. A complete P&L needs all four. POS reports are an input to outlet-wise P&L, not a replacement for it.
How is outlet-wise P&L different from same-store sales reporting?
Same-store sales tracks revenue growth at outlets open for more than a year. Outlet-wise P&L tracks profitability at every outlet, including new ones, with full cost attribution. Same-store sales tells you the chain is growing. Outlet-wise P&L tells you whether it's profitable while it grows — the second number is the one your investor cares about.
How long does it take to build outlet-wise P&L on FireAI?
The platform connects to Petpooja, Posist, Tally, Swiggy and Zomato partner data, and the major payroll systems out of the box. The first signed-off P&L usually takes 2–4 weeks. Most of that time goes into agreeing on the outlet master, defining the allocation rules, and validating the FireAI total against the consolidated Tally number.
What's the biggest mistake chains make when building outlet-wise P&L?
Allocating shared costs by gut feel and revising the rule whenever someone complains. The fix is to write the rule, version it, date it, and surface it on every report. Operators argue with the rule once. They trust the number after that.
How often should outlet-wise P&L refresh?
Daily on revenue and COGS, weekly on labour, monthly on shared cost allocation, single signed-off close on month-end. If the report is monthly only, you catch margin breaks 30–45 days after they happen — too late for most operating decisions.
Does outlet-wise P&L work for cloud kitchens and dark stores?
Yes, and arguably more cleanly, since there's no dine-in stream to reconcile. The main difference is that rider economics, zone surge fees, and packaging dominate the variable cost lines instead of front-of-house labour.
Can outlet-wise P&L handle franchise (FOCO / FOFO) outlets alongside company-owned ones?
Yes. The structure stays the same; the allocation rules and access rights change. Franchisees see only their own outlet, with the commissary recharge and royalty calculation shown line by line. FireAI's Data Guard enforces this at the row level so one dashboard serves the whole chain.
Where to start
If you run a multi-outlet chain and your current P&L is consolidated only, the prerequisite work is unglamorous: every cost voucher in Tally needs an outlet tag, and every employee in payroll needs to map to an outlet master. Get that hygiene done first — no reporting tool can fix unattributed data.
The reporting layer itself can come from FireAI, a restaurant accounting platform like Restaurant365, or an internal BI build. The choice turns on one question: are you willing to re-platform your accounting? For most Indian chains running on Tally and Petpooja or Posist, the answer is no, and the connect-and-model route is the faster, lower-risk path.
See your own outlet P&L on FireAI at app.fireai.in, or book a demo and we'll wire your stack into a working outlet P&L inside the call.
Posted By:
Ishita Shah
Content Editor, FireAI
10+ years of leading Product Management, New Ventures and Project roles at Delhivery, Zomato, and eInfo Solutions. Notion Affiliate and Member of Insurjo Cohort.
10+ years of leading Product Management, New Ventures and Project roles at Delhivery, Zomato, and eInfo Solutions. Notion Affiliate and Member of Insurjo Cohort.
Loading...