Get started with Fenómenus
This chapter takes a restaurant from an empty site to a menu that guests can scan at a table. It separates the work deliberately: understanding the product, preparing the site, running the one-time setup, building content, and approving the result. Each step answers a different question and has a different way back.
Fenómenus presents restaurant concepts — menu types, categories, items, serving prices, allergens, languages — instead of asking staff to understand WordPress posts and taxonomies.
Choose the right article
| If you need to… | Read |
|---|---|
| Understand what the product does before changing anything | What Fenómenus does |
| Check the platform, companion products and accepted file formats | Requirements and supported file formats |
| Sign in and decide who on the team can do what | Access your Fenómenus account |
| Create the restaurant's structure, colors and layouts | Complete the setup assistant |
| Record the restaurant's name, logo, fiscal and contact details | Configure your restaurant information |
| Learn what every screen is for | Tour the Fenómenus interface |
| Build and publish one real menu, end to end | Create and publish your first menu |
| Prove the menu works on a guest's phone | Test your first digital menu |
| Approve the whole restaurant for launch | Restaurant menu launch checklist |
| Keep a live menu correct, or prepare a useful support request | Updates, support, and safe maintenance |
A safe route to the first public menu
- Read what the product does and confirm the site meets its requirements.
- Sign in, and give the team the accounts and profiles they need.
- Run the setup assistant, enabling only the menu types the restaurant actually sells.
- Complete the restaurant profile.
- Create the smallest useful category structure for one menu type.
- Add one representative item, with every serving price and allergen that applies.
- Check that item on a phone while signed out.
- Add the rest of the content in small, reviewable batches.
- Add translations only once the source menu is stable.
- Generate the QR code, scan a printed proof, and produce the PDF from reviewed content.
- Work through the launch checklist before the codes reach the tables.
The publishing rule
An administration screen that reports a saved change is not the end of a task. Check the public URL while signed out, on a phone, and in every affected language.
Three copies of the same information can disagree: the item you edited, the page a browser or page cache is still serving, and a PDF or printed QR produced earlier. Only the first one is the source of truth.
Where the rest of the documentation goes
- Menu types — the nine restaurant experiences, and how to enable or rename them.
- Items and categories — creating, ordering, featuring, duplicating and retiring content.
- Prices — every serving format and the menu types that support it.
- Allergens and dietary information — what the software does, and what the restaurant remains responsible for.
- Wine lists — vintages, formats, technical sheets.
- Bulk editing and Excel — exports, pasted tables, large updates.
- Design and display — layouts, navigation, colors and the contact dock.
- QR codes — generating, printing and maintaining codes.
- PDF menus — printable menus built from the same items.
- Languages and translation — multilingual menus.
- AI tools — the optional wine assistants.
- Settings — every option on the settings screen.
- Developers — the stable integration points.
- Help — troubleshooting that starts from a visible symptom.
Start with What Fenómenus does, which also explains where the product's responsibility ends and the managed service takes over.