Dots runs both shapes of a food business. A mono-brand setup is one brand, one app, one identity — everything tuned to a single name. A multi-brand setup puts several brands on the same platform: each gets its own menu, design, and customer-facing app or site, while you manage all of them from one admin panel with one team.
The second brand is where platforms usually break
The typical path hurts: a restaurant launches a second concept and ends up with a second subscription, a second tablet on the counter, a second courier roster, and staff re-entering the same dishes into another dashboard. Every additional brand multiplies the overhead. On Dots the marginal cost of a brand collapses — the kitchen, couriers, payment setup, and back office are already there. You add a menu and a skin, not an infrastructure. That is exactly the economics behind virtual brands: one kitchen selling as three names captures three demand streams for one rent. We ran the numbers in virtual brands from one kitchen.
How it works in the Dots platform
Each brand is configured independently: menu, prices, app design, working hours, delivery zones. Underneath, everything converges. Orders from all brands land in the same monitoring panel, so one dispatcher sees the whole operation. One courier fleet serves every brand — a driver carries a pizza order and a poke bowl on the same run. The customer base is shared where you want it to be: analytics show whether your burger brand and your dessert brand are feeding each other customers or competing for the same ones, and reports split revenue, order counts, and margins per brand so weak concepts can't hide inside a blended total.
Who gets the most out of it
- Ghost kitchens — launching concept number four without buying software number four.
- Restaurant groups — separate brand identities, one operations team and one P&L view.
- Single-brand restaurants planning growth — start mono-brand; the second concept is a configuration, not a migration.
