Comparing sites fairly

Raw revenue makes the biggest site look best and tells you nothing. Which measures actually compare across locations, and which differences are not problems.

The first thing every multi-site operator builds is a league table of revenue by location. It is the most natural report in the world and close to useless, because it mostly ranks your sites by how big they are and where they sit.

Normalise before you compare

A fair comparison divides by something. Which denominator you choose determines what question you are actually asking, and using several is better than trusting one.

  • Per cover. Removes size and traffic, and shows how well each site converts a guest who already walked in.
  • Sales per labor hour. Shows whether the staffing fits the demand, which is the comparison most likely to be actionable.
  • Per square foot or per seat. Useful when sites differ physically, and the only way to judge a small site fairly.
  • Margin, not revenue. A high-revenue site in an expensive lease can contribute less than a quiet one with cheap rent.
The comparison that usually changes minds

Sales per labor hour by daypart, per site. It routinely shows that the location everyone considers the weakest is running the tightest shifts, and the flagship is carrying hours nobody has questioned in a year.

Differences that are not problems

Some variance between sites is correct and chasing it destroys value. A site with a different daypart mix, a different neighbourhood or a different physical constraint should not produce the same numbers, and pushing it to do so usually means asking a manager to break something that works.

  • Different average check across neighbourhoods. Usually the market, not the selling.
  • Different labor percentage where wages or minimum staffing differ.
  • Different menu mix. A site selling more of a lower-margin item may simply have different customers.
  • A new site under-performing during its ramp. Judge it against its own trajectory, not against a mature location.

The most useful multi-site question is not which location is best but which is moving. A site that is quietly declining while remaining second in the league table is the one that needs attention, and a snapshot ranking hides exactly that.

Group sites into meaningful sets, too. Comparing a suburban store against a downtown one tells you less than comparing suburban against suburban.

Where the numbers come from

Opero reports a per-location breakdown and can roll figures up by brand and by region, so a group with more than a handful of sites can compare like with like rather than against one flat list. Because orders, payments and labor sit on one spine, per-cover and per-labor-hour figures come from the same records rather than from three exports stitched together.

One thing to plan around: access in Opero is account-wide. Everyone with a membership sees the whole group, so there is no way to give a regional manager a view limited to their own sites. If restricted visibility matters to how you are structured, that is a real gap to weigh.

See per-location breakdown with brand and region roll-ups.

Explore multi-location

Frequently asked questions

What is the single best measure to compare locations?
If forced to one, sales per labor hour by daypart — it removes size, exposes staffing fit, and is directly actionable. In practice use it alongside a per-cover figure and margin, because each answers a different question.
Can I give a regional manager access to only their locations?
Not today. Access in Opero is account-wide, so anyone with a membership sees every location. There is no region-scoped or location-scoped visibility, which is worth weighing if your structure depends on it.
Should all my locations hit the same targets?
No. Neighbourhood, daypart mix, rent and wages all legitimately move the numbers, and forcing identical targets usually pushes a manager to damage something that works. Compare each site against its own trend first.

Run your whole restaurant on one platform

POS, kiosk, QR ordering, kitchen display, and payments on one spine — you bring the tablets, and the card reader is the one piece you buy from us. Unlimited devices, no per-device fees.

Explore the platform

Keep reading

Opero™ is a product of TackOn LLC. · The Restaurant Operating System