Restaurant management built around the kitchen pass Seven modules, one order record, one login
Dearrasa

Home/Multi outlet chains

Many kitchens, one standard

The same dish should cost the same and taste the same in every one of your kitchens.

Growth breaks the informal systems that got you here. A chain does not fail because outlet four is bad, it fails because nobody can prove why outlet four is different from outlet one.

Control from the centre

What head office should decide, and what an outlet should still own.

Over centralise and outlets stop reacting to their own trading conditions. Under centralise and you have five restaurants wearing the same name.

Governed centrally

  • Menu structure and item definitions, so a dish name means the same thing everywhere.
  • Recipes and portion standards, including sub recipes produced by a central kitchen.
  • Base pricing with permitted local variance, because a mall location and a high street location are not the same business.
  • Tax configuration and invoice series per outlet, held to one standard.
  • Roles and permissions, so an outlet manager's authority is identical across the group.
  • Discount and comp policy, with the ceilings set once rather than negotiated locally.

Left with the outlet

  • Daily availability. The outlet that ran out of prawns marks prawns off, immediately, without asking anyone.
  • Roster and staffing for its own floor, within the group's cost guidance.
  • Local purchasing where you allow it, with rates recorded so the centre can see what local buying actually costs.
  • Reservations and floor layout, which are physical facts about that building.
  • Its own wastage log, because the outlet is the only place that knows what was thrown and why.
Comparison that holds up

Outlet against outlet, on figures nobody can argue with.

Comparison is only fair when every outlet is measured the same way, from the same recipes, at the same granularity. That is a data structure problem before it is a reporting problem.

Compare

Sales and covers

Revenue, covers, average bill and item mix by daypart, indexed so a smaller outlet is not judged against a larger one on absolute numbers alone.

Compare

Food cost and variance

Expected consumption from the same standard recipes against actual movement. An outlet consistently over consuming on one ingredient is a specific conversation.

Compare

Labour against sales

Hours and cost beside revenue for the same hours, per outlet, so the outlet that looks expensive can be checked against the volume it actually handled.

Compare

Kitchen speed

Ticket times by station and daypart. A slow station in one location is usually equipment, layout or headcount, and knowing which is worth the trip.

Compare

Exceptions

Discounts, voids, comps and reprints per outlet, per thousand rupees of sale. Outliers are visible without accusing anyone of anything.

Compare

Guest feedback

Sentiment by outlet and by dish, joined to the bills it came from, so a complaint pattern points at a kitchen rather than at a rumour.

Central kitchen and transfers

If one kitchen feeds the others, the costing has to follow the food.

Central production is where most chain costing quietly breaks, because a transfer gets treated as a purchase and the margin ends up in the wrong place.

  • Sub recipes are produced as stock. A gravy base made centrally becomes a costed stock item with its own yield.
  • Transfers create both sides of the entry. Dispatch from the central kitchen and receipt at the outlet are one event, so nothing goes missing between them.
  • Outlets consume at the transferred cost, which means an outlet's food cost reflects what it actually received.
  • The centre sees its own efficiency. Production yield at the central kitchen is measured separately from outlet performance, because they are different problems.
Practical questions

Rollout, franchises and access.

How do you roll out across several outlets without stopping trade?

One outlet at a time, usually starting with the one your operations team knows best. The menu, recipes and policy are configured once centrally, so each additional outlet inherits the standard and the rollout gets faster rather than slower.

Some of our outlets are franchised.

Franchised locations can be scoped so the franchisee sees their own operation completely and the group sees the reporting it is contractually entitled to, without exposing one franchisee's numbers to another.

Can an area manager see several outlets but not all?

Yes. Permissions are scoped by outlet as well as by function, so an area manager covering four locations sees exactly those four.

Do all outlets have to use every module?

No. Module state is per outlet. A delivery only location has no use for reservations, and a flagship with a large floor might be the only one running the full table module.

Next service

Pick two outlets you cannot currently compare fairly.

Send us their menus, recipes and a month of sales. We will normalise them and show you where the difference actually is, before you buy anything.