Skip to content
DT Nova

How to build a food delivery app: the apps, the rules and the steps

How to build a food delivery app starts with knowing what you are actually building. A delivery service is not one app but several: one for customers, one for couriers, one for restaurants and a console for your own team, joined by dispatch, payments and live tracking. This guide explains the business models, the features each app needs, the EU rules that shape the build, and the steps to scope it, with sources from the rule makers themselves.

The short version

  • Choose the model first: one restaurant, a restaurant group, a marketplace or a grocery and dark kitchen service. The model decides the apps.
  • Payments run outside the app stores' in-app purchase, through a payment provider that can split money between restaurants and couriers.
  • Allergen and food information must be shown before the order is placed, not on the receipt.
  • Courier management is now regulated: automated decisions about couriers need human oversight and transparency.
  • Launch in one area with a few restaurants, measure delivery times and repeat orders, then grow.

Four business models

ModelWho deliversWhat you build
Single restaurant or chain ordering appOwn staff, or a delivery partner's couriersCustomer app, kitchen view, simple driver app or partner integration, loyalty
Restaurant group or franchiseOwn couriers shared across sitesCustomer app with site selection, central menu management, dispatch across kitchens
MarketplaceCouriers working for the platformCustomer, courier and restaurant apps, onboarding, commission and payout logic, support tools
Grocery or dark kitchenOwn couriers, often on short shiftsCustomer app with large catalogues and substitutions, picking app, dispatch, stock (see our grocery delivery app development guide)

The marketplace is the model people picture, and the hardest to make work, because it has to win customers, restaurants and couriers at the same time. A restaurant group with loyal customers has the opposite problem: it already has the demand and needs software that stops paying a marketplace commission on its own regulars.

What each app has to do

Customer app. Browse menus with photos, options and allergens, build a basket, choose delivery or pickup and a time, pay, track the order on a map and get updates, reorder in one tap, and contact support when something goes wrong. Search, favourites and a loyalty scheme matter more than visual extras.

Courier app. Go online, receive offers with pickup and drop-off distance and the expected earnings, accept or decline, navigate, confirm pickup and delivery with a photo or code, report problems such as a closed door, and see earnings and history. It has to work with one hand, in the rain, on a low-end phone and a weak signal.

Restaurant app. Usually a tablet: incoming orders with a sound, accept and set preparation time, mark items out of stock, see when the courier arrives, manage menus and opening hours. Integration with the restaurant's point of sale removes the double typing that causes errors at busy times.

Operations console. The live map of orders and couriers, manual reassignment, refunds and credits, restaurant and courier onboarding, zones and delivery fees, and reports on delivery times, cancellations and complaints.

Dispatch and delivery times

Dispatch decides which courier gets which order, and when. Sending the courier too early leaves them waiting at the restaurant; too late leaves food going cold. Good dispatch uses the restaurant's own preparation time for each order, the courier's real travel time from live map data, and batching of two orders from the same kitchen going the same way. It starts with simple, explainable rules and gets more clever only when the data shows where time is lost. Everything it decides should be visible to the operations team, which also matters for the platform work rules below.

Payments and the app stores

Food delivery is a physical service, so the app stores' own in-app purchase does not apply. Apple's App Review Guidelines, rule 3.1.3(e), say apps that sell physical goods or services consumed outside the app must use purchase methods other than in-app purchase, such as Apple Pay or traditional card entry. Google Play's payments policy names food delivery among the physical services for which its billing system must not be used. (Both read on 11 November 2026.)

A marketplace also needs to split each payment: the restaurant's share, the courier's earnings and tip, the platform's commission and the delivery fee. Payment providers offer marketplace products for exactly this, such as Stripe Connect or Adyen for Platforms, which also handle the identity checks of the restaurants and couriers who receive money. Refunds, partial refunds for a missing item and chargebacks need their own flows from the first version.

Food information and allergens

In the EU, food sold online is covered by the food information rules. Regulation (EU) No 1169/2011, Article 14, requires that for food sold by distance communication, the mandatory food information is available before the purchase is concluded, and that for non-prepacked food, such as restaurant meals, the particulars required under Article 44 are made available the same way. Article 44 makes allergen information mandatory for non-prepacked food, and lets Member States add national rules. (Read on 11 November 2026.)

