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.
A guest starts from a restaurant link or permanent QR. Menu browsing, language choice, service mode, safety information, and the accessible list do not require a MenuFaro account.
Public route; no restaurant-team permission is required.Scan the restaurant’s permanent QR or open its published restaurant and location link. If you are only exploring MenuFaro, use the sample library.
A QR stores an opaque stable token, not a release, tenant, asset, or language. The same printed code can resolve a later reviewed release.Browse public menu samplesChoose a published language and the restaurant’s available dine-in, takeaway, or delivery view. Prices can differ by service mode.
A language or mode choice changes presentation only. It does not create an order, payment, reservation, or food-safety guarantee.No action is required from this guideOpen dish details and read confirmed allergen and cross-contact wording. Ask the restaurant directly when the information is uncertain or your health depends on it.
MenuFaro never calls a dish safe or allergen-free because a filter, absence value, or AI suggestion says so.No action is required from this guideIn Fullscreen Swipe Menu, use swipe, scroll, Previous and Next, or switch to the normal list. Gestures are never the only route.
The public experience keeps keyboard focus visible, respects reduced motion, and exposes dish content in a readable sequence.Open the public menu exampleRetry after your connection returns. The current service worker is network-only and does not cache private workspaces or pretend that an old response is current.
A complete last-published-menu offline cache is still a target-track feature. The current web slice provides honest connection recovery instead.Open connection recovery helpUse the Privacy Center to clear supported local preferences and understand which organization controls a request.
A guest can contact the privacy route without signing in. MenuFaro does not claim a request is complete merely because it was sent.Open the Privacy CenterShared 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.