Delivery Driver Shortage in Amman -- How Technology Solves the Last Mile

At 8:47 PM on a Thursday in Amman, a restaurant in Sweifieh receives three delivery orders simultaneously -- one through Talabat, one through Careem, one through their own website. The kitchen starts preparing all three. The Talabat order gets picked up in 22 minutes. The Careem order sits on the counter for 38 minutes before a driver appears. The direct order? The restaurant's own driver is already out on a different delivery. The food waits 51 minutes. The customer calls to cancel.

This scenario plays out hundreds of times every evening across Amman. The problem isn't the kitchen. The problem isn't the food quality. The problem is the last mile -- getting the food from the counter to the customer's door -- and there aren't enough drivers to do it reliably.

The Numbers Behind the Shortage

Jordan's food delivery market has grown by approximately 340% since 2019, driven by COVID-era behavior changes that became permanent habits. The Jordan Food and Drug Administration estimated that delivery and takeaway now represent 35-40% of total restaurant revenue in Amman, up from roughly 15% pre-pandemic.

But the driver workforce hasn't kept pace. Talabat and Careem, the two dominant delivery platforms in Jordan, have collectively struggled to maintain driver supply during peak hours. Industry estimates suggest Amman needs approximately 8,000-10,000 active delivery drivers during peak evening hours (7-10 PM) to maintain sub-30-minute delivery times. The actual number of active drivers during those hours is closer to 5,000-6,000.

The gap of 2,000-4,000 drivers manifests as extended wait times, declined orders, and surge pricing -- all of which cost restaurants revenue and damage customer satisfaction.

Why Drivers Are Scarce

Several factors constrain the driver pool in Amman:

• Fuel costs: With fuel prices in Jordan among the highest in the region, driver margins are compressed. Many drivers calculate that after fuel, vehicle maintenance, and platform commissions, their effective hourly wage drops below minimum wage during non-peak hours.
• Work permit restrictions: Non-Jordanian workers, who have historically filled service roles, face regulatory barriers to delivery work. The Ministry of Labor's Jordanianization policies limit certain categories of work, creating artificial supply constraints.
• Vehicle requirements: Unlike some markets where bicycle delivery is viable, Amman's hilly terrain and sprawling geography necessitate motorized vehicles. The upfront cost of a motorcycle or car, plus insurance and registration, creates a barrier to entry.
• Competition from ride-hailing: Careem and Uber also compete for the same driver pool for passenger rides, which often offer better per-trip earnings than food delivery.
• Seasonal volatility: During Ramadan, demand for delivery spikes by 60-80% while the available driver workforce contracts (drivers observing the fast prefer not to work during the hottest hours, and evening demand concentrates in a narrow window around iftar).

What the Driver Shortage Costs Restaurants

The financial impact is concrete and measurable:

Rejected and Cancelled Orders

When no driver is available, platform orders either get rejected by the platform (the restaurant never sees them) or accepted by the restaurant and then cancelled by the customer after excessive wait times. Industry data suggests that during peak hours, 12-18% of delivery orders in Amman experience significant delays or cancellations due to driver unavailability.

For a restaurant doing 50 delivery orders per evening at an average order value of 12 JD, losing 15% means 7-8 lost orders per night, or approximately 90-100 JD in lost daily revenue. Monthly: 2,700-3,000 JD.

Customer Churn

A customer who waits 50 minutes for a delivery that was estimated at 30 minutes will order from a different restaurant next time. Delivery platforms show that a single bad delivery experience reduces the probability of re-ordering from the same restaurant by 40-60%. The restaurant loses not just that order, but the customer's lifetime value -- potentially hundreds of dinars over the following year.

Rating Damage

On platforms like Talabat, delivery time affects the restaurant's rating even though the restaurant has no control over driver availability. A 4.2-star restaurant that drops to 3.8 due to delivery delays sees a measurable decline in order volume -- typically 15-25% -- because customers filter and sort by rating.

The Multi-Platform Trap

The intuitive response to driver shortages is to list on more platforms: if Talabat doesn't have drivers, maybe Careem does. If Careem doesn't, try ToYou or your own fleet. This strategy has merit, but it creates operational chaos without the right technology.

The Tablet Problem

A restaurant listed on three delivery platforms has three tablets behind the counter, each running a different app, each with different notification sounds, different order formats, and different acceptance workflows. During a Friday evening rush, the kitchen is receiving orders from three screens while also managing dine-in. Orders get missed. Items get confused. The staff member managing the tablets becomes a bottleneck.

This is the "tablet hell" that multi-platform restaurants in Amman know intimately. And it's a direct consequence of treating each delivery channel as a separate system rather than an integrated pipeline.

Menu Synchronization

When the restaurant runs out of a menu item, someone needs to update availability on three separate platforms. When prices change, three menus need updating. When a new item launches, three platforms need new listings. This manual synchronization is time-consuming and error-prone. The restaurant that forgets to mark an item as unavailable on one platform will accept orders it can't fulfill, leading to cancellations and rating damage.

How Technology Solves This

The driver shortage is a supply constraint that individual restaurants cannot solve. But the operational problems it creates -- cancelled orders, poor delivery times, multi-platform chaos -- are solvable with the right technology stack.

1. Delivery Aggregation: One Dashboard, All Platforms

