Restaurant Website With Online Ordering in Lebanon

If you run a restaurant, café or snack in Lebanon and you're tired of paying commission on every delivery order, the real decision is not "which platform" but what kind of restaurant website you actually need: a fast one-page site with a live menu and a WhatsApp order button, or a full ordering system with a cart and online payment. For most small and mid-sized venues here the first one wins: it costs a fraction, works on a weak mobile connection, and puts the order in the channel your customers already use. This guide covers the choice, the pages you need, who updates the menu when prices move, and what the work costs.

Menu site or ordering system: decide before you shop for a developer

Two different products, two different price tags, and much of the money wasted on restaurant websites in Lebanon goes on the second when the first would have done the job.

• A menu site. One to three pages: your menu on screen, photos, location, hours, phone, and a big "Order on WhatsApp" button. No cart, no accounts, no payment. It loads in a second.
• An ordering system. A real cart, item options (extra cheese, no pickles), delivery zones with different fees, order status, and card payment or cash on delivery. It's a small e-commerce build that needs someone watching orders come in.

Ask one question: when an order lands, who sees it and what do they do? If the answer is "whoever is near the phone," you want a menu site with WhatsApp. If you have a dedicated tablet in the kitchen and real volume, a cart starts making sense. Buy the system your staff can operate on a Saturday night, not the one your competitor has. Our small business website service page shows the scope that fits a single-branch venue.

The pages a restaurant site actually needs

Restaurant sites get bloated with pages nobody opens. What earns its place:

1. Home. Who you are, one strong photo, where you are, and the order button on the first screen without scrolling.
2. Menu. The reason people came. It deserves its own page and its own clean URL you can paste into a Story.
3. Order / Delivery. Even if this is just WhatsApp: delivery zones, minimum order, rough delivery time.
4. Contact and location. Tappable phone link, WhatsApp, a Google Maps embed, opening hours, parking.
5. About, only if you have a real story. Skip it if it's filler, and skip the gallery page entirely: the good photos belong on the menu items, where they sell something.

Your digital menu, and why a PDF is a mistake

The most common failure on Lebanese restaurant sites is a PDF menu. Someone exports the printed menu, uploads it and calls it done. On a phone it opens in a viewer, downloads slowly, and the customer has to pinch and drag around a page designed for A4 paper. Half of them close it.

Build the menu as real web pages: categories, item name, short description, price, photo where you have a good one. That gives you three things a PDF never will. Text customers can search, text Google can read and show for "manakish near Hamra," and a price you change in ten seconds.

Two local details worth insisting on. Optimise every photo: on a slow connection outside Beirut, or a phone on its last bar of data, a heavy menu page is a lost order. And decide your languages honestly: many venues run an English menu with Arabic dish names, which is fine, but a proper Arabic version must be right-to-left and properly laid out, not English boxes with Arabic dropped in.

WhatsApp orders vs a real cart vs the aggregators

Be honest about how Lebanon orders food. It orders on WhatsApp. It sends a voice note. It asks whether the shawarma comes with garlic. Fighting that habit is expensive.

The WhatsApp order button is a link that opens a chat with your number and a pre-filled message carrying the item the customer tapped. Nothing to abandon, no card details, no account. The trade-off is manual handling: somebody has to be on that phone answering fast, and it doesn't scale past a certain volume.

A cart with checkout gives you accurate orders, no misheard items, and a record of everything. But online card payment is genuinely hard for many small venues here, and you may end up with a cart that ends in cash on delivery and a WhatsApp confirmation anyway, which means you paid for e-commerce and used it as an order form. Sometimes the accuracy is worth it. Often it isn't.

Aggregators bring orders on day one, real value for a new venue. What they don't give you is the customer: the number, the order history, the ability to message someone who ordered twice last month, all of it stays with the platform, and a commission comes off every order. Your own page isn't there to replace them overnight, it gives regulars a cheaper door. Put the link in your Instagram bio, on the receipt and on the delivery bag.

Who updates the menu when prices move

Almost nobody asks this before signing, and it decides whether the site is still accurate a year from now. Prices in Lebanon move, and a menu showing last spring's price is worse than no menu because it starts an argument at the door.

Settle it in the brief: can you edit prices yourself, without calling anyone? Insist on a simple admin screen or light CMS where you or your manager can change a price, hide a sold-out item and add a dish, plus a handover video. If the developer keeps the keys and charges per edit, you've bought a bill that never ends. Agree the after-launch terms too: a month of small fixes included is normal, and beyond that an hourly rate fixed in writing.

