POS for Restaurants in Kenya : Prices & Features

A POS for restaurants in Kenya exists because a kitchen and a checkout are two different worlds that must agree to the shilling every night. One customer orders half chicken with ugali and no chilli, the bar pulls two sodas, and the bill is split three ways because nobody carries cash on a Friday. A supermarket till cannot follow any of that.

A restaurant system exists to carry the order from table to kitchen to bill without a handwritten docket getting lost — or getting “lost”. That single sentence is the whole buying brief. If a machine cannot do that, nothing else it promises matters much.

The problem with shopping under pressure is that fear makes buyers lazy. A dealer says the magic words “it works for any business”, the owner nods, and a retail till gets bolted onto a restaurant where the products are table numbers and the stock is bottles in a fridge. A serious POS for restaurants in Kenya is built around orders, tables and split bills — not around a cash drawer with a screen.

Three months later the waiters are writing dockets in duplicate, the kitchen is shouting across the pass, and the bar stock never matches the sales. Nobody can tell which waiter’s tables under-report every night. This guide shows you exactly where a real system differs — in the demo, in the costs, in the Friday-night rush and in the renewal price.

The tests are identical whether you run a nyama choma joint in Langata, a café in Nakuru, a family restaurant in Kisumu or a busy lunch spot feeding offices in the CBD. Every vendor — boutique developer, national brand, or the POS for restaurants in Kenya reseller visiting Westlands with a bundle — should face the same scorecard before a shilling changes hands. The vendor who welcomes the test is the one worth hiring.

This article walks through what a proper system must prove on day one, what it costs per month in Kenyan shillings, and the ten questions that separate genuine restaurant systems from repackaged tills. Whether you are quoted by a POS for restaurants in Kenya specialist, a general POS for restaurants in Kenya platform provider, or a dealer attaching POS for restaurants in Kenya hardware leases to a software contract, the same tests apply. By the end, you will know how to enter a demo and leave with evidence rather than promises.

Why a Shop Till Is Not a POS for Restaurants in Kenya

A shop till records transactions; a restaurant runs operations. In a shop, the product walks to the counter; in a restaurant, the order walks to the table, changes in the kitchen, grows with another round, and becomes a bill that three people insist on splitting.

A till has no table map, no kitchen ticket, no way to hold a bill open for an hour, and no way to split anything. When owners force a retail till into a restaurant, waiters keep paper dockets as the real system and type totals at the till. The till becomes decorative — and the paper docket is where both honest errors and quiet theft live.

No add-on turns a retail till into a POS for restaurants in Kenya. Orders, tables and split bills have to be built into the core, because they touch every sale, every hour, every day. Anything bolted on later arrives late and leaves early.

A genuine POS for restaurants in Kenya carries one order through its whole life: taken at the table, sent to the right kitchen or bar ticket, modified without a shout, grown with another round, printed as one bill, split as many bills, and closed into the day’s numbers. It knows a crate holds twenty-four sodas and each sale draws down a bottle. It also knows the bill for table 7 has been open for fifty minutes and should probably be checked on.

And it remembers who served which table, because accountability at the pass is where restaurant money is won or lost. A till tells you the day’s takings; a real system tells you which dishes sell and which waste prep, which hours carry the business, which waiter’s sales dip every Tuesday, and how long tables take from order to payment.

Every dealer in the market — from POS for restaurants in Kenya specialists who understand service to regional teams selling a POS for restaurants in Kenya package at trade days — will promise all of this. The demo is where the promise meets a busy table. The sections below give you the exact tests to run.

From Table to Kitchen: How Orders Should Flow

The heart of a restaurant system is the order journey, and you should walk it in every demo. The waiter opens table 7, adds two half chickens — one with no chilli — three sodas and a chapati, and sends the order. The kitchen ticket should print at the kitchen station with the food; the bar ticket prints separately with the sodas, because your kitchen does not need to know about drinks.

