Most online-ordering advice is written for restaurant groups. Multiple locations, a marketing person, an ops manager who lives in dashboards. If you run one place and also work the line three nights a week, a lot of that advice is just noise. You need the short version that fits between the lunch rush and prep.
So here's the one-location playbook. It assumes you, one kitchen, and not much spare time.
Start smaller than the guides tell you
The big write-ups want you to launch pickup, delivery, loyalty, gift cards, and a branded app all at once. Don't. For a single location, the version that actually works is almost embarrassingly small:
- Your menu, online, on your own web address.
- Pickup only, to start.
- Card payment landing straight in your account.
No delivery zones to draw, no driver to schedule, nothing for customers to download. Pickup is the highest-margin order you can take, it has zero logistics, and it's the fastest piece to get right. Get that one loop clean and busy before you bolt anything else on.
The menu is the slow part, not the technology
Owners expect the tech to be the hard bit. It almost never is. The part that eats a week is the menu: real photos, prices that match what you charge today, and modifiers that match how people actually order. No onions. Extra cheese. Dressing on the side.
Here's something you can do this afternoon without paying anyone. Open a plain spreadsheet and list every item with three columns: exact price, every modifier a customer might ask for, and honest prep time. That sheet is most of your setup, and it's the thing you can hand to whatever ordering tool you pick.
We've watched more small-restaurant launches stall on a missing "no pickles" option than on anything technical. A customer who can't order it the way they eat it just closes the tab, and you never see the sale that didn't happen.
What a one-location shop does not need
A single location can skip most of the enterprise checklist, and skipping it is the point:
You don't need multi-location menu syncing, regional pricing, or a franchise dashboard. You don't need a native app in the App Store on day one. A fast ordering page on your own domain does the same job, and a phone bookmarked to your menu behaves like an app without the download friction. You don't need to draw a delivery map before you've taken a single pickup order.
The honest boundary: once you're genuinely slammed, running two locations, or your staff can't keep up with the pickup pace, that's when the extra machinery starts earning its keep. Before that, it's cost and complexity you'll pay for and won't use.
Adding delivery later, and who should drive
When pickup is steady and you're ready for delivery, keep it boring. For a tight radius, your own staff on a slow shift is often cheaper than any commission. Past that radius, an on-demand driver service you pay a flat fee per run beats handing a marketplace a cut of every order forever.
Set a delivery minimum that covers the driver cost, cap the radius at what your food survives (fries don't travel 25 minutes), and turn it off during your busiest 90 minutes if the kitchen can't carry both. Delivery should add profit, not chaos.
Keeping the customer is the actual win
The reason to own your ordering isn't only the commission you save per order, though that adds up fast. It's the list. Every direct order gives you a name, a phone number, and what that person likes to eat. A one-location restaurant that knows its regulars can fill a dead Tuesday with a single text. A restaurant that rents all its customers from an app is one algorithm change away from a rough month.
You don't have to break up with the delivery apps to do this. Treat them as a discovery channel, a way for new people to try you once. Then win the second order onto your own page: print your direct link on every bag and receipt, and give one small, specific reason to switch, like free delivery over a set amount or a perk on their next pickup. Marketplaces to get found, your own ordering to keep them.
If you want the longer version of the setup itself, we wrote a full walkthrough on how to set up restaurant online ordering. And if you'd rather see what a branded ordering setup looks like for a single location, take a look at Eatz, our restaurant ordering product. Plans are on the pricing page, and everything launches commission-free.
Frequently asked questions
Do I need delivery to launch online ordering at one location?
No. Start with pickup only. It's the fastest to set up, has the best margin, and has no driver logistics. Add delivery once pickup is running smoothly and you actually want the extra volume.
How long does it take a small restaurant to go live?
The menu is the slow part, not the software. If your photos, prices, and modifiers are ready, a branded ordering page can go live in days. Most of the wait is you finalizing how items are priced and what modifiers to offer.
Is online ordering worth it for a small or single-location restaurant?
Yes, mainly because you keep the customer relationship and stop paying a per-order cut. Even at modest volume, the flat cost of your own ordering beats a commission that grows every time you sell more.
Should I still use DoorDash or Uber Eats?
Use them to get discovered by brand-new customers, but move your regulars to your own ordering, where each order costs you nothing extra and the customer's details are yours. Running both is fine; letting the apps keep your repeat business is the expensive mistake.
Do I need a mobile app for customers to download?
Not at first. A fast ordering page on your own domain does the same job, and customers can bookmark it to their home screen so it opens like an app. A native app is worth revisiting later, once you have steady repeat orders to justify it.