A guest finds you on Maps. The listing says open. The website still shows last year’s Christmas hours. They tap Order. The button dumps them into a courier app with a different menu and a closed-store message. Your photography is fine. The site failed the only job that mattered: tell them whether they can eat with you in the next hour, and how.
A restaurant website with ordering does not need to be a brochure. It needs, in a few seconds, the name, whether you are taking guests or collection today, and one clear next tap.
One job for the first screen
Someone booking dinner behaves differently from someone hunting lunch or arranging collection after work. The site can support several goals. One viewport should not shout all of them.
Match the lead action to how you actually serve:
- dine-in: menu, booking, location;
- pizzeria or collection-led: ordering easy to spot;
- café: today’s offer, hours, a fast contact route;
- delivery: area, fulfilment options, order-taking hours.
There is no universal layout. Venue formats snag in different places, so the primary CTA should follow real service, not a template.
What must be visible before the footer
- What is this place? Name, a short line on the food or format, an image that does not hide the hours.
- Can I use it now? Current opening hours. For orders, collection and delivery windows, not only dining-room hours.
- What do I do? One lead CTA: View menu, Book, or Order.
- Where is it? Address, map, phone. Especially if the business runs on collection.
Walk it on a phone as if you had never seen the site. If you cannot tell whether the button is a booking, a card or a courier, the information order is still wrong.
A menu a thumb can read
The menu is often the most important part of the site. It should not force a zoomed document or a hunt through social posts. Guests need categories, names, prices, basic availability and only the variants the kitchen will cook.
If the menu is meant to lead to an order, check three things:
- items and extras match the till and the pass;
- an unavailable dish can be hidden or marked quickly;
- after a choice, payment, collection, delivery and confirmation are obvious.
A form will not fix operations. The wider workflow is on the online ordering system. The site leads to a decision. The team still has to fulfil it.
Make Order a path, not a badge
After the tap, new puzzles should not appear. The guest knows whether this is collection, delivery or a table, what details they give, when confirmation shows, and that the order is not sitting in a mailbox nobody opens.
Keep the path short: site, menu, selection, summary, fulfilment method. You do not need to outrun every marketplace. You do need hours, card and basket to agree.
A site with ordering can be part of an owned sales channel. It does not have to replace platforms on day one. Direct online in OrderNow is not in Start. Do not assume it in an entry plan before you check feature scope.
What must be true in the venue before you redesign the homepage
A new layout will not save wrong hours, an inbox nobody checks, or a kitchen that never sees the guest note. Before you change the look, agree:
- who updates the menu and 86s;
- who sees a new order;
- how the team splits collection, delivery and dine-in;
- what the guest sees when you cannot take the order;
- whether phone, address and hours match the site, Maps and the door.
That is daily work, not a list of page widgets. If those answers are empty, a rebuild will only advertise last year’s hours faster.
Not every venue needs a full online channel first. Sometimes the first step is a readable menu, true hours and one contact route. Add ordering when you know who catches the click.
Compare formats on OrderNow industries. Talk through scope on a demo.
Related articles:
- Online ordering system for restaurants: what should it do?
- When does an owned restaurant sales channel make sense?