Takeaway Ordering Platform — Web, Admin & Mobile

Context

Takeaway restaurants pay heavy commissions to delivery marketplaces. The goal: an ordering system a restaurant owns, reusable across businesses without hard-coding branding, currency, fees, opening hours or API URLs.

System design

  Customer app (Expo, iOS/Android)      Restaurant admin (Next.js)
               │                                   │
               └──────────────┬────────────────────┘
                              │ HTTPS
                    ┌─────────▼─────────┐
                    │ Nginx + Certbot   │  TLS, api./www. routing
                    └─────────┬─────────┘
         ┌────────────────────┼─────────────────────┐
         │          ┌─────────▼─────────┐           │
         │          │ Django REST (web) │── JWT     │
         │          └──┬──────────┬─────┘           │
         │     ┌───────▼──┐   ┌───▼─────┐           │
         │     │ Postgres │   │  Redis  │◄─┐        │
         │     └──────────┘   └─────────┘  │        │
         │                    ┌────────────┴──┐     │
         │                    │ Celery worker │     │  order emails,
         │                    └───────────────┘     │  payment events
         └──────────── Docker Compose ──────────────┘
                              │
                        Stripe (+ webhooks)

Key decisions

• Tenant configuration, not forks. Branding, currency, delivery fee and hours come from config, so a new restaurant is a deployment, not a code change.
• Celery for anything slow — payment webhooks and notifications never block an order request.
• One Compose file for the whole stack (API, worker, admin, Nginx, Certbot, Postgres, Redis) — reproducible on a single droplet, with a documented first-deploy runbook.
• Expo + EAS Build for one TypeScript codebase on Android and iOS, with TanStack Query, Zustand and SecureStore for tokens.

Status

Backend, admin and deployment stack built; mobile app in active development. Delivered through KohzadTech.