Sign in Subscribe
8 min read

Delivery Apps Take 15% to 30% of Every Order. Build a Direct Ordering and Loyalty Channel Instead (HighLevel)

Restaurant delivery app commission runs 15% to 30% per order. This HighLevel for restaurants build puts an order form with payment, an SMS loyalty list, a birthday workflow and review automation on your own number, so repeat guests order direct and you keep the margin.

TLDR

  • According to DoorDash Merchants pricing, delivery commission is 15% on Basic, 25% on Plus and 30% on Premier, plus 6% on pickup orders.
  • The apps own the guest's name, phone and order history. You own the kitchen.
  • GoHighLevel gives the restaurant an order or reservation form with payment on its own domain.
  • A QR code on tables and takeout bags grows an SMS loyalty list that gets one offer a week.
  • A birthday workflow fires from a custom date field. A review request follows every visit.
  • The WhatsApp add-on handles group bookings for $10/month per sub-account.
  • HighLevel is not a POS or a delivery fleet. It owns the customer list and the direct channel. The build fits inside the 30-day free trial.

Who This Is For

  • Restaurant owners watching up to 30% of every app order leave before food cost.
  • Operators with regulars who order through an app because they do not know another way.
  • Restaurants with slow Tuesdays and no list to text.
  • Venues taking group bookings by phone and missing the calls during service.
  • Agencies serving hospitality clients who want a HighLevel for restaurants Snapshot with the loyalty engine built.

The Restaurant Delivery App Commission Problem

Restaurant delivery app commission is not a marketing cost. It is a tax on regulars. According to DoorDash Merchants pricing, delivery commission is 15% on Basic, 25% on Plus and 30% on Premier, plus 6% on pickup orders. Restaurant Business Online describes the wider market the same way: rates usually start at 15% for basic services like delivery and a marketplace listing, and scale up to 30%.

Here is the cost chain when regulars order through the app.

  • A guest eats in on Friday. Leaves without giving a phone number.
  • Tuesday, the guest wants the same dish. Opens the app. Orders.
  • The app takes its commission. The restaurant makes the food.
  • The app sends the guest a promo next week. For a competitor.
  • The guest's order history, phone number and birthday live in the app.
  • The restaurant cannot text that guest. It cannot thank them. It cannot fill Tuesday.

The app did the marketing. The restaurant paid for it. The guest belongs to the app.

Why Loyalty Programs Fail

  • Paper stamp cards get lost.
  • The email list gets built and never used.
  • Birthday offers depend on a manager remembering.
  • Reviews are asked for at the till, in a rush, by whoever is nearest.
  • Group booking calls arrive during service and go to voicemail.

The fix is a direct channel the restaurant owns. A form. A number. A list.

What HighLevel is not. It is not a point of sale. It does not manage a kitchen display, a delivery fleet or tips. It owns the guest record and everything sent to it. The POS stays. The apps can stay for new customers. The regulars move.

What GoHighLevel Sets Up

Six components. Together they are a direct ordering and loyalty channel.

  1. Order or reservation form with payment. A Sites > Forms page on the restaurant's own domain. Guests pick items or a table time, pay by card and get a confirmation text. Why it matters: a direct order carries no app commission. Example: "Order for pickup: two Pad Thai, one Green Curry, $48. Pay now, ready in 25 minutes." Impact: the margin on regulars' orders stays in the restaurant.
  2. SMS loyalty list with weekly offers. Guests join by texting a keyword or scanning a QR code. One offer a week, sent from the restaurant's number, timed for the slow night. Why it matters: the restaurant can fill Tuesday without paying an app to do it. Example: "Tuesday is taco night. Show this text for a free side. Order direct here." Impact: slow nights get a lever the restaurant controls.
  3. Birthday workflow via custom date trigger. The join form asks for a birthday. A custom date reminder fires a set number of days before it with an offer and a booking link. Why it matters: birthday tables are large tables. Example: "Your birthday is next week. Book a table for the group and dessert is on us." Impact: the highest-value booking of the year arrives on a schedule.
  4. Google review automation. After a paid order or a seated reservation, Reputation sends a review request. Why it matters: the request lands while the meal is fresh, not when a manager remembers. Example: "Thanks for dining with us tonight. Would you leave a quick Google review?" Impact: reviews arrive on a rhythm, from guests who just ate.
  5. WhatsApp add-on for group bookings. The $10/month per sub-account WhatsApp add-on connects the restaurant's number to the Conversations inbox. Group organisers send the headcount, dietary needs and time in one thread. Why it matters: group bookings are the calls most likely to be missed during service. Example: a hen party organiser sends "14 people, Saturday 8pm, two vegans" and gets a confirmed booking back. Impact: the largest bookings stop depending on a phone being answered.
  6. QR code on tables and takeout bags. Every table tent and every bag carries a QR code that opens the join form. Why it matters: the guest is already in the restaurant or holding its food. That is the moment to ask. Example: "Scan for a free dessert on your next visit." Impact: the list grows from guests the restaurant already won.

Keep it short. One offer per text. One link.

For agencies: the order form, join form, custom fields, weekly offer template, birthday workflow and review workflow go into one Snapshot. Every restaurant client gets the same channel. Only the menu, the offer and the QR artwork change.

Niche Starting Point

HighLevel publishes a Steakhouse Playbook bundle for restaurants. It ships pre-built forms, workflows and page templates you can load into a fresh account and adapt to the setup below. Start the account from the 30-day link at the end of this post rather than the bundle page's own trial button. The trial is longer and the bundle loads the same way.

