Efes POS
The point-of-sale side of EfesMenu: table map, orders and a kitchen display, sharing one database with the menu.
- Role
- Sole developer — architecture, build, deployment
- Year
- 2026
- Status
- live
- Next.js
- TypeScript
- Supabase
- PostgreSQL
- Tailwind CSS
- Vercel
The staff side of EfesMenu, built for a phone held in one hand while the other is carrying something.
Three screens for three jobs
Table map. Zones, occupied tables with the running total, how long people have been seated and how many of them there are.
Order screen. Categories that scroll, a two-column product grid, and a cart bar that stays within reach of a thumb.
Kitchen display. Orders turn amber after seven minutes and red after fifteen, so the thing that is late is the thing you see first.
Built for touch from the start
Every button is big enough to hit while moving. The important actions sit at the bottom of the screen, where a thumb already is. Anything destructive asks first, and an error appears next to the thing that caused it.
It deliberately looks like the EfesMenu admin panel: same type, same colours meaning the same things. Someone who uses both is learning one product.
Notes
Same database as EfesMenu, so the menu stays the source of truth for products. Light and dark are both first-class, because a kitchen tablet and a phone in sunlight are not the same room.