Routes automatically
Burgers, grills, fries land on the hot screen. Salads, desserts, prep on cold. Cocktails and shakes on the bar. The pass screen sees everything, in firing order, with course pacing.
Kitchen Display System
The kitchen sees every order. One screen.
Dine-in, takeaway, Yemeksepeti, Trendyol Go, Getir Yemek, Wolt, Bolt Food — routed, timed, paced, on the same display.
One screen
The kitchen doesn't care where the order came from.
A dine-in ticket from the waiter app. A Yemeksepeti order. A Wolt scheduled for 19:30. A phone takeaway. On every other system you've used, those are four separate flows on three separate screens. On dojofood's KDS they are four tickets in the same column, in the same workflow, with the same controls.
The cook fires the ticket, bumps it, moves on. They don't read the channel name. They don't need to. The origin lives in the corner of the card — for the operator, not the cook. The kitchen has enough to think about at 8pm on a Friday. Where the ticket came from isn't one of them.
That's the whole product in one line: one queue, one screen, one workflow — no matter which channel the order came through.
Ticket aging
Colour, not guesswork.
Every ticket carries a timer from the moment it lands. Green while it's inside prep target. Amber when it crosses the warning threshold. Red when it's running late.
You set the thresholds per item, per channel, or per time slot. Lunch service runs tighter than Saturday dinner. A Wolt order with a courier already on the way gets a different aging curve than a phone takeaway scheduled for an hour later. The cook reads the colour and acts. No mental math, no stopwatch on the wall.
Recall is one tap. Bumped the wrong ticket, or the guest came back to change a modifier — the cook pulls it back to the screen with the original timer state intact. Nothing gets lost in "the ticket already went."
Station routing
Hot, cold, bar, pass.
Set the rules once
In the catalog — by item, by modifier, by branch. From then on every order, every channel, walks itself to the right station. A Wolt salad doesn't show up on the grill screen. A Trendyol burger doesn't get lost in the dessert queue.
Multi-brand view
Multi-station kitchens running ghost-kitchen or multi-brand setups get a brand-tagged view: every ticket carries its concept colour, every station only sees what belongs to it.
Course pacing
Table-aware.
Dine-in service is not just a stream of tickets. It's a sequence: starter, main, dessert, with a beat between each one. dojofood's KDS reads the table from the waiter app and paces the kitchen accordingly.
The starter fires now. The main holds in the queue until the runner clears the starter plates. The dessert sits behind the main with the right gap. The cook sees the next ticket in the right order, not a wall of food fired all at once.
For takeaway and marketplace orders, pacing collapses to scheduling — the ticket fires when prep needs to start to hit the courier pickup window or the customer's chosen time. Same logic, different anchor.
Modifications
Visible, not buried.
When the waiter app sends a modification — "no onion," "extra spicy," "swap fries for salad" — it doesn't sit in a side panel. It sits on the ticket, large, where the cook is already looking. Same for marketplace modifiers; Wolt's "no pickles" gets the same visual weight as the dine-in one.
If a guest changes their order after the ticket fires, the change lands on the existing ticket with a clear flag — not a new ticket, not a chase. The cook sees what was, what is, and what changed.
86 an item from the kitchen and every channel updates the same second. The waiter app marks it unavailable. Yemeksepeti, Trendyol, Getir, Wolt mark it out. The runner doesn't need to be told. The website doesn't need a separate update. One queue, one source of truth, no menu drift.
The boring details that matter
Bump bar, all-day prep, prep-time stats.
Bump bar support — or no bump bar, your choice
Real kitchens use bump bars. dojofood's KDS supports standard USB and Bluetooth bump bars — bump, recall, fire, scroll. Plug it in, map the keys, the cook runs the screen without taking hands off the line. If you don't want a bump bar, the screen is fully touch. Tap to bump, long-press to recall, swipe between stations. Both ship in the base product, no extra module fee.
All-day prep — the morning view
Before service starts, the kitchen needs to know: how many burgers do we need ready, how much sauce, how many salad bases. The all-day view rolls every confirmed and scheduled order — dine-in reservations, marketplace pre-orders, catering — into one prep list per station. Open it in the morning, work the list, stop guessing.
Prep-time stats per item — built in
Every ticket records the time from fire to bump. dojofood rolls those numbers up into per-item prep-time stats — median, peak, channel-by-channel. Use them to set realistic prep windows for marketplace channels (the wrong number costs you ratings), to flag when an item is slowing the line on Friday nights, and when training a new cook on the grill.
Hardware
Standard screens. No proprietary terminal.
The KDS runs on standard 19" / 21" / 24" touchscreens. iPad in portrait works for tight stations. Wall-mount Android panels work for the line. Use what your kitchen already has, or buy whatever fits — we don't lock you into a branded KDS terminal that costs three times what it should.
If you've been quoted a $1,200 "proprietary KDS hardware kit" by another vendor, you've been told the wrong story. The screen is a screen. The intelligence is in the software.
20 minutes with our team
See your kitchen on one screen.
Bring your station map, your channel mix, your Friday-night volume. We'll show you what the KDS looks like with your orders flowing through it — dine-in, takeaway, and every marketplace in the same column. Real human, your language, under 2 hours if it ever breaks. Monthly billing. No proprietary hardware. No hidden module fees.