Restaurant and Cloud Kitchen Website Design in Kenya: Menus, Bookings and M-Pesa Orders

A cloud kitchen has no signage, no passing trade and no dining room. Everything a customer learns about it, they learn on a screen. A restaurant with a physical location is only slightly different: most people look you up before they decide to come.

Which makes the website a strange thing to leave to a PDF menu from 2023 and an Instagram bio link.

This is what a restaurant or cloud kitchen site needs in Kenya, in the order it matters, with the ordering and payment parts that actually move money.

The Three Things Every Visitor Wants

Watch somebody use a restaurant website on a phone. They want three answers, fast: what do you serve, how much is it, and how do I order or get there. Everything else is decoration.

So the home page should carry, above the fold on a phone: what kind of food, where you are or which areas you deliver to, today's opening hours, and one obvious button to order. The story of the founder's culinary journey goes further down, if it goes anywhere.

Digital Menus, Done Properly

The single most common mistake is a menu as a PDF or a photograph. On a phone it loads slowly, it cannot be read without pinching, Google cannot index a word of it, and your search visibility for the dishes you are known for is zero.

Details that matter in practice:

• Prices visible without asking. Hiding them loses more customers than a high price does.
• One place to edit. When a price changes, it changes once, not across a PDF, a poster and three delivery apps.
• Availability shown honestly. A dish marked unavailable beats an order you have to cancel.
• Photos of your own food, compressed properly. Stock photography of someone else's burger is obvious and it costs trust.
• Allergen and dietary notes, especially vegetarian and halal, where relevant to your customers.
• Menu structured data, so search engines can read the menu itself. Our schema markup guide explains the idea.

Taking Orders Without an Aggregator

Delivery platforms bring volume, and they take a commission on every order plus ownership of the customer relationship. The sensible position is not to abandon them. It is to stop being dependent on them, by making direct ordering genuinely easy.

There are three workable levels, and most kitchens should start at the first.

Two things ruin direct ordering regardless of level. Unclear delivery areas and fees, which produce orders you cannot fulfil, and no confirmation, which produces phone calls asking whether the order arrived. Set delivery zones explicitly, and confirm every order in writing.

If your inbox is the bottleneck rather than the website, a WhatsApp AI agent can answer the standard questions, take details and hand real decisions to your staff, around the clock.

M-Pesa at the Checkout

For a food business, paying on the website rather than on delivery does two things: it removes no-shows on prepared food, and it ends the evening spent matching M-Pesa messages to orders.

Integrated properly, the customer taps Pay, gets the prompt on their phone, enters their PIN, and the order is marked paid when Safaricom confirms it. Not when someone forwards a screenshot, which can be forged.

We charge KES 5,000 once for M-Pesa integration, all-inclusive, covering STK Push, Paybill and Till confirmation, reconciliation and the Daraja registration with Safaricom, tested with real transactions before launch. The detail is on the M-Pesa integration page, and the business case is in integrating M-Pesa.

Table Bookings

For sit-down restaurants, a booking form beats a phone number for anyone deciding after hours. Keep it short: date, time, number of people, name, phone. Ask for anything more and bookings drop.

• Confirm instantly on screen, then by message
• Say what happens next, including how late you hold a table
• Block out dates you are closed, so nobody books a public holiday you are not open on
• Send the booking into the calendar your floor staff actually use

What Changes for a Cloud Kitchen

A cloud kitchen has no room to impress anyone, so the website carries the whole burden of trust. Four things matter more than they would for a restaurant:

Being Found When Someone Is Hungry

Food search is local and immediate. Somebody wants nyama choma near Kilimani, or pizza delivered to Syokimau, and they decide within minutes.

1. Claim your Google Business Profile and keep hours, photos and the menu link current. For a delivery-only kitchen, follow Google's rules for service-area businesses and hide the address. Our Google Business Profile guide covers it.
2. Make a page per area you deliver to, with the real delivery fee and time for that area.
3. Use the words customers use, including dish names and neighbourhoods, in real page text.
4. Ask for reviews after delivery, within Google's rules, and reply to all of them.
5. Keep the site fast. A hungry person on mobile data does not wait. Test it with our free speed test.

What It Costs to Build

Most kitchens we work with start with the first row and add ordering once direct demand proves itself. That order of operations is deliberate: prove people will order from you directly before paying for the machinery to take those orders at scale.

Frequently Asked Questions

Should my restaurant menu be a PDF?

No. A PDF loads slowly on a phone, cannot be read without pinching, and Google cannot index a word of it, so you rank for none of the dishes you are known for. Put the menu on a web page as real text, organised by section, with prices next to items.

Do I still need delivery apps if I take orders on my website?

Most kitchens should keep both. Aggregators bring volume but take a commission and own the customer relationship. A direct ordering route on your own site gives you a channel where the margin and the customer are yours, and the sensible goal is to stop being dependent rather than to walk away.

What is the simplest way to take orders online?

Start with WhatsApp ordering: each menu item has a button that opens WhatsApp with the item already written into the message. It needs no new software and no training. Move to a form, then a full cart with M-Pesa, as direct demand grows.

Why integrate M-Pesa rather than just showing a Paybill?

Integration removes no-shows on prepared food and ends the evening spent matching messages to orders. The customer gets a prompt, enters their PIN, and the order is marked paid when Safaricom confirms it rather than when somebody forwards a screenshot, which can be forged.

How should a delivery-only kitchen handle its Google listing?

As a service-area business. Google's guidelines say businesses that travel to customers rather than serving them at a storefront should hide the address and list the areas they serve instead.

What does a restaurant website cost in Kenya?

A menu, photos, location and WhatsApp ordering fits a basic site at KES 20,000 to 30,000. Multi-section menus, booking forms and several locations sit in the professional range at KES 50,000 to 120,000. Full online ordering with delivery zones is an e-commerce build from KES 50,000, plus KES 5,000 one-time for M-Pesa.