Restaurant Website Cost in the UK in 2026: Menus, Bookings and Takeaway Orders in GBP

A restaurant website in the UK in 2026 costs, as an indicative market range and excluding VAT, around £450 in first-year cash costs for a do-it-yourself site, £1,450 for a professionally built base site with proper menus and a booking-ready structure, and £2,750 in this guide's worked example for a Manchester bistro adding online table booking, its own takeaway ordering and allergen-filterable menus. This guide prices each feature separately, compares own-site ordering with the delivery platforms honestly, and lists the UK-specific details — VAT, allergen information, data protection — that a restaurant site has to get right.

A restaurant website is read in a state of hunger and haste. Most visitors arrive from a map search or a recommendation, on a phone, wanting four answers in under a minute: what is on the menu, what does it cost, when are you open, and how do I book or order. A site that answers those four beautifully will outperform a prettier site that buries them, every week of the year. The money in this guide is therefore priced against those jobs — menus that stay current, booking that takes seconds, ordering that keeps the margin in the business — rather than against decoration.

How These Prices Were Compiled

Methodology note: the ranges in this guide are compiled from published tariffs and our project data, checked October 2026, and every price excludes VAT at the standard rate, because UK businesses compare quotes net. Delivery-platform commission figures are described as reported ranges rather than exact tariffs, because platform terms vary by contract and change; check your own agreement before acting on any comparison. Where our own packages are a useful yardstick for brochure sites generally, they are named as such; a restaurant build with ordering sits above entry brochure pricing because ordering is payment plumbing, and payment plumbing is testing work.

The Build, Priced by Route

Route	Indicative cost (GBP, excl. VAT)	You also supply	Best for
DIY site, first year	~£450	Your own time for every menu change, photo and fix	A single-site café testing demand before investing
Professional base site	£1,450 (calculator base)	Menus, photography, opening-hours discipline	Most independent restaurants and bistros
Worked example: booking, takeaway, allergen menus	£2,750	Your reservations process; allergen information per dish	Restaurants whose Fridays and takeaway nights are real revenue lines
Two-location group	£3,250 on the same list	Per-site menus and hours kept separately current	Small groups that outgrew a single shared page

Cost Calculator: Build Your Own Estimate

Start from the base site and tick only what your service genuinely needs at launch. The worked example after the calculator uses these same prices, so its £2,750 total can be reproduced exactly by ticking the same three boxes.

If the calculator does not run on your device, the static table below reproduces the worked example in full.

Worked example — a Manchester bistro	GBP (excl. VAT)
Professional base site (base)	1,450
Online table booking	300
Takeaway ordering on its own site	650
Allergen-filterable menus	350
Total	2,750

The bistro seats forty, does a brisk Friday and Saturday, and had been taking takeaway orders only through a delivery platform. Notice the order in which it bought. Booking came first because the phone ringing through service was the daily pain. Takeaway ordering followed because the platform commission on its existing order volume was a visible monthly sum, and even a partial shift to own-site orders pays the feature back — the maths is in the next section. Allergen-filterable menus were not a luxury: with allergen enquiries arriving most services, a menu a diner can filter with confidence is both a safety aid and a reason a whole table books with you instead of elsewhere. Gift vouchers were deferred to phase two, deliberately.

Own Ordering vs the Delivery Platforms: the Honest Maths

Delivery platforms sell reach, and reach is real: a listing puts a restaurant in front of people who would never have found its own website, and for discovery that has genuine value. The cost is commission per order, commonly reported in a broad range running into the teens and sometimes higher depending on the service bundle — read your own contract for your figure, because it is the only one that matters. Own-site ordering inverts the trade: no marketplace shelf, so every order starts with someone who already chose you, but the per-order cost collapses to card processing. The working pattern most independents land on is both — platforms for discovery, your own site for the regulars a platform taught to find you — which is why this guide prices own ordering as an addition to a good base site, not as a platform replacement. Our USA guide to restaurant website costs works the same economics in dollars for readers with sites on both sides of the Atlantic.

Menus, Allergens and the Details UK Diners Check

Your menu belongs on your site as real text — readable, searchable and updatable in minutes — never only as a photograph of a printed menu or a PDF nobody can read on a phone. Prices on the menu matter: a growing share of diners simply will not book where they cannot see them. Allergen information deserves the same seriousness. UK food law requires allergen information to be available for the dishes you serve, and the rules around prepacked food labelling tightened in recent years; a website is not a substitute for your kitchen's allergen process, and this guide is not legal advice — but a site that lets a diner filter dishes by the allergens they must avoid, and that tells them plainly to confirm with the team when ordering, is both safer and more welcoming. Confirm your current obligations with your local authority or food-safety adviser, and keep the website's allergen data under the same discipline as the kitchen's matrix: when a recipe changes, both change.

Data, Domains and the UK Basics

Three quiet UK specifics belong in every restaurant website plan. First, the domain: a .co.uk address reads as local and established to UK diners, and registering it in the business's own name protects you when staff move on. Second, data protection: a booking form, a mailing list and an ordering checkout all process personal data under UK GDPR, which means a plain-English privacy notice, a lawful reason for each list you keep, and — for most businesses — registration with the Information Commissioner's Office and its data protection fee; check the ICO's current fee tiers for your size rather than relying on any figure printed here. Third, reviews: display them honestly and answer them like a host. The discipline in our guide to collecting customer reviews properly — ask well, get permission, never buy them — applies word for word to restaurants.

