Multi-location software for restaurant groups and chains

Imagine Marani Group. It started with one Kakhuri Supra restaurant in Vake. Today Kakhuri Supra has three branches, in Vake, Saburtalo and Mtatsminda, and the group also runs a second brand, Georgian Burger, in Isani, Gldani and Didube. There are two legal entities, because the burger business has a partner. Every Monday the owner asks the same question: which of the six branches actually made money last week?

The answer takes days. Each branch has its own spreadsheet, its own supplier prices and its own idea of what a portion of mtsvadi weighs. By the time the numbers are put side by side, the week they describe is long gone.

This is the usual story of a restaurant group, and it rarely comes from bad management. It comes from growth. The system that worked for one restaurant was never designed for six. This article walks through how Wox handles a group: its structure, its menus and prices, its numbers and its people.

Where restaurant groups lose money

The first leak is drift. Menus, recipes and supplier prices start the same and slowly diverge. A dish that should cost the same everywhere ends up costing differently in each branch, and nobody notices because nobody compares.

The second is buying in isolation. When each branch buys alone, the group never sees its total volume with a supplier, and so never negotiates as one customer. The third is the lack of comparable numbers. Without a shared system, comparing food cost across branches is a project, not a glance.

Start with the real structure of the group

Most software treats a group as a flat list of locations. Real groups are not flat. They have brands, and under the brands there are legal entities that file their own taxes, and under those there are the actual restaurants where people cook and serve.

Wox models that as a tree: the group at the top, then brands and legal entities, then locations. Each level has a purpose. Accounting looks at the legal entity. The menu and the concept belong to the brand. Daily operations, stock and staff belong to the location. Access is set along the same tree, and reports can be read for a single location or for the whole group, depending on who is asking.

For Marani Group, that means one organisation, two brands and six locations: Kakhuri Supra in Vake, Saburtalo and Mtatsminda, and Georgian Burger in Isani, Gldani and Didube. The owner sees the whole tree. The partner in Georgian Burger sees the three burger branches. Each branch manager sees their own restaurant.

One way of working, local prices where they make sense

A group wants consistency, but not uniformity. Kakhuri Supra in Mtatsminda and Kakhuri Supra in Saburtalo have different rents and different guests, and their prices may rightly differ. With per-location pricing, each branch can keep its own prices while the menu structure stays recognisably the same.

What should not differ is how cost is calculated. In Wox, each dish has a recipe linked to inventory ingredients, and every sale deducts those ingredients from stock. When every branch costs its dishes the same way, a difference in food cost between branches points to how the branch is run, not to how the spreadsheet was built. The guide to recipe costing explains how to set this up.

When every branch calculates cost the same way, a difference in food cost points to the kitchen, not to the spreadsheet.

Numbers that can be compared

Sales reports in Wox can be read for one location or rolled up for the whole organisation: daily summaries, sales by item, by hour and by server, and tax summaries. When the group is rolled up, totals are added across branches and ratios such as average check are recalculated from those totals, rather than averaging each branch's percentage. That detail matters more than it sounds. Averaging percentages gives a small branch the same weight as a large one.

Food cost works the same way. Wox reporting shows cost of goods sold, waste and the gap between actual and theoretical food cost, per location or for the group. A branch whose gap keeps growing stands out on Monday morning, not at the end of the quarter. The article on the metrics every owner should track is a good starting point for deciding which numbers to review each week.

wox.ge

Wox

Analytics

March 2026 · Downtown

Week

Month

Quarter

Food Cost

28.4%

↓ 1.6% vs target

COGS

$18.4k

↓ $1.2k MoM

Waste

$312

Stockouts

3

Weekly SpendLast 7 weeks

W1

W2

W3

W4

W5

W6

W7

Top Spend Category

Proteins

38% of total spend

Price Variance

+2.1%

vs last month average

For accountants and partners, data can be exported (see data export). And on paid plans, Wox Analyst answers questions such as which branch had the highest food cost last week, in Georgian or English, from live data. When it suggests a change, for example a reprice on a dish whose margin has slipped, nothing is applied until a person confirms it.

Suppliers and rs.ge across the group

Most of a Georgian group's deliveries come with an electronic waybill on rs.ge. Wox connects the organisation to rs.ge once, imports twelve months of waybill history and then syncs every night. It proposes suppliers and matches products to your items, and nothing reaches stock until someone has reviewed it. Confirmed deliveries update stock and cost through normal receiving, in lari.

Because all branches share one supplier directory, the group can finally see what it buys from each supplier in total. That figure is the starting point for any conversation about price, and the article on vendor management covers how to use it.

People and access

Every person in Wox has a role, and access can be limited to the locations they work in. A branch manager sees their branch. A partner or franchise operator can be given access to their own locations without seeing the rest of the group. Head office sees everything.

One person can also belong to more than one organisation, which is common for consultants and for owners with separate businesses, and switch between them without signing out. Managers and owners can protect their accounts with multi-factor authentication. The guide on team roles and permissions explains the details.

Opening the next branch

The real test of a group's system is the day a new branch opens. In Wox, a new branch is a new location in the tree. You set its time zone and address, its storages and prices, its stations for the kitchen display, and its staff. Waybills from rs.ge can be mapped to it, and from its first service its numbers sit next to the other branches in the same reports.

The multi-location setup guide walks through each step. If you run, or plan to run, more than one restaurant, a demo with your own structure is the fastest way to see whether it fits. Plans and limits are on the pricing page.