Show what is on tonight.
A pub is not a restaurant with beer.
Quiz night, changing hours, a kitchen that is not always on, a roast list that moves every Sunday. Pub sites that look like fine dining — or like a chain template — miss the room you actually run.
Leading restaurant websites and Quiteful live menus for this room — London, the South, the North, Scotland, Ireland and nationwide.
What usually goes wrong
- The site cannot hold wet-led and food-led in the same breath. Events are a Facebook dump.
- Sunday roast is a PDF from March. The pie list changed. Allergens did not.
- Specials exist on a board the regulars can see and the website cannot.
- Guests who need gluten-free wait for a server who is pouring pints.
why Lemon Octopus
Pubs need events, quiz nights, rooms, opening hours that change by day, and a booking path that does not feel like a tasting-menu site. Lemon Octopus builds sites that hold all of that without looking like a chain clone, and can add the custom bits that actually matter: what is on tonight, which kitchen is open, whether the garden is serving.
- Hours, events and food in one place — not a restaurant template with a beer photo.
- Bookings that fit a pub: tables, rooms, Sunday lunch, not a fine-dining widget bolted on.
- Custom “what is on tonight” when the CMS you were sold cannot describe a quiz and a kitchen close.
- Ongoing updates so seasonal events ship instead of sitting in a WhatsApp chat.
why Quiteful
Pub food dies on printed specials boards and a roast PDF nobody reprints. Allergens on a changing pie list are a liability. Quiteful lets the kitchen publish today’s specials and the allergen record without a designer. Guests filter gluten-free or vegetarian on a phone at a sticky table instead of waiting for a server.
- Daily specials and Sunday roasts published from the kitchen, not the marketing folder.
- Allergen records that move when the pie filling does.
- QR at the table so the board and the phone agree.
- Last-updated on a roast menu — often the difference between a booking and the other pub.
Why both together *
The pub site shows what is actually on. Events and hours live on the Lemon Octopus site; the menu and allergens live in Quiteful; both stay current because staff can update without a CMS tutorial. One stack for the room you run after 5pm, not a restaurant brochure wearing a pint glass.
Quiteful, in this room
Not every Quiteful capability belongs on every lander. These are the ones that earn their keep for pubs.
Live menus
Update once. Publish to QR, web, embeds and signage.
Staff workflows
Publishing designed for busy kitchens, not a CMS tutorial.
Allergens
All 14 UK/EU regulated allergens, with contains, may-contain and cross-contact logic.
QR / web access
Table-side QR and website embeds from the same live menu.
Last-updated information
Diners deserve to know when the menu was last true.
proof, without a fake quote
Built for service, not a staging call.
If publishing is slower than the kitchen, staff will bypass it. Quiteful’s staff workflows exist because we operate menus inside hospitality. Lemon Octopus wires that into a pub site your team can actually run on a Saturday.
“Clear scope, fast staging links and no calendar theatre. The site launched looking like the product we actually sell.”
“Pricing was honest, the brief turned into a real plan, and the build held up under real traffic.”
Cafés
Win the pavement queue. Fast café websites for hours, brunch and walk-ins — with Quiteful for milk, nuts, gluten and a board that changes twice a day.