Apps & screens
The platform's four interfaces and their key screens. This is a guide for the MVP — detailed during design.
Interface map
1. Customer storefront (SSR)
The brand's public site — MVP priority.
- Catalog: categories, items, images, descriptions, prices.
- Item card with modifiersModifierAn option that alters a menu item: add-on, size, doneness, ingredient removal. May affect the price..
- Cart: add, change quantity, remove.
- CheckoutCheckoutOrder checkout: entering contacts and address, choosing time/delivery, payment and confirmation. In the custom stack it is fully under our control.: contacts, address/pickup, time, payment (MollieMollieA European payment provider. Accepts payments (cards, iDEAL, Apple/Google Pay, etc.) and reports payment status via webhooks.), confirmation.
- Real-time order status tracking.
2. Super-admin — Company AdminCompany AdminThe platform owner. Sees and manages all brands, restaurants, orders and cross-brand analytics; creates new brands. (SPA)
The platform owner's panel.
- Dashboard: orders, revenue, average ticket — across all brands.
- List of brands and kitchens, drill into any of them.
- Creating a brand (flow) and kitchens.
- User and role management (RBACRBACRole-Based Access Control — access management based on roles. Permissions are granted to a role (Company Admin, Brand Admin, Restaurant Manager) rather than to each user individually.).
- Platform-wide financial reports.
3. Brand admin — Brand AdminBrand AdminAdministrator of a single brand. Manages its restaurants, menu and settings, and sees analytics for that brand only. (SPA)
The same, but scoped to one brand.
- Brand dashboard (orders, revenue, average ticket — for this brand only).
- Menu management: categories, items, prices, modifiers, images.
- Managing the brand's kitchens and their menu publications.
- Inviting kitchen managersRestaurant ManagerManager of a specific kitchen. Works with incoming orders (KDS), the local menu and the settings of one location..
:::tip Basic CRUD — from Directus Managing menus/brands can, to start, be done right in the DirectusDirectusAn open-source headless platform on top of PostgreSQL: provides the data model, REST/GraphQL API, authentication, RBAC and a ready-made admin UI without writing code. admin (it already does CRUD + permissions). Custom Nuxt screens are built where a convenient flow is needed: dashboards, the brand-creation wizard, KDS. :::
4. Kitchen panel and KDSKDSKitchen Display System — a screen in the kitchen showing incoming orders and their statuses instead of paper tickets. — Restaurant ManagerRestaurant ManagerManager of a specific kitchen. Works with incoming orders (KDS), the local menu and the settings of one location.
The kitchen's workstation.
- KDS: a real-time feed of incoming orders, status changes (accepted → cooking → ready).
- Stop-list: quickly disable an unavailable item at this kitchen.
- Local menu and kitchen settings (hours, time slots, zones).
MVP priority
| Queue | What |
|---|---|
| 1 | Storefront + catalog + cart + checkout + payment |
| 1 | KDS (order intake and statuses) |
| 2 | Brand admin (menu, kitchens) |
| 2 | Super-admin (brand creation, cross-brand dashboard) |
| 3 | Promo codes/loyalty, delivery providers, advanced analytics |