Apullay — a Peruvian ceviche restaurant website template

Starter is £19/mo excl. VAT and includes a complete restaurant website, a live structured menu, enquiry and newsletter forms, and managed search readiness. Growth is £39/mo excl. VAT and adds direct live bookings, a custom domain with managed SSL, and table and floor-plan operations. Full is £69/mo excl. VAT and adds online ordering and multi-site management for up to five restaurant sites. TableSpark commission is 0%. Stripe's standard card-processing fees apply to online payments.

Take it for a drive.

Apullay is bright warm paper with an acid lime that comes straight off a lime crate. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

Rather than explain, here is the thing itself: the builder’s Theme controls on one side, the live site on the other, both real. You cannot break it, nothing saves, and no account is required to have a go. Go on.

The whole template, not a sample of it

6 pages, and every one of them is here. Nothing below is a screenshot: the frame renders it through the same engine that publishes your site, so every tab is the real page and every link inside it works. Switch to Phone to watch the same design reflow.

Why it looks like this

A cevichería is a lunchtime restaurant, and lunchtime restaurants live or die on speed of comprehension. The design opens with a vertical plaque — the name, the hours, one line about the kitchen — and gets the guest to the menu in one movement.

A bright ground rather than a dark one is the right call for food that is raw, citrus and cold. Photographs of tiradito on a pale page look like the plate; on a dark page they look like a magazine.

What is on the home page

Eight blocks, built for a lunch service:

• Hero — Big opening image, name & buttons, in the Vertical Plaque treatment: Vertical name plaque, photograph, and an opening-hours panel.
• Intro statement — Big opening statement line.
• Offer banner — Time-bounded offer that hides itself when it ends.
• Menu preview — A few dishes on a sliding rail.
• Marquee strip — Scrolling awards or words.
• Numbers — Headline stats.
• Reviews — Guest quotes with stars.
• Newsletter — Email signup band.
• Call to action — Headline + button band.

The statement block currently reads The Pacific on one side, the Andes on the other, and lime on everything. — one line you will rewrite in about four seconds.

How the menu is set, and why it matters twice

This template uses the Accordion layout — sections sit collapsed on one screen and open in place, so a long menu never becomes a long scroll. The accordion suits a cevichería’s structure — cebiches, tiraditos, causas, calientes — where sections are short and a guest wants to see all of them before opening one.

The fish changes, so the menu has to. Descriptions carry the species and the leche de tigre; sold-out marks what has gone; prices are edited in seconds when the market moves. All of it flows to the ordering page and the structured data at the same time.

Whichever layout you choose, the point is the same: every dish, description and price is real text in the page with Restaurant schema around it, not a PDF and not a photograph of a laminated sheet.

The ordering page: same habit, different economics

This is the part worth pressing. Apullay uses the Chip bar ordering layout — sections become filter chips across the top, so a short menu is ordered from in three taps. The chip-bar layout puts sections as filters across the top, which is the fastest ordering interaction for a short menu at lunchtime.

Sizes and heat sit as chips on the row, the total stays on screen, and collection asks only for a name and a number. Payments settle into your own Stripe account with 0% commission taken by us. Stripe’s standard card-processing fees apply to online payments.

The form adapts to the mode. Eating in? A table number. Collecting? A phone number. Delivery? An address. Nothing more is demanded.

The pages guests read before they come

The story page carries the chef and the coast — narrative, sourcing, interview, timeline and gallery — and the events page holds the tasting dinners and collaborations. The visit page handles a room that is busiest between one and three.

You will not be retyping the menu

The tedious part comes first, and it is barely a part at all. Upload the menu exactly as it exists today, whether that is a printed card, a photograph of a board or an old PDF. Sections keep their order, dishes keep their descriptions, prices land in the price field, and dietary and spice marks come across where they were legible. You are the proofreader, not the typist.

That structure is the reason the rest of the site works. Everything downstream reads from it: the menu page, the ordering page, the highlights on the home page and the Restaurant structured data a search engine reads. Change a price once afterwards and all of them follow.

The title and description a search result shows are drafted for you too, by a Write with AI button that works from the page’s own content. You edit before it ships, every time.

How long this actually takes

Most of the work was done before you arrived. The design, the layouts and the plumbing are all in place; what is missing is your restaurant. From opening the builder to a live site is usually about ten minutes, at which point guests can already book a table. Your inbox catches the booking; an automatic email catches the guest.

The money side is a single step: connect Stripe, and deposits and payments go directly into your account. Nothing is skimmed at any plan level — 0% commission. Stripe’s standard card-processing fees apply to online payments.

1. Pick ApullayThe full site arrives in your account as a working draft.
   1 min
2. Change the name and the wordsRewrite the words by clicking them; the name carries everywhere.
   4 min
3. Upload your menuSend the menu in as a photograph and check what comes back.
   3 min
4. PublishIt goes live on your address and starts taking bookings.
   1 min
5. Connect StripeNow you can take deposits on tables and payment on orders — direct to your account.
   1 min

Run it on your own domain

A restaurant’s address is part of its name. Publishing does not wait for a domain. Start on ours, move to yours — the same site, a different name over the door.

The technical work is ours: issuing and renewing the certificate, securing the connection, redirecting the bare domain, and keeping the search engines aimed at the live address through the change. You can keep the domain you have had for a decade — the change at your registrar is a single record.

The email after the booking is yours to design

Something arrives in their inbox with your name on it. That is worth designing. It arrives at once, with the booking details, your address, your phone number and a link the guest can use to cancel without phoning. Everything after the booking — the reminder, the receipt, the cancellation — comes from here too.

What the guest sees is your identity, not our template. Six templates; your colour; your logo; a cover shot; a left, centred or banded header; your sign-off; your links; your social accounts. Your domain, once connected, becomes the sending address as well as the web address.

What follows is not a screenshot of an email — it is an email, drawn by the module the booking system calls. Change the style or the colour and it redraws.

What you change, and what stays

• Yours from the first minute: the restaurant name, every line of copy, all photography, the menu and its prices, opening hours, address, and the colours and typefaces in the Theme tab.
• Kept for you: the layout logic — how the menu reads at 200 dishes, how the basket behaves on a phone, how sections stack on a small screen, and how the whole thing stays legible when you switch to a light palette.
• Never locked: move sections, delete them, add new ones from the module library, create pages, remove pages. Nothing here is fixed.

Findable, not merely online

Getting a page online is easy. Getting it discovered, read and understood is the actual work. Live and invisible is a common combination — caused by stray robots directives, canonical conflicts, unlinked pages, PDF menus, missing schema, or verification that stalled halfway. The restaurant ends up buying back its own customers, because the people searching for it are meeting someone else’s page.

You inherit it finished. Nobody can sell you a ranking or guarantee indexing. This sells you the groundwork that makes both possible.

Common questions