Restaurant Websites — Delivery Fees, Cost & Features [2026]

A restaurant website is no longer a business card — it is a sales channel: delivery platforms (Pyszne.pl, Glovo, Uber Eats, Wolt) charge 15–30% commission on every order value, and a restaurant turning over 40,000 PLN in deliveries hands intermediaries over 10,000 PLN a month. In 2026, a restaurant website costs from 800–1,500 PLN net for a business card with an online menu, through 1,500–3,500 PLN net for a site with table reservations and online ordering, to 4,000–12,000 PLN net for a dedicated system integrated with the POS and delivery platforms. A direct ordering channel pays for itself within a dozen or so orders a day.

Najważniejsze: A restaurant website in 2026 costs from 800–1,500 PLN net (business card with an online menu) through 1,500–3,500 PLN net (table reservations and online ordering) to 4,000–12,000 PLN net (dedicated system integrated with POS and delivery platforms). Pyszne.pl, Glovo, Uber Eats and Wolt commissions run at 15–30% of the order value — a direct ordering system charges no commission. The online menu must include allergen information, and promotions are subject to Omnibus (lowest price from the prior 30 days).

How much does a restaurant website cost in 2026?

Restaurant website pricing depends on whether the site merely presents the venue or takes reservations and delivery or takeaway orders.

• Add the running costs: a domain (50–150 PLN per year), hosting (100–400 PLN per year), a free SSL certificate — and food photography, the position restaurateurs forget most often. A professional food shoot costs 500–2,500 PLN, and photos sell more than any amount of copy.

What drives the cost of a restaurant website?

• An online ordering system — cart, delivery zones, ordering hours, online payments and order printing in the kitchen. The most frequently requested feature.
• Table reservations — a calendar with a dining-room layout, confirmations and SMS reminders.
• POS integration — automatic order and status flow, menu and price synchronisation.
• Delivery platform integration — receiving Pyszne.pl, Glovo or Uber Eats orders in a single panel.
• Language versions — venues in city centres and resorts need English (and often German) versions.
• Gallery and media — professional photos of dishes and interiors; video raises engagement but needs weight optimisation.
• Local SEO and content — optimisation for "restaurant [city]", "pizza [district]", dish descriptions and events.

If the ordering system is meant to work like a full application — with a kitchen panel, delivery zones, discounts and integrations — the budget approaches that of a custom web application.

Direct ordering system or Pyszne.pl, Glovo and Uber Eats?

Delivery platforms charge commission: Pyszne.pl takes around 13–15% with the restaurant's own delivery and up to 30% with platform couriers; Glovo with delivery is around 30%; Uber Eats and Wolt are similar. On an 80 PLN order, a 30% commission means 24 PLN handed to the intermediary — before you count ingredients and labour.

The model that works best is two channels in parallel: platforms as a source of new customers and your own ordering system as the service channel for regulars. A restaurant that points customers to its own website on flyers, in the venue and on social media moves most orders there within a few months — commission-free. We build dedicated ordering systems in Laravel, designed for performance, and the mechanics of carts and payments are covered in our e-commerce store development guide.

What should a restaurant website include?

1. An online menu in HTML — not a PDF. It ranks in Google, works on every phone and lets you mark allergens.
2. Allergen information — a duty under EU Regulation 1169/2011; it applies to menus published online as well.
3. Table reservations — a calendar with available times and confirmation; for many venues more important than online orders.
4. Online ordering with delivery or takeaway — cart, delivery zones, ordering hours, online payment.
5. A gallery of dishes and interiors — professional photos of food, the dining room and the team. They decide the first impression.
6. Location, hours and contact — map, parking, accessibility information, phone.
7. Reviews and social media — embedded Google reviews, a link to an Instagram feed with current photos.
8. Events and special offers — catering, corporate events, weddings, themed evenings. Dedicated pages rank for those queries.
9. A newsletter or regulars' programme — an e-mail base is the cheapest way to announce news and promotions.
10. A Google Business Profile and the legal layer — a complete profile with menu and photos, plus a privacy policy and cookie consents.

