How bipulkumar62/fooddelivery-system works
This is a single-restaurant food-ordering and operations system. Customers browse the menu, request a delivery quote, and place Cash-on-Delivery orders; administrators manage orders, riders, menu availability, restaurant settings, and revenue. The backend is the only application runtime represented in detail by the supplied sources; the tree exposes an Android host entry point but not the Flutter client features. Several routes and services are unsampled, so those capabilities are retained where README evidence supports them, without asserting unshown call relationships.
Main entry points: order.service.ts Order workflow · admin.routes.ts Admin routes · order.repository.ts Order and menu queries · tracking.instance.ts Tracking service
Components 24
API runtime
- HTTP API
backend/src/app.ts - Order routes
backend/src/routes/orders.routes.ts - Admin routes
backend/src/routes/admin.routes.ts
Ordering and delivery
- Order handlers
backend/src/controllers/orders.controller.ts - Order workflow
backend/src/services/order.service.ts - Delivery quotes
backend/src/utils/deliveryCalculator.ts - Order and menu queries
backend/src/repositories/order.repository.ts - Orders
backend/src/models/Order.ts
Restaurant operations
- Menu items
backend/src/models/Menu.ts - Admin handlers
backend/src/controllers/admin.controller.ts - Menu management
backend/src/services/menu.service.ts - Settings handlers
backend/src/controllers/restaurantSettings.controller.ts - Restaurant settings
backend/src/services/restaurantSettings.service.ts - Revenue reporting
backend/src/controllers/revenue.controller.ts - Admin and rider login
backend/src/services/auth.service.ts
Live tracking
- Tracking handlers
backend/src/controllers/tracking.controller.ts - Tracking service
backend/src/services/tracking.instance.ts - Tracking events
backend/src/services/trackingEvents.ts - Socket server
backend/src/server.ts
Other components
- Customer
- Administrator
- Rider
- MongoDB
- Google Maps
Connections 26
- Customer → HTTP API: uses
- Administrator → Admin routes: manages
backend/src/routes/admin.routes.ts - Rider → Socket server: sends locations
- HTTP API → Order routes: mounts routes
backend/src/app.ts - Order routes → Order handlers: routes requests
backend/src/routes/orders.routes.ts - Order handlers → Order workflow: calls
backend/src/controllers/orders.controller.ts - Order workflow → Delivery quotes: calculates distance
backend/src/services/order.service.ts - Order workflow → Order and menu queries: reads and writes
backend/src/services/order.service.ts - Order and menu queries → Orders: queries
backend/src/repositories/order.repository.ts - Order and menu queries → Menu items: queries
backend/src/repositories/order.repository.ts - Order workflow → Restaurant settings: checks settings
backend/src/services/order.service.ts - Admin routes → Admin handlers: routes requests
backend/src/routes/admin.routes.ts - Admin handlers → Order workflow: manages orders
backend/src/controllers/admin.controller.ts - Admin handlers → Menu management: manages menu
backend/src/controllers/admin.controller.ts - Menu management → Menu items: reads and writes
backend/src/services/menu.service.ts - Admin routes → Settings handlers: routes requests
backend/src/routes/admin.routes.ts - Settings handlers → Restaurant settings: calls
backend/src/controllers/restaurantSettings.controller.ts - Restaurant settings → MongoDB: persists settings
- Admin routes → Revenue reporting: routes requests
backend/src/routes/admin.routes.ts - Administrator → Admin and rider login: authenticates
- Order workflow → Tracking service: uses tracking
backend/src/services/order.service.ts - Tracking handlers → Tracking service: uses
backend/src/controllers/tracking.controller.ts - Socket server → Tracking service: requests snapshots
backend/src/server.ts - Tracking service → Tracking events: uses events
backend/src/services/tracking.instance.ts - Socket server → Order and menu queries: verifies order
backend/src/server.ts - Administrator → Google Maps: opens coordinates