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 manager and a menu editor can share a menu workspace, but they do not have the same authority. Never share an owner password; use a verified membership and let the server enforce the assigned role.
Owner, manager, and menu-editor workspace access is connected when membership exists.Sign in with your own identity and open only the restaurant and menu assigned to your active membership.
A restaurant or menu selected in the browser is navigation context only. Server queries derive the allowed organization, role, and menu again.Sign in to the owner workspaceCreate or revise dish names, descriptions, categories, prices, sizes, availability, and draft media notes. Use AI only as an editable starting point.
Saving a dish writes a draft with revision checks. A menu editor cannot turn an AI prompt into confirmed allergen evidence or a public release.Open the assigned dish workspaceIf another device saved a newer revision, reload and compare it. Do not overwrite the server version blindly.
Stale revisions return a conflict. The connected iPhone web app and desktop website use the same authoritative revisions.No action is required from this guideAn authorized restaurant manager or owner can attest the location’s commercial policy and confirm allergen evidence for the current recipe.
Menu editors cannot confirm commercial or allergen records. No role can bypass country-specific professional review.Open manager review settingsRun the publication preflight, correct every blocker, and let an authorized owner or manager confirm the exact reviewed revision.
The publication route rejects a menu editor’s final confirmation. It also rejects stale fingerprints and duplicate or unconfirmed effects.Open the draft and preflightShared 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.