A capable POS for restaurants in Kenya does this routing automatically, with modifiers that follow the item onto the ticket rather than living in the waiter’s memory. Ask the vendor to demonstrate a modifier live — “no onions, extra avocado” — and watch where it appears. It should be on the ticket and on the bill, not nowhere.

Bills are the second half of the journey, and Kenyan tables will test them hard. One table, five friends, three paying by M-Pesa, one by cash, one by card; another table that arrived as six and pays as two groups; a table that moves and must carry its bill along. This is a normal Friday, not an edge case.

A capable POS for restaurants in Kenya splits any open bill by items or by amount, takes each part in a different payment method, and closes the table cleanly into the day’s report. Ask to see a three-way split with mixed payments in the demo. The systems that fake it fall apart the moment one part is cash and another is M-Pesa.

Menu structure is the quiet third piece. Your menu is not a price list; it is a family of items with sizes, sides and choices — half or full, ugali or rice or chapati, plain or with sukuma. A capable POS for restaurants in Kenya builds those variants once, prices them properly, and reports on them separately, so you can see that the full chicken with rice is your profit and the sides are your traffic.

Daily specials, happy-hour pricing and seasonal changes should be manageable by a manager in minutes. A POS for restaurants in Kenya menu that requires the vendor to visit every time you add a special is a subscription to dependence, not software. Ask who can change prices and how long it takes.

What a POS for Restaurants in Kenya Should Do on Day One

Ignore brochures for an hour and judge every candidate by five concrete tests, run on their own demo kit with a sample of your real menu loaded. A serious POS for restaurants in Kenya provider will welcome the exercise; a repackaged till will start negotiating around it.

• Take an order at a table and watch the routing: food to the kitchen ticket, drinks to the bar ticket, each with the right items and nothing extra.
• Send a modifier — “no chilli, extra chapati” — and confirm it prints on the ticket and appears on the bill.
• Split a table’s bill three ways and pay each part differently — cash, M-Pesa, card — then close the table into the day’s report without a residue.
• Void an item after its ticket reached the kitchen, using a manager PIN, and show where the void is logged with a user and a time.
• Unplug the router and keep serving — order, ticket, bill — then reconnect and produce the day-end report with sales per waiter and per hour.

Notice that none of these tests is exotic — they are simply a normal Friday night. The split-bill test and the offline test are where candidates fail most often, because neither can be faked with a screenshot. Run both twice if the vendor seems nervous: a POS for restaurants in Kenya that passes twice is real, and a POS for restaurants in Kenya that stalls twice has told you everything you need to know before price is even discussed.

Taking Payments: Cash, M-Pesa, Cards and Split Bills

Restaurant counters take money in every form Kenya uses, and the system must record all of them on one bill. Cash dominates the lunch trade, M-Pesa carries the evening, cards appear when corporate clients dine — and the same table often mixes all three. A capable POS for restaurants in Kenya takes a KES 4,850 bill as KES 1,000 cash, KES 2,850 M-Pesa and KES 1,000 card in one closure, and the day-end report reconciles drawer, phone and card batch to the shilling.

Pay-at-table versus pay-at-counter should both work. The waiter settles at the table during dinner service; the lunch crowd pays at the till on the way out. The system should not care which direction the money came from.

M-Pesa deserves its own scrutiny because it is where restaurant books quietly drift. The money lands on the phone, the bill closed at the table, and by Sunday night the two numbers disagree by an amount nobody can explain. Ask every vendor how their POS for restaurants in Kenya closes that gap.

The strong answers include STK push triggered from the bill so the payment attaches to that table automatically, an automatic or one-click match against the M-Pesa statement at day end, and a loud flag for any closed bill without a matching payment. Weak answers — “the waiter just marks it paid” — are how both revenue and bottles disappear in the same evening. There is no middle ground worth buying.

Service charge, tips and staff meals deserve explicit rules in the system rather than counter habits. A service charge should be a visible line the system applies and reports; tips should be recordable without polluting the VAT numbers; staff meals should be a controlled transaction with a manager PIN, not a free-for-all at 10pm.

