FoodFleet Audit Report

Audit of FoodFleet — multi-vendor food delivery marketplace (Uber-Eats clone). Marketing page is substantially built; the demo is a placeholder pending actual app launch. A FoodFleet API service IS running on PM2 (foodfleet-api) with 6 days uptime — suggests more backend plumbing than the placeholder reveals.

2 live + API

Pages / Routes

Bugs Found

Fixed

Open

Executive Summary

FoodFleet aims to be a complete food-delivery SaaS with Super Admin, Vendor, Delivery, and Customer panels (PWA). The marketing site at /foodfleet/website/ has a polished dark-cyan hero with phone mockup + partial feature tabs (below empty). The demo at /foodfleet/ is a placeholder like StockNova/SupportDesk with credential hints. The foodfleet-api PM2 process has 6 days of uptime serving /foodfleet/demo/{customer,admin,vendor,delivery}/api/ — so the backend is live and deployed, just without a rendered frontend connected.

Stack & Access

Backend API	Node.js PM2 `foodfleet-api` on port 5050 (6d uptime)
Frontend	4 SPA panels at `/foodfleet/demo/{admin,customer,vendor,delivery}` — nginx serves `index.html` fallback
Marketing	foodfleet/website/
Demo landing	foodfleet/
Hinted creds	[email protected]/Admin@123, [email protected]/Vendor@123, [email protected]/Delivery@123, [email protected]/Customer@123

Screenshots

**/foodfleet/website/** — Hero 'The Complete Food Delivery SaaS Platform' with phone mockup; feature tabs (Customer PWA / KDS / Multi-Vendor / Delivery Zones) — middle sections empty.

**/foodfleet/** — Placeholder with 4 panel icons (Super Admin / Vendor / Delivery / Customer PWA), 4 feature highlights, credential table, 'Demo setup in progress', 'Buy on CodeCanyon Coming Soon'. 4 hinted logins but no clickable demo panels from this page.

Bugs

BUG-001MAJOROPEN

Demo placeholder doesn’t link to the actual SPA panels that exist at /foodfleet/demo/{role}/

Found during audit: Nginx has fallback rules for /foodfleet/demo/customer|admin|vendor|delivery with try_files $uri $uri/ /index.html — meaning SPA shells are deployed, but the placeholder demo page doesn’t link to them.
Additionally: One tested path /foodfleet/demo/ returned 403.
Fix plan: Replace the placeholder demo page with 4 prominent links to each role's SPA (Admin / Vendor / Delivery / Customer PWA), and fix the 403 on /foodfleet/demo/.

Recommendation

Of the 'Coming Soon' batch (StockNova / SupportDesk / FoodFleet), FoodFleet is closest to demo-ready because the backend API and SPA shells are already deployed. Linking the placeholder to the real demo panels is a 15-minute task.

FoodFleet audit · 2026-04-19 · 2 screenshots · 1 bugs