Loading or processing
Wait for the visible stage. Do not submit again while a consequential request is active.
Six clear starting points · one authoritative product
Choose the guide that matches what you need to do. This page is guidance, not completion tracking. Selecting a guide never grants access, writes data, connects a provider, or publishes a menu.
Role selector
Each option loads a server-rendered guide. All core instructions and links work without client-side JavaScript.
Owners control restaurant identity, billing, country-specific commercial settings, safety review, and the final release. Every protected action checks identity, tenant, role, and plan again on the server.
Connected web workflow; provider and production configuration still apply.Complete restaurant name, location, country and time zone, specialty, source language, currency, service modes, menu name, drink-size defaults, and a required starting logo made from reviewed letters and a color choice.
Setup confirms only after D1 readback and R2 logo creation. It creates a private draft, Brand Kit, and theme; it never publishes the menu.Start private restaurant setupCreate clear category and dish text, exact prices, sizes, availability, dish or menu of the day, formules, and optional promotions. Keep every change in draft until review.
AI can suggest editable dish text, possible allergen prompts, or dietary prompts. AI output stays a hidden draft and is never a safety determination or automatic publication.Open dishes and AI draftingChoose approved library media or upload eligible images. Review crop, purpose, and alternative text before using media in a release.
Private uploads require validation and approval. Storage and processing remain plan- and provider-governed; the interface does not promise unlimited storage or auto-publication.Open design and photo libraryIn Settings, record the country, currency, whether displayed price includes tax, the reviewed rate and label, and whether service is absent, included, mandatory, or optional for each service mode.
No universal VAT or TVA rate is assumed. The commercial-policy draft API exists and the owner form saves only after server validation and D1 readback. Optional service is never preselected.Review tax and service settingsFor each dish, assess every EU allergen category and the separate cross-contact risk using current recipe and supplier evidence.
The review is bound to the saved recipe checksum. A recipe change makes it stale. Unknown cross-contact blocks publication; possible cross-contact remains a visible warning.Open owner allergen reviewFree starts with one restaurant. Plus is €2.99 per month for the first restaurant and €1.99 per month for each additional restaurant, before applicable subscription tax.
MenuFaro activates or changes quantity only after Stripe’s server/provider confirmation. A new paid restaurant is first prepared as PAUSED with a private DRAFT menu.Review plan and billing statusResolve identity, menu, template, content, commercial-policy, allergen, language, entitlement, media, and permanent-QR blockers. Confirm the exact reviewed fingerprint before publishing.
Success appears only after the server commits and reads back the new immutable release, current menu pointer, and unchanged QR. Rollback restores history into a new draft and still needs publication.Open publication preflightAdd MenuFaro to an iPhone Home Screen for faster access. The installed experience and the website use the same routes, identity, tenant checks, D1/R2 data, and publication authority.
This is a progressive web app, not a native App Store release. Private offline writes and push notifications are not enabled in this slice.No action is required from this guideShared release model
The website and installed web app use the same release contract. A visual preview is never the live menu.
Dish, price, media, theme, translation, availability, tax/service, and safety changes remain private.
Resolve permission, plan, content, media, language, commercial-policy, allergen, and QR blockers.
Only an authorized owner or manager confirms the exact revision and fingerprint. Success waits for durable readback.
The stable token resolves the current immutable release. Republishing does not require reprinting the code.
State and recovery guide
Wait for the visible stage. Do not submit again while a consequential request is active.
Private work stays network-only. Reconnect, then reload the authoritative revision before editing or publishing.
Sign in with your own account, request the correct role, or ask an operator to restore the missing dependency.
Compare the newer server version with your work. Never force a blind overwrite from another browser or phone.
Trust a release, receipt, or provider state only after the page shows authoritative confirmation and identifiers.
Keep Plus pending, failed, or past due until the billing provider and signed lifecycle event confirm the result.
Optional connected iPhone access
Installation changes how you launch MenuFaro, not where data lives. It is not a native iOS release.