None of this is glamorous, but the POS for restaurants in Kenya that handles it cleanly is the same one whose end-of-day numbers need no forensic reconstruction. The POS for restaurants in Kenya reports should show the difference between a busy night and a profitable one — precisely the distinction most restaurants cannot currently make.

Selling Through Power Cuts and Friday-Night Rushes

Every restaurateur knows the pattern: the lights flicker, the router dies, the dining room is full, and the kitchen keeps cooking while the bills stop coming out. Service, stock records and compliance all collapse together at that moment. A POS for restaurants in Kenya worth buying is built for that evening.

Ordering must continue fully offline: waiters take orders, tickets print at the kitchen and bar, bills open, close and split. The invoices generated during the blackout should queue automatically and transmit when connectivity returns, with a screen showing exactly what is waiting. During the demo, unplug the router yourself — the router test — and watch what happens to the third order in the queue, especially one that gets modified while offline.

Power is the twin problem; heat and grease are the quiet ones. A small UPS keeps the counter terminal and printers alive through short outages, and kitchen printers live hard lives next to hot passes — ask the vendor which models they actually install there.

Speed under pressure is part of the same test. Ask how many touches it takes a waiter to send a four-item order, because at 1pm on payday, eight touches per order is the difference between two table turns and one. A capable POS for restaurants in Kenya is measured in seconds per action, not in feature lists, and the demo should feel like the rush rather than a slideshow.

Be equally direct about what happens after reconnection. The rules on how quickly invoices must reach KRA, and what is acceptable during an outage, are exactly the kind of detail to confirm with KRA or your accountant rather than trusting a sales pitch. What you can demand from the POS for restaurants in Kenya itself is transparency: a visible queue, timestamps, automatic retry, and an alert when something has sat unsent too long.

The POS for restaurants in Kenya installations that age well are the ones where the manager can see the transmission status at a glance. Invisible queues are how invoices quietly die and how a full house becomes a complicated audit. Demand the screen before you demand the discount.

What a POS for Restaurants in Kenya Costs per Month

Let us talk shillings. The Kenyan market clusters into three honest tiers. Entry-level systems run roughly KES 500 to KES 3,000 per month and will take orders and print bills — workable for a tiny kibanda with one counter, but you will feel the ceiling the moment you ask for table management, waiter accountability or bar integration.

Mid-market systems, where most serious restaurants land, run about KES 3,000 to KES 7,000 per month and add table maps, split bills, kitchen routing, staff permissions and dependable support. Platform-grade systems charge roughly KES 7,000 to KES 15,000 per month and carry multiple outlets, central menu control, consolidated reporting across branches, and integrations worth having at scale.

Hardware is the separate, one-off conversation, and restaurants need more of it than shops: a counter terminal, a cash drawer, a printer for customer bills, and at least one more printer for the kitchen — plus the bar if you want true separation. That pushes a working setup between KES 60,000 and KES 120,000 depending on screens and stations. Add up to KES 30,000–40,000 for setup, menu building and training, and be suspicious of quotes that pretend this work is free, because menu entry done badly is the most common reason new systems stall on day one.

When comparing any POS for restaurants in Kenya quote, force it into the same shape: software per month, hardware once-off, setup once-off, and support terms in writing. Three cost traps deserve your paranoia. The first is the year-two price: some vendors discount year one and recover it later, so ask what the identical package costs in month thirteen and get it in writing — a POS for restaurants in Kenya contract is a relationship, and renewal surprises are the leading cause of bitter switching.

The second trap is the “free” system that charges per terminal or per waiter; a floor with six waiters and two terminals must do that arithmetic against the flat option. The third is support billing: ask whether the monthly fee includes support calls, updates and menu changes, or whether each one is invoiced. The POS for restaurants in Kenya vendors who answer all three without flinching are usually the ones whose other promises hold; the POS for restaurants in Kenya quotes that hide behind “it depends” deserve to wait until numbers appear on paper.

Waiter Permissions and Bill Discipline

