Sushi Lovers
An interactive architecture proposal for one admin that publishes menu, price and content to every channel.
- Target operating model
- Central admin
- Interactive proposal
- Bilingual
- Shareable decision artifact
- HTML + PDF
The challenge
One publishing model for every channel.
Point-of-sale, marketplace/QR admin and mobile-app admin hold overlapping menu and content. Each dish change is copied by hand.
Product & engineering
What I delivered
An interactive architecture proposal for a sushi restaurant group: why three admin panels cannot scale, and how one central admin should publish to every channel.
- 01
Architecture proposal
A bilingual interactive proposal covering analysis, target architecture, impact framing and roadmap.
- 02
Shareable exports
PDF and standalone HTML export from the proposal page.
System design
How the pieces connect
- 01
Catalog
Menu, content and pricing ownership.
- 02
Control plane
Central publishing and branch rules.
- 03
Operations
POS, kitchen and cashier boundaries.
- 04
Channels
Owned website, app and marketplace.
Product interface
- React
- TypeScript
- Vite
Proposed, not implemented: a central admin as control plane; POS keeps kitchen, cashier and operational orders; marketplace/QR stays integration middleware; owned website and app consume the same published data.
Outcome & evidence
What the work produced
Delivered outcome
A shareable architecture proposal. The restaurant platform itself was not built in this engagement.