FlowsBook a callSign inCreate free accountSign up
Population and demographics

Setting a delivery fee by area density: shorter drops, fairer charges

In dense streets a rider makes more drops per hour, so each one costs less. How to map residents per square kilometre, turn it into fee bands, and keep the map up to date.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

Setting a delivery fee by area density means charging less where many people live close together and more where homes are spread out, because a rider or van completes more drops per hour in dense streets. Map residents per square kilometre in small cells around your kitchen, shop or warehouse, group the cells into a few bands, and give each band its own fee or minimum order. Customers pay closer to what their delivery actually costs, and you stop losing money on long, empty runs.

This is for food delivery and quick commerce operators, restaurant groups with their own riders, pharmacies, grocers and parcel firms setting local zones. It covers why density drives cost, how to build bands without prices on the map, a worked example, the mistakes that annoy customers, and a flow that redraws the bands for every branch.

Why density drives the cost of a drop

A delivery's cost is mostly the rider's or driver's time. In a dense block of flats, orders cluster: one trip can serve two or three addresses a few hundred metres apart, and the ride back is short. In a low-density suburb, a single order may mean a 15-minute ride each way with nothing to pick up on the return. Distance matters too, but two addresses at the same distance from the kitchen can differ widely in cost depending on how many neighbours order with them.

Residents per square kilometre is a good stand-in for that clustering, especially when you have little order history in a new area. Once orders build up, your own drop density should take over, but population density gives you a sensible starting map on day one.

From density to bands

  1. Cut the delivery area into small cells. Hexagons of about 0.1 km2 are fine enough to follow streets and coarse enough to be stable.
  2. Give each cell its residents per km2. A population grid supplies this directly.
  3. Choose three or four bands. For example dense, medium, sparse and remote, with thresholds you set from your own costs.
  4. Combine with travel time. A dense cell 25 minutes away is still expensive. Use the band and the drive time together.
  5. Attach a fee, minimum order or delivery window to each band in your ordering system, not on the public map.

A made-up example around a Lyon kitchen

Say a delivery kitchen in Lyon serves a 15-minute drive area. The thresholds and shares below are invented to show how the bands come out.

BandResidents per km2Share of cellsTypical setting
Denseabove 12,00030%lowest fee, smallest minimum order
Medium6,000 to 12,00035%standard fee
Sparse2,000 to 6,00025%higher fee or larger minimum
Remotebelow 2,00010%delivery on set days only

Invented thresholds and shares, for illustration only. No fee amounts are suggested.

Most orders will come from the dense and medium cells, which are also the cheapest to serve. The remote cells are a tenth of the map; moving them to scheduled delivery days frees riders at the evening peak. After a month, the kitchen compares actual drops per hour in each band with the plan and moves a threshold if a band behaves differently from what density suggested.

Mistakes that make customers angry

  • Bands that split a street. Two neighbours paying different fees feels unfair. Smooth the edges so bands follow main roads or district lines.
  • Too many bands. Five fees in one town confuse people. Three or four are plenty.
  • Ignoring daytime demand. Offices and campuses have few residents but many orders. Override those cells from your own data.
  • Never revisiting. New housing fills sparse cells quickly. Redraw the bands every quarter.
  • Hiding the rule. Tell customers why fees differ: shorter rides in busy areas. Clear reasons cut complaints.

Redrawing the bands with an AI employee

An xMap Flows AI employee can rebuild the density map for each branch and hand the bands to your team in a sheet. How such flows fit into daily operations is explained in the guide to AI employees for field operations.

  1. Schedule: every quarter (Schedule).
  2. Travel area: the 15-minute drive area around each kitchen or shop (Travel area).
  3. Demographics, set to give back every hexagon: residents and people_per_km2 for each cell (Demographics).
  4. Calculated field: band = if(people_per_km2 >= 12000, "Dense", if(people_per_km2 >= 6000, "Medium", if(people_per_km2 >= 2000, "Sparse", "Remote"))) (Calculated field).
  5. Show on a map: the cells coloured by band, for the operations team (Show on a map).
  6. Email or a row each in Google Sheets: every cell with its band, ready to load into the ordering system.

Each quarter the team receives a fresh map and a table of cells with their band. Nobody redraws polygons by hand, and the same thresholds apply in every branch. The template Same-day pet food delivery zones around my stores uses drive areas the same way, and Where to open a delivery kitchen helps choose the kitchen in the first place. More on the food delivery and quick commerce page.

Questions

Should fees depend on density or distance?

Both. Distance sets how long one drop takes; density sets how many drops you can combine. Bands by density, adjusted for travel time, capture both.

How small should the cells be?

Hexagons of about 0.1 km2, the size the population grid uses, follow streets closely without jumping around from one run to the next.

Can I use my own order data instead?

Yes, and once you have enough orders you should. Upload them to My data and blend drop density with population density in the same Calculated field.

Does this work for a new city with no orders yet?

That is where it helps most, as long as the country is covered by the population grid. It gives a reasonable first set of bands before order history exists.

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.