Monitor Your Restaurants on Talabat
Talabat is the Delivery Hero-owned food delivery marketplace of five Gulf markets, Egypt, Jordan and Iraq, headquartered in Dubai and listed on the Dubai Financial Market since December 2024. This page collects the verified facts a restaurant chain needs about Talabat as of August 2026, and explains what Kitchain watches on the platform: downtime, ratings, promotions, menu prices, listing position and delivery coverage.
Talabat at a glance
- Ownership: 80% held by Delivery Hero SE (Berlin) as of 31 December 2025, with 20% free float on the Dubai Financial Market (ticker TALABAT) since the December 2024 listing; Uber agreed in July 2026 to acquire Delivery Hero, with closing expected in H2 2027.
- Headquarters: Dubai, UAE. Founded 2004 in Kuwait, which is still its oldest market.
- Markets: 8 countries as of August 2026 – UAE (largest by GMV), Kuwait, Qatar, Bahrain, Oman, Jordan, Egypt (largest by users) and Iraq.
- Delivers: restaurant food; groceries and retail through Local Shops, InstaShop and about 160 own talabat mart dark stores; pharmacy and flowers; and DineOut dine-in discounts in the UAE.
- Positioning: says it leads food delivery in all eight markets (its own claim, citing Redseer, year-end 2025); FY2025 GMV USD 9.4 billion, about 71,000 restaurant partners and 7.7 million monthly active customers.
- Kitchain on Talabat: live for Alert, Rating, Promo, Menu; Visibility and Coverage configured per account.
What Kitchain watches on Talabat
About Talabat
Talabat started in Kuwait in 2004 and passed via Rocket Internet (2015) to Delivery Hero (2016). It absorbed the sister brand Carriage in January 2020 and Egypt's Otlob in August 2020, and in February 2025 it bought InstaShop from Delivery Hero for USD 32 million. Talabat Holding plc was incorporated in ADGM in September 2024 and listed on the Dubai Financial Market on 10 December 2024 after an IPO that raised AED 7.5 billion (about USD 2 billion). Delivery Hero SE held 80% at the end of 2025 and remains the majority owner as of August 2026; in July 2026 Delivery Hero agreed a takeover by Uber, expected to close in the second half of 2027.
In FY2025 Talabat reported GMV of USD 9.4 billion, with roughly 84,000 active partners, about 71,000 of them restaurants; by Q2 2026 active partners across all verticals had reached about 97,000. The GCC accounted for 82% of GMV in FY2025 and 78% in Q2 2026. Revenue comes from partner commissions (blended across all verticals at about 13% of GMV in H1 2026; restaurant rates are negotiated and not published), delivery and service fees, talabat pro subscriptions (branded t pro in Egypt), own grocery sales through around 160 talabat mart dark stores, and advertising and listing fees, which brought in USD 323 million in 2025. Talabat pro subscribers accounted for 51% of GMV in Q2 2026.
For a restaurant, the partner side of Talabat runs through the Vendor Portal, the talabat partner mobile app and a talabat-supplied order tablet; per the UAE and Kuwait partner FAQs, a branch can pause orders from the tablet for a set period or flag itself as busy. Talabat runs its own rider fleet alongside third-party logistics partners, and some vendors deliver with their own drivers. Kitchain watches Talabat from the outside, opening the same public pages a customer opens, so head office learns about a paused branch, a slipping rating or a missing offer without anyone checking the app by hand. Our Talabat monitoring guide covers setup in detail.
Where Talabat operates
As of August 2026 Talabat delivers food in eight countries: the five GCC markets of the UAE, Kuwait, Qatar, Bahrain and Oman, plus Jordan, Egypt and Iraq. Each has its own country site (talabat.com/uae, talabat.com/kuwait and so on; Iraq sits on a separate iraq.talabat.com domain), and most have their own partner sign-up site (ae.partner.talabat.com, kw.partner.talabat.com and equivalents for Qatar, Oman, Jordan, Egypt and Iraq). Restaurant pages are area-based: the customer selects a delivery area before branch availability, delivery time and fees appear, so anything measured on Talabat has to be measured per delivery area. Launch years below come from Wikipedia where Talabat's own filings give no per-country dates.
| Country | Since | Notes |
|---|---|---|
| United Arab Emirates | 2012 | Largest market by GMV; HQ; Dubai, Abu Dhabi, Sharjah and more. |
| Kuwait | 2004 | Founding market and its oldest per Annual Report 2025. |
| Qatar | 2013 | Doha; launch year per Wikipedia only. |
| Bahrain | 2012 | Launch year per Wikipedia only. |
| Oman | 2012 | Muscat, Salalah, Sohar, Nizwa, Sur among listed cities. |
| Jordan | 2017 | Amman, Aqaba, Irbid, Zarqa; non-GCC segment. |
| Egypt | 2020 | Former Otlob; largest user base, third by GMV; t pro. |
| Iraq | 2021 | Separate site iraq.talabat.com; launch year per Wikipedia only. |
Saudi Arabia, where Talabat launched in 2009 according to Wikipedia, is no longer a Talabat market: Delivery Hero serves it through the sister brand HungerStation, and Talabat's Annual Report 2025 explicitly excludes it from the company's countries of operation.
Kitchain on Talabat: six monitors, one outside-in method
Kitchain reads the same public Talabat pages a customer opens. There is no partner-portal login, no API key and no point-of-sale integration: you give us one listing per location, and each monitor reads what the customer is shown. Availability is checked about every 10 minutes per listing; ratings, promotions and menus are captured daily; listing position is measured at set times of day from real addresses; delivery coverage is captured for the platform and hour you book.
Talabat downtime and availability alerts: Kitchain Alert
Live on Talabat
Talabat downtime is silent. A branch is paused from the talabat-supplied tablet and nobody switches it back on, the tablet is switched off at close and left off, or a branch drops out of the area feed after a listing change. The customer sees the branch as closed or busy, or does not see it at all, while head office sees nothing. An outside-in check has to open the listing the way a customer in that area does.
Kitchain Alert opens each Talabat listing about every 10 minutes, 24/7, confirms the outage on a second read and sends an alert by Email, WhatsApp or Telegram, typically 10–20 minutes after the branch went offline. Every incident is logged with start, end and duration, and a daily report goes out at 10:00 local time. Our UAE and Kuwait delivery downtime reports show what we measured across platforms in those markets.
Kitchain Alert — Availability and downtime alerts by Email, WhatsApp, Telegram →
Talabat rating tracking: Kitchain Rating
Live on Talabat
On Talabat a restaurant page shows a decimal score out of 5 beside a ratings count, for example 3.3 (1000 Ratings), with a customer reviews section beneath it. Talabat rating monitoring is about catching a slide early: a branch drifting from 4.4 to 3.9 over five weeks looks fine on any single day and only shows up when the days are lined up.
Kitchain Rating collects the displayed score and review count for every branch once a day and keeps the history. The score and the count are the two numbers Talabat publishes on the restaurant page, and both are per branch and per country site, so a chain running the same brand on talabat.com/uae and talabat.com/egypt has two independent rating populations that move at different speeds. Review count sets the speed: a branch on 40 ratings can recover in a fortnight, a branch on 4,000 with the same score cannot. Kitchain takes only the public score and count; it does not collect review text or reply to reviews.
Kitchain Rating — Daily star ratings and review counts across platforms →
Talabat promotion monitoring: Kitchain Promo
Live on Talabat
Promotions on Talabat are largely partner-funded: partners paid for USD 588 million of customer savings in 2025 through vouchers, discounts and talabat pro benefits such as free delivery from participating pro partners. The failure is silent: a chain-wide voucher shows in Dubai but not in Ajman, a 25% discount is displayed as 15%, or free delivery stops showing on one branch after a listing edit. The customer sees a full-price restaurant next to a discounted competitor, and nothing on your side reports an error.
Kitchain Promo monitors Talabat promotions from the customer side: it captures the offers a customer can see once a day per branch, on the same visit that checks availability, so an offer that disappears at noon shows up in the next day's capture, not within minutes. The grid shows which offers are live where, the change feed shows what appeared, disappeared or changed value since yesterday, and an alert fires when an expected campaign is missing. Competitor offers in the same area are captured too.
Kitchain Promo — Promotion visibility, gaps and change alerts →
Where you rank in the Talabat listing: Kitchain Visibility
Configured per account
A Talabat feed is ordered by Talabat's own ranking, with sponsored placements bought through its self-serve, cost-per-click advertising sitting among the organic cards. Rank is local: a branch with good ratings, full hours and no downtime can still sit below the first screen for the residential area next door, and no internal report will say so. Whether a branch takes part in talabat pro matters as well, since more than one in four active customers subscribe.
Kitchain Visibility measures your Talabat listing position from saved map points at set times of day, in the city's timezone, both in the whole feed and within your cuisine, and records the competitor cards shown above you with their rating, promotion and quoted delivery time. It is not Google SEO. Visibility is set up per account: name the Talabat markets, brands and map points you want measured.
Kitchain Visibility — Position in the platform listing, measured by address →
Talabat delivery coverage by district: Kitchain Coverage
Configured per account
At the edge of a zone, what decides a Talabat order is the quoted delivery time: the branch is still available, but the wait shown is long enough that the customer scrolls on. Talabat's UAE and Kuwait partner FAQs give a default delivery zone of about a 15-minute drive from the outlet, and a 15-minute drive in Dubai is one shape at 13:00 and another at 20:00 on a Friday. Nothing tells the chain which districts drop out at peak or where a competitor has widened its zone into your area.
Kitchain Coverage measures Talabat delivery coverage zone by zone: it records whether your brand can be ordered in each measured zone and the delivery time Talabat quotes, from captures you book for the hours that matter, against a monthly allowance. It is not continuous and sends no alerts, and the quoted time is what Talabat shows, not the real delivery time. Coverage runs per account: tell us the Talabat markets, the zones and the hours worth booking.
Kitchain Coverage — Delivery reach by district, branch and platform →
Frequently asked questions
What do we need to start monitoring our Talabat branches, and in which countries?
One Talabat listing URL or restaurant ID per branch, in any of the eight Talabat markets, plus the operating hours each branch is meant to keep so a scheduled closure is not reported as an outage. Setup takes about 10 minutes with no integrations: Kitchain never signs in to the Vendor Portal, the talabat partner app or your tablet, and cannot change anything on Talabat.
Can Kitchain tell us whether a Talabat outage was our fault or Talabat's?
Partly. The incident timeline gives start and end times, and the weekday-by-hour pattern shows whether the same slot goes dark repeatedly, which usually points at a shift handover or a tablet left paused rather than the platform. If every branch in a city drops at the same minute, that is likely a platform-side event. Kitchain reports what the public listing showed; it cannot see what happened inside Talabat's systems.
Can Kitchain see whether our sponsored placement or free-delivery offer on Talabat is actually showing?
Kitchain Promo records the offers a customer can see on a branch page, including free delivery, and Kitchain Visibility records which competitor cards appear above yours at each measured map point and whether they carry a promotion. Kitchain does not buy placement or read Talabat's ROAS analytics, but positions measured before and after a paid campaign, at the same points and times, show whether it moved you.
Where does the Uber takeover of Delivery Hero stand, and what does it mean for Talabat?
The transaction has not closed. Delivery Hero's 16 July 2026 announcement names Talabat's eight countries among the businesses Uber would acquire, at EUR 41.50 per Delivery Hero share, subject to a 50% acceptance threshold and regulatory clearance; closing is expected in H2 2027. Talabat's own 16 July 2026 disclosure covers only Uber's intention to make the offer, and Delivery Hero remains Talabat's majority owner as of August 2026.
Facts about Talabat are as of August 2026 and drawn from public company and press sources. Markets, ownership and partner tools change; confirm with Talabat before relying on them. Kitchain is independent of Talabat and reads only its public customer-facing pages.