Money leaves a restaurant quietly: through orders taken and never rung, items voided after payment, “complimentary” rounds that were never authorised, and bills that close lower than the kitchen prepared. The POS for restaurants in Kenya you choose should make each of those exits structurally harder. Start with named user accounts — no shared login that eight waiters know — and role-based permissions: waiters take orders and print bills; supervisors approve voids, discounts and complimentary items; only you touch menu prices, recipes and user accounts.

Every sensitive action needs a manager PIN at the moment it happens, and every void should carry a reason. A void log is the most honest document in any restaurant. Read it weekly and you will rarely need a detective.

Waiter accountability is the daily discipline that turns permissions into performance. The system should attribute every order, bill and payment to a named waiter, so the day-end report shows sales per server — and the manager can see whose tables under-report, whose voids spike, and whose customers wait longest. Ask each vendor to show you a void log and a sales-by-waiter report in the demo; a POS for restaurants in Kenya that cannot answer “who removed that KES 3,500 round last Friday” is only pretending to protect you.

Bills need the same rigour. A bill that is reopened after closure, discounted after payment, or transferred between tables without a record is a classic hole that both staff and regulars find within weeks. The audit trail should survive deletion attempts, because the point of a record is that it cannot be quietly unrecorded.

Every price change, discount, void and late-night correction should be stamped with a user and a time. When you call references, ask the awkward question directly: has this POS for restaurants in Kenya ever helped you catch or resolve a staff issue? Owners who have lived through it will name the exact report they pulled; owners whose systems were never tested will hum.

Reports That Run a Kitchen, Not Just a Counter

The reports that matter split into two families: the ones KRA and your accountant need, and the ones that run a kitchen. On the compliance side you should be able to pull, in minutes: total sales per day and month, VAT collected where applicable, the invoice register with confirmations, all credit notes, and an export your accountant opens in Excel without a ceremony. A capable POS for restaurants in Kenya produces these as standard, not as a paid add-on.

The figures must match what was actually transmitted. Reconciliation between your reports and the KRA side is precisely what you are paying the system to guarantee. Ask to see it demonstrated, not described.

The operations family is where restaurant systems earn their keep. You want sales by hour, so you can see that your business is really a lunch business with a Friday bonus; sales by item, so you know which dishes pay and which occupy menu space; sales by waiter, which is both an accountability tool and a training map; and void and discount trends that surface problems before they become culture. Ask the vendor to demo a POS for restaurants in Kenya report you did not request — good systems have depth that shows up in unexpected corners.

If you take stock seriously, ask about portions and recipes. A crate of sodas should draw down bottle by bottle; a kilo of flour becomes a countable number of chapatis; a bottle of oil serves a knowable number of plates. Not every restaurant wants recipe-level control on day one, but the POS for restaurants in Kenya you choose should at least support it as you grow, and the vendor should show it rather than promise it.

Then run the accountant test: export a month of demo data to Excel and hand it over with one question — can you work with this? If the sigh is audible, believe the sigh, whatever the brochure promises about the POS for restaurants in Kenya dashboards. Accountants see every system’s worst day, the month-end scramble, and they do not flatter.

Hardware Checklist for a POS for Restaurants in Kenya

Restaurants need more hardware than shops, and the extra pieces are not optional. The working core: a counter terminal with a real operating system — a decent touchscreen or laptop; sealed calculator-style boxes cannot be updated — a cash drawer, a thermal printer for customer bills, and at least one kitchen printer, ideally two so the kitchen and bar print separately. Kitchen printers live hard lives next to heat and steam, so ask the vendor which models they actually install behind a pass and how they protect them.

Budget KES 60,000 to KES 120,000 for a working setup of this quality, less if you can reuse a serviceable laptop. Treat that figure as the floor for a serious floor, not the ceiling of ambition.

Additions depend on your layout: waiter handhelds or tablets that send orders from the table, a kitchen display screen that cannot run out of paper mid-rush, a 4G failover router that keeps the POS for restaurants in Kenya transmitting when the fibre dies, and a buzzer or order-number display for a counter-service café. Each earns its place in speed, not in glamour. Each should also be priced as a separate line, because bundles hide bad arithmetic.

