We rebuilt the KDS because restaurants told us the old version was still causing friction. Too many taps to acknowledge an order. No visual way to see which table was waiting longest. And the floor plan lived in a completely separate screen. So we fixed all of it.

What wasn't working

The v1 KDS required kitchen staff to tap through sub-menus to dismiss orders. In a quiet service that's manageable. During a Saturday lunch rush at a 60-cover restaurant in Sea Point or Melville, those extra taps add up, and they add up at exactly the moment when things are already moving fast.

There was also no urgency system. A ticket that arrived 20 minutes ago looked identical to one that arrived 2 minutes ago. Kitchen staff had to mentally track timing themselves, which is one more cognitive load when they already have seven things on the go.

And the floor plan was a separate module entirely. Front-of-house had to switch between screens to check kitchen status. Kitchen couldn't see the floor at all. Two parts of the same service, working with incomplete information.

What's new in KDS 2.0

Colour-coded urgency tiers

● 0–5 min, Normal ● 5–10 min, Attention ● 10+ min, Urgent

Tickets now change colour based on time-since-fired. White means it just came in. Amber means it needs to move soon. Red means it's overdue and should have left the kitchen already. Kitchen staff can see the full board's priority at a glance, no timestamps, no mental maths.

One-tap acknowledgement

Orders arrive on the screen. One tap to acknowledge, kitchen has seen it. One tap to mark done, ticket leaves the screen. That's it. No sub-menus, no confirmation dialogs, no extra steps. We measured this: the old workflow averaged 4 taps per ticket. This one is 2. On a 100-cover service, that's hundreds of unnecessary taps eliminated per shift.

Floor plan integration

The floor plan is now embedded directly in the KDS view. Kitchen staff can see which tables are occupied and pending service, without asking front-of-house and without switching screens. Front-of-house can see kitchen status on their tablet in the same way. It's one shared view of what's happening across the whole restaurant.

Smart ticket routing

If your kitchen has multiple stations, grill, cold prep, drinks bar, orders now route automatically to the right screen based on item tags. The grill station sees grill items. Cold prep sees their items. No shouting across the kitchen, no paper tickets handed between stations. You set up the tags once; the routing handles itself after that.

Offline-first

If your internet drops or your router goes down, the KDS keeps working. Tickets queue locally on the device and sync when connection returns. Service doesn't stop. This was a specific request from several Durban restaurants who were getting caught out mid-service when their connection dropped.

KDS 2.0 is available to all Nexo PLAN and PRO subscribers. There's no additional cost, it's part of the same subscription you're already on. No upgrade needed, no add-on to purchase.

How to upgrade

If you're on Nexo version 3.2 or higher, go to Settings → Features → Kitchen Display and select "Enable KDS 2.0". It's a toggle. Your existing ticket layout, station assignments, and item tags all carry over automatically. There's nothing to reconfigure.

If you're on an older version, the in-app update prompt will guide you through the upgrade first, it takes under 5 minutes and doesn't require any downtime.

If you're setting up KDS for the first time, the onboarding flow walks you through station setup and item tagging before you go live. Budget about 20 minutes to do it properly.

What's coming next

  • Voice-to-ticket: Server calls the order aloud; it goes straight to the kitchen display. Still in testing with pilot restaurants in Cape Town.
  • Multi-language support for kitchen staff: Display items in the kitchen's preferred language while front-of-house sees English. Zulu, Afrikaans, and Portuguese in the first release.
  • Prep time estimator: Learns from your average service times and gives front-of-house a realistic "ready in X minutes" for each ticket. More useful than a generic estimate.

This update came directly from feedback from restaurants in Cape Town, Joburg, and Durban. If you're using the KDS and have something to say, good or bad, we want to hear it. Reply to any of our product emails, or drop us a WhatsApp. We read them.

Book a demo to see KDS 2.0 in action

We'll walk you through the full setup and show you how routing, urgency tiers, and floor plan integration work in a live environment.

Book a demo →