Single-branch tool
Log in, log out. Compare in your head.
The group report is a CSV. Built for multi-branch: one screen, every branch, outliers flagged before Friday.
For operators running 2 to 50+ branches
Menu changes once. Live in every branch in 60 seconds.
HQ sees every branch. Each branch runs its own day, inside the rules you set. One platform, one support line.
Built for multi-branch
Most POS were built for one place. A report got bolted on.
The honest version. Most restaurant POS systems were designed for one branch. Multi-branch came later, as a report.
You log into one branch, log out, log into another, compare in your head. The "group dashboard" is a CSV export.
dojofood was built the other way around. Branches are first-class — not a workaround. Catalog, roles, inventory, marketplace map, analytics — all designed for six places before one.
If you do volume across stores, you feel it on day one. Not month six.
The morning coffee screen
Revenue across all branches at a glance. Outliers flagged.
The HQ dashboard is the morning coffee screen.
Today's revenue, by branch, ranked. Yesterday's comparison. Week-on-week. Channel mix per branch. Peak-hour heatmap. Average ticket per branch.
Outliers get flagged. Branch 03's lunch dropped 22% vs last Tuesday. Branch 05 tilted toward Uber Eats overnight. Your regional manager finds out on the dashboard — not on a Friday phone call.
Drill into any branch from any tile. Same screen, scoped down. Same numbers. Nothing reconciles in a spreadsheet.
Running 5+ branches?
Inside your policy
Each branch runs its own day. Inside your rules.
Branches are not clones. The office cafe closes at 4pm and runs a lunch menu. Downtown opens at 11 and serves until midnight. The flagship has different staffing, a different price band, a different marketplace mix. dojofood handles that.
Menu items per branch
Inherit the master catalog. Enable, disable, or override at the branch level — within what HQ allows.
Hours per branch
Each branch keeps its own clock. Day-part menus follow the clock — breakfast at the office cafe ends at 10:30, brunch at the downtown branch runs until 3.
Staff per branch
Branch managers see their branch only. Regionals see their cluster. HQ sees everything. No "share my login."
Pricing per branch
Override an item price at one branch. The rest of the group stays at the master price. Or push a group-wide promo and exclude one location.
The pattern is the same throughout: HQ sets the policy. Branches operate inside it.
Catalog inheritance
One master menu. Branches inherit. Override where you allow it.
The catalog is the spine. HQ controls it. Items, modifiers, recipes, photos, allergens, languages — all in the master catalog. Add at HQ, live in every branch in 60 seconds. Discontinue at HQ, gone everywhere. Branches inherit by default. Then, within the policy HQ defines, branches can:
Disable locally
Branch 03 doesn't sell the burger.
It exists in the catalog. It just doesn't show up on Branch 03's POS or QR menu.
Override a price
Branch 04 is in a different rent band.
Coffee runs 5 lira higher there. The rest of the group doesn't see the change.
Branch-only item
The rooftop cocktail at the flagship.
Exists only on Branch 02. Never appears in the group menu.
HQ can lock any of these levers. Lock the price column and branches can no longer override pricing. Lock the menu and branches inherit, period. Operator's call.
Per-branch marketplaces
Branch A is on Uber Eats and Wolt. Branch B is on Bolt Food and Uber Eats. Both run from the same screen.
Marketplaces are not group-wide.
Branch 01 is on Uber Eats and Wolt — that's the delivery coverage there. Branch 02 is on Bolt Food and Uber Eats because Wolt doesn't deliver yet. The flagship runs all four.
Map marketplaces to branches once. Every order, every marketplace, every branch — one ticket queue, scoped to the kitchen.
Per-branch pricing per marketplace too. Branch 01 runs +12% on Uber Eats. Branch 02 runs +10%. Branch 04 runs parity. Each branch sets its own rules, inside HQ policy.
Live Uber Eats · Trendyol Go · Getir Yemek · Yemeksepeti · Migros Yemek
Coming Wolt · Bolt Food · Just Eat · Deliveroo — two-week SLA on new ones.
Role tree
Branch managers see their branch. Regionals see their cluster. HQ sees all.
Visibility follows the role tree.
Branch manager
Today's revenue, today's labour, today's stock, today's tickets — for this branch only. No "what is Branch 04 doing." That's a different role.
Regional manager
Their cluster. Drill into any branch in the cluster. Compare across the cluster.
HQ / owner
Everything. Cross-cluster comparisons. Group analytics. The full picture.
Kitchen and floor
Their station, their tickets. No financial visibility unless you grant it.
Permissions are a tree, not a switch. Define a role once, apply it across branches. New branch, new manager — scope them in two clicks.
Group ledger, not branch silo
Branch 02 ran out of cold brew kegs. Branch 04 has six. Transfer in three taps.
Inventory is a group ledger, not a branch silo.
See across the group
Stock across every branch on one screen. Spot a shortage at one branch and a surplus at another.
Move stock, ledger updates both sides
Branch 04 loses two kegs, Branch 02 gains two, the transfer log records who, what, when.
Reorder points
Per branch and group-wide. Branch 03 hits its reorder level on espresso beans? Trigger a supplier order from the branch — or escalate to central purchasing if HQ owns procurement.
Recipe-level depletion. One sale at one branch deducts the right grams of the right ingredients from that branch's stock. No spreadsheet at the end of the week.
Each branch keeps its own clock
The office cafe closes at 4pm. The downtown one runs until midnight. Each branch keeps its own clock.
Day parts are per branch.
Office cafe: breakfast 8–10:30, lunch 11:30–15:00, then closed. Downtown: brunch 9–15, dinner 18–23:30, late menu 23:30–00:30. Same master catalog. Different schedules.
Items appear and disappear automatically. Dine-in, takeaway, every marketplace — one clock per branch. Uber Eats stops selling the breakfast burrito at 4pm. The catalog handled it.
Time-windowed promos follow the same logic. Happy hour downtown only, 17:00–19:00. The rest of the group doesn't see it.
Roll-ups and drill-downs
Group, region, branch, channel, item. Move between them on the same screen.
The reporting layer is one tree.
Start at the group. Total revenue, covers, tickets, channel mix, peak hours. Drill into region, branch, channel inside a branch, item inside a channel.
Same screen. Same numbers. Same filters.
Branch managers see what HQ sees about their branch — no hidden numbers. HQ sees every branch, summed up correctly. No reconciliation drift.
Daily, weekly, monthly. Custom date range. Compare to last week, last month, last year, same period.
Scaling past one brand — franchises, food courts, hotels, custom integrations and SSO? See dojofood Enterprise.
Have questions? Let's talk.
Bring your branch map. We'll show you one screen.
20 minutes with us. Show us how many places you run, your branch-by-branch marketplace map, where menu drift hurts. We'll show you HQ, branches and marketplaces on one platform. Multi-branch goes live in 14 days. Real humans when it breaks. One support line, your language, under 2 hours.