Food delivery platforms for restaurants connect a food business with customers who want delivery or pickup, then add discovery, ordering, payment, dispatch, marketing, and support. They can create demand faster than a small restaurant can build alone, but an order is only worthwhile after food, packaging, commissions, promotions, payment fees, and labor are counted. The durable model is hybrid: use marketplaces for reach, then make direct ordering easy for repeat customers.
A marketplace is useful when a restaurant needs to be discovered by people who do not know the brand yet. A restaurant website or direct ordering page becomes more valuable when customers already know the business and need a clear route to order again. Nommy’s website builder, digital menu, and link-in-bio page can provide that owned information layer while linking customers to the delivery services already in use.
The DoorDash and Uber Eats merchant pages show why a universal commission table ages quickly: plans and channel fees vary by market. Use the local agreement—not a generic blog percentage—when checking profitability.
Quick answer: For many restaurants, a hybrid model is a practical starting point: use one or two marketplace apps to reach new customers, then make a restaurant-owned website, menu, pickup route, or direct-order link easy for repeat customers. Judge each channel by contribution after food, packaging, fees, promotions, delivery, and incremental labor—not order count alone.
| If the priority is… | Start with… |
|---|---|
| New-customer discovery | A delivery marketplace |
| Repeat orders | Direct ordering or pickup |
| No delivery staff | Marketplace or on-demand courier |
| Reach and retention | A hybrid model |
In this guide
- What are food delivery platforms and what do they actually provide?
- How do third-party delivery platforms compare with direct online ordering?
- What does a delivery order really cost?
- How should delivery-order profit be calculated?
- Should restaurants charge higher prices on delivery apps?
- What should change between a delivery menu and a dine-in menu?
- How can restaurants build more direct repeat demand?
- Which delivery metrics deserve weekly review?
- How should a restaurant choose a delivery model?
- Frequently asked questions
What are food delivery platforms and what do they actually provide?
Delivery platforms do more than display a menu. They may provide discovery, order capture, payment collection, courier dispatch, tracking, customer support, promotions, and reporting. The more work a platform performs, the more carefully the restaurant should compare its cost with the sales and labor it replaces.
Most restaurant delivery setups combine these channel types:
| Channel type | Examples | Primary value | Cost or fulfilment pattern |
|---|---|---|---|
| Delivery marketplace | DoorDash, Uber Eats, GrabFood, Deliveroo | Discovery and courier access | Commission or per-order fee; platform may fulfil delivery |
| Direct ordering | Restaurant website, ordering page, phone, or WhatsApp | Repeat demand and channel control | Payment, software, delivery, and acquisition costs |
| Delivery-as-a-service | On-demand courier or local delivery partner | Fulfilment without a marketplace listing | Per-delivery fee or agreed courier rate |
| Owned menu and website | Live menu, link-in-bio page, or restaurant site | Owned discovery and routing | Software and maintenance; ordering may happen elsewhere |
Hybrid delivery combines a marketplace with direct ordering or an owned website. Do not treat all platform work as one line called “commission”: a fee may pay for acquisition, software, payment, delivery, support, or promotion. A direct order may still require payment processing, delivery, staff time, and acquisition.
How do third-party delivery platforms compare with direct online ordering?
When comparing delivery channels, compare the contribution left by a similar order—not the headline fee alone. Third-party marketplaces are strongest at discovery; direct ordering is strongest when a customer already knows the brand. Neither channel is automatically better.
| Decision area | Third-party marketplace | Direct online ordering |
|---|---|---|
| Discovery | Strong for people searching without a specific restaurant in mind | Depends on brand, search, social, and repeat traffic |
| Ordering interface | Built and maintained by the platform | Built and maintained by the restaurant or ordering provider |
| Delivery | Often available through the platform’s courier network | Restaurant fleet, courier partner, pickup, or on-demand service |
| Main channel cost | Marketplace fee, promotions, and possible adjustments | Payment, software, delivery, and customer acquisition |
| Customer relationship | Mediated by platform terms and the marketplace experience | More control over brand, message, and next action |
| Best role | Reach new customers and test demand | Serve repeat customers, pickup, catering, and owned traffic |
The strongest pattern is often a deliberate split: keep a marketplace listing active for discovery while making the website, social profile, and direct-order link easy to find for repeat customers. The marketplace earns its cost when it brings profitable new demand; the owned channel earns its place when it makes repeat orders easier to complete.
What does a delivery order really cost?
Delivery channels should be evaluated against the complete cost of accepting an order. Start with food and packaging, then add every expense that rises because that order was accepted. The platform’s headline commission is only one line.
| Cost line | What to include | Why it matters |
|---|---|---|
| Food cost | Ingredients, recipe yield, waste, and portion cost | Shows whether the menu price covers production |
| Packaging | Containers, seals, bags, sauces, cutlery, and labels | Delivery packaging is part of the product |
| Marketplace or ordering fee | Commission, per-order charge, or software fee | The fee base may differ by contract and channel |
| Payment processing | Card, wallet, gateway, or payout charges | Direct ordering still has payment costs |
| Promotions | Restaurant-funded discounts, free items, loyalty credits, and ads | Discounted volume may contribute less than full-price volume |
| Fulfilment and labor | Courier, mileage, packing, dispatch, support, and refunds | A busy channel can change the kitchen’s staffing needs |
Separate pass-through amounts from restaurant costs. Taxes and tips may appear on a statement but are not normally revenue available for ingredients and labor. A customer-paid delivery fee may also be passed through or offset against delivery expense, so read the settlement statement and contract.
The complete restaurant food costing and menu pricing guide explains the recipe and plate-cost foundation. For channel decisions, extend that work with contribution margin—the amount left after costs that rise with the sale. The food cost percentage versus gross margin guide explains why a healthy ingredient ratio does not guarantee a healthy delivery result.
Check the first statements against the merchant agreement. Record the commission base, payment fees, promotions, refunds, payout timing, and adjustments. Keep a dated fee schedule because terms can change.
How should delivery-order profit be calculated?
Calculate contribution at the order and channel level—not from gross sales alone. Start with the revenue the restaurant actually keeps, subtract the order-specific costs, and compare the result with the time and capacity consumed.
Delivery contribution =
Order revenue kept by the restaurant
− food and beverage cost
− packaging
− marketplace or ordering fees
− payment processing
− restaurant-funded discounts and ads
− delivery fulfilment cost
− incremental delivery labor
− refunds, remakes, and other order-specific leakage
Here is an illustrative $30 marketplace order. The 25% platform fee is a learning scenario, not a universal market rate.
| Cost or revenue | Marketplace | Direct |
|---|---|---|
| Menu subtotal | $30.00 | $30.00 |
| Food cost | −$9.00 | −$9.00 |
| Packaging | −$1.50 | −$1.50 |
| Platform fee | −$7.50 | none |
| Payment processing | −$1.20 | −$1.20 |
| Promotion or acquisition | −$3.00 | −$0.50 |
| Packing labor | −$1.50 | −$1.50 |
| Delivery contribution | $6.30 | $16.30 |
The $6.30 is not final net profit. Fixed costs still need to be paid; it is the contribution available to help cover them after order-specific costs are recognized.
The direct example keeps the same food, packaging, payment, and packing-labor costs. It replaces the marketplace fee and $3 promotion with a $0.50 acquisition cost, so the contribution is $16.30 before any difference in delivery cost.
Review the calculation by item and order. A low-price dish may fail after packaging and fees; a bundle may perform better because one container and dispatch support several items.
Should restaurants charge higher prices on delivery apps?
Delivery apps can justify higher channel prices when fees materially change the order economics, but a blanket markup is not the only answer. Test the contribution at the current price first, then consider a price change, a smaller menu, better bundles, or a different fulfilment model.
Use this simplified planning formula:
Required channel price =
(food cost + packaging + fixed order costs + target contribution)
÷ (1 − percentage-based channel fees)
If food, packaging, and other fixed order costs total $12, and the restaurant wants $8 of contribution before fixed overhead, an illustrative 25% percentage-based fee produces this price floor:
($12 + $8) ÷ (1 − 0.25) = $26.67
Add payment fees, promotions, delivery subsidies, taxes, and other fee bases before publishing. Then check the agreement, local rules, and customer expectations.
| Pricing response | Benefit | Risk to check |
|---|---|---|
| Keep the same price | Simple and familiar | Contribution may fall too low |
| Use channel-specific prices | Protects the contribution target | Price rules or customer trust may limit it |
| Create a delivery menu | Removes weak or fragile items | The shorter menu still needs variety |
| Build bundles and add-ons | Raises basket value | Discounts can hide weak item economics |
| Improve direct ordering | Reduces dependence on marketplace fees | The restaurant still needs to attract and fulfil orders |
Never hide a price difference through unclear descriptions or surprise charges. Make the channel and total clear before checkout.
What should change between a delivery menu and a dine-in menu?
A delivery channel still depends on a menu designed for travel. A delivery menu should be shorter, clearer, and tested for holding time—not copied from the dine-in menu. It should protect quality and highlight items that retain contribution after channel costs.
| Menu element | Dine-in approach | Delivery approach |
|---|---|---|
| Item selection | Broad range supports browsing | Prioritize dishes that travel and fit the packaging |
| Description | Explain ingredients and preparation | Clarify portion, sides, spice level, and what arrives |
| Modifiers | Staff can explain complex choices | Keep options explicit and easy to execute |
| Photos | Show appetite and presentation | Show an honest portion that survives transit |
| Bundles | Pair items around the table | Group items that travel together and improve basket economics |
| Availability | Staff can explain substitutions | Hide sold-out items and set realistic prep times |
Run a delivery-menu audit:
- Remove dishes that become soggy, spill, or lose their intended texture.
- Cost the full pack, including container, bag, sauce, label, and extra portion.
- Simplify modifiers that cause missed selections or kitchen questions.
- Photograph the delivered portion rather than the ideal plated version, and update availability, hours, and service areas when operations change.
A mobile digital menu can keep categories, prices, photos, dietary details, and availability structured while the delivery platform remains the transaction channel. The digital menu optimization guide covers the menu work behind it.
How can restaurants build more direct repeat demand?
Marketplace listings are useful for discovery, but a restaurant should not make a paid app the only place customers can find the brand. Build a useful home outside the app without violating marketplace rules or treating platform data as a direct marketing list.
Use this sequence:
- Create one reliable destination. Put the website or link-in-bio page on social profiles, Google Business Profile, packaging, receipts, and staff messages where appropriate.
- Make paths obvious. Show the menu, pickup, delivery apps, direct ordering, phone, map, hours, and catering contact as separate actions.
- Give direct ordering a reason. Pickup convenience, scheduled orders, a fuller menu, catering, or permission-based loyalty benefits can be more sustainable than permanent discounts.
- Use packaging responsibly. Add a branded card or QR code only where the agreement and local rules permit it, and collect future email, SMS, or loyalty contacts through explicit opt-in—not scraped marketplace data.
A branded link-in-bio page can route customers to the preferred delivery app, live menu, map, WhatsApp, reservations, or direct ordering. A restaurant website gives the business a fuller home for search and repeat visits.
Which delivery metrics deserve weekly review?
Weekly reporting should show contribution, reliability, and customer behavior—not just order count. Separate promotions from organic demand and compare the same period and channel.
| Metric | Simple calculation | Question it answers |
|---|---|---|
| Orders by channel | Count orders by marketplace, direct source, pickup, and phone | Where is demand coming from? |
| Net channel sales | Revenue minus refunds, discounts, and pass-through amounts | How much sale value remains to analyze? |
| Contribution per order | Channel contribution ÷ completed orders | Does the average order help cover fixed costs? |
| Contribution margin | Channel contribution ÷ net sales × 100 | Which channel keeps the stronger share? |
| Average order value | Net sales ÷ completed orders | Are bundles and add-ons building useful baskets? |
| Cancellation and refund rate | Cancelled or refunded orders ÷ accepted orders × 100 | Where are failures occurring? |
| Direct repeat rate | Returning direct customers ÷ identifiable direct customers | Is the owned channel becoming more useful? |
Each week, reconcile the statement with the order export and payout, cost the five most ordered items, and choose one change to test. Review four-week patterns before deciding.
How should a restaurant choose a delivery model?
The right delivery model depends on demand, geography, menu, staff capacity, and repeat traffic. Choose the simplest setup that performs the required job while leaving a measurable contribution.
Use this five-question delivery test before adding or changing a channel:
- Does it create demand the restaurant would otherwise miss?
- What contribution remains after every order-specific cost?
- Can the kitchen fulfil it without harming dine-in service?
- Do the menu items survive delivery well?
- Does the channel strengthen or weaken repeat customer access?
If demand is high but contribution is weak, change pricing, menu, promotions, or fulfilment before deciding the platform itself is the problem. Read the commercial terms, model a representative order, and keep the website, live menu, hours, pickup information, and ordering links accurate.
Nommy can support the owned information layer without replacing the delivery provider: use a live digital menu, restaurant website, and delivery links for the routes already in use.
Ready to give delivery customers one clear place to find the menu and ordering links? Start free with Nommy and build the restaurant website and digital menu around the delivery channels already in use.
Frequently asked questions
Are food delivery platforms for restaurants worth it for small businesses?
They can be worthwhile when they bring profitable incremental demand, fill unused capacity, or provide delivery without a restaurant fleet. They are not worthwhile when promotions, low-contribution items, packing time, and refunds are ignored. Review contribution per order alongside gross sales.
What is a reasonable delivery-platform commission?
There is no universal reasonable rate. The useful rate is the one the order economics can support after food, packaging, payment, promotions, labor, refunds, and fixed overhead. Compare the complete statement and the customers, coverage, support, and marketing included.
Should delivery menu prices be higher than dine-in prices?
Sometimes. A higher channel price can protect contribution when a marketplace fee changes the economics, but it must follow the merchant agreement, local rules, customer expectations, and the restaurant’s positioning. Removing weak items or building bundles may solve the problem better.
Can a digital menu replace a food delivery platform?
A digital menu can replace a static PDF as the place where customers browse current items, prices, photos, and dietary details. Delivery platforms still handle ordering, payment, dispatch, or courier support; the menu can act as the owned front door and link to the preferred provider.
Use marketplaces when their reach is worth the cost, keep an owned channel ready for repeat demand, and measure both with the same order-level economics.