Domain, hosting and uptime: own everything

Three lines in your agreement save a lot of grief later. The domain is registered in your name, not the developer's account, so if you part ways you keep the address customers know. Hosting sits in an account you control, because restaurants have lost sites when a freelancer's hosting expired and nobody had the password. And you get the files and admin logins at handover, in writing.

On uptime: with power cuts and unstable local connections, host on a normal cloud host, never on a machine in the back office. Then test your own site on mobile data, in the evening, on a street in Beirut. If it's slow for you, it's slow for the person deciding where dinner comes from.

Getting found: Google Maps and the local basics

A site nobody finds is decoration. Before anything clever, do the boring things.

• Claim your Google Business Profile. Maps often sends a restaurant more customers than its website. Correct pin, correct hours including holidays, real photos, and the site link pointing at your menu page.
• Keep name, address and phone identical on the site, on Maps and on Instagram.
• Let Google read your menu. Dish names as text are how you appear for someone searching a dish nearby, the real argument against the PDF.
• Feed the site from social, as our guide to restaurant social media marketing in Lebanon covers.

Plan for the summer diaspora rush too: people arriving in July search for you from Maps weeks ahead, on a foreign phone.

What it costs, and how to brief the person building it

Typical observed ranges in Lebanon, in fresh dollars, for freelance work:

• A one-page site with menu, photos and a WhatsApp order button: roughly $150-$500, responsive, with a contact form or WhatsApp CTA and basic SEO.
• A three-to-five page site (home, menu, order, contact, about): roughly $350-$900, mobile responsive with light template customisation.
• A five-to-ten page WordPress site with custom layout and a blog: roughly $700-$1800.
• A real ordering system with a cart is a small e-commerce build: roughly $700-$2000 for catalog, checkout and basic payment and delivery setup.

These are observations, not quotes. What pushes a job to the top of a range: custom design instead of a template, a proper Arabic RTL version, photography, complex delivery zones, POS integration, and a big menu someone has to type in. What keeps it at the bottom: a clear brief, a template, one language, and you supplying photos and text. More detail in our website cost breakdown for Lebanese businesses.

Write the brief before you talk to anyone. Our guide on how to write a website brief gives the structure, and when proposals arrive, work through the web developer hiring checklist so you compare on substance, not on who quoted lowest.

Your next step

Pick your lane: a fast menu site with a WhatsApp button for most venues, a real cart only if you have someone to run it. Insist you can edit prices yourself, own the domain and hosting, and test on mobile data before the last payment. When you're ready, find a web developer on Furrsati: post the project, compare proposals from verified Lebanese freelancers, fund a milestone that Stripe holds, and release it once the site is live and approved. Freelancers get paid inside Lebanon by OMT, Whish, bank transfer or USDT, and you need no verification to post.

Frequently Asked Questions

Do I really need a website if I'm already on the delivery apps?

Yes, for one reason: the apps own your customer. Their number, their order history and their attention stay on the platform, and a commission comes off every order. Your own site is the cheap door for regulars and the page Google shows when someone searches your name.

Is a WhatsApp order button enough, or do I need a real cart?

For most single-branch restaurants and cafés in Lebanon a WhatsApp button is enough and often better: nothing to abandon, no card details, and customers can ask questions. Move to a cart when volume is too high to handle by hand, or when someone is dedicated to watching orders.

Can I take card payments online for my restaurant in Lebanon?

It's possible, but it's the hardest part of the build and many small venues skip it. Cash on delivery with a WhatsApp confirmation is still the norm. Raise it in the first conversation if it matters, because it changes scope and price.

How much does a restaurant website cost in Lebanon?

As typical observed local ranges in fresh dollars, a one-page menu site with a WhatsApp button runs about $150-$500, a three-to-five page site about $350-$900, and a real ordering system with a cart sits in small e-commerce territory, roughly $700-$2000. Custom design, a proper Arabic version and POS integration push you to the top of a range.

Who updates my menu when prices change?

You should be able to, and this belongs in the brief before you sign. Ask for a simple admin screen where you or your manager can change a price, hide a sold-out dish and add an item, plus a short handover video. If the developer holds the keys and bills per edit, an ordinary price change becomes a recurring cost.

Should the menu be in Arabic or English?

Follow your customers. An English menu with Arabic dish names is normal in Beirut. If a large share of your customers reads Arabic, build a real right-to-left version rather than pasting Arabic into an English design.