In the app, that means allergens on every dish and option, kept by the restaurant in the menu tool, shown before checkout, and updated when a recipe changes. It is a data model decision, not a label added at the end: an option such as "add peanut sauce" changes the allergens of the dish it is added to.

Couriers and the Platform Work Directive

The EU's Platform Work Directive (EU) 2024/2831 must be transposed into national law by 2 December 2026, and its legal presumption of employment applies to the period from that date. (Read on 11 November 2026.) For a delivery app, the parts that change the software most are these:

  • Data limits. Article 7 forbids automated systems from processing data on a courier's emotional or psychological state or private conversations, and from collecting data while the person is not offering or performing platform work. Tracking stops when the courier goes offline.
  • Transparency. Couriers must be informed about the automated systems that monitor them or make decisions about them, such as how offers are allocated.
  • Human oversight. Article 10 requires the platform to evaluate the impact of automated decisions regularly, and any decision to restrict, suspend or terminate a courier's account must be taken by a human being.
  • A data protection impact assessment. Article 8 treats automated monitoring and decision-making of platform workers as high-risk processing.

Whether your couriers are employees, contractors or the staff of a delivery partner is a legal question for your advisers. The software should support the model they choose and keep a log of every automated decision and every human review.

Location, notifications and the stores

The courier app needs location in the background during a shift, so the customer can track the order. Google Play requires a permissions declaration, a video demonstration and a prominent in-app disclosure before an app may use location in the background, and Apple's guideline 5.1.5 allows location only where it is directly relevant to the app's features. The customer app should ask for location only while it is open. Push notifications for order status are expected; marketing notifications need the customer's consent.

Build checklist

  • Business model and who delivers: own staff, partners or platform couriers.
  • Launch area, restaurants for the pilot and expected orders per day.
  • Apps in the first version, and which can be a web app instead of a store app.
  • Payment provider, payout model, tips, refunds and VAT on fees.
  • Menu data: options, allergens, photos, availability and who maintains them.
  • Point of sale integrations for the pilot restaurants.
  • Dispatch rules, preparation times and delivery zones.
  • Courier model, the platform work requirements and the impact assessment.
  • Support flows for late, missing and wrong orders.
  • Store accounts, hosting and code in your company's name.

How we help

This guide is the background. When you are ready to build, our on-demand app development service covers the customer, courier and partner apps, and app development covers the wider build. We build delivery and ordering systems from the first scope to the stores and maintenance, with EU hosting and the code in the client's own repository. For ordering and loyalty apps around a restaurant brand, see restaurant app development, and for retail brands, e-commerce app development. For pharmacies delivering medicines, see our guide to medicine delivery app development. For other service marketplaces, see on-demand app development. For passenger trips rather than food, see taxi app development. For couriers and routes at larger scale, see logistics software development, and for budgets, how much app development costs. For location permissions and geofencing in detail, see our guide to mobile app geolocation.

Questions people ask

How many apps does a food delivery service need?

Usually four parts: a customer app, a courier app, a tablet or web app for restaurants, and an operations console for your own team. A single restaurant delivering with its own staff can manage with a customer app and a simple kitchen and driver view.

Do Apple and Google take a commission on food orders?

No. Food delivery is a physical service used outside the app, so both stores require payment through other methods, such as card payment through a payment provider, Apple Pay or Google Pay. The payment provider's fees apply instead.

Do we have to show allergens in the app?

In the EU, yes. For food sold at a distance, the mandatory food information must be available before the purchase is concluded. For restaurant meals, which are non-prepacked food, that means at least the allergen information, plus any extra national rules.

Are couriers employees under the new EU rules?

The Platform Work Directive creates a legal presumption of employment where facts indicate direction and control, from the national laws that transpose it by 2 December 2026. Whether your couriers are employees depends on how the work is organised and on national law. Your legal advisers decide; the software has to support either model.

Should we build our own app or use a marketplace?

A marketplace brings customers; your own app keeps the customer relationship and the margin. Many restaurant groups use both: the marketplace for discovery, their own app for regular customers and loyalty. The decision depends on how many of your orders come from returning customers.

Sources