Should Restaurants Charge Higher Prices on Delivery Apps?

Yes—restaurants can often charge higher prices on delivery apps, and doing so may be necessary when marketplace fees and delivery-only costs would otherwise push an item below its contribution target.

A 15–30% commission plus packaging, packing labour, and refund leakage can consume the entire margin of a dish priced for in-store sales. The right markup is not a guess. It is the price that restores the item’s target contribution after channel fees, and it should be calculated per item before it is published.

This is the pricing decision inside the complete guide to food delivery platforms. Before changing any price, audit what the channel actually costs—the true cost of food delivery commissions shows how promotions, packaging, and fees stack on top of the headline rate.

Why do delivery-app prices differ from in-store prices?

Delivery-app prices differ because the same dish costs more to sell through a marketplace. In most merchant agreements, the restaurant sets the item prices shown in the app, while the platform separately charges customers its own service and delivery fees. The restaurant’s cost to fulfil an app order—commission, processing, packaging, packing time, and refund reserves—is higher than the cost of serving the same dish at a table.

In the US, DoorDash currently lists marketplace delivery commissions of 15%, 25%, and 30%, while Uber Eats lists standard marketplace tiers of 20%, 25%, and 30%, with different rates in some markets and service configurations.

Those are market-specific examples, not a benchmark for every restaurant—your actual agreement is the number that matters—but they explain the gap: a dish priced to hit its in-store margin can contribute very little—sometimes nothing—once the channel takes its share. A higher app price is the mechanism for restoring that contribution.

How much higher should delivery-app prices be?

The markup should be high enough that each item still clears its contribution floor after percentage-based fees—and it should be calculated per item, not applied as one blanket percentage. Work backwards from the dish, not forwards from a rule of thumb:

Required app price =
  (food cost + packaging + packing labour + target contribution)
  ÷ (1 − percentage-based channel fees)

1. Start from the recipe cost. Use the current ingredient cost of the exact portion sold, including realistic yield. The guide to pricing a menu item with food cost percentage covers this baseline.
2. Add delivery-only costs. Packaging, packing labour, and expected refunds, remakes, or order-error cost belong in the calculation because they occur only when the order travels.
3. Set a target contribution. This is what the item must leave after variable costs—enough to cover its share of fixed overhead plus profit. If a target has never been set, calculating delivery-order profit shows how to build one.
4. Divide by the fee remainder. Percentage-based fees scale with the price, so dividing by (1 − fee rate) grosses the price up correctly. A 25% commission plus 3% processing means dividing by 0.72, not adding 28%. Add any fixed per-order charges or other variable costs separately rather than folding them into the percentage unless they genuinely scale with menu price. One caution: payment processing fees often apply to the total transaction value including tax and tip, not just the menu price—check the merchant statement and adjust the fee rate accordingly.
5. Round and re-check. Move the result to a natural-looking menu price, then run the contribution math again on the rounded number to confirm it still clears the floor.

If the restaurant funds app promotions, test the discounted price too. Run the calculation again using the restaurant’s actual proceeds after the discount—lower commission dollars do not necessarily compensate for the revenue given up through the promotion, so an item that clears the floor at full price can miss it during a campaign.

What does a delivery markup look like in practice?

Consider an illustrative dish with a $16.00 in-store price, $5.00 food cost, $1.40 packaging, and $1.50 of incremental packing labour. The restaurant wants $6.00 of contribution per order, and percentage-based channel fees total 28%:

($5.00 + $1.40 + $1.50 + $6.00) ÷ (1 − 0.28)
  = $13.90 ÷ 0.72
  = $19.31 → publish at $19.30

Here is what happens to the same order at each price:

At the store price copied into the app, the item leaves $3.62 before fixed costs—under the $6.00 floor. The $19.30 app price exists to cover channel costs, not to profiteer.

There is no universal delivery markup. Two restaurants paying the same commission can need very different app prices depending on food cost, packaging, labour, promotions, and the contribution they expect from delivery orders.

How do you calculate the delivery markup percentage?

Once the required app price is known, the markup percentage itself is simple:

Delivery markup =
  (app price − in-store price) ÷ in-store price × 100

($19.30 − $16.00) ÷ $16.00 × 100
  = 20.6%

This dish needs a 20.6% markup—not because 28% fees "usually" produce it, but because its specific costs and a $6.00 contribution target produce it. A dish with lower food cost or a smaller contribution target could need less; a heavily promoted or expensively packaged item could need more. Run the numbers per item rather than applying one percentage across the menu.

If the calculated app price looks too high for the market, don’t automatically accept a lower margin. Change the economics instead: remove the item, redesign the portion or packaging, bundle it, renegotiate the fee, or reserve it for direct orders. Sometimes the output of the formula shouldn’t be “charge $26”—it should be “this dish doesn’t belong on the app.”

What are the risks of charging higher prices on delivery apps?

Charging higher prices on delivery apps protects margin, but it carries real risks that deserve equal attention:

• Customer trust. Customers compare the app price against the menu on the restaurant’s website or QR code. An unexplained gap reads as overcharging, especially when the app already shows its own service fees stacked on top.
• Price-parity terms. Some merchant agreements and some local rules restrict how far app prices can diverge from in-store prices, and platforms publish their own pricing guidance—DoorDash, for example, advises merchants against large gaps versus in-store menus. Large divergences can affect store visibility in search and rankings. Check the agreement and applicable regulations before publishing.
• Conversion and order frequency. Higher displayed prices can hurt conversion before they affect repeat frequency—customers may abandon the cart when item prices look high next to the app’s own service fees. Watch order counts for a month after a change, not just per-order contribution.
• Menu drift. Two price lists go stale. When a supplier price changes or a dish is repriced in-store, the app copy is often forgotten—so the margin problem returns inside a few months. Use a restaurant menu update checklist whenever a change affects the dining-room menu, website, or delivery apps.

None of these risks argue against higher prices on delivery apps. They argue for a deliberate markup, reviewed on a schedule.

Which alternatives protect margin without a blanket markup?

Raising item prices is one lever among several. Alternatives that often work better in combination:

1. Build a delivery-only menu. A shorter menu of items that travel well, package efficiently, and are priced correctly for the channel beats marking up a fragile dish. The delivery menu versus dine-in menu guidance covers what should change.
2. Sell bundles and add-ons. A bundle spreads packaging and packing time across more revenue, lifting contribution without touching single-item prices. Drinks, sides, and desserts are the usual candidates.
3. Move repeat customers to a direct ordering channel. A direct channel can remove the marketplace commission, although payment processing, ordering software, and delivery costs may still apply. The third-party delivery versus direct ordering comparison weighs the trade-offs.
4. Audit and renegotiate the fee itself. A fee audit sometimes finds a lower tier, duplicate charges, or promotions costing more than they return—margin recovered without touching menu prices.

How should price differences be explained to customers?

Explain the difference clearly, or remove the surprise. Customers accept that delivery costs more; they resent discovering it item by item at checkout.

• Keep the owned menu current. A digital menu on the restaurant’s website shows in-store prices, so the comparison customers make is at least accurate.
• Use one plain line where the platform allows it—“app prices help cover packaging and delivery fees”—in the store description or item descriptions.
• Never recover channel costs through unclear descriptions, surprise charges, or shrunken portions. The guide to food cost percentage versus gross margin covers why quiet portion changes are a margin trap, not a pricing strategy.
• Revisit the gap quarterly. If the fee plan, promotions, or costs change, the honest price changes too.

The right delivery-app price is the one calculated from real costs and reviewed on a schedule, not copied from the dining room and forgotten.