FlowsBook a callSign inCreate free accountSign up
Population and demographics

Population density and delivery costs: why a drop costs more in the suburbs

Population density and delivery costs are linked through the distance between drops. How to measure density in each zone and turn it into drops per hour and zone rules.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

Population density and delivery costs are linked through one thing: the distance between one drop and the next. Where many people live close together, a courier finishes the next order in a few minutes, so each drop carries a small share of the courier's hour. Where homes are spread out, the same courier spends most of the hour driving, so each drop costs more. Measure people per km² in each zone, estimate how many drops an hour that allows, and set delivery times, minimum orders and zone edges from it.

This article is for operations and finance people at delivery businesses: grocery, meal kits, pharmacy, parcels, laundry and home services that run their own drivers. It explains the link, a simple way to estimate it, a made-up example in Melbourne and Mumbai, the usual errors, and an AI employee that reports density and drop spacing for every zone.

Where the cost of a drop comes from

A delivery hour has three parts: driving between drops, the minutes at each door, and the run out from the depot and back. The minutes at the door are roughly the same everywhere, though stairs and lifts add time in tall buildings. The run out depends on how far the zone is from the depot. The driving between drops is where density matters, and it is often the largest part.

  • High density: drops a few hundred metres apart, short driving between them, more drops per hour. Parking and stairs can slow the door time.
  • Middle density: a mix. Batching orders by street makes the biggest difference here.
  • Low density: drops kilometres apart, long driving, few drops per hour. Each drop carries much more of the driver's time and the vehicle's running.

The point is not that suburbs lose money. It is that the same delivery promise and the same minimum order cost very different amounts to fulfil in different zones, and you can see that before you open a zone.

Measuring density for each zone

Draw each delivery zone, or the area a driver can reach from the depot with Travel area, and ask Demographics for totals in each. You get residents, the area in km² and people per km² for every zone. For a closer look, ask for every hexagon instead and see where inside a zone people actually live: a zone can have a dense core and empty edges, which matters for where you draw the line.

From density to drops per hour

Residents are not orders, but they set how close orders can be. If one household in fifty orders on a given day, a zone with twice the density gives twice as many orders per km², so drops are closer together. A rough rule for a planning sheet: the typical distance between drops shrinks with the square root of how many orders fall in each km². Four times the orders per km² roughly halves the distance between them.

The cleanest way to test it on your own streets is to route a sample day. Put a day's real or sample orders for a zone into Route planner, read the route's total distance and time, and divide by the number of stops. Do it for a dense zone and a sparse one and the difference in minutes per drop is your cost difference.

A made-up example: Melbourne and Mumbai

All figures here are invented to show the arithmetic. A grocery delivery company runs one zone in inner Melbourne, one in an outer Melbourne suburb, and is planning its first zone in Mumbai.

ZonePeople per km²Orders a day (planned)Route minutes per dropDoor minutesTotal minutes per drop
Inner Melbourne6,500180448
Outer Melbourne1,2009011314
Mumbai (planned)28,000400268

Made-up figures, for illustration only.

The outer suburb takes almost twice the driver time per drop of the inner zone, so the company sets a later cut-off and two fixed delivery windows there instead of a one-hour promise. Mumbai is extremely dense, so driving between drops is short, but door time is longer because of tall buildings and building security, so its total ends up close to inner Melbourne's. Density explains the driving; it does not explain everything.

Mistakes when linking density to cost

  • Using the zone's average density when people live in a few pockets. Map the hexagons and see where the orders will actually come from.
  • Forgetting door time. In dense, tall districts it can outweigh the saving on driving.
  • Treating residents as customers. Density sets how close orders could be; your own conversion rate sets how close they are.
  • Setting one promise and one minimum order for every zone, then wondering why the sparse ones lose money.
  • Drawing zones as circles. A river with one bridge doubles the distance between neighbours on opposite banks.

An AI employee that reports zone density

In xMap Flows, an AI employee can report density and drop spacing for every zone each month, or for a new zone before you open it. It belongs with the tools in the guide to location intelligence automation.

  1. Area of interest: your delivery zones, drawn on the map.
  2. Demographics: totals for each zone, with people per km².
  3. My data and Route planner: a sample day's stops for each zone, routed in a second branch.
  4. Data analyst: minutes per drop for each zone, and how it moves with density.
  5. Make a report: a table of zones with density, minutes per drop and a suggested promise.

What lands in the inbox is a short monthly report: each zone's density, the routed minutes per drop, and which zones are costing more per order than the rest. The templates Where to put the next dark store and Where to put micro-fulfilment hubs look at the same trade-off from the depot side.

Questions

Why does a delivery cost more in the suburbs?

Because drops are further apart. The driver spends more of each hour driving between doors, so fewer drops share the same hour of wages and running costs.

Is higher density always cheaper to serve?

Usually for driving, not always in total. Tall buildings, parking and security can add minutes at each door that eat into the saving.

How do I estimate drops per hour for a new zone?

Measure people per km², assume a share of households ordering each day from your other zones, and route a sample day of stops to see the minutes per drop.

Can I measure density in the United States or United Kingdom?

Not from the population grid, which has no figures there. Use your own past order addresses to measure how close drops fall in each zone.

Templates that do this

Read next

More on population and demographics · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.