The foundations common to every industry are covered in our business websites guide.

Online menu — HTML, QR code or PDF?

This is the most important technical decision on a restaurant website, and many venues still publish a PDF. Three formats, three different consequences:

• PDF — convenient for the kitchen, terrible for guests and Google: it does not rank as content, displays badly on phones and is often unreadable for screen readers.
• An HTML menu on the site — the best option: it ranks ("margherita pizza [city]"), scales on mobile, allows dish search and allergen marking. It can also carry schema.org structured data (the Menu type), so Google understands the menu.
• A QR code — great as an addition on the table and in the window, provided it leads to the HTML menu on the site. A QR code pointing to a PDF is the same trap in different packaging.

An HTML menu is updated in the admin panel within minutes — a price change or a new seasonal dish requires nobody to generate a new file.

Table reservations and online ordering

Good table reservations handle a dining-room layout (not just times), confirmations and SMS reminders, and for larger venues an integration with the reservation system used by staff. A good online ordering system:

• accepts orders only during kitchen hours — switching off automatically outside them,
• handles delivery zones — with a fee based on distance and a minimum order value,
• takes online payments — BLIK, cards, instant transfers; paying upfront eliminates failed orders,
• prints orders in the kitchen — integration with a printer or POS, no retyping from a screen,
• sends status updates — order acceptance, courier departure,
• collects a customer base — e-mail and phone for future campaigns.

At high order volumes, it is worth adding AI automation: a chatbot answering questions about hours and the menu, automatic reservation confirmations and catering enquiry qualification.

Restaurant local SEO

• Google Business Profile — for restaurants this is the most important marketing tool: menu, photos, hours, attributes ("takeaway", "child-friendly"), reservations and reviews. Most guests find the venue right here.
• Reviews — respond to all of them, including critical ones; regular reviews lift your position in Maps and local results.
• Local and dish keywords — "restaurant [city]", "pizza [district]", "takeaway sushi [city]". An HTML menu ranks for dozens of queries with dish names.
• Tripadvisor and portals — complete the profiles, but treat them as a supplement: the Google profile and your own website deliver commission-free reservations.
• Local Google Ads — campaigns for "[cuisine] [city]" with a budget of 300–1,000 PLN per month; point traffic to the site with reservations, not to a delivery platform profile.
• Performance and mobile — photo galleries weigh a lot; a restaurant site must load within seconds on a phone. Optimisation techniques are covered in our Laravel performance optimization guide.

The law — allergens, Omnibus, GDPR and EAA

• Allergens — Regulation 1169/2011 requires informing about the 14 allergens in non-prepacked food; a menu on a website must carry that information just like the menu in the venue.
• Omnibus — when announcing a promotion ("-20% on all pizzas"), you must show the lowest price from the 30 days before the reduction. It applies to the online menu, ordering and the shop.
• GDPR — reservations and orders collect personal data: you need a privacy policy, cookie consents and secure (encrypted) forms.
• EAA — since 28 June 2025, sites taking online orders fall under the accessibility duty (WCAG 2.1 AA). An accessible menu and cart also mean more orders from guests with special needs.
• Payment security — encryption, updates and backups. The rules are covered in our Laravel application security — OWASP Top 10 guide.

How long does it take to build a restaurant website?

The biggest timeline risk is content availability: the menu with prices and allergens, dish photos and the ordering terms. Restaurants that prepare materials in parallel with design cut delivery time by up to half.

Most common mistakes when ordering a restaurant website

