How kunalkharga/inventory-management-system works
Project type and purpose
• This is a full-stack, monolithic PHP/MySQL web application—an Inventory Management System.
• It provides a browser-based UI for administrators to perform CRUD on products, track stock, manage sales and suppliers, and generate PDF invoices/reports.
High-level file-structure analysis
• Top-level PHP scripts (add_product.php, sales.php, admin.php, etc.) act as controllers/pages.
• includes/ holds shared modules: config.php (DB credentials), database.php (DB connection), sql.php (queries), session.php, upload.php, functions.php.
• layouts/ contains view templates (header, footer, menus).
• libs/css and libs/js serve static assets for styling/interaction.
• fpdf/ is an external library for PDF generation.
• uploads/ is the filesystem store for user- and product-uploaded images.
• DATABASE FILE/inventory_system.sql holds the MySQL schema.
README insights
• Confirms tech stack: Frontend – HTML/CSS/Bootstrap/JS; Backend – PHP; Database – MySQL; Local Server – XAMPP.
• Mentions core features like CRUD, stock tracking, sales processing, user auth, responsive design, PDF reports.
Main components and relationships
A. Browser (Client)
• Sends HTTP(S) requests, renders HTML/CSS/JS.
B. Web Server + PHP Runtime
• Receives requests, routes them to the appropriate .php page (index.php, auth.php, sales.php).
• Each page includes common modules (includes/*.php).
C. Business-Logic Layer (includes/functions.php + page scripts)
• Validates input, enforces rules (e.g., stock limits).
D. Data-Access Layer (includes/database.php + includes/sql.php)
• Executes SQL against MySQL.
E. MySQL Database
• Stores tables for users, products, categories, groups, sales, suppliers, sessions.
F. File Storage (uploads/)
• Persists uploaded product/user images.
G. PDF Generator (fpdf/)
• Generates invoice/sales PDF on demand.
H. Static Assets (libs/)
• CSS for styling, JS for client-side behaviors.
Data Flow:
1. Client → HTTP request → PHP page
2. PHP page → includes → business logic → data access → MySQL
3. MySQL → result → PHP builds HTML
4. PHP → HTML + CSS/JS → Client
5. On PDF/report: PHP → fpdf library → PDF → Client download
6. File upload: Client → PHP upload module → writes to uploads/ → DB updated with file path
Architectural patterns & design principles
• Layered architecture (Presentation / Business Logic / Data Access).
• Modularization via includes/ for reuse (e.g., session handling, DB connection).
• Logical separation of view templates (layouts/) from controllers (PHP pages) and models (SQL scripts).
• Use of external library (fpdf) for a cross-cutting concern (PDF generation).
Technologies and frameworks
• PHP 7+ on Apache (XAMPP)
• MySQL 5.7+
• fpdf for PDFs
• Bootstrap (via libs/css) for responsive UI
• Vanilla JS for client interactivity