03 / The Build Log / Food Ordering / FoodTech
Kay's Deli
Guest checkout without leaking the guest
A mobile-first food ordering app with a SECURITY DEFINER order function, privacy-aware tracking and an admin intelligence dashboard.
- Role
- Frontend Development
- Category
- Food Ordering / FoodTech
- Status
- In build
- Year
- 2026

[build: deli-build-log] — In build
01 / The brief
A real deli, a real menu, no online ordering
Kay’s Deli is a food business in Delta State with rice dishes, proteins, deli items, cakes, smoothies and cocktails. Ordering ran through WhatsApp and phone calls. The brief was a mobile-first ordering site with a kitchen-grade admin panel.
Guest checkout was required. Phone number replaced email, because dispatch calls customers. The admin needed real business insight, not just a list of orders.
“Privacy by omission, not by obscurity.”
02 / Architecture
TanStack Router, Supabase and a privacy boundary
The app is React with TanStack Router, TypeScript, Tailwind and Supabase. Recharts powers the revenue and best-seller views. Telegram carries order notifications to the kitchen.
The `place_order` function is a SECURITY DEFINER: it validates the order server-side. The `get_order` query deliberately omits the customer phone number, so a guest can track an order without exposing contact details to the query layer.
- Guest checkout with phone number — no account required
- SECURITY DEFINER place_order, privacy-aware get_order
- Order tracking timeline with a timestamp on every status change
- Admin: revenue, best-sellers, top customers, status board
03 / System map
Guest order path
Guest
No account
place_order
SECURITY DEFINER
Order
Validated server-side
get_order
Phone omitted
Track
Status timeline
Dispatch can call the customer from the admin side; the public tracking query never returns the phone number.
04 / The hard parts
Privacy by omission, not obscurity
A guest order means a phone number travels through the system. The design decision was to keep the phone number out of the tracking response entirely, while still letting dispatch call the customer from the admin side.
The admin analytics had to answer real questions: revenue by period, best-selling dishes, top customers by spend and order status by stage — all from a single date-range filter.
05 / The proof
Built in July 2026 — not yet live
The ordering and admin sides are complete. The restaurant is still onboarding, so the site is not live yet. The initial specs were scaffolded with Lovable; the production code, database schema, RLS and admin panel are built from scratch.
- Mobile-first ordering for a real restaurant in Delta State
- Guest checkout with phone number
- Admin revenue charts, best-sellers, top customers and status board
- Built solo July 2026 — design, frontend, Supabase backend, admin
06 / Selected screens
Inside the build


07 / What I’d change
Real food photography and a kitchen display
The placeholder food images are temporary; real photography is planned before launch. The next operational feature is a kitchen display view, so the line can work from a screen instead of refreshing the order list.
Built with
Next in The Build Log
Borrowly
A React front-end prototype with one price calculation shared across eight screens, local state and no backend.