Use casesFood & drink
Your menu, your room, and a diary that fills itself.
Your site should do the two things a hungry visitor came for: show them the food, and take the table. Lili Pod puts your menu on the page as a menu — sections, dishes, descriptions and prices — and runs reservations against your real sittings, so "Dinner, 6–9pm" fills up on its own while you’re on the pass.
Restaurants, cafés, bars, supper clubs and pop-ups
This is for you if…
- You want people to read the menu and book a table in the same visit, on their phone.
- You keep a diary by service — lunch, dinner, a late sitting — and want it to fill without the phone ringing.
- You’re tired of handing a booking platform a slice of every cover you seat.
- You want the reservation page to look and read like your room.
How people book: Party size, then service
A guest says how many are coming, picks a service on the day they want — a named window such as "Dinner Service, 6–9pm" — and confirms, in about fifteen seconds and without making an account. Covers count against that service’s capacity, so a full sitting closes itself and you’re never double-booked by a diary that didn’t know it was full.
The words it uses
These aren’t settings you have to configure — they’re simply what the app calls things once you’ve told it what you do. Menus, page titles, dashboard tiles and emails all follow.
- The person cooking
- Chef
- A named sitting
- Service
- Someone at the table
- Guest
- One item
- Dish
- What the guest makes
- Reservation
What matters here
A menu that reads like a menu
Sections, dishes, descriptions and prices, laid out to be read on a phone by someone deciding where to eat tonight. Change a dish and it changes on the site — the menu is yours to edit, not a PDF somebody has to re-export every time the specials board moves.
Every cover is yours
A flat monthly price and nothing per reservation, ever. On a busy Saturday that’s the difference between a full room and a full room you’ve already paid for — and the takings land in your own Stripe account, not in ours.
Your room, with domain setup confirmed during onboarding
On a Pro plan the reservation page becomes your whole hosted website, Home, About, Menu and Book, with domain setup confirmed during onboarding, with your photographs and your colours, and Fern answering the questions that arrive at 11pm about parking, allergens or whether you do a set lunch, only from facts you’ve given her.
Which plan you’d be on
A restaurant floor is a team: Team covers up to ten people taking reservations, and Large Team removes the limit for multi-room or multi-site operations. Solo is for sole traders with a single diary, so it’s not the right fit for a room with staff.
HR is a separate, optional add-on at a flat price per person, on every plan, with no cap on how many people you add.
Questions we get asked
- Do you charge per cover?
- No. There are no per-reservation or per-cover charges at all — just the flat monthly plan.
- Do guests have to pay to reserve a table?
- Not by default. Table reservations take no payment unless you decide otherwise, which is the normal way a restaurant diary works.
- Can I put my menu on the site as well as the booking?
- Yes — the menu is part of the food setup, laid out to be read: sections, dishes, descriptions and prices, edited by you whenever the kitchen changes something.
- How do sittings work?
- You define named services on a date — "Lunch, 12–2:30pm", "Dinner, 6–9pm" — each with a capacity in covers. Reservations fill them and stop when they’re full.
Try it on your own dates
One month free on your first subscription, no card needed to start. Set up your real schedule and see how it reads.