Use case · Scaling

From one place to many. Same brand. Same catalog. Same morning rush handled.

One brain across every branch. Change a price once. Open a new location in a week. One morning number, not a tab per branch.

Talk to our team about your second branch →See the inflection points
Who this is for

If you're about to open your second place, this page is for you.

Operators with one strong location and a lease signed for the second. Restaurant groups with three to ten branches and a centralized ops team. Concept brands going from five to fifty. Franchise operators bringing brand standards to independently-owned branches.

Still on your first place? Bookmark this. Choosing the right stack now is the cheapest decision you'll make. The wrong POS at branch two is the most expensive thing in your operation by branch five.

The three inflection points

What changes when you go from 1 to 2, 5 to 10, and 20+.

Multi-location isn't one problem. It's three. Each transition breaks a different part of the operation.

1 → 2 · the duplication

The "we keep copying the menu" moment.

Branch one's menu lives in a POS. Branch two opens. Now you have two menus, two pricing trees, two marketplace catalogs. Change a coffee price, you change it four times. Something gets missed. The Friday-night manager finds out from a customer.

What breaks: the menu, the pricing, the marketplace catalog sync, the staff handoff between branches.

What dojofood does: one catalog, both branches read from it. Change a price once — live everywhere in 60 seconds. Per-branch overrides only where you need them (location-specific items, location-specific pricing). The default is "same."

5 → 10 · the visibility

The "I can't see all my branches anymore" moment.

At five branches you can call every manager every morning. At ten you can't. You need numbers. The system that worked at three — a tab per branch, a Sunday spreadsheet — breaks at ten. A branch has a bad week and you find out in the month-end report.

What breaks: daily visibility, food-cost surprises, marketplace performance gaps, staff coverage gaps, the founder's sleep.

What dojofood does: one operator brain across every branch. One screen with all ten branches' covers, channel mix, top sellers, food cost, marketplace rating — by branch, side by side. Yesterday vs. last week vs. last month. The morning check is two minutes, not forty.

20 + · the standards

The "brand standards or chaos" moment.

Twenty branches in, you're not running restaurants. You're running a system that produces restaurants. The question shifts from "is branch 12 doing okay" to "is branch 12 within brand standard." Pricing variance has to be controlled. New franchisees must onboard in a week. The catalog has to enforce, not advise.

What breaks: brand consistency, pricing discipline, franchise onboarding speed, royalty reporting visibility, the operator's last bit of trust in the franchisees.

What dojofood does: franchise mode. Brand-locked catalog (franchisees can't change core items or pricing). Royalty calculation by branch, automated. New-branch onboarding template — clone the standard, swap the location, live in days. Branch-level controls (which franchisee can change what, with what approval).

The platform that grows with you

Same product. Different shape at each scale.

You don't switch software at branch 5. Or at branch 20. The same dojofood that ran your first place runs your fiftieth — with the controls turned on as you need them.

1-4 branches

Multilocation Management.

One catalog. Each branch reads from it. Per-branch staff and floor plans. Per-branch marketplace IDs. One central reporting view. See multilocation
5-20 branches

Multilocation Marketplace.

Push the same catalog to every branch's Wolt, Yemeksepeti, Trendyol, Getir, Migros Yemek accounts. Per-branch pricing. Per-branch open/closed status. One sync, every channel.
Franchise

Franchise Management.

Brand-locked catalog. Royalty reporting per branch. New franchisee onboarding template. Role-based access (franchisor sees everything; franchisee sees their branch). Approval workflows for menu changes. See franchise
The new-branch playbook

Opening branch N+1 should take days, not weeks.

When you've already got dojofood running, opening another location is mostly logistics, not software setup.

Day 1

Clone the standard.

Clone the new branch from your standard template — catalog, floor plan, station setup, KDS routing, marketplace template. Swap the address, the staff list, any local-only items. 30 minutes, not three days.
Day 2-4

Hardware + marketplaces.

Hardware ships or we install on the tablets you already bought. Marketplace accounts get connected to the new branch — Wolt, Yemeksepeti, Trendyol Go, Getir, Migros Yemek. Onboarding times depend on the marketplace, not us.
Day 5

Staff training.

If the brand is already on dojofood, your existing managers train the new branch's team. We're on the line if anything is unfamiliar. 24 hours, not a week.
Day 6-7

Soft open, then live.

A soft open weekend (limited menu, limited marketplaces) before going full. The HQ dashboard sees the new branch the moment it starts taking tickets — same as every other branch.
Honest about scope

What we don't do for multi-location operators.

If any of these are central to your operation, plan for them separately.

We don't run your supply chain

  • Inventory tracks ingredients per branch
  • We don't manage your central kitchen / commissary as its own entity
  • Integrate with your wholesaler / commissary system; we report stock movements

We don't run multi-country tax

  • Branches in different countries need different tax setups
  • We support TR (KDV), NL (BTW), DE (USt), and a growing list
  • Tell us your countries — we'll be honest about what's tested

Workforce management is light

  • Basic staff scheduling, shift view, branch coverage
  • Not a full WFM platform — no demand forecasting yet
  • Integrate with your existing scheduling tool if you have one
Have questions? Let's talk.

Bring your branch list. We'll show you one screen.

Bring your current branches, your near-term roadmap, your marketplace setup. We'll walk the inflection point you're closest to — and what your stack looks like on the other side.

Book a 20-min walk-through →See multi-location pricing