Not a website — one platform that handles the entire loop: ordering, admin operations, ECT auto-assignment, live GPS, driver app, menu management and KPI tracking. Three role-isolated surfaces (customer, admin, driver) sit on a single PostgreSQL backbone, wired together by Realtime channels and a custom dispatch engine.
The customer browses the menu, builds a cart, fills in name, phone and a live-map delivery pin (geocoded against the city). On submit the order is persisted in PostgreSQL with full address, items, totals and a structured note field — ready for the kitchen.
The new order shows up in the admin queue in real time over WebSockets — no refresh needed. The dispatcher filters by Today / Hour / Week / Month / Custom interval, jumps between branches, and acts directly from the row: call, WhatsApp, navigate or copy the address.
Admin picks the prep time (15 / 20 / 30 / 45 / 60 min or no-ETA). The custom ECT (Expected Completion Time) algorithm proposes the driver who has been idle the longest, balanced against active workload, so the fleet self-levels. Auto (idle) is the default; a human can override in one tap.
A live overview of the entire fleet: who is available, who is busy, current ETA, today's deliveries per driver, average rating and revenue contribution. The dispatcher sees the operation at a glance and can intervene in seconds.
All active drivers stream their GPS to a Leaflet / OpenStreetMap canvas, refreshed every 5 seconds. Each marker shows the driver's distance from the restaurant, online state and which order they are currently running.
The assigned driver gets the order on their own role-isolated app: customer name, address, items, prep ETA. They tap Start to begin the run, navigate via the system map, chat with the customer if needed and close the loop with Complete.
The same admin manages the menu — bilingual (SQ + EN) names and descriptions, price, category, ingredients and optional extras. Whatever the customer sees on the ordering app is editable here, no developer required.
Orders, menu, dispatch, GPS, chat, ratings and driver-efficiency overviews all live on the same PostgreSQL backbone. Customer, admin and driver apps are physically isolated by Row-Level Security so they can never see each other's data — but operationally they move as one.