What Fenómenus does
Fenómenus turns a WordPress site into a restaurant menu system. Instead of asking staff to think in posts, taxonomies and custom fields, it presents the objects a dining room already works with: menu types, categories, items, serving prices, allergens and languages.
Everything a guest can see — the digital menu, its QR code and its printable PDF — is produced from the same item records, so a price corrected once is corrected everywhere it is published.
Nine menu experiences
A site enables only the menu types it sells. Each enabled type becomes its own admin menu with its own categories and its own public archive.
| Menu type | Typical use | Serving prices it stores |
|---|---|---|
| À la carte menu | Main dining-room dishes | Full portion, half portion, unit |
| Terrace menu | A separate outdoor menu with the same dish fields | Full portion, half portion, unit |
| Breakfast | Morning service | Full portion, half portion, unit |
| Desserts | Dessert section | Full portion, half portion, unit |
| Bar menu | Counter and snack service | Full portion, half portion, unit |
| Wine list | Bottles and wines by the glass | Glass, bottle, Magnum, Benjamin |
| Cocktails | Signature and classic cocktails | One price per cocktail |
| Beverages | Soft drinks, beers, spirits | Glass, shot, bottle |
| Tasting menu | Multi-course experiences | Priced inside the menu itself |
| Set menu | Daily or fixed menus with choices | Priced inside the menu itself |
The first seven are item lists: one record is one dish, wine or drink. Tasting menu and Set menu work differently — one record is a complete menu built from titled course blocks, and a set menu can also offer dishes to choose from inside each block.
An administration shaped like a menu, not like WordPress
For every enabled menu type, Fenómenus replaces the default WordPress screens:
- All items is a single list grouped by category. Items are reordered by dragging, and the order saved there is the order guests see.
- All categories manages the category tree with drag-to-indent, one level of nesting, and inline editing.
- Opening the standard WordPress list screen or the standard category screen for one of these content types redirects to the Fenómenus equivalent, so there is only one place to work.
Inside All items you can, without opening an item, edit its serving prices, switch it between Published and Draft, mark or unmark it as featured, move it to another category, duplicate it, or delete it. A search box, a category filter and a status filter narrow long lists, and a counter shows how many items the menu type currently holds.
What an item carries
An item record holds the content the public menu needs: title, subtitle, a short description, an expandable long description, a photo gallery, an optional video, the serving prices that apply to its menu type, its category, its allergens, and — where it makes sense — a recommended wine or cocktail pairing.
Wine records go further. A wine keeps its vintage, its wine type, sale prices for each bottle format, and a technical sheet with characteristics, tasting notes and market price references.
What guests get
The public menu is an archive page per menu type, rendered with the layout chosen for it: a vertical full-screen feed, a plain price list, a horizontal carousel, a masonry grid, a swipe view, or one of the two dedicated designs reserved for tasting and set menus.
Around that content, the archive can show a sticky category navigation, a floating contact dock linking to the other menus and to the home page, an allergen filter, a favorites view and a language switcher. Each of those elements is enabled, colored and labelled per menu type.
Output beyond the website
- QR codes are generated for the home page, any menu archive, any category archive, or any custom URL, and downloaded as PNG or SVG. On a multilingual site one code is produced per language.
- PDF menus are built from the same items, with a chosen template, typography, colors, logo, price prefix and suffix, allergen display and footer legend, then previewed and downloaded.
Translations
When the site runs a supported translation layer, menus are published in several languages from one source. Publishing or unpublishing an item can carry its translations with it, the admin lists stay in the main language, and QR codes and PDFs are produced per language.
AI assistance for wine lists
Optional tools search a wine and fill in its record, complete missing details across an existing wine list, or read a photographed wine list and turn it into editable rows. These tools are switched on individually, and they always leave the result on screen for review before anything is saved.
Product boundary
Fenómenus is delivered as part of the managed Pomatio/Fenómenus service and runs together with the POM theme, which registers the content types, custom fields and public templates that Fenómenus configures. It is not a stand-alone plugin you download and license yourself, and it has no customer-facing license-key screen. Account access, availability and updates are handled through the service.
Continue with Requirements and supported file formats to confirm what the site needs before the first menu is built.