E-Paper
Sign In
From ‘Place Order’ to optimisation: What happens next
Inside talabat’s expanding kitchen network, data, timing and proximity work in sync to deliver speed at scale
- PUBLISHED: Thu 12 Feb 2026, 6:01 PM
Imagine this: It is just before dinner in a residential district in Dubai, when phones begin to light up with food orders. A customer taps “Place Order” on the talabat app. From the outside, it looks like a simple transaction. A few seconds of confirmation. A countdown timer appears. Estimated delivery time: 28 minutes. What happens next is not simple at all.
The moment the order lands
Recommended For You
The second the order is placed; it does not just appear on a screen inside a kitchen. It enters a system that has already anticipated it.
At the heart of talabat Kitchens is Pepper, an in-house integrated platform developed by Delivery Hero. Pepper is not reacting in real time alone. It has been forecasting this neighbourhood’s demand all day.
“Talabat Kitchens optimises kitchen utilisation across different brands and dayparts through Pepper, our in-house integrated platform,” explains Tarek El Halabi, Country Lead, Kitchens, talabat UAE. “This comprehensive system employs predictive demand forecasting to anticipate order volumes across different time periods, while intelligent partner and location matching ensures optimal brand mix in each facility.”
By 8pm, Pepper already knows that this district leans heavily towards fast casual and comfort food in the evening. It knows how many riders are active nearby. It knows which kitchen stall is best positioned to prepare the order quickly without creating bottlenecks.
The order is automatically routed to the appropriate stall inside the nearest talabat Kitchens hub.
Inside the hub
There is no dining area here. No front-of-house staff. Just a corridor of branded kitchen units operating side by side.
A screen lights up in one of the stalls. The order details appear instantly, already sequenced within the prep queue. Pepper has factored in the complexity of the dish, current workload and expected rider arrival time.
At this point, speed is not about rushing. It is about synchronisation. “Pepper powers predictive demand forecasting, intelligent partner and location matching, kitchen efficiency optimisation and real-time performance monitoring,” says El Halabi. “We’re not just placing kitchens, we’re predicting demand, optimising preparation, shortening delivery loops and identifying the right partners before the market does.”
The kitchen team begins preparation. Meanwhile, the system signals to the rider network. A nearby rider receives a notification, timed so that arrival aligns with the estimated completion of the order. Not too early, not too late. This coordination is deliberate.
The invisible handover
One of the most critical moments in delivery is the handover between kitchen and rider.
A few minutes of delay here can extend total delivery time significantly. “Technology plays a central role in ensuring order accuracy, optimising prep time and coordinating handovers between kitchen teams and riders,” says El Halabi. “Pepper manages core operational elements such as workflow coordination, prep timing and dispatch scheduling, while talabat Kitchens leverages synergies across the wider talabat ecosystem.”
Inside the hub, dispatch screens track readiness in real time. The moment the meal is sealed and scanned, the system updates both rider and customer. The rider arrives within a narrow time window, minimising idle time and preventing food from sitting on a counter.
This is where proximity changes the equation. Because talabat Kitchens are strategically located closer to high-density residential clusters, delivery routes are shorter by design. That geographic advantage compounds with every minute saved in preparation and dispatch.
It is one of the reasons talabat reports delivery time improvements of up to 13 per cent compared to traditional brick-and-mortar locations. Within the network, the UAE has seen nine per cent faster deliveries, Bahrain 13 per cent and Qatar four per cent.
Behind the scale
Now multiply that single order by thousands. Across more than 30 hubs in five markets, over 500 kitchen stalls are operating simultaneously. Each one is handling its own brand identity, recipes and staff, yet all are synchronised through a shared operational backbone.
Scaling that environment is not straightforward. “Scaling cloud kitchens in the UAE comes with three main challenges: real estate costs, operational complexity and maintaining consistent quality across multiple brands,” El Halabi notes.
talabat’s solution has been structural. The model is asset-light. As Awais Malik, General Manager, Kitchens, talabat MENA, puts it: “talabat Kitchens was built to solve two things at once: faster delivery for customers and smarter growth and stronger unit economics for our restaurant partners. We don’t own brands, we enable them by giving them proximity, data intelligence and operational leverage at scale.”
Partners bring their own teams, recipes and equipment, preserving authenticity and reducing capital barriers. talabat standardises safety, hygiene and dispatch frameworks across hubs. “talabat Kitchens implemented an asset-light, partner-first model that removes heavy CapEx barriers by allowing partners to bring their own teams, recipes and equipment,” he explains. “Standardised safety and hygiene protocols ensure all kitchens operate under licensed standards to maintain quality and compliance across locations.”
So, while each brand cooks differently, the infrastructure supporting them behaves consistently.
What changes, what stays constant
As talabat expands towards 50 hubs over the next three years, not every variable can be controlled centrally. “We’re very deliberate about what we standardise and what we localise,” says El Halabi. “The operational backbone, safety and hygiene protocols, kitchen layouts, dispatch flows and performance management is consistent across all locations.”
“What remains flexible is everything driven by local demand,” he continues. “Partner selection, cuisine mix, peak ordering times and customer preferences vary significantly by neighbourhood and by country.”
A hub in Dubai will not mirror one in Kuwait or Jordan. Demand curves differ. Affordability thresholds shift. Evening ordering habits vary. Pepper continuously reads those signals, adjusting brand placement and capacity allocation accordingly. That balance between uniform systems and local nuance is what allows talabat Kitchens to scale without becoming generic.
The order arrives
Back in that residential district, 27 minutes after the order was placed, the rider pulls up outside the customer’s building. The countdown timer on the app reaches zero just as the doorbell rings.
To the customer, the experience feels seamless. They never see the predictive modelling, the kitchen queue optimisation, the synchronised dispatch timing or the proximity planning that made it possible.
But behind that one delivery sits a network designed for compression of time and distance.
As talabat moves towards its goal of fulfilling up to 10 per cent of food orders in mature markets through its kitchen network, the cloud kitchen is no longer just a supplementary channel. It is becoming part of the region’s physical and digital food infrastructure.
Behind every “order delivered” notification sits a system calibrated for timing, placement and scale. The visible transaction lasts seconds. The operational machine behind it is now regional.
Sana Eqbal is a journalist with over 10 years of experience and a media strategist specialising in corporate communications, public relations, digital media, and content management.