01 — Order channels
Map every place an order can start.
Hospitality orders rarely start in one place. Counter, table, self-service kiosk, phone, web, marketplace apps (Uber Eats, Just Eat, Deliveroo) — each one is a different door into the same kitchen. The first decision is not “which channel” but “does every channel land in one place we can act on?”
- List every channel that already takes an order today, including the ones staff handle informally (a phone written on a notepad still counts).
- For each channel, write down: who captures the order, where it appears, and how it reaches the kitchen.
- Flag any channel where the order has to be retyped into a second system. Those are the leaks.
- Aim for one Order Hub: every channel funnels into the same list, with the source visible.
Counter, table, kiosk, phone, web and delivery-app orders all land in the same record. Kitchen routing reads from one source — no re-keying, no parallel queues.
per order, every channel
- Order Hub — the single record every channel writes to.
- KDS — routes items to the right prep station by product and service type.
- Reporting — channel mix and sales visible while the day is live.
02 — Counter & kiosk
Design POS and kiosk flows for the queue, not for a demo.
A POS or self-service kiosk wins or loses on the journey from “next customer” to “next customer.” Staff should be able to search, modify and take payment without leaving the basket. Kiosks should let a guest order, customise and pay without ever needing staff to intervene.
- Build categories around how guests actually order, not how the menu is printed.
- Make modifiers obvious — meat doneness, milk choice, allergens — so staff are not guessing.
- Keep refunds, voids and reprints one tap away; auditing them is a separate problem.
- For kiosks: short navigation depth, clear payment status, and a fallback to staff when needed.
03 — Table service
Make table service follow the floor plan.
If your venue has tables, the POS should know about them. A table layout that mirrors the room means staff stop hunting for tickets and start running covers. Pay-at-table and QR ordering only work when they share the same table state as the floor staff’s handheld.
- Build a table layout that matches the real room, not an idealised one.
- Decide how courses are timed — manual fire, auto fire after main, or station-driven.
- For QR table ordering: keep the same modifiers and pricing as the counter.
- Tip and split-bill rules should be set once, centrally, not improvised on the floor.
04 — Kitchen Display
Route work to the right station, not to the wall.
A Kitchen Display System (KDS) earns its keep when it routes the right item to the right station based on product, service type and time. A grill order does not belong on the drinks screen. A delivery order needs a different timing than a dine-in main.
- Define your stations first: grill, fry, drinks, assembly, QC, dispatch. Then map products to them.
- Use service type (dine-in, takeaway, delivery, collection) to drive priority, not the manager’s instinct.
- Surface late tickets visually — colour, timer, escalation — before they become complaints.
- Bumping an item should update the order state everywhere: floor, dispatch, customer notification.
A burger order should always reach the grill. A delivery order should always carry a delivery timing. The KDS picks the right station and prioritises by service type before the ticket even prints.
- ServiceDine-in · Table 7
- TimingFire on main
Routed by product family
Routed by product family
Plate · dine-in
Fires when all bumped
- Cook stations — grill, fry; routed by product family with prep-time targets.
- Drinks & cold prep — separate queue so cooks aren’t waiting on sodas.
- Dispatch / floor — fires only when all items on the ticket are bumped.
05 — Phone orders
Treat the phone as a real channel.
For many venues, the phone is still the highest-value order source — and the most invisible one. A ringing phone with no caller history means the team is guessing what the customer ordered last time. A missed call with no follow-up is a missed order.
- Tie inbound calls to the customer record where possible, so order history opens automatically.
- Define who answers, who takes the order, and who calls back missed callers.
- Build a missed-call queue with an owner — not a shared inbox no one watches.
- For repeat callers, surface the last order so re-orders take seconds, not minutes.
06 — Delivery apps
Bring delivery-app orders into the same flow.
Uber Eats, Just Eat and Deliveroo each have their own tablet, their own commission and their own quirks. When those tablets stay separate, every busy shift turns into a triage exercise. Pulling those orders into the same KDS and stock model is the lever that makes delivery profitable.
- Decide which apps you want orders to flow through and which menus they get.
- Map app SKUs to your master products so stock movement is correct.
- Set rules for pausing channels when prep capacity is exceeded — automatically if possible.
- Reconcile commission and payout against your own sales record, not just the app’s dashboard.
07 — Menu & stock
Make stock follow the menu.
When a guest orders a burger, your stock model should know that means a bun, a patty, lettuce, sauce and a slice of cheese came out of inventory. Recipes and modifiers connect menu sales to stock usage — and that connection is what makes buying decisions reliable.
- For each menu item, decide whether you track at finished-item level, recipe level, or both.
- Modifiers (extra cheese, oat milk, no onions) should adjust stock and price together.
- Set reorder thresholds based on actual sell-through, not assumed pars.
- Surface stock pressure to the floor — running out of a side mid-service is a service decision, not a stock one.
08 — Payments
Keep card payments tied to the order, not the terminal.
Card readers handle the transaction; the system around them handles the relationship. The payment should be a property of the order — visible to the manager, the kitchen and the reporting view — not a separate event that only the bank knows about.
- Assign readers to terminals so payments are linked to the right counter or table.
- Track refund and settlement state next to the original order.
- For self-service kiosks, surface payment failure to staff immediately.
- Reconcile card and cash totals at shift-end without rebuilding the day from receipts.
09 — Staff & shifts
Sign-in is the spine of accountability.
Without staff sign-in, every report becomes anonymous. Sign-in lets you tie sales, voids, refunds and prep performance to a person — not to blame them, but to coach them and to spot patterns.
- Use staff PINs or cards for sign-in at the POS and KDS.
- Make voids, refunds and discounts require a sign-in trail.
- Run end-of-shift reports per staff member so coaching is concrete.
- Build a hand-off note between shifts so context does not vanish when a manager goes home.
10 — Reporting
Make today’s service inform tomorrow’s service.
Hospitality reporting that arrives at month-end is too late to change anything. The reports that move the needle are the ones the manager reads in the back office during the lull — covers vs forecast, prep times, missed calls, top-selling modifiers — and uses to brief the team for tonight.
- Define the five numbers a manager should see at every shift change.
- Surface variances against forecast or against the same day last week.
- Make stockouts and missed-call counts visible to managers, not just to owners.
- Keep reports drillable to the order, customer or shift behind the number.
11 — Multi-site
Plan group-level visibility from day one.
If you have more than one venue (or plan to), build for it now. Central menu, local stock, group-level reporting and per-site sign-in are decisions that cost very little when set up early — and a great deal of pain to retrofit later.
- Decide which catalogue is central and which can be overridden locally.
- Set stock at branch level; transfers should be a known workflow, not improvised.
- Build group dashboards that compare like-for-like — not just totals.
- Keep sign-in and reporting consistent across venues so people transferring between sites are not re-learning the system.
12 — Rollout
Cut over by service risk, not by calendar.
The fastest way to lose a service day is to swap everything at once. Pilot the new POS at one counter, route one station through the new KDS, take phone orders on the new flow for one shift — and validate before you expand.
- Pick the lowest-risk service first (a quiet Tuesday lunch, not a Saturday night).
- Run the new flow alongside the old one for at least one shift.
- Reconcile cash, card, stock and orders at the end of the pilot — twice.
- Train staff in the actual flow, not from a slide deck.
SUMMARY
The shape of it.
A hospitality operation works when every order — wherever it started — reaches the right station, the right customer record and the right report without anyone retyping anything. Most teams already know which gaps cost them service quality. This guide is a structure for closing them in order.