How to measure profitability at each location

A restaurant group can close the month with record sales and, at the same time, have one location losing money. The problem is that strong results from some locations quietly offset the poor performance of others: total revenue keeps growing, the group stays in the black, and the warning sign only shows up once that location has been racking up losses for months.

Knowing which restaurant actually makes money takes more than comparing sales. You need to combine centralized operational reporting with a separate P&L for each location. The first helps you understand what's happening; the second tells you how much money is actually left after covering the costs of running that specific location.

The restaurant that sells the most isn't always the one that earns the most

When you manage several locations, it's easy to fall into a simple comparison: Madrid Centro sold more than Barcelona Eixample, Valencia grew 12%, and the newest opening is still below average. That's useful information, but it only tells part of the story.

A restaurant can bring in a lot of revenue and still have a thin margin because it needs more staff, pays higher rent, relies too heavily on delivery, or sells a product mix with poor margins. Another location can sell less and still contribute more to the group's bottom line because it runs far more efficiently.

That's the key difference between looking at sales per location and looking at profitability per location. The first tells you how much business a location generates. The second shows you how much of that business actually stays in the company.

Centralized reports and profitability answer different questions

Centralized reporting helps you understand how the operation is behaving. It lets you compare locations, review sales, products, channels, accounts or activity, and spot when something starts to shift. If a location becomes increasingly dependent on delivery, applies more discounts, or its average ticket drops, those movements can show up well before the month closes.

A P&L does a different job. It sets each restaurant's revenue against the costs needed to generate it: cost of goods, staff, rent, utilities, commissions, promotions and other operating expenses. That's how you go from “this location brought in €120,000” to a far more useful question: “how much was actually left after running it?”

These aren't two competing ways of analyzing the business. Profitability tells you where a problem exists, and operational reports help you understand why it's happening.

A simple example: three locations, three different stories

Imagine a group with three restaurants. If the team only looks at monthly revenue, they'll probably conclude that Madrid Centro is the strongest location, Barcelona Eixample is close behind, and Valencia Ruzafa is simply moving a bit less volume.

Once you factor in costs, the picture changes completely. Madrid Centro nets €16,000, while Barcelona Eixample, despite bringing in €105,000, barely generates €2,000. Valencia Ruzafa is losing €3,000 a month.

The group as a whole still shows a positive result of €15,000. If the analysis stops there, Valencia's problem can stay hidden inside the consolidated numbers, and Madrid can keep covering for its losses for months. This is exactly the kind of situation that looking at profitability by location is designed to catch.

What your per-location P&L should include

You don't need to turn every monthly close into an endless accounting exercise. What you do need is to apply the same criteria across every location. If one restaurant includes certain costs and another records them differently, comparing them loses much of its value even if each figure is correct on its own.

A practical structure can start from net sales → cost of goods → gross margin → staff → rent and occupancy → utilities → channel commissions → promotions and discounts → other operating expenses → operating result. From there you can add more detail depending on the group's financial structure.

It's also worth separating each restaurant's own costs from the company's central overhead. A location's rent clearly belongs to that location; the cost of a marketing team working across ten restaurants doesn't. Allocating overhead without a clear criterion can make some locations look better or worse than they actually are.

A margin gap is where the interesting analysis begins

Now imagine two restaurants bring in almost the same revenue, but one has a 14% operating margin and the other has 4%. Knowing there's a ten-point gap matters, but it doesn't yet tell you what to change.

That's where you need to go back to the operation. One might have higher cost of goods, need too many staff hours for the volume it moves, or sell a different product mix. It could also depend much more heavily on delivery platforms, run more promotions, or concentrate sales in time slots where keeping the restaurant open barely pays off.

The financial result works as a signal that tells you where to dig. Sales and operational data let you go one level deeper to understand what behavior is driving that difference.

The channel mix can be deceiving

This matters especially when locations combine dine-in, takeaway, their own channel and delivery platforms. Two restaurants can generate exactly €100,000 in sales with completely different economics.

If one gets most of that revenue directly from the dining room and another relies much more on external platforms or promotions, revenue can look identical while margin doesn't. That's why comparing only how much each location sells leaves out an essential question: how are those sales actually being generated?

The same happens with the menu. A restaurant can sell a lot of high-cost-of-goods products while another concentrates demand in higher-margin categories. If you only look at total sales, that difference stays hidden.

Not every location should be compared the same way

Saying one location sells 25% less than another can sound worrying until you find out it has half the tables, shorter opening hours, or has only been running for four months against a restaurant that's already fully established.

That's why, beyond absolute results, it's worth using relative metrics too. Margin on sales, cost of goods as a percentage of revenue, staff cost, average ticket, or the sales split by channel usually tell a far more useful story than a simple revenue ranking.

The goal isn't to build a dashboard with fifty indicators. It's to have enough signals to understand why two restaurants that appear to sell similarly can end up producing very different results.

Monthly close or daily reports? You need both

Waiting for the accounting close to spot an operational problem often means finding out several weeks too late. The P&L is very useful for confirming each location's financial performance, but it shouldn't be the first time you notice something is off track.

During the month, you can spot signals earlier. If delivery's share grows quickly, average ticket drops, discounts increase, or an important category starts selling less, you probably don't have the month closed yet, but you already have a reason to dig in.

A simple way to work is to use daily data to spot changes, weekly reports to confirm trends, and monthly analysis to measure the financial impact. That way, the close stops being just an explanation of what happened and becomes confirmation of something the team was already tracking.

Four rules for making per-location analysis actually work

1. Use the same criteria across the whole organization. Define what counts as sales, cost of goods, staff, commissions and operating expenses, and keep those rules stable across locations and periods.
2. Separate restaurant costs from central overhead. First analyze whether each location can sustain its own operation. Then you can add its share of overhead using a clear allocation criterion.
3. Connect finance and operations. If you find a margin deviation, drill down into products, channels, accounts, promotions and sales behavior. A financial number on its own explains very little.
4. Look at the trend, not a single snapshot. One bad week can be circumstantial. A location whose margin drops for three months in a row shows a pattern that deserves a deeper review.

Where Last.app's reports fit in

A POS doesn't replace a restaurant's accounting, and it shouldn't be presented as if it did. Calculating full profitability requires information that can live outside the sales system, like staff, rent, utilities or other company expenses.

What a POS can do is bring together much of the information you need to understand what's behind the result. Last.app's reports and analytics include data on sales, average ticket, products, channels, accounts, tables and other metrics, plus configurable reports.

This is especially useful for groups with several restaurants. Last.app lets you manage multiple locations within a single organization, so the team can work on a shared operational layer instead of building each analysis from separate systems.

The idea isn't for POS reporting to replace the P&L. It's for both to complement each other. The numbers show you where you're losing margin; the operation helps you find out what's causing it.

From knowing how much the group sells to knowing which location drives profitability

When you have a single restaurant, many deviations can still be spotted by staying close to the operation. With five, ten or twenty locations, relying on that instinct stops scaling.

You need a view broad enough to understand how the group is performing and, at the same time, the ability to drill down quickly to a specific location when something doesn't add up. That combination lets you discover that the problem isn't simply that “sales are down,” but that one location depends too much on delivery, another has a staffing structure that's hard to sustain, or a third is growing revenue while losing margin.

Because in a multi-location operation, knowing how much each location sells is just the starting point. The question that really matters is how much of those sales end up turning into margin, and what's making one location behave differently from the rest.