QR Menus for Restaurants in Kenya: What Works and How to Start

A QR menu sounds simple: print a code, stick it on the table, and guests read the menu on their phones. In practice, many Kenyan restaurants try it once, get complaints, and quietly go back to laminated cards. The idea is not the problem. The setup usually is. This guide covers what a QR menu should do, the mistakes that make guests hate it, and how to roll one out without upsetting your regulars or your waiters.

Three kinds of “QR menu”

People use the same name for three quite different things, and it helps to know which one you want before you pay anyone.

A PDF behind a code. The code opens a scan or PDF of your printed menu. It is cheap, but guests have to pinch and zoom on a small screen, prices go out of date the moment you change the printed version, and nothing tells the kitchen anything.
A live menu page. The code opens a fast web page with categories, prices and short descriptions. You can change a price or hide a dish from your phone in seconds. Guests still order through a waiter.
Order and pay at the table. The guest builds an order on the menu page, sends it straight to the kitchen and bar, and can pay by M-Pesa without waiting for the bill. This is where the real time savings are, but it needs the kitchen side to work too.

Most places should start with a live menu page and move to table ordering once staff are comfortable. Skipping straight from paper to full self-ordering on a busy weekend is how pilots fail.

What guests complain about, and how to avoid it

“It won’t load.” Many guests are on prepaid data with a weak signal indoors. Keep the menu light: small, compressed photos or none at all, no heavy animations, and no app download. The page should open in the phone’s browser in a couple of seconds.
“I can’t read it.” Use large text, strong contrast and one dish per line with the price on the same line. Avoid white text on dark food photos.
“My phone is dead.” Always keep a few printed menus at the counter, and train waiters to offer one without making the guest feel awkward. A QR menu should be an option, not a barrier.
“I ordered something you don’t have.” If the kitchen runs out of tilapia, the dish must disappear from the menu at once. Whoever controls stock needs to be able to switch items off from a phone, not wait for the owner to log in.
“The code doesn’t scan.” Print codes at a decent size, laminate them, and test every table with an older Android phone, not only the newest iPhone.

Getting the menu itself right

A QR menu exposes a messy menu faster than paper does. Before going digital, cut duplicate items, group dishes the way guests think (starters, grills, local dishes, drinks), and write one honest line per dish. State portion sizes where it matters: “nyama choma, 1/2 kg” is clearer than “nyama choma, large”. Show prices including VAT so there are no surprises on the bill, and mark items that take longer to prepare.

Keep the menu link stable. If the code points to a page you control, you can change the menu every day without reprinting a single sticker.

Table ordering: the kitchen side

Letting guests order from the table only helps if the order lands in the right place. If tickets print in the kitchen but nobody sees them, or drinks orders go to the grill, you have added confusion rather than removed it. Before switching on self-ordering, make sure:

food and drink orders are routed to the right station, on a screen or a printer;
each order carries a clear table number and time, so late tickets stand out;
waiters can see what a table has already ordered, so they can still upsell and check on guests;
payments, whether M-Pesa, card or cash, end up on one record you can cash up against at night.

That last point is where many restaurants lose money without noticing. If QR orders, waiter orders and counter sales live in three different places, closing the day becomes guesswork. A till and kitchen display that takes orders from all three channels removes most of that work, and keeps KRA eTIMS invoicing in the same place.

Paying at the table with M-Pesa

Waiting for the bill is one of the most common complaints in busy restaurants. With pay-at-table, the guest sees the total on their phone and pays by M-Pesa, and the payment is matched to that table automatically. Agree a few rules first: how tips are handled, what happens when a group wants to split the bill, and who confirms that a payment has actually arrived before the guest leaves. A screenshot of an M-Pesa message is not proof of payment, so staff should confirm against the system, not the guest’s phone.

A sensible rollout plan

Week 1: put up a live menu page on a few tables, keep paper menus in use, and ask waiters what guests say.
Week 2: fix the complaints, then roll the codes out to every table.
Weeks 3 to 4: switch on table ordering during quieter hours only, with a waiter checking each QR order.
After that: add pay-at-table and extend ordering to peak hours once the kitchen is coping.

Measure what matters to you: time from seating to first order, time waiting for the bill, and how often a dish is ordered after it ran out. If those improve, the system is working.

Where Ananke fits

Our QR menus and table ordering product is being built for Kenyan restaurants: a QR code per table, a light menu that opens in the browser, M-Pesa payment from the table, and items switched off the moment the kitchen runs out. It sits alongside the rest of our hotel and restaurant tools. Demos are open now, take 30 minutes, and you leave with a written quote. If you are not ready for software, our free website check will at least tell you whether guests can find your restaurant and menu online.

Related guides

Want help with this?

Tell us about your business in a few lines. We reply within one working day.

Ananke Digital may reply to me about this. Privacy

Prefer WhatsApp? +254 790 939 404 · We reply within one working day.