A delivery aggregation system consolidates orders from every platform -- Talabat, Careem, the restaurant's own website, WhatsApp orders -- into a single interface. One screen. One notification system. One acceptance workflow. The kitchen receives a unified order queue regardless of where the order originated.

This eliminates tablet hell. It also enables something more powerful: cross-platform driver selection. When an order comes in through the restaurant's own website, the system can dispatch it to whichever delivery fleet currently has available drivers -- the restaurant's own fleet, a third-party logistics provider, or even a platform's delivery service used on-demand.

2. Intelligent Order Dispatching

Not all orders are created equal. A large catering order going 8 kilometers needs a different handling than a single shawarma going 2 kilometers. Intelligent dispatching considers multiple factors:

• Order value: High-value orders get priority driver assignment to reduce cancellation risk
• Distance: Nearby orders are bundled for the same driver when possible
• Preparation time: The system coordinates driver arrival with kitchen completion time, reducing counter wait
• Driver location: Orders are assigned to the nearest available driver, not just the next one in the queue
• Customer history: Repeat customers with high lifetime value can receive priority delivery

This approach maximizes the productivity of available drivers. Instead of one driver waiting at the counter for 15 minutes while the food is prepared, then driving 20 minutes round-trip, the system times the driver's arrival to coincide with food readiness and optimizes the route to combine multiple deliveries when practical.

3. Route Optimization for Own-Fleet Drivers

Restaurants that operate their own delivery drivers (common in Amman for restaurants doing 50+ deliveries per day) can dramatically increase driver productivity with route optimization. Amman's geography -- steep hills, one-way streets, construction zones, and the notorious traffic circles -- makes efficient routing genuinely difficult for a driver making ad-hoc decisions.

Route optimization software considers real-time traffic data, delivery windows, and order batching to generate routes that are 15-25% more efficient than driver-selected routes. For a restaurant with three own-fleet drivers, this efficiency gain effectively adds the capacity of a fourth driver without hiring one.

4. Dynamic Delivery Zone Management

One of the smartest operational moves a restaurant can make is adjusting its delivery radius based on real-time driver availability. When all drivers are deployed, the system automatically restricts new orders to closer zones -- say within 3 kilometers instead of 6 -- ensuring that accepted orders can actually be delivered within reasonable times.

When driver capacity returns, the zone expands again. This prevents the common failure mode where a restaurant accepts an order for a distant delivery, then has no driver available, resulting in a 50-minute delay and a cancelled order. Better to decline the distant order upfront than to accept it and fail.

5. Predictive Demand Planning

Driver shortages are worst when they're unexpected. If the restaurant knows that Thursday evening between 8 and 9 PM typically generates 40 delivery orders, it can pre-position drivers, pre-prepare popular items, and alert third-party delivery partners of expected volume. Historical order data, combined with factors like weather, holidays, and events, enables surprisingly accurate demand forecasting.

Restaurants using demand prediction report 30-40% fewer driver-related delays because they're staffing for actual demand rather than reacting to it in real time.

The Direct Channel Advantage

Here's the strategic dimension that most restaurants miss: the driver shortage problem is worst on third-party platforms because restaurants have no control over driver allocation. Talabat and Careem distribute their driver pool across all restaurants on the platform, and their algorithms prioritize restaurants that pay for promoted placement or generate higher commission revenue.

A restaurant with its own ordering channel -- its own website with its own delivery fleet -- controls the entire chain. It controls when orders are accepted, how they're routed, and which customers get priority. During peak periods when Talabat drivers are stretched thin, the restaurant's own channel keeps operating at full capacity.

The economics reinforce this. An order through a restaurant's own website with its own driver costs roughly 8-12 JD in delivery labor per hour of driver time. An equivalent order through Talabat costs 25-30% commission on the order value plus the delivery fee that the customer pays. For a 15 JD order, the platform cost is 3.75-4.50 JD. The own-channel cost, when the driver is handling 3-4 orders per hour, is effectively 2-3 JD per order.

Building a direct delivery capability isn't just about independence -- it's about having a fallback when the platforms fail, which during peak hours in Amman, they increasingly do.

Practical Steps for Amman Restaurants

Solving the last mile isn't a one-time project. It's an operational capability that improves over time. Here's a realistic roadmap:

1. Consolidate platforms into one dashboard. This is the highest-impact, lowest-effort step. Stop managing three tablets separately. Get a system that aggregates all delivery orders into one view.
2. Start tracking delivery metrics. Measure average delivery time, order cancellation rate, and delivery cost per order. You can't improve what you don't measure.
3. Build a direct ordering channel. Even before you have your own drivers, a website that accepts orders gives you data on demand and gives customers a non-platform option.
4. Test own-fleet delivery for the densest zone. Start with one driver covering a 3-kilometer radius. Prove the economics before expanding.
5. Implement dynamic zones. Automatically adjust delivery radius based on current capacity. This single change can reduce cancellations by 20-30%.

The driver shortage in Amman isn't going away soon. The structural factors -- fuel costs, work permit constraints, competition from ride-hailing -- are deep and slow to change. But the restaurants that build technology-driven delivery operations around this constraint will outperform those that simply wait for more drivers to appear.

The last mile is the hardest mile. It's also where the most revenue is won or lost.

---