Recurring Costs a UK Restaurant Should Expect

Cost line	Indicative range (excl. VAT)	Notes
Domain (.co.uk)	Roughly £10–£20 per year	Registered to the business, renewed on a card that will not expire unnoticed
Hosting	Roughly £60–£300 per year	Menu-speed matters more than headline capacity
Booking system	Free tiers to a monthly fee, by provider	Compare per-cover charges against flat fees at your covers volume
Card processing on own orders	Per your processor's current tariff	A percentage plus a small fixed fee per order is the usual shape
ICO data protection fee	Per the ICO's current tiers	Check the current figure; it is modest and it is not optional for most
Care and updates	Staff time, or a care plan	Menus, hours and holiday closures kept current — stale hours cost real bookings

Five Mistakes That Make Restaurant Websites Cost More

• A menu only as a PDF or a photo. Unsearchable, unreadable on phones, and a weekly chore to update — the most common and most expensive habit in the trade.
• Booking hidden behind a phone number alone. Every caller you miss mid-service is a table another restaurant fills. Online booking catches the 10pm planners.
• Letting the platform be the whole takeaway business. Keep the discovery, win back the regulars: own ordering for repeat customers is where the margin recovers.
• Stale opening hours. A site (and a Google listing) showing last year's hours trains customers to distrust both. Our Google Business Profile guide covers the listing side of the same discipline.
• Allergen information treated as decoration. It is safety information. Keep it accurate, dated and honest about confirming with the team.

A Realistic Timeline

Phase	Typical duration	What the restaurant supplies
Content and menus	Week 1–2	Current menus with prices, allergen data per dish, photography, hours
Design and build	Week 2–4	One named decision-maker for feedback rounds
Booking and ordering setup	Week 4–5	Reservations rules, payment account, test bookings and a test order
Checks and launch	Final week	Staff briefed on where enquiries land; someone watches the first weekend

Questions to Ask Any Developer Before You Sign

• Show me the menu-editing screen. You will use it weekly for years. If adding a dish looks like a chore in the demo, it will be skipped in February, and the site will quietly go stale.
• What happens to bookings if the site goes down on a Friday? The honest answer names the booking system's own uptime and a fallback — a phone number displayed prominently when the diary cannot be reached.
• Who owns the domain, the site and the ordering account? All three should belong to the restaurant. A developer is a user on your accounts, never the owner of them.
• How are allergen updates handled after launch? The answer should be a routine your own team can run the day a recipe changes, not a support ticket.
• What will this cost in year two? Hosting, the booking system, care and renewals, in one list. A developer who answers year two clearly is pricing year one honestly too.

Seasonal discipline closes the loop: when the menu turns over, the website, the allergen data and the Google listing should change in the same week, by the same named person. That one habit is worth more bookings than any redesign.

Conclusion: Answer the Four Questions Beautifully

Menu, prices, hours, booking: a restaurant website that answers those four in under a minute earns its keep before any flourish is considered. Add own-site ordering where the volume justifies it, keep allergen and hours information under kitchen discipline, and the site becomes what it should be — the quietest, most reliable member of the front-of-house team. Our UK small business website cost guide covers the wider picture for your other pages and plans.

Frequently Asked Questions

How much does a restaurant website cost in the UK in 2026?

As indicative market ranges, excluding VAT: around £450 in first-year cash costs for a do-it-yourself site, £1,450 for a professionally built base site, and £2,750 in this guide's worked example with online booking, own takeaway ordering and allergen-filterable menus. A second location takes the same price list to £3,250. Every figure is an indicative range, not a quote.

Why do all the prices exclude VAT?

Because UK businesses compare and claim back VAT, quotes are conventionally compared net. Your invoice will add VAT at the standard rate where it applies; the comparisons in this guide stay honest by keeping every figure on the same net basis.

Is it worth taking takeaway orders on our own site?

If you already have repeat takeaway customers, usually yes: the per-order cost falls to card processing, against platform commission that is commonly reported in the teens or higher depending on your contract. Keep the platforms for discovery, and give regulars a reason to order direct.

What must our website show about allergens?

Allergen information must be available and accurate for the dishes you serve, and your site should make it easy to find — filterable menus help — while telling diners to confirm with the team when they order. The website supports your kitchen's allergen process; it does not replace it, and this guide is not legal advice. Confirm current obligations with your local authority or food-safety adviser.

Do we need to register with the ICO?

Most UK businesses that process personal data — and a booking form, mailing list or checkout all count — must register with the Information Commissioner's Office and pay its data protection fee. Check the ICO's current tiers for your size; the fee is modest, and registration is a normal part of trading online.

How long does a restaurant website take to build?

A base site typically takes three to five weeks once menus and photography are ready; adding booking and own ordering stretches it to five or six, mostly for payment and diary testing with real test bookings. Content — especially accurate allergen data — is the item most often late.

Can we update menus and hours ourselves?

Yes — that is the point of building menus as real text in a manageable site. Menu changes, seasonal hours and closure notices should take minutes, and the launch handover should include a short written routine your team can follow without calling a developer.