Guides
Deciding which areas you actually serve
Almost no meal-plan business decides its service area. It accumulates, one reasonable exception at a time, until a driver is spending ninety minutes reaching three customers.
Each individual yes looks fine
A prospect signs up from a community twenty-five minutes beyond your normal round. Turning down revenue feels wrong, the drive is absorbed into an existing route, and nobody records the cost.
Repeat that eight times over a year and you have a scattered tail: a set of customers who are individually profitable on paper and collectively responsible for a round that cannot be run inside the delivery window. The cost never appears as a line item, which is precisely why it grows.
Ways to draw the boundary
Hard geographic limit
Simplest to communicate and to enforce. Works well where your city has clear community boundaries customers recognise.
Drive-time radius
More accurate than distance, because twenty minutes of clear road and twenty minutes of congestion are different problems. Harder to explain to a customer.
Day-restricted areas
Serve a distant community only on specific days. This concentrates scattered demand into a round worth running and is far easier to say than a flat refusal.
Minimum density
Open an area once a threshold of customers exists there, and hold a waitlist until then. Turns a cost into a pipeline.
The day-restriction option is underused
Most operators frame the choice as serve or refuse. The middle option — this community receives on Sundays and Wednesdays only — is better for both sides. The customer gets service rather than a rejection, and you get stops concentrated into a round that makes sense.
It also converts an operational constraint into something a customer can plan around, which is far more acceptable than a vague promise that delivery times may vary.
Revisit it, and be willing to withdraw
Density changes. An area that was uneconomic two years ago may now hold fifteen customers, and one you opened for a single enthusiastic prospect may still hold exactly that prospect.
Withdrawing from an area is uncomfortable and occasionally correct. Handled honestly — notice, a clear reason, help finding an alternative — it costs less than continuing to run a round that loses money on every pass, and customers generally understand it better than operators expect.
Common questions
- How do most meal businesses end up with an unprofitable service area?
- By accumulation rather than decision. Each individual exception looks marginal and gets absorbed into an existing round, and the cost never appears as a line item until the round no longer fits its window.
- Is drive time or distance the better boundary?
- Drive time is more accurate, since congestion makes equal distances unequal. Distance is easier to communicate, so many operations use distance publicly and drive time internally when deciding whether to open an area.
- What is the alternative to refusing a distant customer?
- Serving that community on specific days only. It concentrates scattered demand into a viable round, gives the customer something they can plan around, and is much easier to say than no.
- Can you withdraw from an area you already serve?
- Yes, and occasionally you should. With reasonable notice, a clear reason and help finding an alternative, customers generally accept it — and it costs less than running a round that loses money every pass.
See how this works in practice
The home page walks through the same mechanics against a real admin loaded with a demonstration kitchen: production, packing, routes and the customer side.
Related reading
- GuidesWorking out how many customers you can actually serveMost operators estimate capacity from their kitchen equipment and then discover the real ceiling somewhere else entirely — usually in the delivery window or in the coordination workload.
- GuidesDelivering meals across several emiratesA kitchen serving more than one emirate is running a single production operation against several delivery realities, and only one half of the business needs to change.
- SolutionsRoute planning and driver manifests for meal deliveryA meal-plan round is not a set of ad-hoc jobs appearing through the day. It is a known list, knowable the night before — which makes it a planning problem rather than a dispatch problem.
- GuidesPreventing meal delivery address errorsAddress problems look like small individual incidents and are actually one of the largest recurring costs in a delivery operation, because each one consumes two people at once.