Two hardware questions belong in every negotiation. First, ownership: confirm in writing that the hardware is yours outright once paid, and that the POS for restaurants in Kenya software will run on it even if you later change software providers. Vendors who lock hardware to software are selling a trap with a receipt.

Second, serviceability: ask the turnaround on a dead kitchen printer at 8pm on a Saturday, whether loaner units exist, and which spares sit in local stock. The POS for restaurants in Kenya installations that survive year one are the ones where hardware failure means a swap, not a handwritten evening. Then ask what the dealer runs in their own offices — the POS for restaurants in Kenya hardware a vendor actually uses daily tells you more than any datasheet.

Delivery Apps, Riders and Your Own Kitchen

Delivery is now part of the Kenyan restaurant business whether you planned for it or not. Glovo, Bolt Food and Uber Eats bring orders through tablets and phones that live beside your counter, and every one of those orders must still become food, a receipt and clean numbers. A capable POS for restaurants in Kenya either integrates with the aggregators directly, pulling their orders into the same kitchen flow as your tables, or at minimum provides a fast manual channel.

That manual channel is a delivery-order button that prints a kitchen ticket exactly like a table order, so the kitchen never runs two systems during one rush. Ask each vendor to demonstrate an aggregator order arriving live. “We support delivery” and “delivery orders print like table orders” are two different promises, and only one of them helps your kitchen.

Reconciliation is where delivery money leaks. Each platform remits on its own schedule, minus commission, and the amounts rarely match the gross order values; without a system view, the books show sales you never banked.

The strong answer is a report that separates dine-in, own-delivery and aggregator sales, and lets you record platform commissions so profitability is visible per channel. Ask to see that report in the demo. A POS for restaurants in Kenya that treats every shilling as identical will leave you guessing which channel actually pays.

Your own riders deserve the same structure if you deliver directly. Orders should carry the customer’s location and phone, the rider should be attached to the order, and the day’s deliveries should reconcile with the cash and M-Pesa they bring back — the same discipline as a table bill, just on a motorbike.

Keep the compliance question honest: whether you need the platform’s invoice, your own, or both for a given order is exactly the kind of detail to confirm with KRA or your accountant, because aggregator paperwork and eTIMS rules are still settling. A capable POS for restaurants in Kenya keeps your own documents clean regardless of which channel the order arrived through. The POS for restaurants in Kenya that cannot separate channels will blend them into fog precisely when you need clarity.

Compliance: County Health Rules and eTIMS

A POS does not replace your licences, and any vendor who implies otherwise is selling you something. A restaurant operates under county single business permits, food handling and hygiene requirements, and public health inspections — those are confirmed with your county office and public health team, not with a software dealer. What the right system does is make the business’s records clean enough that an inspection or renewal is routine.

Clean records mean purchase records showing where stock came from, sales records showing what was served, and staff accountability showing who did what. Treat the POS for restaurants in Kenya as the record-keeper of a compliant business, nothing more. The permits live at the county office, not in the software.

On the tax side, KRA’s eTIMS regime now shapes what a counter system must do, and the details of who must onboard and through which mode keep evolving — so confirm your exact position with KRA or your accountant. The buyer’s test, however, stays simple and non-negotiable.

The vendor must demonstrate a live invoice reaching KRA from the demo machine, must show a credit note being issued through the same pipeline, and must handle the VAT treatment of meals and service charges the way your accountant directs. A POS for restaurants in Kenya that cannot pass those demonstrations in the room is not ready for your counter, whatever the brochure says.

There is also a quieter compliance dividend worth naming. When every order, void and payment is stamped and stored, the questions that used to need reconstruction become printouts: what was sold on the night of the fifteenth, who closed that bill, why is this refund here. The POS for restaurants in Kenya installations that weather audits and disputes calmly are the ones whose owners could produce the record in minutes — not because they anticipated trouble, but because the record was simply how the restaurant already ran.