• A PDF menu — it does not rank in Google, works badly on phones and hurts accessibility.
• No allergen information — a legal duty, not just good practice.
• Delivery platforms only — the restaurant gives away 15–30% of its margin and never builds its own customer base.
• No online reservations — a guest who cannot book a table in the evening calls the competition.
• Poorly lit phone photos — food sells with the eyes; weak photos ruin the best menu.
• A slow site with a heavy gallery — especially painful on phones, where most orders come from.
• No Google Business Profile — without it the venue does not exist in local results.
• Forgetting Omnibus on promotions — the lowest price from the prior 30 days is a duty, not advice.

Choosing the right vendor matters — check whether they understand hospitality specifics: POS and platform integrations, kitchen hours and allergens. Read more on the about page and in the hire a Laravel developer service.

Frequently asked questions

How much does a restaurant website cost in 2026?

From 800–1,500 PLN net for a business card with an online menu, 1,500–2,500 PLN net for a site with table reservations, 1,500–3,500 PLN net for an online ordering system, to 4,000–12,000 PLN net for a dedicated system with integrations. Off-the-shelf platforms on subscription cost 50–300 PLN per month. Add food photography: 500–2,500 PLN.

Does a restaurant need its own website if it is on Pyszne.pl and Glovo?

Yes. Platforms charge 15–30% commission on every order and keep customer data. Your own website is a commission-free ordering channel, a base of regulars and full control over the menu, prices and promotions. The best model is platforms as a source of new customers plus your own system as the service channel — with customers pointed to your own site.

Should the menu on the website be a PDF?

No — a PDF does not rank in Google as content, displays badly on phones and hurts accessibility. An HTML menu works on every screen, allows allergen marking, and Google understands it through structured data. A PDF can stay as a downloadable extra, but the HTML menu should be the foundation.

Does a restaurant website have to include allergen information?

Yes. Regulation 1169/2011 requires informing about allergens in non-prepacked food, and a menu published on a website is subject to the same requirements as the menu in the venue. It is one of the most frequently skipped duties, and breaches can carry sanctions and liability for damages.

How does an online ordering system for restaurants work?

The guest picks dishes from the menu, provides an address or pickup method, pays online and receives a confirmation with status. The order reaches the kitchen — ideally through integration with a printer or POS. The system handles delivery zones, ordering hours and a customer base for future campaigns.

How much does it cost to maintain a restaurant website?

A domain is 50–150 PLN per year, hosting 100–400 PLN per year, SSL is free, and with an ordering system a subscription or technical care starts at around 100–300 PLN per month. Budget separately for menu and photo updates — best when you do them yourself in the panel within minutes.

What is Omnibus and how does it apply to restaurants?

Omnibus is the duty to show the lowest price from the 30 days before a reduction when announcing a promotion. A restaurant advertising "-20% on all pizzas" must show the pre-reduction price. It applies to the online menu, the ordering system and the online shop. Fines are imposed by Poland's UOKiK authority.

How do I win guests through a restaurant website?

• Above all locally: a complete Google Business Profile with menu and photos, regular reviews, keywords like "restaurant [city]" and "takeaway [cuisine] [city]", an HTML menu ranking for dish names, and Google Ads campaigns pointed at the site with reservations. Send regulars a newsletter and a promotional programme.

Sources and tools

• Regulation (EU) No 1169/2011 — food information and allergens (EUR-Lex)
• UOKiK — information duties for price reductions (Omnibus)
• GDPR — Regulation (EU) 2016/679 on data protection
• Directive (EU) 2019/882 — European Accessibility Act
• schema.org — Restaurant and Menu structured data
• Google — Business Profile guidelines for restaurants
• web.dev — Core Web Vitals

👉 Running a restaurant or food venue? See how custom Laravel websites and ordering systems work in my offer — from UX/UI design and the photo shoot, through reservations and online ordering, to POS and platform integrations. Get in touch via the contact form or at kontakt@informatix.com.pl.

👉 Building the foundations too? Check the business websites guide and the e-commerce store development guide.

📖 See also: Laravel performance optimization and Laravel application security — OWASP Top 10.