Key takeaways
- Mobile ordering is mainstream: 57% of US adults have recently used it, so a phone-first ordering page is the baseline.
- Pick the system by how it connects to your POS and kitchen, not by its feature list.
- Most launch problems come from the menu build: modifiers, prep times and item availability.
- Run at least a week of staff test orders across dayparts before you announce it to guests.
Why start online ordering now
Off-premises is no longer a side channel. Nearly 75% of US restaurant traffic now happens off-premises[1], and 57% of adults have recently used mobile ordering, including 74% of millennials and 65% of Gen Z adults[2]. Guests who cannot order from your website on a phone will order from someone else's, or from a marketplace that takes a commission on every ticket.
Starting your own ordering does not have to be a big technology project. For most independent restaurants it is a four-week job: choose a system, build the menu properly, set the kitchen rules, test hard and then launch quietly. The order below matters, because most failed launches skip the menu build and the testing.
Week 1: choose the ordering setup
There are three common setups. The right one depends mostly on your point-of-sale system and how much you want orders to flow straight to the kitchen without anyone re-keying them.
| Setup | How it works | Best for | Watch out for |
|---|---|---|---|
| Ordering built into your POS | The POS provider's own online ordering page, sharing the same menu and printers | Restaurants happy with their POS and wanting the least moving parts | Design limits and the POS provider's processing terms |
| Independent ordering platform integrated with the POS | A separate ordering provider that sends tickets into your POS | Restaurants wanting better design, loyalty or multi-location control | Menu sync gaps and an extra vendor to call when it breaks |
| Marketplace storefront | A branded ordering page run by a delivery marketplace | Restaurants already on that marketplace wanting quick setup | Who owns the guest data, and the fees on direct orders |
Use five questions to decide. Does it print or display on your kitchen screens without re-keying? Can it pause items and change prep times in seconds? Does it give you guest names, emails and order history to keep? What does it cost per order, including payment processing? And who do you call at 7 pm on a Friday when it stops working? Write the answers down for each option and pick the one with the fewest "no" answers on the first two.
Three-quarters of delivery customers value tech-enabled ordering and payments[3], so the guest side should be simple: a fast menu page, saved cards and wallet payments, clear pickup times and order status. You do not need a dedicated app to start. For the trade-offs, see our comparison of first-party and third-party ordering.
Week 2: build the menu properly
The menu build is where most of the work is, and where most guest complaints start. A dine-in menu is written for a server who can answer questions. An online menu must answer them itself.
Start from what travels
Leave off dishes that fail after 20 minutes in a box. Fewer, better items beat a full copy of the dine-in menu.
Write short, specific item names and descriptions
Say what the dish is, the portion and anything surprising, such as spice level or that it comes with one side.
Build modifiers as required choices
Make temperature, side and sauce choices required where the kitchen needs them, so tickets never arrive incomplete.
Price modifiers correctly
Extra protein, substitutions and add-ons should carry a price where they cost you food.
Flag allergens and dietary notes
Use consistent tags and add a notes field with a character limit, plus a line asking guests with allergies to call.
Add photos for the top sellers
Clear, well-lit photos of the dishes that sell most, shot from the angle the guest will see in the box.
Set categories in the order people decide
Popular and combos first, then mains, sides, drinks and desserts.
Ask a server who did not build the menu to order five items as a guest would. Every question they ask is a gap in the descriptions or modifiers.
Week 3: set kitchen rules before guests see it
Online orders arrive in bursts, and a ticket that lands at 7:15 with a 15-minute quote can wreck a full dining room. Decide the operating rules first.
- Prep times by daypart: a default quote for quiet periods and a longer one for peaks, which a manager can extend from the tablet or POS.
- Order throttling: a cap on orders or items per 15-minute window so the line is not buried. See throttling online orders on busy nights.
- Item availability: who marks items sold out, and how quickly, so guests do not pay for a dish you cannot make.
- Ticket routing: which printer or screen online tickets hit, and how they are marked so expo can tell them from dine-in.
- Pickup point: a labeled shelf or counter, with the order name and number on every bag.
- Hours: online ordering should close before the kitchen does, so late tickets do not force the line to stay open.
Speed is the expectation guests bring. 94% of consumers say speed is critical when ordering off-premises[4], so a realistic quote that you hit beats an optimistic one you miss.
Decide prices, fees and tips for your own channel
Settle the money questions before launch so the menu build does not stall halfway. Most restaurants keep direct online prices the same as the in-store menu, because the point of your own channel is to be the best-value way to order. If you add a small service or packaging fee, show it on the menu and at checkout, not only on the receipt, and use the same wording everywhere.
Decide how tips work as well. Will guests be prompted to tip on pickup orders? Who receives those tips, and how do they reach payroll? A clear answer avoids awkward conversations with staff later.
Then set delivery rules if you plan to deliver yourself or through an on-demand courier: a delivery radius, a minimum order and a delivery fee. Start small. It is easier to widen a radius after a month of on-time deliveries than to win back guests whose food arrived cold.
Finally, decide who handles problems. Online guests will call about late orders, missing items and refunds. Give phone staff access to the order screen, a short refund rule and the authority to issue a credit on the spot, and write the pickup instructions in the confirmation so the most common call, "where do I collect my order?", never needs to happen.
Week 4: test orders, then a soft launch
Do not announce the launch until staff have placed real orders across every daypart. Test orders find the gaps a menu review cannot: a modifier that prints in the wrong place, a tax rate that is off, a sold-out item that still shows.
Place 20 or more staff test orders
Use different phones, browsers, payment methods and order times, including the busiest hour of your week.
Check every ticket in the kitchen
Does each modifier print clearly? Are notes visible? Does the quote match reality?
Reconcile one day of orders
Match orders, payments, tips, taxes and refunds against the POS and the payout report.
Test failure modes
Mark an item sold out mid-order, pause ordering, issue a refund and cancel an order, and confirm each works.
Soft launch to regulars
Tell your mailing list or loyal guests first, watch a week of orders and fix what you find.
Announce widely
Add the link to your website header, Google Business Profile, social profiles, receipts and table cards.
Example: a fictional neighborhood taqueria runs 25 test orders and finds that the "no cilantro" modifier prints below the line where cooks look, that taxes are not applied to delivery fees as its accountant expects and that the pickup time ignores Friday's rush. All three are fixed before a single guest orders.
Make it work on the phones your guests use
91% of US adults own a smartphone[5], and 16% are smartphone-only internet users without home broadband[6]. That makes the phone experience the whole experience for many guests. Check that the menu loads quickly on a mid-range phone on mobile data, that buttons are big enough to tap, that the guest can pay with a saved wallet and that the confirmation says exactly where and when to pick up.
Full-service guests are comfortable with this too: 63% are comfortable using a smartphone app to place an order[7]. If your guests are older or less online, keep the phone line open for orders and make the online link easy to text to someone who asks.
Measure the first 30 days
Pick a few numbers and look at them every week after launch:
- Orders per day and average ticket, by daypart.
- Share of orders arriving within the quoted time, checked at the pickup shelf.
- Refunds and remakes by reason, especially missing items and wrong modifiers.
- Repeat rate: how many guests order a second time within 30 days.
- Calls to the restaurant about online orders, which shows where the menu or confirmation is unclear.
If you also sell through marketplaces, compare margins channel by channel. Our guides to delivery app commissions and pricing menu items on delivery apps cover how to set those prices once your own ordering is running.
Frequently asked questions
How do I set up online ordering for my restaurant?
Choose a system that connects to your POS, build an online menu with required modifiers and accurate prices, set prep times and order limits, run staff test orders across every daypart, then soft launch to regulars before announcing it widely.
Do I need an app for online ordering?
No. A fast mobile ordering page linked from your website and Google profile is enough to start. A branded app makes sense later if you have frequent repeat guests and a loyalty program.
How long does it take to start online ordering?
For a single independent restaurant, about four weeks is realistic: a week to choose a system, a week to build the menu, a week for kitchen rules and a week of testing.
What is the most common online ordering mistake?
Copying the dine-in menu without required modifiers, realistic prep times or a way to mark items sold out. Those gaps cause most wrong orders, late pickups and refund requests.
References
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
National Restaurant Association (2024). Restaurant Technology Landscape Report 2024 (opens in a new tab) ↑