Questions to Ask Before You Pay Any Deposit for a POS for Restaurants in Kenya

Print this list and carry it into every meeting. Score each vendor out of ten as you go; the arithmetic at the end is usually decisive. Any POS for restaurants in Kenya seller who resents being audited by the buyer has answered your real question already.

1. Walk me through one order from table to kitchen ticket to bill — live, including a modifier like “no chilli, extra chapati”.
2. Show me a bill split three ways, paid in cash, M-Pesa and card, closing cleanly on one table.
3. What happens when the internet dies at 1pm on a Saturday — where is the order queue and how do I watch it clear?
4. Show me a void after the ticket reached the kitchen — who approves it, and where is it logged?
5. What exactly does the monthly fee include, and what is billed separately — support, updates, extra waiters, extra terminals, menu changes?
6. What will this identical package cost in month thirteen? Put the renewal price on the quote itself.
7. How long from deposit to first service, and who builds my menu and table map — your team or mine?
8. Can orders from Glovo, Bolt Food and Uber Eats reach the same kitchen ticket as table orders, and how are commissions reconciled?
9. Which three restaurants like mine run on your system today, and may I call two of them this week?
10. What is the total first-year cost — software, hardware, setup, training and support — as one written figure?

Notice how many answers must land on paper rather than in the air. A POS for restaurants in Kenya vendor who completes this scorecard in one meeting, with numbers and names, has earned serious consideration; one who needs to “check with the office” on more than three items has told you how the next three years will feel. When the scores come back close, weight the kitchen-routing demo, the split-bill test and the reference calls heaviest — those three are the hardest to fake and the most expensive to get wrong, whichever POS for restaurants in Kenya you finally choose.

And like the renewal answer from question six, the data-exit terms from question eight belong on the contract itself. A POS for restaurants in Kenya promise that never reached the signature page never happened. That single rule will save you from more bad deals than any feature comparison.

Common Restaurant POS Mistakes and How to Avoid Them

The most expensive mistake in this market is buying on fear from the first salesperson who knocked — and the most common version of it in this trade is accepting a demo that never touches a table, a kitchen ticket or a split bill. A system that cannot route an order and split a payment can never recover, because that is the restaurant. Give every POS for restaurants in Kenya candidate the same five day-one tests in this guide, even when the landlord and the licensing renewal are both pressing; a genuine vendor compresses timelines, a fake one compresses diligence.

The second cluster of mistakes happens after the purchase. Only one person gets trained, so the system dies with every sick day and resignation; voids and complimentary items become habits instead of logged exceptions; the paper docket survives in a drawer as the real system, so the shop pays for two systems and trusts neither.

Every one of these is a habit failure, not a software failure, and every one is avoidable with a two-week parallel run done honestly: new system as the only record, old totals as a cross-check, daily reconciliation of bills, cash, M-Pesa and card batches. Owners who treat the first month after installing a POS for restaurants in Kenya as a learning period reach effortless service by month two. Owners who switch everything off on day one inherit the old chaos in a new interface.

The third mistake is treating the purchase as a receipt machine instead of a steering wheel. An invoice that satisfies the taxman but teaches you nothing about your kitchen is half a system. The restaurants that pull ahead read the same data differently: which dishes pay and which waste prep, which hours deserve the extra waiter, which channel — dine-in, delivery, aggregator — actually banks money after commissions.

Ask your references one more question with this in mind: what decision did this system change for you last quarter? Owners of a POS for restaurants in Kenya installation that merely prints bills answer vaguely; owners whose system is a steering wheel answer with numbers. The POS for restaurants in Kenya deployments they describe are the ones worth chasing.

Getting Started Without Stopping Service

A sensible migration follows a rhythm any restaurant can keep. Week one: choose the vendor, sign with the renewal price and data-exit terms attached, and hand over your menu, prices and floor plan — that is all the raw material the setup team needs. Week two: the vendor builds your menu, variants and table map while you keep serving as usual; you approve the quick-key layout and sample tickets rather than doing the typing.

