Case study
WarehouseX management platform(mobile & website for admin + mobile driver app)
WeareHouse X is a warehouse and inventory system with a Laravel API, a Flutter driver app, and a React admin dashboard. Drivers use the app to view assigned stock, make sales, request stock from the warehouse, and get push notifications.
Technologies
About This Project
<p><span style="font-size: 24px; color: rgb(139, 92, 246);">WeareHouse X</span></p><p>is a warehouse and inventory management system with three main parts:</p><p>1. <span style="color: rgb(16, 185, 129);">Flutter app (flutter_app_wearhouse) — Driver app</span></p><p>Users: Drivers (field/mobile).</p><p>Role: Login, view assigned stock (“my stock”), sales (cart, checkout, history, invoices), stock requests (orders to warehouse), notifications (FCM), profile, settings (theme, language).</p><p>Architecture: DDD, feature-first, BLoC only, get_it DI, go_router, single NetworkClient (Dio) in data layer, token from storage.</p><p>Features: auth, home (dashboard), stock, sales, stock_request, notifications, profile, settings, menu.</p><p>2.<span style="color: rgb(16, 185, 129);"> Web dashboard (web_dashboard) — Admin app</span></p><p>Users: Admins (office).</p><p>Role: Rooms (CRUD, door config), room layout generation (validate, generate, optimize, 2D/3D view), warehouse stock, products/categories/dimensions, drivers (CRUD, analytics, inventory, settlement), sales, stock orders (approve/reject), notifications (send to driver(s)), Firebase/FCM diagnostics.</p><p>Stack: React, Vite, Tailwind, Axios, Firebase.</p><p>3.<span style="color: rgb(16, 185, 129);"> backend (backend) — Restful API</span></p><p>Role: One API for both app and dashboard; Sanctum auth with driver vs admin middleware.</p><p>Driver routes: login, my-stock, dashboard, sales, stock-orders, products (read), FCM token.</p><p>Admin routes: categories, products, warehouse-stock, rooms, room layout (validate, generate, optimize, placements), product dimensions, visualization, drivers, admin sales, stock orders (approve/reject), notifications (send), FCM diagnostics.</p><p>Room layout: Implements the algorithms in doc/<a target="_blank" rel="noopener noreferrer nofollow" class="text-primary underline" href="http://algorithms-and-architecture.md">algorithms-and-architecture.md</a>: Compartment, LAFF, Hybrid packing, smart grid, validation, optimization, persisted in MySQL.</p><p>Document created</p><p>A full system description is in:</p><p></p><p>It includes:</p><p>Project overview and high-level architecture diagram</p><p>Flutter app: role, tech stack, DDD/feature structure, features list, main user flows</p><p>Web dashboard: role, stack, main pages</p><p>Backend: role, API layout (driver vs admin), room layout and algorithms</p><p>Cross-cutting: auth/roles, FCM, config</p><p>Data flow (driver vs admin, stock, sales, layout)</p><p>Summary table (Flutter vs Web vs Backend)</p>