Step-by-Step Setup

  1. Settings > Phone Numbers. Buy a local number. Complete A2P 10DLC registration so loyalty texts reach US guests. Enable missed call text back in Phone System settings for booking calls missed during service.
  2. Payments > Integrations. Connect Stripe. The order form and reservation deposits bill through it.
  3. Settings > Custom Fields. Create Birthday (date), Favourite Dish (text), Dietary Notes (text), Last Order Date (date) and Join Source (dropdown: table, bag, website).
  4. Settings > Tags. Create tags: loyalty-list, ordered-direct, reservation, group-booking, review-requested, birthday-sent.
  5. Sites > Forms, join form. Fields: first name, mobile, birthday, SMS consent checkbox. Set the redirect to a thank-you page with the first offer.
  6. Sites > Forms, order form. List the pickup menu with prices. Add a payment element. Set the confirmation message with the ready time. Build a separate reservation form with date, time, party size and a card deposit if the restaurant takes one.
  7. QR codes. Generate a QR code for the join form link. Add it to table tents, the takeout bag sticker and the receipt footer.
  8. Automation > Workflows, join. Trigger: form submitted, join form. Actions: apply loyalty-list, set Join Source, send the welcome text with the first offer.
  9. Automation > Workflows, order confirmation. Trigger: form submitted, order form, payment received. Actions: apply ordered-direct, set Last Order Date, send the confirmation text, notify the kitchen by internal notification or email. Wait 3 hours, send the review request through Reputation.
  10. Automation > Workflows, weekly offer. Build the offer as a reusable SMS template. Send it as a bulk action to the loyalty-list tag each week or schedule it in Marketing > Campaigns for the slow night.
  11. Automation > Workflows, birthday. Trigger: custom date reminder on Birthday, 7 days before. Actions: send the birthday offer with the reservation form link, apply birthday-sent. Wait 4 days. If no reservation, send one reminder.
  12. Reputation. Connect Google Business Profile and the Facebook page. Set the review request template.
  13. WhatsApp. Enable the WhatsApp add-on on the sub-account at $10/month plus usage. Connect the restaurant's number. Route group booking enquiries to the Conversations inbox with a group-booking tag.
  14. Test. Join the list with a test number. Place a test order. Confirm the confirmation text, the kitchen notification and the review request. Set Birthday to 7 days from now and confirm the workflow fires.

Compliance notes. Register A2P 10DLC before the first loyalty text. Collect SMS consent on the join form and store it. Include opt-out wording in the welcome text. Send weekly offers at consistent times and honour opt-outs immediately.

Revenue Model

Every number below is illustrative. Replace with your own.

Item Illustrative example
App orders per month Say 400
Average order value Say $40
App commission at say the 30% Premier rate $40 x 30% = $12 per order
Orders moved to the direct form per month Say 100
Illustrative commission kept per month, before card processing 100 x $12 = $1,200
Loyalty list size after say 3 months of QR codes Say 600 guests
Extra covers from the weekly Tuesday offer Say 20 at say $35 = $700
Birthday bookings per month Say 5 tables at say $200 = $1,000
HighLevel Starter plan plus WhatsApp add-on $97 + $10 = $107/month

These are worked examples, not study findings. Your order volume, ticket size and list growth will differ.

For agencies reselling this setup. Sell the restaurant Snapshot in SaaS Mode with Stripe rebilling. Illustrative pricing is $297-$497/month per venue. Say 10 venues x $297 = $2,970/month. Marked-up rebilling of SMS, email and AI usage requires the Agency Pro plan at $497/month. See SaaS Mode explained.

FAQ

Can HighLevel replace DoorDash or Uber Eats? No. HighLevel does not run a delivery fleet or a kitchen display. It gives the restaurant a direct order form with payment and an SMS list, so regulars can order without the app commission.

Does HighLevel work as a restaurant POS? No. The POS stays for in-house orders and tips. HighLevel holds the guest record, takes direct orders and reservations by form and sends every text, email and review request.

How do guests join the SMS loyalty list? They scan a QR code on the table tent or the takeout bag. Texting a keyword to the restaurant's number works too. The join form asks for a name, mobile, birthday and SMS consent.

Which HighLevel plan does a restaurant need? The $97 Starter plan covers forms with payment, workflows, Reputation and the custom date trigger for a single venue. The $297 Unlimited plan suits restaurant groups and agencies serving several venues.

Is there a free trial? Yes. HighLevel offers 30 days free. You can build the order form, the join form and the birthday workflow inside the trial and print the QR codes before paying.

How much does WhatsApp cost in HighLevel? The WhatsApp add-on is $10/month per sub-account plus usage. It connects the restaurant's number to the Conversations inbox for group booking threads.

Can I take a deposit on reservations? Yes. Add a card payment to the reservation form or attach a partial payment to a calendar booking. The deposit is collected at booking time.

Do I need A2P 10DLC registration to text guests? Yes, for US numbers. Register in Settings > Phone Numbers before the first offer goes out. Unregistered messages get filtered by carriers.

Put the QR Code on the Bag This Week

For the wider hospitality build including reservation reminders and no-show follow-up, read GoHighLevel for restaurants: own your guest list and fill slow nights.

The join form and the order form take an afternoon. You get 30 days free to grow the list before the next app invoice.

✅ HighLevel 30-Day Free Trial

Claim Your Free Month

What's New in GoHighLevel

  • Sept 4, 2026, Phone System. Missed call text-back now automatically selects an eligible sending number when the originally called number cannot send SMS. A restaurant whose main booking line cannot text still gets the text back sent from a number that can.
  • Sept 3, 2026, Phone System. Carrier fees for Verizon and other providers increase effective Oct 1, 2026. A restaurant sending a weekly offer to a growing list should budget for slightly higher per-message costs from October.