menu/os Restaurant back-office
The operating layer behind better restaurant menus
An in-development back-office for venues to manage menus, QR codes, themes, roles, publishing and assisted content workflows.
- My role
- Product design and full-stack development
- Platform
- Restaurant operations platform
- Status
- In development
01 / Challenge
The task
A good digital menu is not only a public page. Restaurant teams need a dependable workspace for structure, pricing, availability, visual identity, access control and publication, without turning every update into a developer task.
02 / Process
How I built it
- 01
I modelled venues, menus, sections and items as a connected operational system rather than a collection of standalone pages.
- 02
I built editing, theming, team roles, QR generation and publishing into the same workspace so the path from change to customer-facing menu stays visible.
- 03
I am developing assisted workflows for importing, translating and refining menu content while keeping the restaurant in control of the final publication.
03 / Decisions
What matters
One source of menu truth
Menu structure, content and presentation live in the same system, reducing duplication between operations and the published experience.
Real team boundaries
Venue roles and access rules are part of the product foundation, not a future administrative layer.
Assistance, not autopilot
AI-assisted tools are designed to accelerate repetitive content work while preserving review and publication control.
04 / Interface
In use
A closer look at the visual system and the product at real screen sizes.
05 / Result
Where it landed
menu/os is currently in active development. The working foundation covers venue and menu management, themes, team access, QR creation and publication, with further assisted workflows being refined.