Auto-accept windows by channel
You might auto-accept Wolt within 30 seconds and require manual approval on a marketplace that gets pranked.
Unified Order Management
Kill the tablet wall.
Every order channel — dine-in, takeaway, Uber Eats, Wolt, Bolt Food, Deliveroo and the rest — into one ticket queue.
The row of tablets is gone
On a Friday night the row of tablets isn't a workflow. It's a hazard.
You know the counter. One tablet for Uber Eats. One for Wolt. One for Bolt Food. One for Deliveroo. Add Just Eat and the rest once you expand, and you're at seven. Plus the POS. Plus the phone for the table-12 dessert order.
Each one beeps in its own voice. Each one has its own dashboard, its own menu to update, its own outage at the worst possible time.
dojofood replaces the row with one screen. One ticket queue. One source of truth. The tablets go in a drawer.
Every channel, same screen, same workflow
Channel parity isn't a feature we bolted on. It's how the system was built.
A Wolt order is a first-class ticket. A Bolt Food order is a first-class ticket. A dine-in order from the waiter app is a first-class ticket. Same colour code, same prep timer, same routing to the kitchen, same controls.
A real shift looks like this: Table 12's dine-in dessert, a Wolt order scheduled for 19:30, and a phone takeaway for pickup at 18:55 — same screen, same workflow. The operator doesn't context-switch between four apps. The runner doesn't ask "where's the Uber Eats one?" The kitchen doesn't have to know which tablet a ticket came from to fire it.
That's what channel parity means in practice. Not "we integrate with marketplaces." We give every channel the same seat at the table.
One queue. One source of truth.
Every order, every channel, every branch — written into the same queue, in real time.
The waiter app and the kitchen display look at the same order, the same modifiers, the same status. When the kitchen bumps the ticket, the waiter app sees it bumped. When the dispatcher accepts a Wolt order, the KDS sees it the same second.
No duplicate entry. No "did it go through?" anxiety. No reconciling four dashboards at the end of the night. One queue is the operations claim, and it's the one we'll live or die on.
What changes for the kitchen
The KDS does not care where the order came from.
It sees: this dish, this modifier, this prep timer, this station. Hot, cold, bar, pass — same routing logic regardless of channel. An Uber Eats burger goes to the hot station the same way a dine-in burger does, on the same screen, with the same course pacing.
That's the point. The kitchen has enough decisions to make at 8pm on a Friday. The origin of the ticket isn't one of them. The cook fires the ticket, bumps it, and moves on. dojofood handles the channel-back the operator never had to think about.
For ghost kitchens running three brands out of one room, the same screen pivots into multi-brand view — every order tagged with its brand, every marketplace order routed to the right concept's station group.
Per-channel rules, without per-channel chaos
The screen is unified; the configuration is per-channel and per-branch.
Prep-time overrides
Per channel and per time slot. Lunch is faster than Saturday dinner.
Per-channel pricing
Same catalogue, separate marketplace markup so the marketplace fee doesn't eat your margin.
Per-branch availability
Close a branch on one marketplace, leave it open on another, without touching the menu.
One screen. One workflow. Rules that match how operators actually run channels.
The screens don't talk → now they do
The single most repeated complaint we heard from operators: the screens don't talk.
Each system runs alone, the operator becomes the integration, and every busy night something falls through the cracks. The tablet wall is the symptom; disconnected screens is the disease.
dojofood was built to undo that. The POS, the KDS, the waiter app, the marketplace integrations, the QR menu — they all read from one catalogue and write into one order queue. Change a price on the catalogue, every channel sees it. 86 an item from the kitchen, every channel marks it unavailable.
The screens don't talk. Now they do.
20 minutes with our team
See your row of tablets become one screen.
Bring your current stack, your marketplace list, your Friday-night volume. We'll show you what one queue looks like with your channels live in it. Real human, your language, under 2 hours if it ever breaks. Monthly billing. No payment-processing lock-in. No hidden module fees.