In brief
- Stava is the courier company in our group. It runs on-demand deliveries for restaurant and retail chains: couriers in about 50 cities.
- Its fleet dispatch runs on our platform: the system decides which courier takes which order, in what sequence and when to leave.
- Result: 3.0 orders per courier working hour across the whole fleet. That is more than the averages of large food-delivery platforms in Poland (Glovo, Uber Eats, Wolt), which public data puts at about 2.0–2.6. Only a few of their regions reach 3.0.
- Stava achieves this without the advantage of scale: an average branch handles about 120 orders a day.
The client
Stava has been in the delivery market since 2014. It runs on-demand deliveries from nearly 1,000 pickup points in about 50 cities, both for major brands including KFC, Pizza Hut, McDonald’s and Stokrotka and for many local businesses.
Stava is part of our group: Dispatch Rangers grew out of its courier business (our story). Today it is one of our clients, on an equal footing with the others.
The challenge
In on-demand delivery, orders come in all day from many pickup points, each one has to be delivered quickly, and demand changes from hour to hour.
An average Stava branch handles about 120 orders a day. At that scale it is hard to combine orders into one trip, so productivity depends on the quality of dispatch, not on volume.
What our platform does
Stava’s logistics has run on our platform since 2014. Every day the platform:
- assigns orders to couriers and combines them into one trip when it pays off,
- sets the delivery sequence and the departure time, matched to when the order is ready at the pickup point,
- re-plans routes with every new order and every delay.
Beyond dispatch itself, the deployment covers:
- courier numbers and schedules matched to the demand forecast,
- a supervision panel for the operations team and a courier app,
- integrations with clients’ order systems.
Results
-
Courier productivity: 3.0 orders per courier working hour across the whole fleet.
- Against the market: large food-delivery platforms in Poland average about 2.0–2.6, and only 3 of 45 regional and city figures reach 3.0. To handle 100 orders an hour, Stava needs about 33 couriers, compared with 38–50 at the platform averages.
-
Measurement period: 3.0 is the monthly average from December 2024 to June 2025 (2.91 to 3.04 in individual months).
-
Scale: about 50 branches and about 1,000 couriers. In May 2025 branches handled from about 30 to about 280 orders a day, and the smallest of them also reached about 3.0.
Orders per courier working hour: 45 regional platform results and Stava’s whole fleet
- regional or city result
- platform average
- Stava, whole fleet: 3.0
Only 3 of 45 regional results reach 3.0. Stava achieves this level as the average of its whole fleet.
How many couriers are needed to handle 100 orders an hour?
Stavaabout 33
Platform averages38–50
Sources and calculation: see “Where does the market data come from?”.
Where does the market data come from?
Courier productivity is rarely published directly, but it can be calculated from pay data. If you know a courier’s average earnings per hour and per order for the same period, dividing one by the other gives the number of orders per hour. Payroll partners of Glovo, Uber Eats and Wolt couriers publish such figures because they recruit new couriers. We link to MB Partner’s pages as copies in the Internet Archive, because the partner later changes the dates on them while keeping the same data.
| Platform and source | Period | Orders per hour |
|---|---|---|
| Glovo, MB Partner: 936 couriers, 131,165 deliveries, 16 regions | January–February 2024 | 2.07 |
| Glovo, AppJobs: 166,820 deliveries | 90 days to March 2024 | 1.92 |
| Uber Eats, MB Partner: over 200 couriers, 15 cities | July 2025 | 2.53 |
| Wolt, MB Partner: 14 regions (median) | 2025 | 2.62 |
| Highest regional figure: Wolt, Dolnośląskie | 2025 | 3.25 |
| Stava, whole fleet | 3.0 |
The restaurant chain fleet in our other case study was at Glovo’s 2024 level, 1.99 orders per hour, before the pilot.
Does high productivity require a large scale?
No. The belief that productivity will come by itself once the scale is large enough is one of the most common in the delivery industry. Large scale and order density help, but they are not a prerequisite.
Large platforms build productivity largely through external conditions: a high number of orders per location, operating in large cities and their centres, small zones, short distances and deliveries by bike. These factors raise productivity regardless of the quality of dispatch.
The data show this. In the measurement period Uber Eats and Wolt operated mainly in large cities, while Glovo also operated in many smaller towns, and Glovo’s average is clearly lower. For Wolt the highest figures are in regions with large cities: 3.25 in Dolnośląskie, 3.09 in Wielkopolskie and 2.87 in Mazowieckie. Despite these conditions, only 3 of 45 regional and city figures reach 3.0.
Stava reaches 3.0 as the average of its whole fleet, in branches handling about 120 orders a day on average. In May 2025 the smallest branch, with about 30 orders a day, also reached about 3.0.
The advantage comes from dispatch, not from scale. If our tools reach 3.0 at about 120 orders a day on average, and even in a branch with about 30 orders, then at a scale of several thousand orders a day in one city the result would be clearly higher.
How can you compare this with your fleet?
Divide the number of completed orders by your couriers’ paid working hours in the same period. If you only have pay data, divide the average courier earnings per hour by the average earnings per order. Compare fleets with similar order density: a high result is easier with several hundred orders a day in one zone than with a hundred.
How we measure
- Productivity is the number of completed orders per courier working hour (OPH, orders per hour), across the whole fleet. Orders combined into one trip count separately, just as in the platform data.
- About 120 orders a day per branch refers to the same period in which the whole fleet averaged 3.0 orders per hour.
- Stava has worked with our tools from day one, so there is no result from before the deployment. That is why we compare it with the market; the effect of switching tools alone is shown in our other case study.
- The platform data is an approximation from pay, not the result of a study. Hourly earnings may include bonuses, the hours are time in the app, and couriers working in several apps at once lower the figure for any single platform. That is why we give a range and describe the sources rather than quote a single number.
What it means for you
Stava uses the same platform and the same team as our other clients. Its result shows what automated dispatch delivers at full scale and over the long term, not just in a pilot.