Updates, support, and safe maintenance
Fenómenus is part of the managed Pomatio/Fenómenus service. There is nothing to download, activate or license inside the product: new versions are deployed for you, and the menus keep running while that happens.
What stays on your side is the content. This page covers the maintenance rhythm that keeps a live menu correct, and how to ask for help in a way that gets it resolved on the first reply.
Daily service
The one habit that matters during service is the status switch.
When a dish runs out, open All items for its menu type and set it to Draft. It disappears from the public menu immediately and keeps all its content, so putting it back is one click. Deleting a sold-out dish and recreating it tomorrow loses its photos, description, allergens and position.
The same applies to a wine that is finished, a cocktail whose ingredient did not arrive, and a set menu that is not running today.
Weekly review
- Compare prices against the current card, one section at a time.
- Check that seasonal items match the season.
- Look for photos that no longer represent the plating.
- Confirm Uncategorized Items is empty on every menu type.
- Skim the menu on a phone the way a guest would, rather than in the admin list.
After a bigger change
Some changes need a follow-up check because they affect more than the row you edited.
| What changed | What to re-check |
|---|---|
| Category names or structure | The public navigation, every QR destination that pointed at a category, and the PDF |
| A price format or currency convention | Every menu type, so the whole card is written the same way |
| Allergen list or allergen assignments | The public allergen filter, and the PDF if it prints allergens |
| Colors, icons or archive layout | Every affected menu, on a phone, signed out |
| A menu type enabled or disabled | The contact dock links, the QR generator list, and the home page links |
| Translations | Each language, end to end |
| A bulk import | The whole affected menu type, not just a sample of rows |
Bulk saves are already careful with the site's page cache: instead of clearing it once per row, they clear it once when the batch finishes. Even so, if the site uses a page cache or a CDN and an old menu keeps appearing after a change, purge that layer before concluding that the content is wrong.
Reviewing what a bulk edit did
The Excel export is the fastest audit tool available. Before a large import, download the current items from All items → Download as Excel and keep the file. After the import, download it again and compare the two. Differences you did not intend are far easier to see in a spreadsheet than in a scrolling list.
Tasting menus and set menus have no export, so review those menu by menu.
Keeping the printed and digital menus in step
The PDF is generated from the items as they were at that moment. It does not update itself.
Whenever prices, dishes or allergens change, regenerate the PDF and replace the file wherever it is published or handed out. Keep the digital menu as the single source of truth, and treat every PDF as a snapshot with a date.
QR codes behave the opposite way: they encode an address, so content changes never require a reprint, and address changes always do.
Before asking for help
Most reports resolve faster after two minutes of checking:
- Reproduce the problem in a private browser window, signed out.
- Note whether it happens signed in as well.
- Note whether it affects one item, one category, one menu type, one language, or everything.
- Reload the page once, in case you are looking at a cached copy.
- Note what changed just before the problem appeared — an import, a settings change, a new language, a new photo.
What to include in a support request
- The exact public URL where the problem is visible.
- Whether it happens signed out, signed in, or both.
- The menu type, category and item involved.
- The language, if the site is multilingual.
- The device and browser used, especially if the problem only appears on a phone.
- What you expected to see and what you saw instead.
- The steps that reproduce it.
- What changed immediately before.
- A screenshot with any account information cropped out.
What never to send
- Passwords or login links.
- Hosting, database or email credentials.
- Screenshots that show a signed-in session's account details.
- Personal data about guests or staff.
- Supplier contracts, cost prices or other commercial data that has nothing to do with the fault.
If a support conversation asks for something on this list, stop and confirm through your usual service contact first.
Recovering from a bad change
- An item edited by mistake: reopen it and type the correct value back. Menu items do not keep revision history, so there is nothing to roll back to — this is why one item is checked before a batch is imported.
- A whole batch imported wrongly: compare against the export you kept before the import, correct the rows, and re-import.
- A category deleted by mistake: recreate it and reassign the items, which appear under Uncategorized Items rather than being deleted with it.
- A setup step re-run by mistake: colors and layouts can be set again from the settings screens without re-running the assistant.
The safest habit is the smallest one: change one thing, save it, look at it signed out, and only then change the next.
Return to the Fenómenus start-here chapter for the rest of the documentation.