At Praxium Labs — Nepal's AI and automation consultancy — we see this pattern across most Nepali engagements. Food delivery in Nepal is structurally harder than ride-share because of the multi-vendor (restaurant) coordination layer. The technical architecture must orchestrate four parties simultaneously — customer, restaurant, courier, ops — across a single order lifecycle.
The four-party orchestration
- Customer: browses, orders, tracks, rates
- Restaurant: receives order, prepares, marks ready
- Courier: picks up, delivers
- Ops dashboard: monitors live state, intervenes on exceptions
Order state machine
- Created — customer submits
- Accepted by restaurant (or auto-accepted)
- Preparing — kitchen working
- Ready — courier called for pickup
- Courier assigned — courier en route to restaurant
- Picked up — courier has food
- Delivered — handover to customer
- Cancelled / refunded — exception flow at any stage
Tech stack
- Mobile (customer + courier): Flutter or React Native
- Restaurant tablet: Android tablet running a dedicated app (we use Flutter for cross-platform; some prefer native Android for stability)
- Backend: Node.js / Go; Postgres for orders; Redis for live courier locations and queues
- Real-time: WebSocket via Socket.io / native Channels; Firestore listeners for less-critical paths
- Maps: Google Maps or Mapbox
- Payments: eSewa, Khalti, Fonepay, COD
- Notifications: FCM + WhatsApp Business API for customer order confirmations
Kitchen capacity management
Restaurants have finite simultaneous-order capacity. Naive: accept every order; let kitchen overflow. Better: each restaurant has a configurable "max in-flight orders". The dispatcher checks capacity before assigning; if at cap, customer sees longer ETA or queue. This single feature differentiates "professionally operated" apps from ones that mostly burn restaurant relationships.
Courier supply
- Demand-prediction model for couriers — peak lunch/dinner times need pre-positioned supply
- Incentives for couriers to be online during peaks (surge pay, completion bonuses)
- Multi-pickup routing: one courier picks up 2-3 nearby orders to improve unit economics; complex routing optimisation
- Driver onboarding: background check, vehicle verification, training. The ops cost is significant
COD handling at scale
COD is meaningful share of Nepali food-delivery orders. Reconciliation: at end of day, each courier returns cash; settles against their orders. Apps handle this via end-of-day cash deposit at hub or via real-time digital settlement (courier pays restaurant's share digitally, takes cash). Either way, the bookkeeping is non-trivial.
What does Foodmandu / Pathao Food do differently?
Beyond technology: deeper restaurant integration (POS-level), better courier supply (more drivers per zone), surge pricing during demand spikes, packaging standards, and dispute resolution playbooks. A new entrant matches on technology in 12-18 months; matching operations and unit economics takes 3-5 years and significant capital.
Logistics-side architecture
The hardest part of a food-delivery app in Nepal is not the customer-facing UI; it is the dispatch optimisation. Given N riders and M open orders at any moment, the system must continuously assign riders to maximise throughput while minimising delivery time. Algorithms: simple distance-first works at < 100 orders/hour. Real bin-packing / vehicle-routing optimisation becomes necessary above that. Foodmandu, Pathao, Foodmario all run dispatch engines that have evolved over years. See our ride-sharing architecture post for parallel patterns.
Local realities
- Addresses are imprecise in Kathmandu Valley — landmarks more useful than house numbers. Capture both
- Cash on delivery remains dominant for non-tech-comfortable users; have a cash-reconciliation flow for riders
- Restaurant prep variability — average prep is wildly different across restaurants; learn it per-restaurant rather than assuming a flat 15 minutes
- Rider attrition is the biggest operational cost driver; weight incentives toward retention not just per-order earnings
- Festival / event spikes — Dashain dinner, Tihar bhai-tika lunch are 5-10x normal volumes; cap dispatch or prepare extra capacity
Frequently asked questions
Should we build vs partner with Foodmandu / Pathao Food?
For most new entrants: build only if you have a specific niche (cuisine, geography, B2B corporate). Mass-market consumer is dominated by incumbents; the unit economics are punishing without scale.
How long to MVP?
8-14 months for MVP across all four parties. Pilot in one neighbourhood with 5-10 restaurants is achievable in 6 months if scope is disciplined.
What's the right city to start in?
Either a Kathmandu neighbourhood (high density, demand) or a Tier-2 city (less competition, lower customer-acquisition cost). Pokhara and Biratnagar have growing demand and less competitive supply than Kathmandu.
How do restaurants prefer to receive orders?
Most prefer a dedicated tablet over receiving orders mixed with phone calls. The tablet must work reliably during peak hours and not require manual refresh — too many apps fail here. Default to an Android tablet with the merchant app in kiosk mode.
What about commission rates?
Industry standard 15-25% commission; restaurant negotiations are part of the business. New entrants typically offer 8-12% commission to acquire restaurant supply; raise once entrenched.
Build vs license existing platform?
For new Nepali entrants, building from scratch rarely makes economic sense unless you have a clear differentiation (cloud kitchen integration, niche cuisine). White-label platforms exist but most successful Nepali food-delivery is custom-built with years of iteration.
How does GPS accuracy affect dispatch?
Significant — urban canyons in dense Kathmandu wards drop GPS accuracy to 30-50m. Combine with WiFi triangulation and rider self-reporting for usable position data.
Who can build this in Nepal?
Praxium Labs — Nepal's AI and automation consultancy, based in Lalitpur — designs and builds the systems described in this guide for Nepali businesses and for international teams hiring from Nepal. Start a project or see all services.