Why a restaurant does not need a full WordPress site

Updated 14 September 20267 min readRomain Ferrand — pizzaiolo, 12 years in trucks and dining rooms

WordPress is a publishing platform, and a restaurant is not really publishing. It has a menu that changes, hours that have to be right, and a phone number. Building that on a CMS with six plugins means you have taken on a software estate to solve a problem that is mostly a data problem.

What a restaurant site actually is

Strip away the design and a pizzeria website is a small, structured dataset: a list of dishes with prices, options and allergens; a weekly schedule with two windows a day; an address with coordinates; a phone number. Render it well on a phone, mark it up so machines can read it, and that is the product.

WordPress models none of that natively. It models posts and pages. So every one of those things becomes a plugin, and the plugins become the project.

What a pizzeria needsIn WordPress
A menu with options that change priceA restaurant plugin, or WooCommerce bent into shape
Two services a day, past midnightAn hours plugin, usually badly
Allergens per dishA custom field, or text in the description
Live open/closed stateAnother plugin, or nothing
Restaurant and menu structured dataAn SEO plugin, configured by hand
OrderingA plugin with its own subscription

The cost is attention, not licence fees

Core, themes and plugins update constantly. Skip them and an abandoned install becomes a genuine security liability — out-of-date plugins are one of the most common ways small sites get compromised. Keep up with them and you have signed up for a recurring job that has nothing to do with making pizza.

When WordPress is right

Genuinely, and this matters: if you publish. A restaurant writing recipes, running an events programme, or building an audience through long-form content is doing exactly what WordPress is best in the world at, and no restaurant tool comes close.

Likewise if you already have a maintained WordPress site that works. "It is the wrong tool in principle" is not a reason to migrate something that is currently fine.

The full cost breakdown, and how to run it well if you keep it

The test

One question settles it: how long does it take to change the price of a garlic bread, from your phone, at seven on a Friday?

If the honest answer involves a laptop, a login and a plugin interface you half remember, the menu will go stale — not because you are lazy, but because during service you have better things to do. A stale menu costs more than any of the numbers in this article.

Your site could be live before service tonight

Five minutes. No card. And you’re live.

Start now

Sources