Should a restaurant build its own ordering app or use delivery marketplaces?
For most independent restaurants and small groups, the answer is both, with a clear job for each. Marketplaces are for discovery: they put you in front of people who have never ordered from you. Your own ordering channel is for repeat customers: it keeps their contact details, their order history and more of each sale. A fully custom app makes sense once repeat orders, catering or several locations make the off-the-shelf tools feel tight.
The mistake we see most is treating this as one decision. It is really three: where orders come from, who delivers them, and which systems the order has to reach once it is placed.
What do delivery marketplaces actually cost?
Commission is the main cost, and it is charged on the order subtotal. DoorDash's US merchant pricing page lists three plans: Basic at 15%, Plus at 25% and Premier at 30% on delivery orders, with pickup at 6% on all plans (DoorDash). On a $40 delivery order, that is $6 to $12 before food, packaging and labor. The higher plans buy more visibility and customer perks, so the right tier depends on how much new demand you actually need.
Some cities cap these fees. In New York City, the Administrative Code limits a third-party delivery fee to 15% of each online order, other fees to 5% combined, and the transaction fee to 3% unless the platform can show its own processing cost is higher (NYC Admin. Code § 20-563.3). Check whether your city has similar rules before you compare plans.
What do you get from your own ordering channel?
The biggest gain is the customer relationship. When someone orders on your site or app, you hold the name, email, phone number and full order history. That is what lets you run a loyalty program, send a reorder reminder or tell regulars about a new menu. On a marketplace, the platform owns that relationship and decides what you can see.
You also control the menu, the photos, the pricing and the checkout. The costs move rather than disappear: payment processing, hosting, development and, above all, the marketing it takes to send people to your channel instead of an app they already use. Even DoorDash notes that orders through its own online ordering product are commission-free but still carry a payment processing fee.
Who delivers orders placed on your own app?
You have three practical options:
- Your own drivers. Full control of the experience, but you carry scheduling, payroll, vehicle insurance and slow nights.
- On-demand couriers through an API. Your app sends the order to a delivery network, which dispatches a driver. DoorDash Drive On-Demand, for example, lists a flat fee of $6.99 to $10.99 per delivery order, with tips passed to the driver (DoorDash Drive On-Demand).
- Pickup only. The simplest start, and often the best margin.
A flat fee per delivery behaves very differently from a percentage. It costs more on a small order and much less on a large catering order, so run your own average ticket through both before you choose.
Should you buy an ordering platform or build a custom app?
Start with what you can buy. Many POS systems and ordering platforms handle a single-location menu, payment and pickup well, and they are quick to launch. We suggest a custom build when your needs look like these:
- Several locations or brands sharing one kitchen, with different menus and hours.
- Catering, scheduled orders or large group orders with deposits.
- Loyalty and offers that must live in your CRM, not inside a vendor's tool.
- Complex modifiers, allergens or build-your-own items that generic menus handle badly.
- Orders that must flow into inventory, accounting and reporting without retyping.
It is the same trade-off retailers face with ecommerce platforms. Our guide on Shopify vs custom ecommerce walks through that thinking in more detail.
What should your ordering system connect to?
An ordering app is only as good as what happens after the customer taps "Place order." Before you build or buy, list the systems each order must reach:
- POS and kitchen display, so orders print or appear without staff retyping them.
- Menu and availability, so a sold-out item disappears everywhere at once.
- Payments, using your processor's hosted payment fields so card data never touches your own servers.
- Delivery dispatch, sending address, ready time and order details to your courier.
- CRM and email, so every direct customer joins your list with consent.
- Accounting, so sales, fees and tips reconcile without spreadsheets.
If you already sync sales into your books, our post on QuickBooks CRM integration covers what to connect first.
How do you move customers from marketplaces to your own channel?
Read your marketplace agreement first, because some terms limit pricing and promotions. DoorDash's pickup rate, for instance, depends on pickup menu prices matching in-store prices. Within those rules, the levers you control are simple: signage and receipts in the restaurant, an order link on your Google Business Profile and website, loyalty rewards that only apply to direct orders, and a fast checkout that remembers returning customers. The goal is not to leave the marketplaces. It is to make sure your best regulars order direct.
What should you decide before you start?
- Your current split of dine-in, pickup and delivery, and your average ticket.
- Which marketplace plan you are on and what it costs per order.
- Who delivers direct orders: your staff, a courier API or no one.
- The systems every order must reach, from POS to accounting.
- Whether a ready-made platform covers all of that, or only part of it.
- How you will send customers to your own channel and measure it.
Frequently asked questions
Usually not at first. A good off-the-shelf ordering tool tied to your POS covers most single-location needs. Custom work pays off when you add locations, catering or loyalty that the tool cannot handle.
Start with a fast mobile web ordering site. It works for every customer without a download. A native app makes sense later, when regulars want saved orders, push notifications and quicker reordering.
Yes. Services such as DoorDash Drive On-Demand let your site or app send an order through an API and pay a flat fee per delivery, while the customer orders from you.
It depends on scope. A first version with menu, checkout, pickup and one delivery integration is a much smaller project than multi-location catering with loyalty and accounting sync. Scope the first release tightly and add from there.
Sources
- DoorDash: Commission rates and pricing
- DoorDash: Drive On-Demand
- New York City Administrative Code § 20-563.3, fee caps for third-party food delivery services
Planning your own ordering app?
We design and build ordering apps that connect to your POS, delivery partners, CRM and accounting, so every order lands where it should without retyping.
See application development
