ProjectsKedai Cak KumLive
Kedai Cak Kum

Kedai Cak Kum

A small kitchen loses time walking back and forth to take orders. Here the table does it: each table has its own QR, the customer orders from their phone, and the admin board updates the moment an order is placed. No refresh, no shouting across the room.

What it does

  • A QR per table, so an order always knows where it belongs.
  • Menu browsing, cart and checkout on the customer's own phone.
  • Admin order board that updates live as orders come in.
  • Menu management with image upload and category grouping.

How it fits together

  1. Step 1Table QRScanned by the customer
  2. Step 2OrderPlaced from the phone, written through Drizzle
  3. Step 3PostgreSQLSingle source of truth for the order
  4. Step 4Admin boardRealtime channel pushes it to the kitchen

Diagrams

How the product behaves, and how the pieces behind it talk to each other.

Business flow
Business flow diagram for Kedai Cak Kum
System flow
System flow diagram for Kedai Cak Kum
Order sequence
Order sequence diagram for Kedai Cak Kum

Stack

App
Next.js 16 (App Router, Turbopack)TypeScript
UI
Tailwind CSS v4shadcn/ui
Data
PostgreSQLDrizzle ORMpostgres-js
Platform
Supabase Auth (Google)Supabase StorageSupabase Realtime

Worth noting

  • Orders are written in a transaction, so a cart never half-lands when something fails.
  • The admin board listens on a realtime channel instead of polling for new orders.
  • Row-level security backs the role rules, so the database refuses what the UI hides.

Next up

  • Payment gateway integration (Midtrans or Xendit).
  • A dynamic QR per transaction instead of a static one per table.
Generating0%