Foodcourt Sungai Panas

A multi-tenant food court platform: one admin panel for every branch and brand, a Flutter cashier and waiter app, and a print service on the outlet PC.

Type
Client projects
Stack
Laravel, Android
Client
Foodcourt Sungai Panas
Year
2026, ongoing
Role
Backend developer, Laravel and MySQL, plus the print service and its deployment.

The problem

A food court is many tenants under one roof. Each brand needs its own menu, prices and staff, and the cashier still has to print to thermal printers that sit on the outlet LAN, where a cloud server cannot reach them.

What I decided

  1. Branch and brand isolation is enforced in the query layer, not by hiding menu items, so a typed URL cannot cross a tenant boundary.
  2. The print service runs on the outlet PC in three containers (app, MySQL, per-branch worker). One failing printer blocks one branch queue, never the others.
  3. Print jobs are idempotent on a request id, so a phone that retries on a weak signal never prints the same ticket twice.

Where it landed

The panel covers every back-office module the outlets need, with automated tests for soft delete, cross-branch pricing and authorization.

All projectsNext project: Roxit

Client systems stay private: no source code, internal URLs or production screenshots appear here. Every figure comes from the repositories or a read-only count on the production database.