Week three: hardware goes in midday between services, not mid-rush; staff train against test tables; and go-live is set for a Monday or Tuesday, never a Friday. From deposit to a confident floor, most single-outlet restaurants need two to four weeks. A POS for restaurants in Kenya provider who can put that calendar in writing probably has the installations to show for it.

The first fortnight after go-live decides everything. Run the new system as the only record, but keep your old daily totals as a parallel check; reconcile bills, cash, M-Pesa, card batches and bar stock every night after close; put the void flow and the complimentary-item flow on the wall in plain language. Review the first month-end with your accountant in the room — not to fix problems, but to confirm there are none and to catch the small habits that are cheap in week three and expensive in year three.

A POS for restaurants in Kenya launch handled this way becomes boring very quickly, which is the highest compliment a service system can earn. Boring means the bills print, the numbers tie, and the kitchen never asks twice. Aim for boring.

Then turn from defence to offence. At the ninety-day mark, sit down with the reports and ask the questions the docket era could never answer: which dishes carry the margin, which hours deserve staffing, what did voids really cost last month, and which delivery channel actually banks money after commissions. Take the answers into your next menu change and your next roster.

That is the real return on this whole exercise — not merely a receipt the taxman accepts, but a restaurant you can finally see clearly, steered by a POS for restaurants in Kenya that pays its own way. Start the way every good installation starts: with the five day-one tests, a printed scorecard, and the willingness to walk away from any POS for restaurants in Kenya vendor who cannot pass what any serious owner should demand. The market has enough genuine options — including POS for restaurants in Kenya providers and the others named throughout this guide — that nobody needs to gamble on the first pitch that walks through the door.

Frequently Asked Questions

Is a POS for restaurants in Kenya different from a shop POS? Yes, and the difference is structural. A restaurant system manages tables, sends orders to kitchen and bar tickets, holds bills open, splits them across friends, and attributes every action to a named waiter — none of which exists in a retail till. If a vendor cannot demonstrate table-to-kitchen routing and a three-way split bill during the demo, they are selling you a shop till with a new sticker.

Do waiters need their own devices? Not on day one, but they help. A handheld or tablet lets a waiter send orders from the table, which shortens ticket times and removes the counter queue at lunch. Price handhelds as separate line items, confirm battery life for a full shift, and make sure offline ordering works on the handheld exactly as it does at the counter.

What happens when power or internet fails during service? A well-built system keeps serving fully offline — orders, kitchen tickets, bills and splits — then queues the invoices for transmission when connectivity returns, with a visible screen showing what is waiting. A small UPS keeps the counter and printers alive through short outages. Run the router test in every demo: unplug, take three orders, reconnect, and watch the queue clear.

How much should I budget every month? Most single-outlet restaurants land in the mid-market tier of roughly KES 3,000 to KES 7,000 per month, with hardware as a one-off of KES 60,000 to KES 120,000 — restaurants need kitchen and bar printers in addition to the counter — and setup up to KES 30,000–40,000 for a deep menu. Whatever tier you choose, get the year-two renewal price in writing before signing.

Can it handle Glovo, Bolt Food and Uber Eats orders? Either directly or through a disciplined manual channel — both can work, but they are different promises. Direct integration pulls aggregator orders into the same kitchen flow as tables; a good manual flow prints a delivery ticket identical to a table ticket. Insist on channel reporting: dine-in, own delivery and aggregator sales shown separately, with commissions recorded.

Can it split a bill across five people? It must, because Kenyan tables will ask for it every weekend. The split should work by items or by amount, each part payable in a different method — cash, M-Pesa, card — and the table should close cleanly into the day’s report with no residue. This is one of the five day-one tests in this guide, and it is where weaker systems fall apart fastest.

Can it track the bar separately from the kitchen? Yes, and it should. Drinks print at the bar ticket, food at the kitchen ticket, and stock draws down separately — bottles by unit from the crate. Ask the vendor to demonstrate bar-to-kitchen routing and a bar stock report in the demo; if drinks and food blur into one ticket stream, service slows and the fridge becomes a rumour.