Kitchen tickets that keep the whole pass in sync.
Cibus KDS routes orders from POS, QR ordering, Storefront and delivery to configured kitchen stations. Cooks claim, prep, complete items and bump tickets while the expediter reviews the table across every routed station.
- Ribeye BakarMedium, sambal on the side
- Ikan Siakap
- Kerabu x2
- Rendang
- Nasi Ulam x2
- Tart
- Ribeye Bakar
- Rendang
POS, QR, Storefront and delivery orders can share the kitchen flow.
Claim, prep, bump and serve with individual item readiness.
The whole table across every station, in one place.
Configure station, layout, sound, display and printer preferences.
Paper tickets break when the kitchen gets busy.
During a rush, paper tickets can be buried, modifiers can be missed, allergen notes can rely on relayed messages, and front of house has to ask what is ready. Cibus KDS turns connected orders into a live kitchen workflow: routed by station, tracked by age, visible to the pass and connected back to service views.
- Paper tickets on the rail
- Shouted changes
- Duplicate prints
- Lost modifiers
- No prep-time history
- FOH asking ‘how long?’
- Live tickets by station
- Modifiers and allergens on the card
- Prep timers and priority badges
- Item-level completion
- Expediter all-station view
- Ticket history and reprints
Each item goes where it is actually cooked.
A single table can touch multiple configured stations. Drinks can go to Bar, grill items to Grill, starters to Cold and desserts to Pastry. Cibus routes each item by menu configuration while keeping the table grouped for the expediter.
- 2× Kerabu Mangga & Pucuk Paku→ Cold
- 1× Rendang Daging Tok→ Grill
- 1× Ribeye Bakar, Sambal Hijau→ Grill
- 1× Ikan Siakap Stim Limau→ Grill
- 2× Nasi Ulam→ Pass
- 4× Air Bunga Telang Limau→ Bar
- · 2× Kerabu Mangga & Pucuk Paku
- · 1× Rendang Daging Tok
- · 1× Ribeye Bakar, Sambal Hijau
- · 1× Ikan Siakap Stim Limau
- · 2× Nasi Ulam
- · 4× Air Bunga Telang Limau
- Cold· preparing
- Grill✓ ready
- Pass· claimed
- Bar· preparing
Claim, prep, bump, serve — without losing the thread.
Connected tickets follow a clear kitchen lifecycle. Cooks claim ownership, work the ticket, mark individual items complete, bump when ready and serve when the table has gone. Recall, unclaim and unbump actions support mistake correction.
- 01NewA ticket arrives from POS, QR, Storefront or delivery.
- 02ClaimedA cook claims it so the line knows who owns it.
- 03PreparingThe station works the items with modifiers and notes visible.
- 04Item completeIndividual items can be marked ready before the whole ticket is done.
- 05BumpedThe station marks the ticket ready for the pass.
- 06ServedThe order is completed once it has left the kitchen.
Make ageing tickets easier to see.
Prep timers make service pressure visible. Tickets sort by age and priority, with visual thresholds so stations and expediters can see what needs attention first.
- · Ribeye Bakar
- · Ikan Siakap
- · Kerabu x2
- · Rendang
- · Nasi Ulam x2
- · Tart
The pass sees the whole table, not just one station.
The expediter view brings every station together. It shows which tables are nearly ready, which station is holding the table and when to fire service.
Modifiers, allergens and notes stay on the ticket.
- Ribeye BakarMedium, sambal on the side
- Ikan Siakap
Configured customer instructions, item modifiers and allergen notes can appear directly on the kitchen ticket, so staff can review them without depending solely on relayed messages.
Item-level checkmarks let stations mark parts of a ticket ready before the whole ticket is bumped.
Built for real kitchen devices.
Each kitchen screen can be tuned to the station and the room: layout, card size, font scale, theme, sound alerts, auto-hide completed tickets, screen lock and printer defaults.
Not a screen of orders. A kitchen that stays in sync.
Configured item routing, visible ticket age and grouped table readiness give the expediter one connected view from first fire to final bump.
KDS turns connected orders into kitchen action.
Cibus KDS connects to the rest of the restaurant operating system. POS sends tickets, QR and Storefront orders can use the same kitchen flow, Staff Mobile can show status and Admin can provide ticket history.
Send table and counter orders to the right station with modifiers, notes and payment status connected.
Guest orders from the table can enter the connected KDS flow and use the same configured station logic as POS items.
Online orders for pickup and delivery enter the kitchen flow with prep timers and source tags.
Servers see live ticket status on their phone, so they know when to clear, deliver or fire next.
Ticket history, prep times by station and shift-level patterns sit alongside revenue and labour.
Bumped-ticket state remains associated with the connected order, bill and receipt record.
A table order at the pass.
T12 includes Kerabu Mangga & Pucuk Paku, Rendang Daging Tok, Ribeye Bakar, Sambal Hijau, Ikan Siakap Stim Limau. Cibus routes each item to its configured preparation station. The expediter can see when the table is waiting on one station and decide when the routed items are ready to serve together.
Same order record. Same shift. Visible from POS, KDS and the manager dashboard.
- OrderT12 sent from POSKerabu Mangga & Pucuk Paku and Rendang Daging Tok enter the kitchen workflow.
- RouteConfigured station tickets createdItems split by preparation station; the expediter sees the table grouped.
- ClaimStation claims its itemsTicket state changes to claimed and the prep timer runs.
- ReadyFirst items are bumpedThe expediter sees partial readiness at the pass.
- ReviewOne station is still preparingThe configured threshold indicator draws the expediter's attention.
- PassRouted items are readyThe expediter can release the table to service.
- ServeOrder marked servedThe completed ticket is available in ticket history.
KDS questions, answered.
Can Cibus KDS route tickets by kitchen station?
Yes. Items can route to configured stations such as Grill, Salad, Bar, Pastry or Pizza. Each station can focus on its assigned items while the expediter uses an all-stations view.
Can one table appear across multiple stations?
Yes. A single table can split across the configured stations its items require. The expediter view groups station readiness by table to support the decision to fire service.
Does KDS show modifiers, allergens and special instructions?
Yes. Configured modifiers, allergen notes and internal instructions can appear on the ticket card so kitchen staff can review them where the work happens.
Can cooks mark individual items complete?
Yes. A station can mark items ready within a ticket before bumping the whole ticket. That item-level state is available to connected expediter and service views.
Can the expediter see all stations together?
Yes. The all-stations view groups each table's station state and can show which station is still preparing, which is ready and when a configured time threshold needs attention.
Can kitchens still print or reprint tickets?
Yes. A device can use an assigned default printer, and authorised kitchen staff can reprint current or historical tickets on demand.
Does KDS support sound alerts and screen lock?
Yes. Sound alerts can be configured for new, priority and overdue tickets. Screens can be locked and resumed with a PIN, while layout, card size, font scale, theme and auto-hide preferences are saved per device or user configuration.
Can managers review ticket history?
Yes. Completed-ticket history can be filtered by date, station, staff context and duration. Claim, preparation, bump and serve timestamps are available for configured ticket workflows.
Bring the kitchen, pass and floor into one live flow.
See how Cibus KDS keeps tickets moving from POS, QR and online orders to the right stations — with prep timers, item-level status, reprints, history and expediter visibility built in.