Your restaurant website: an ordering channel you actually own
What a restaurant site generated from the menu is for, how it differs from a QR code and from a branded app, when a custom domain is worth it, and why it beats renting your regulars from an aggregator.
A restaurant website, in this product, is not a brochure someone has to update by hand. It is a public ordering page generated from the same menu the till uses. Switch it on, share the link, and a guest who will not install an app can still order.
That is the whole point. Maintenance is not a second job.
What the guest actually gets
They open a page, see your dishes with the prices that are live tonight, pick a channel — delivery, takeaway or a table — and pay. The ticket lands in the same orders list as a till sale. Stock moves. The kitchen sees it. There is no parallel menu to drift out of date.
You choose a theme so the page looks like your room rather than like every other template: dark and quiet for a dining room, warm for a café, loud for a counter. You choose the language the page speaks, including a right-to-left layout when that is the language of the room.
By default the address is a subdomain on the product — {your-slug}.gosufra.com. That is enough to send in a message and print under a QR. A custom domain (your own name in the browser bar) is the later step, on the plan that includes it: it looks like a real business in search results and on a shared link, and it is the difference between “a page on someone else’s site” and “our site”.
Website, QR, app — three doors, one kitchen
They are not three products. They are three ways in:
| Door | Best for | Cost to the guest |
|---|---|---|
| Website | First visit, desktop, “I will not install that” | A link |
| QR at the table | Dine-in, no waiter keypad | A scan |
| Branded app | Regulars who already know you | An install and store review, on your side |
Start with the first two. QR at the table is the dine-in half; this page is the link you put in the bio, on maps, on the receipt. The branded app is what you add when enough people come back that asking them to install something is reasonable.
Why it is worth more than it looks
An aggregator will take a slice of the ticket and keep the phone number. Your page keeps both. That is the same arithmetic as any owned channel: discovery you can rent; regulars you should not.
It is also the cheapest way to be findable. People still type the name of a restaurant plus “menu” or “order”. A page that is your menu, on a URL that is your name, is the result you want that search to hit — not a PDF, and not a third-party listing that charges you for the click.
What makes people leave before they order
The same four mistakes as any ordering page, and they are on you, not on the theme:
- A PDF instead of a page.
- Photos on some dishes and not others.
- A delivery fee that appears only at pay.
- An account wall before the first item is in the bag.
Fix those, then share the link. Do not wait for the custom domain, the app or a photographer for the last twelve plates.
A practical sequence
- Today: turn the site on, pick a theme, copy the link, put it in your maps listing and on the printed receipt.
- This week: QR codes on tables pointing at the same menu.
- When the slug looks cheap in a text message: put it on your own domain.
- When the same people order twice a week: offer the app, with points already on the account they used on the site.
The website is not a branding project. It is the till, held out to someone who is not in the room yet.
Run all of this from one system
POS, kitchen, inventory, recipe costing, staff and accounting — connected, and free to start.
Create your free account