MenuWave

01 — Overview

MenuWave puts the whole operation on one multi-tenant platform. A Laravel application owns the data and business rules; dedicated Flutter clients run the point of sale, the kitchen display and the signage screens, each talking to the same tenant-scoped backend.

02 — The problem

Restaurants run on disconnected tools — one for the menu, one for the till, paper tickets for the kitchen and a separate box for in-store screens. Each tool keeps its own data, so owners never see one picture of the business and every menu change is made several times.

03 — My contribution

Product engineer — platform architecture, Laravel backend, admin workspace and Flutter device clients.

04 — System architecture

1. 01 · frontend

   Clients

   • Admin workspace (Blade, Tailwind, Alpine.js, Vite)
   • MenuWav POS — Flutter, Riverpod, go_router
   • MenuWav Kitchen — Flutter, GetX
   • MenuWav Player (signage) — Flutter, GetX, video_player

2. 02 · api

   HTTP & API

   • routes/api.php + web route groups: admin (platform, workspace), pos, kitchen, rider, billing, marketing
   • Laravel Sanctum
   • AuthenticateMenuWaveDevice middleware
   • AssignRequestId & SecurityHeaders middleware

3. 03 · services

   Domains & services

   • 25 domain modules under app/Domains (Tenancy, Orders, Kitchen, Payments, Delivery, Inventory, Workforce, Accounting …)
   • Policies + EnsurePermission / EnsureSubscribed / EnsureKitchenAccess middleware
   • Queued jobs
   • AI usage tracking (AiUsage model)

4. 04 · database

   Data

   • 116 Eloquent models · 75 migrations
   • TenantScope global scope
   • MySQL (server) · SQLite via sqflite (POS & player, on-device)

5. 05 · infrastructure

   Integrations

   • Stripe (stripe/stripe-php, StripeEvent model)
   • Redis
   • AWS
   • OpenAI
   • ESC/POS USB receipt printing (POS)
   • QR-based screen pairing (player)

05 — Technology stack

• Laravel 13
• PHP
• Sanctum
• Vite
• Tailwind CSS
• Alpine.js
• Flutter
• Riverpod
• GetX
• SQLite (on-device)
• MySQL
• Redis
• Stripe
• AWS
• OpenAI

Taken from the project's manifests and architecture documentation.

06 — Modules

• Tenancy & identity
• Catalog & pricing
• Orders & payments
• Point of sale
• Kitchen display
• Guest ordering
• Delivery & riders
• Digital signage & video walls
• Inventory & production
• Workforce & shifts
• CRM, loyalty & promotions
• Accounting & reporting
• Food safety
• Maintenance

07 — Engineering decisions

• Multi-tenancy at the query layer (a global TenantScope) instead of separate databases — onboarding a restaurant is configuration, not a deployment.
• Domain-oriented code organisation (app/Domains/*) so Orders, Kitchen, Inventory and Workforce can grow without a single bloated services folder.
• Separate device authentication for POS tablets and signage screens, distinct from staff logins.
• Native Flutter clients for hardware-facing roles: USB receipt printers, always-on TV playback (wakelock), and on-device SQLite.
• Subscription and permission checks expressed as middleware (EnsureSubscribed, EnsurePermission, RedirectUnpaidTrial) so access rules sit in one place.

08 — Challenges & solutions

09 — Performance & scalability

• Local SQLite on POS and player clients
• Queued jobs for slow work
• Redis configured for cache/queues

10 — Security

• Tenant isolation via global query scope
• Role, permission and subscription middleware
• Device authentication for screens and tablets
• Request IDs and security headers on every response
• flutter_secure_storage for credentials on devices

11 — Infrastructure & deployment

Live at menuwav.com. The repository contains a public_html.htaccess for shared-hosting deployment; hosting topology beyond that is not documented in the repositories.

12 — Outcomes

• Live product at menuwav.com

13 — Evidence

Architecture and implementation documented in source · reviewed 8 Nov 2026

• Private repository
• Architecture document (private repository)
• Private repository
• Architecture document (private repository)
• Private repository
• Architecture document (private repository)
• Private repository
• Architecture document (private repository)
• menuwav.com
• Project inventory in GitHub profile README

Private repositories are available to review on request.