Software to run it · food delivery business · 5 min read

Software to run a food delivery business in India

What a food delivery business needs in software: WhatsApp and sheets first, then hosted ordering and dispatch tools, and when a custom three-sided app pays.

Planning this? Ask an expert, free ↓
FullPlate food ordering app and live kitchen screen
Runs on FullPlate · Food delivery

Part of the playbook: How to start a food delivery business in India

Run the first month on WhatsApp Business, a shared sheet and a free routing map. That is enough for up to roughly 30 orders a day. Buy a hosted ordering and dispatch product when you pass that, and commission a custom three-sided app only when your rules, such as zone pricing or multi-stop batching, no longer fit what products allow.

Prices below are ballpark estimates, and product pricing changes often; check each vendor's current plan. We have not verified any vendor's price, so none is quoted by name.

What the software has to do, by job

A food delivery order touches four people and a payment, and each needs a different screen. Listing the jobs first tells you which tool category to shop for.

A planning checklist for your own requirements; add or remove rows for your model.
JobWho uses itWhat goes wrong without it
Menu and orderingEaterPhone orders with wrong items and addresses; no record of what was promised
Accept order and set prep timeRestaurantKitchen misses orders; riders wait outside
Assign rider and track locationDispatcher and riderWrong rider assigned; no one knows who is stuck
Navigate and capture proof of deliveryRiderLate drops, wrong floors, disputes about delivery
Payments, refunds and settlementsYou and your partnersWeekly restaurant payouts become an argument
Cash on delivery reconciliationRider coordinatorCash leaks between a rider's pocket and your bank
Reports: late orders, refunds by restaurant, orders per rider-hourYouYou cannot tell which part of the operation is losing money

Weeks 1 to 8: WhatsApp, a sheet and a map

Before you pay for software, learn how orders really flow. You can do that with tools you already have, for a few thousand rupees a month.

  • WhatsApp Business with a catalogue, quick replies for the order template and labels such as New, Preparing, Out and Delivered.
  • A shared Google Sheet with one row per order: time, customer, address, partner, items, amount, payment mode, rider, picked-up time, delivered time and notes. Add a second tab for rider cash.
  • Google Maps links and live location sharing for riders; a group per active rider for dispatching.
  • UPI QR codes or payment links from your bank or a payment aggregator. Reconcile each evening against the sheet.
  • A simple weekly restaurant statement built from the sheet: orders, gross sales, commission, deductions and payout.

What breaks first: duplicate orders in WhatsApp, a dispatcher who cannot see all riders at once, and the weekly settlement taking half a day. Those three are the signals to move on. If your sheet is already hard to read, you are near the limit.

When off-the-shelf stops fitting, and when custom pays

Custom software is worth the money when your operating rules are what customers and partners pay you for, and no hosted product can encode them. It is not worth it just to have your own logo on an app.

Rule of thumb: move to custom only after you can describe the rules on one page and have a few months of real orders to test them against.
SignalWhat it usually meansWhat custom would cover
You pay more in per-order fees than a monthly build budget would cost over 12 monthsVolume has outgrown a usage-based toolOwn ordering and dispatch with no per-order tax
Your pricing logic is unusual: zone-based fees, surge in rain, tiered commissions, free-delivery thresholds by areaTools allow one or two simple rulesA pricing engine and an admin to change rules without a developer
You run campus or society delivery with fixed delivery points and slotsGeneric address-based apps are clumsy for itSlot booking, pickup points and bulk drops
Riders carry multiple orders and you want smarter batchingAuto-assign picks nearest rider but not best batchBatching rules, rider load and prep-time-aware dispatch
You want an Open Bill that shows every rupee, or a restaurant-facing settlement viewTransparency is your selling pointItemised bills, commission statements and payout history for each side
You need integration with local restaurant billing systemsOff-the-shelf connectors do not existCustom order push into a specific POS or printer

A custom platform has four surfaces to build: customer app, restaurant screen, rider app and ops dashboard, plus payments and notifications underneath. A first version is typically a matter of weeks, but prices vary widely; our guide to app development costs in India and the hyperlocal delivery app guide explain the drivers. Pay attention to UPI payment handling early, since refunds and settlements are the hardest part to fix later.

The concept build and The Saral

We built FullPlate as a concept to show how the four surfaces share one order: an eater app with an Open Bill, a kitchen tablet that moves an order from New to Picked up and a rider app with zones, drops and earnings. It shows how the pieces could fit together. It is a concept, not a product with live restaurants, and it does not include your restaurants, payment gateway setup, licences, rider operations or support.

The Saral builds custom apps like this for operators who have outgrown off-the-shelf tools. If you are at that stage, see what a food delivery app involves, or send us a brief with your rules and volumes. If you are not there yet, a sheet and WhatsApp is the right answer, and you should not build before you have orders.

More on starting a food delivery business

Questions people ask

What software do I need to start a food delivery business?

Start with WhatsApp Business, a shared Google Sheet and map links for riders. That handles roughly the first 30 orders a day. Then add a multi-restaurant ordering page, a dispatch tool with a rider app and a payment gateway that supports refunds and settlements. Move to a custom platform only when your rules outgrow those tools.

Can I use a single-restaurant ordering plugin for a multi-restaurant platform?

Usually not well. Single-restaurant tools lack separate partner logins, commission rules, per-restaurant payouts and a shared rider pool. Look for products built for marketplaces or multi-vendor ordering, and test with five real partners and two weeks of orders before committing to one.

When is a custom food delivery app worth it?

When your pricing, batching or settlement rules are your edge and no product can encode them, or when per-order fees to a hosted tool exceed what a build would cost over a year. Have a few months of real orders and a one-page description of your rules first. Do not build only to have a branded app.

How do I handle restaurant payouts in software?

Record every order with gross value, commission, taxes and deductions, then generate a weekly statement per restaurant and pay it on a fixed day. Early on a sheet works; later a payment aggregator with split settlement or a dispatch product with payout reports helps. Ask your CA how commission invoices and any GST on the platform's role should be handled.

Should I join ONDC or build my own app?

They answer different needs. ONDC can bring buyers through other apps without you building a consumer app, while your own app builds a customer list you own and lets you control the experience. Many operators do a bit of both. We have not verified current ONDC terms, so read the network's published rules before deciding.

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert