A restaurant owner asked us last month why her new website, built with a well-known drag-and-drop tool, wasn't bringing in any online orders. The site looked great. Nice photos, a clean menu page, a contact form. It just didn't have a single button that let anyone actually buy anything.
That's the gap nobody explains before you buy a website builder plan. It builds a brochure. If you want orders, you need something that processes them.
What a website builder is actually for
A website builder (Squarespace, Wix, and the restaurant-specific ones that resell the same idea) is good at exactly one job: making your business look legitimate to someone who just heard about you. Hours, location, a phone number, photos of the food, maybe a PDF menu. If a customer's next move is to call you or walk in, a website builder does that job fine, and cheaply.
What it doesn't do is take a payment, hold a menu with modifiers and real-time item availability, or remember that the same customer ordered from you three times last month. Those aren't small missing features. They're the entire other product category, called an ordering system, and most website builders either don't offer it or bolt on a clunky version that still routes the order through email or a fax-style printer in the back.
The one-question test
Here's something you can check today without paying anyone: open your current site on your phone and try to place an order for yourself, start to finish, using only your thumbs. Time it.
If you can't get through checkout, or you get bounced to a third-party app that isn't yours, you have a website, not an ordering system. If it takes more than about 90 seconds and doesn't save your info for next time, you have an ordering system that's fighting you. Either way, that's the actual problem to fix, not the color of your homepage banner.
Where the money actually is
We've built ordering flows for restaurants that had beautiful, professionally-designed websites doing zero online revenue, and ugly, bare-bones ordering pages doing six figures a year. The design mattered a lot less than whether the button worked.
The reason is simple: a website builder is a cost. An ordering system is where the transaction happens, which means it's the one piece of your online presence that pays for itself. Every order taken directly instead of through a delivery marketplace keeps the commission in your pocket and puts the customer's name, phone number, and order history in a list you own. A pretty homepage can't do either of those things.
The honest boundary
If you're a single-location shop that mostly relies on walk-ins and phone orders, and online ordering is a small side of the business, a basic website builder page might genuinely be enough for now. Don't rebuild something that isn't broken. The upgrade earns its keep once online orders are a real chunk of revenue, or once you're tired of paying delivery-app commissions on orders you could take yourself.
And you don't have to pick one over the other forever. Most restaurants end up running both: a simple info page for people who just want your hours and address, and a dedicated ordering flow for people ready to buy. The mistake is assuming the first one does the second job.
Setting it up without starting over
You don't need to throw out your existing site to fix this. Point your ordering button (or a new one) at a branded ordering page, keep your current homepage for hours and directions, and link the two together. Customers coming from Google or your socials land on ordering; customers who just want to know if you're open tonight land on the info page.
If you want the full setup walkthrough, from menu to first order, we wrote one here: how to set up restaurant online ordering. For the product itself, take a look at Eatz, our commission-free restaurant ordering system. Plans are on the pricing page.
Frequently asked questions
Can't I just add an order button to my website builder site?
Some let you embed a basic cart, but most route the order through email or a generic checkout that doesn't handle modifiers, real-time menu changes, or repeat customers well. It works in a pinch, not as a real ordering system.
Do I need to replace my whole website to get proper ordering?
No. Keep your existing site for hours, location, and photos, and link it to a dedicated ordering page. You don't have to rebuild anything that's already working.
Which matters more for a new restaurant, a nice website or online ordering?
Ordering, if you want online revenue. A website without ordering is a digital business card. It looks fine, but it can't take a sale.
How do I know if my current setup is actually costing me orders?
Try to order from your own site on your phone. If checkout is slow, confusing, or bounces to a marketplace app, customers are almost certainly abandoning it too.
Is a custom-built website worth the cost for a restaurant?
Usually not, unless your brand needs something highly specific. Most of the value customers care about, working hours, a clear menu, and a fast checkout, comes from the ordering system, not custom design work.