Restaurant Delivery Management in Nigeria: Riders and Delivery Zones

Delivery is often the part of running an online restaurant in Nigeria that breaks first. A restaurant can get its menu right, its pricing right, and its food right, and still lose customers because an order arrived late, a rider got lost, or nobody could tell the customer where their food actually was. Lagos traffic alone can turn a fifteen minute ride into an hour. Add unclear addresses, network wahala, and the sheer size of some cities, and delivery becomes the one part of the business an owner cannot fully control just by cooking well.

Because of this, most Nigerian restaurants end up handling delivery in one of two ways. The first is running their own riders, often okada riders on staff, who know the neighbourhood, know the shortcuts, and can be trusted with cash and card payments. This is the common approach for restaurants that deliver mostly within a few kilometres of their kitchen. The second is plugging into a third party logistics company for orders that go further out or for operations that have outgrown what a small in-house team can manage. Both approaches are valid, and the right one depends on how big the restaurant is and how far its customers are spread out.

Two ways to handle delivery

Managing your own riders means the restaurant is fully in charge, no dispatch company cut, no waiting on another app's rider to become available, and a rider who already knows the customer's street. This is the model most small and mid-sized restaurants in Nigeria use today, and it is the one Restorant is built around by default. A restaurant on Restorant assigns its own riders to orders and tracks each delivery from the dashboard, without needing a separate logistics app running alongside the restaurant's own systems.

For restaurants that grow past what a small rider team can cover, perhaps multiple locations, or delivery zones that stretch far beyond okada range, Restorant supports connecting to a third party logistics company's API on the Enterprise plan. This gives larger operations a way to route deliveries out to an external logistics network when their own riders cannot keep up, without changing how orders are placed or tracked on the customer side. Most restaurants will never need this. It exists for the ones that do.

How delivery zones and fees work

A rider costs time and fuel, and both cost more the further a delivery travels. Nigerian restaurants have always priced delivery this way informally, a plate going three streets down costs less to deliver than one going across town. Restorant makes this a proper system instead of a guess made on the phone.

The restaurant owner sets up delivery zones around their location, areas built around how far a rider can reasonably reach and how traffic behaves in that direction. Each zone gets its own delivery fee. A customer close to the restaurant sees a lower fee at checkout. A customer in a zone further out sees a higher one. This is set once in the dashboard and then applies automatically every time a customer in that area orders, so nobody at the counter has to work out delivery pricing by hand for each order.

This also protects the restaurant from the common problem of a flat delivery fee that is too low for far customers and too high for near ones. Zone based pricing means a customer two streets away is not subsidising a customer forty minutes across town, and a customer forty minutes across town is not put off by a fee that assumed they lived next door.

Assigning and tracking riders

Once an order comes in and is confirmed, the restaurant assigns it to one of its riders from the Restorant dashboard. The rider sees the order details, including the delivery address and any notes the customer left, and takes it from there. The restaurant can track the delivery's progress from the same dashboard, so staff at the counter know which rider has which order and whether it has been picked up, is on the way, or has been delivered, without having to call the rider to ask.

This matters in a Nigerian context where a customer will often call the restaurant directly to ask where their food is, rather than checking an app. Having that information visible on the dashboard means whoever picks up the phone can answer immediately instead of transferring the call around or guessing.

What a restaurant needs before setting this up

Getting delivery running on Restorant does not require a large fleet or outside partnerships. A restaurant needs at least one rider, and this can be the owner's own staff member on a bike, it does not have to be a dedicated delivery hire from day one. What matters more is having clear zone boundaries worked out in advance: knowing roughly how far the restaurant is willing to deliver, which areas are close and quick, and which are further and should carry a higher fee. A restaurant that has not thought through its zones yet can start with a smaller radius and a simple two or three zone setup, then expand as more riders come on board.

Beyond that, the restaurant just needs orders coming in through Restorant's storefront and checkout, since zone assignment and fee calculation happen automatically at that point based on the customer's delivery address.

Getting started

Delivery does not have to be the hardest part of running an online restaurant. With riders managed directly from the dashboard, zones and fees set per area instead of guessed at, and a logistics API option waiting for restaurants that outgrow the self-managed model, Restorant gives a restaurant a way to handle delivery that matches how Nigerian restaurants already operate rather than forcing them into a third party app they do not control. Restorant is built by Brandyeast, based in Nnewi, Anambra State, Nigeria, and plans start at ₦30,000 a month on the Starter tier, with a 14-day free trial and no credit card required to begin.