How to Price Catering Jobs (With Examples) (2026)
Quoting a catering job on gut feel is how you end up working a Saturday for nothing. Pricing catering, line by line, with two costed examples.
What a KDS does, paper versus screen, order routing by station, costs and a rollout plan
Short answer: a KDS (kitchen display system) is a screen that replaces paper tickets in the kitchen. Every order, from the counter, the dining room, your website or a QR table, lands on it instantly, routed to the right station, timed and colour-coded as it ages. Kitchens that switch from paper typically report 50–70% fewer order errors and 20–35% faster ticket times, and because modern KDS software runs on ordinary tablets, the cost case now works for independents, not just chains. Here is what it actually does, the honest numbers, and how to introduce one without the kitchen staging a rebellion.

It is 7:40pm. The printer chatters out ticket forty-one while thirty-eight is still lost under a garnish tray. The pass has tickets in the order they printed, not the order they are needed. An online order arrives with a modifier the printer truncated. Someone re-fires table twelve because nobody could read whether it said “no dairy” or “extra dairy”. None of these are people failing; they are paper failing. A rail of thermal tickets cannot re-sort itself, cannot show elapsed time, cannot merge three order channels, and cannot tell a cook what changed after it printed.
| Paper tickets | KDS | |
|---|---|---|
| Order errors | Misreads, lost tickets, stale rails | Typically 50–70% fewer errors |
| Ticket speed | Manual sorting and delivery | Typically 20–35% faster turnaround |
| Multi-channel orders | Collide at one printer | Merged into one sequenced queue |
| Changes after firing | Reprint and hope | Update appears instantly |
| Priority visibility | Whoever shouts loudest | Colour-coded ageing, timers |
| Data afterwards | None | Ticket times by station, hour, dish |
| Failure mode | Printer jam, no paper | Screen or network outage (rare, recoverable) |
| Best for | Tiny single-station kitchens | Any kitchen with multiple channels or stations |
Take a kitchen averaging 14-minute tickets at peak. A typical post-KDS improvement lands that at 10–11 minutes. The dining room feels it immediately: courses land sooner, tables clear sooner, and at busy times that is roughly one extra seated party per hour, which flows straight into table turnover. The error side pays too: kitchens waste 4–10% of food overall, and remakes from misread tickets are the most avoidable slice. Cut errors by half or more and both the food-cost line and the 9pm stress level improve together.
A guest orders, at the counter, from a server, from your website, or by scanning a QR code at the table. The order hits the system once and fans out: the full ticket to the expo screen, each item to its station screen. Cooks see their queue in priority order with timers running. As items finish, they are bumped; the expo screen assembles the ticket and marks it complete. Front of house sees status without walking to the pass. Nothing is transcribed, so nothing is mis-transcribed.
The old model was proprietary screens, controllers and an installer. The current model is software on ordinary hardware: a consumer tablet or a cheap HDMI screen per station, running KDS software bundled with your POS or platform. For a small kitchen that means the real cost is one or two tablets plus a subscription you may already pay, which moves the question from “can we afford a KDS” to “can we afford Friday-night remakes”.
Kitchens are rightly sceptical of new screens mid-service. The rollout that works: start in a quiet daypart with the KDS running alongside the printer for a week, let the most senior cook own the configuration (station mapping, course grouping, alert thresholds), and only cut the paper once the crew asks for it, which they usually do the first time an online rush merges cleanly instead of burying the printer. Keep a fallback: if the network drops, the POS can still print, so the worst case is Tuesday-as-usual, not chaos.
What is a KDS in a restaurant?
A KDS (kitchen display system) is a screen in the kitchen that replaces paper tickets and printers. Orders from the POS, your online ordering and QR tables land on it instantly, are routed to the right station, timed, colour-coded as they age, and cleared with a tap when done. It is the difference between a rail of curling paper and a live queue the whole kitchen can read.
Is a KDS better than printed tickets?
For most kitchens, clearly yes. Operators switching from paper to a KDS typically report 50–70% fewer order errors and 20–35% faster ticket times, because nothing is misread, lost, or stuck on a rail out of sequence. Paper still suits very small, single-station kitchens with a short menu, simplicity has value, but once orders arrive from more than one channel, paper becomes the bottleneck.
How much faster does a KDS make a kitchen?
Reported gains cluster around 20–35% on ticket turnaround. The practical translation: if your average ticket falls from 14 minutes to 11, a full dining room can seat roughly one extra party per hour at peak, which compounds straight into table turnover and revenue. The speed comes less from cooks moving faster and more from zero time lost to sorting, re-reading and firing mistakes.
Does a KDS reduce food waste?
Yes, through error reduction. Kitchens typically waste 4–10% of food, and a meaningful slice of that is remakes: misread tickets, missed modifiers, dishes fired twice. Cutting order errors 50–70% removes most remake waste, which is why a KDS shows up in the food-cost line as well as the speed numbers.
What does a KDS cost?
Far less than it used to. Legacy systems meant proprietary hardware and installation; modern KDS software runs on ordinary tablets or screens, priced as part of your POS or platform subscription. For an independent, the realistic all-in cost is a consumer tablet or two plus software you may already have, which is why the ROI case now works for small kitchens, not just chains.
Do I need a KDS if I only do dine-in?
It helps most when orders arrive from several channels at once (dine-in, online, QR tables, delivery), because a KDS merges them into one sequenced queue. Pure dine-in with one printer can survive on paper longer. But the moment you add online ordering, the kitchen needs one source of truth, or the printer becomes the place where channels collide.
Storefront, orders, kitchen, CRM and marketing in one place. Start free in a couple of minutes, no card needed. Pop in your email and we'll take you straight to setup.
Storefront, POS, kitchen, CRM, marketing. One login, one bill. NZ$1/month for the first 3 months.
Start free trial