Ordering and Website Systems for Restaurants in Lebanon
Friday 12:40. The grill is full. A story posted at 11 still shows the dish you 86’d at noon. Three voice notes arrive at once: one from Furn el Chebbak with no floor, one asking if you still do the lunch tray in lira, one from a rider who is already downstairs. The cashier has Instagram on one phone, WhatsApp on another, and a paper 86 list that the kitchen has already updated in marker. That is not “we need to be more visible”. That is a restaurant whose doors (street, story, and chat) do not agree.
The lunch-service problems a template homepage never names
The 86 list. A dish dies. Instagram does not know. A customer argues at the door because the story promised it. Staff waste the ticket time explaining. A public menu that the kitchen can mark unavailable (even if that is a WhatsApp status you control from the pass) is worth more than a cinematic hero video that takes eight seconds to load on a tired line.
The address-less order. People order like they are talking to a cousin. “The building near the pharmacy.” The rider guesses. The food cools. You eat the refund. Collecting a suburb, a landmark, and a door instruction before the ticket hits the pass is operations, not “e-commerce theatre”.
The price board. You rewrite USD and LBP with a marker. The PDF menu in the bio is from March. Diaspora family forwarding the link to a parent in the neighbourhood send a price you no longer honour. The fight at the till is not rudeness. It is a stale number you left public.
The private-table and catering leak. Someone WhatsApps “Thursday, twenty people, mixed grill”. It sits under a stickered chat. The owner sees it after the meat is already ordered for a different event. Catering is not a modifier on a burger. It needs a date, a headcount, and a yes that occupies a real kitchen slot.
What we set up for a kitchen, not a “food brand”
A page that opens fast on a phone: where you are, when you are open (including generator reality if you close when the street is dark), the menu as it is this week, allergens you actually stand behind, and a WhatsApp that is the order line rather than the owner’s family group. Photos of your plates, your street, your prices as you charge them, not a stock dining room in a country with stable electricity.
An order path that captures suburb, payment (cash on delivery, Whish, OMT, card if you truly have it), and the 86-aware items. If you already live inside a delivery app, we do not rip it out for sport. We stop the side channel of voice notes from bypassing the ticket. Optional: a simple catering form so fifty-person Saturdays do not hide under a single chat pin.
See a menu-and-order shape on the restaurant example. How people actually pay here is in online payments in Lebanon. Why the story is not enough on its own is in website vs Instagram.
Lebanon on the pass
Riders, cash, and mixed currency are the default, not an integration you enable later. A cut means the till printer dies while phones on data still order. The public site must stay up even when the PC in the back is off. French on a menu in some neighbourhoods is not decoration; it is how a regular reads the fish. Arabic is how the kitchen shouts. English is how a visitor from the airport searches “open now”. Those three can exist without a 40-page brand book.
I will not invent cover counts or “average ticket” for a nameless Beirut bistro. The work is: one menu truth, one way to say 86, one address the rider can use, prices that match the board. If the honest next step is “fix Google hours and stop posting dead dishes”, I will say that on the free call.
Services that fit a restaurant
A website from $350 is usually the door: menu, map, hours, WhatsApp. If you want checkout or a catalog of trays, an online store from $700. If the pain is the voice-note pile, WhatsApp automation from $300 to collect the fields the pass needs. Hosting that is not under the espresso machine is part of the quote conversation, not a surprise month two.
Send the Instagram or the old PDF menu via the free website check. Or tell me which dish you 86’d today on contact or WhatsApp. Twenty minutes free. Paid work only after a written price.
Questions owners ask
Should I take orders on Instagram or a real menu page?
Stories sell appetite. They do not keep hours, allergens, or an 86 list. Keep Instagram for the plate. Put the menu, the street, and how to order on a page that still exists when the story expires. Many kitchens need both.
How do WhatsApp voice-note orders get less chaotic?
Ask for suburb, building hint, and payment method in a path the rider can read, not a two-minute voice the cashier rewinds during Friday lunch. Automation can collect those fields. A human still confirms when the kitchen is on fire.
USD and LBP on the same menu, can a site handle that?
The site should show prices the way you actually charge this week, including a note when the board is in fresh dollars. It should not invent a live Central Bank feed you do not maintain. Honesty beats a widget that lies by Thursday.
Do I need delivery software or just a cleaner order path?
Most small restaurants need the order to stop living only as a chat. A full rider network is a different company. We set up the menu, the WhatsApp or checkout path, and what the kitchen prints or sees. We do not pretend to be a delivery app.
What about catering and private tables?
Those are quotes, not a nine-item lunch menu. A form or WhatsApp with date, headcount, and area is enough at first. Stuffing catering into the same button as a shawarma order is how you miss a Saturday of fifty people.
What does a restaurant setup start from?
A public site with menu and location starts from $350. A store-style order path starts from $700. WhatsApp order intake starts from $300. Commission apps you already use stay yours.
Book a free 20-minute consultation
Tell me what is wasting the day in the shop or clinic. I will say if a site, booking, or orders are the next step, with a written scope before paid work.