The aggregators found you customers. Now they own them.
Let's be fair before we're critical: Talabat and Elmenus did something real for you. They put your restaurant in front of thousands of hungry people in your area who had never heard your name, they handled the app, the search, the ratings, the delivery fleet in some cases, and the trust layer that makes a stranger comfortable paying you. For a brand-new kitchen with no audience, that discovery is worth paying for. Nobody serious is telling you to delete your Talabat listing tomorrow.
But discovery and ownership are two different things, and this is where the relationship quietly turns. When a customer orders your koshari through the app, the app gets their phone number, their address, their order history, and their re-order habit. You get a ticket to fire in the kitchen. You don't get the customer. You can't message them when you launch a new item, you can't run a Ramadan offer to your own regulars, you can't even tell who your top 50 repeat buyers are. You're renting access to people who, on paper, should already be yours.
That's the own-versus-rent line, applied to food. The aggregator is a billboard you rent on a busy street, and it works. But a billboard you rent forever, that takes a cut of everyone who walks through your door, and that won't give you the names of the people who loved your food, is a strange thing to make the foundation of your business. The smart move isn't to abandon it. It's to stop letting it be the only road to your kitchen.
The commission math nobody does out loud
Here's the number that should keep you up at night. Say your average order is 250 EGP and the aggregator takes 25% commission (Egyptian rates typically land somewhere between 20% and 30% depending on your deal and whether they handle delivery). That's about 62.5 EGP gone from every single order, before you've paid for chicken, rice, gas, rent, or staff. On a quiet day of 30 orders, that's roughly 1,875 EGP handed over. Over a month, around 56,000 EGP. Over a year, you've paid the platform somewhere near 675,000 EGP in commission alone.
Now here's the part that hurts: a big chunk of those orders are repeat customers. People who already know they love your food, who would have ordered anyway, who didn't need to be discovered again. You're paying a finder's fee on people who were already found. If even a third of your aggregator volume is repeat business, and you could shift those orders to your own site, you'd keep roughly 225,000 EGP a year that's currently leaving your account, on these example numbers. A custom restaurant website that costs a fraction of that pays for itself in weeks, not years.
We're not pretending your own channel is free. Local payment fees on Fawry, Paymob, or InstaPay are real, your own delivery or a third-party courier costs money, and so does the marketing to push people to your site. But those costs are a few percent and some effort, not a permanent 25% tax on every plate, and crucially the customer relationship stays with you. The aggregator's 25% is the most expensive line item on your menu that never appears on your menu.
The aggregator's 25% is the most expensive line item on your menu that never appears on your menu.
What a restaurant site actually needs (not a brochure)
Most restaurant websites in Egypt fail because they're brochures: a logo, a few pretty photos, a PDF menu that won't open on a phone, and a WhatsApp number. That's not a sales channel, that's a business card. A site that actually wins back margin needs to do the job the app does, minus the commission. Start with a clean, fast digital menu that loads instantly on a phone on mobile data, with real prices and real, appetizing photos. Egyptians order with their eyes. A blurry photo of your molokhia costs you orders the same way a great one wins them.
Then the engine: direct online ordering with local payment that Egyptians actually use. That means Fawry, Paymob, or InstaPay for card and wallet, and cash on delivery left on as an option because a huge slice of the market still prefers it. The checkout has to be brutally simple: pick items, add address, pick payment, done, with a clear delivery zone and minimum order. Add table reservations if you're a sit-down place, your location wired to Google Maps so the driver and the walk-in both find you, your hours, and a phone number that actually rings. Every one of these is something the app currently does for you and charges you for.
Two non-negotiables in this market: it has to be genuinely fast on a mid-range Android over patchy 3G, because that's how most of Egypt browses, and it has to be bilingual, Arabic and English, with proper right-to-left layout so it doesn't feel like a broken translation. A site that's slow or only in English is leaking orders before anyone tastes your food. None of this is exotic. It's the standard kit, and when it's built as a custom site you own outright, there's no monthly platform tax sitting on top of it forever.
Use aggregators for discovery, own the repeat order
The honest strategy isn't all-or-nothing, it's a split. Keep the aggregators on for what they're genuinely good at: pulling in first-time customers who've never heard of you. Pay the commission on that order, treat it as a marketing cost, and accept it. Then do everything you can to make sure that customer's second, fifth, and twentieth order come through your own channel where you keep the full margin. That's the whole game, converting rented discovery into owned repeat business.
How do you make the switch happen? Small, concrete moves. Drop a printed card in every aggregator delivery bag with a discount code that only works on your own site. Put a sign at the counter and a sticker on the receipt. Offer a loyalty perk, every tenth order free, that only exists on your channel. Collect the phone number at your own checkout so you can send a WhatsApp when you've got a new dish or a Friday offer, something the app will never let you do. The food already earned the loyalty. You're just giving it somewhere to live that you control.
This is exactly the kind of owned system we build at YMS. We built and run the custom platform behind IGBS, Egypt's largest IP and trademark firm, a system handling 17,000-plus records that's been live and theirs, code owned outright, for four years. A restaurant ordering site is far simpler than that, and the principle is identical: a fast, bilingual asset you own, tuned to Fawry, Paymob, InstaPay and cash on delivery, built in six to twelve weeks. We start with a free tailored mockup of your menu and ordering flow so you can see exactly what keeping your own customers looks like before you commit a pound.
Frequently asked questions
Should I cancel Talabat and Elmenus if I build my own website?
No, and anyone telling you to is being reckless. Aggregators are genuinely good at one thing: putting you in front of new customers who've never heard of you. Keep them on for discovery and treat the commission as a marketing cost. The goal is to move repeat customers, the people who already love your food, to your own site where you keep the full margin. Use both, but stop letting the app be the only road to your kitchen.
How much does aggregator commission really cost a restaurant in Egypt?
Egyptian aggregator commissions typically run 20-30% per order depending on your deal and whether they handle delivery. On a 250 EGP average order at 25%, that's about 62.5 EGP gone per order before any costs. At 30 orders a day that's roughly 56,000 EGP a month, around 675,000 EGP a year, in commission alone. A big share of that is repeat customers you already won, which is exactly the money a website can win back.
What payment methods should restaurant online ordering support in Egypt?
The ones Egyptians actually use: Fawry, Paymob, or InstaPay for cards and wallets, plus cash on delivery left on as an option because a large share of the market still prefers paying cash at the door. Skipping cash on delivery quietly kills orders. A good restaurant site wires all of these into a simple checkout so the customer picks whatever they're comfortable with and the order goes straight to your kitchen.
What's the minimum a restaurant website needs to actually take orders?
A fast, mobile-first digital menu with real prices and appetizing photos, direct online ordering with local payment (Fawry/Paymob/InstaPay/cash on delivery), a dead-simple checkout with clear delivery zones and minimum order, your location on Google Maps, your hours, and bilingual Arabic/English with proper RTL. Add table reservations if you're a dine-in spot. Anything less is a brochure, not a sales channel. It should load instantly on a mid-range Android over weak data.
How long does it take to build a restaurant website with online ordering?
A custom restaurant ordering site is typically six to twelve weeks, depending on how complex your menu, payment setup, and delivery zones are. It's far simpler than the enterprise systems we build, like the 17,000-record platform behind IGBS that's been live for four years. We start every project with a free tailored mockup of your menu and ordering flow so you can see exactly what you're getting before committing, and you own the code outright from day one, no monthly platform tax.