FleetPulse Enterprise Multi-Tenant Delivery Operating System

FleetPulse – Enterprise Multi-Tenant Delivery Operating System

FleetPulse is a modern, responsive logistics and delivery management frontend designed for courier companies, fleet operators, dispatch teams, and business clients. Built with React 19, Vite 8, Tailwind CSS 4, and React Router DOM 7, it provides five dedicated role-based portals in a modular SaaS-style interface.

Five Operational Portals

Super Admin Portal: Tenant onboarding, subscription management, platform users, global settings, branding, and security configuration interfaces.

Tenant Admin Portal: Operational dashboards, shipment management, driver and fleet administration, service zones, and pricing workflows.

Dispatcher Command Center: Dispatch queues, driver assignment, route planning interfaces, fleet status monitoring, and driver broadcast messaging.

Driver Portal: Task run-sheets, pickup and drop-off workflows, navigation access, earnings, performance, and driver profile interfaces.

Client Portal: Shipment booking, delivery tracking presentation, shipment history, billing, and client-side PDF invoice generation using jsPDF.

Technology Stack

• React 19

• Vite 8

• React Router DOM 7 with lazy-loaded routes

• Tailwind CSS 4

• React Context API for authentication and session state

• Lucide React icons

• Framer Motion animations

• jsPDF and jsPDF-AutoTable for PDF generation

Setup and Development

1. Install dependencies using npm install.

2. Copy .env.example to .env.

3. Configure VITE_API_BASE_URL and VITE_WS_URL when connecting compatible backend services.

4. Start the development server using npm run dev.

5. Run npm run lint for code checks.

6. Run npm run build to generate the production bundle.

7. Run npm run preview to preview the build.

Demo Access

The login page includes a quick demo role switcher for Super Admin, Tenant Admin, Dispatcher, Delivery Driver, and Business Client. The supplied demo credentials are intended for testing the frontend interface.

Backend Integration and Deployment

When VITE_API_BASE_URL is empty, the application uses local demo fixtures and simulated network delays. A centralized API client supports connecting an external REST backend, including bearer-token injection from session storage.

The frontend can be deployed to Vercel, Netlify, or a self-hosted web server with SPA fallback routing configured.

Important: The documented package is a frontend application. A production database, server-side authentication, live WebSocket telemetry, real dispatch integrations, and backend business logic are not included by the README description and may require separate implementation.