POS vs KDS — what's the difference, and do you need both?
If you've shopped for restaurant software in the last five years, you've seen two acronyms used interchangeably: POS and KDS. They are not the same product. They are not interchangeable. And the restaurants that grow fastest are the ones that use both — for two completely different jobs.
The 10-second version
POS = Point of Sale. The screen at the counter where orders are taken and money changes hands. Cashier-facing.
KDS = Kitchen Display System. The screen in the kitchen where tickets appear so the line knows what to cook. Chef-facing.
What each one does best
POS (counter)
- Take orders from walk-ups
- Calculate change, accept payment
- Print a receipt and a token
- Apply vouchers and discounts
- Refund a sale
KDS (kitchen)
- Show live tickets in arrival order
- Route items to the right station
- Mark items ready / cancel with reason
- Time tickets so the chef sees age
- Send "ready" ping to the waiter / status screen
Why a POS alone is a bottleneck
The classic mistake: print the order on a slip, hand it to the kitchen, kitchen makes it, waiter runs it. The order is now a physical object moving through space. When you scale to 40 covers, the slip becomes illegible. The runner becomes the bottleneck. The waiter's "tables" become a stack of paper.
A KDS replaces the slip with a live screen. The chef taps "ready" instead of writing "✓" and the waiter gets a ping instead of a shout. Time saved per order: 30–90 seconds. Across 200 covers, that's 1.5–5 hours of floor time back per shift.
Why a KDS alone doesn't work either
The other classic mistake: a QR menu with no POS. Guests can order from the phone, but the cashier has nowhere to take a cash walk-up, and there's no record of what was sold until you reconcile the payment gateway at midnight. Split bills, refunds, and voids are unworkable.
What to look for in each
For a POS: touch-friendly, fast numpad, partial payment, support for the gateway you already use, and thermal printer compatibility.
For a KDS: sound alert on new ticket, age timer (turns red at 10 min), item-level actions, station routing, and ideally a "bump bar" if you're going to use a physical button instead of a touch screen.
Bottom line: a POS is where you sell things. A KDS is where you make them. You need both, and they should be the same platform — otherwise the order, the payment and the kitchen view are three different versions of the truth.