Customer Data
Stores and manages the depot's customer records.
Case study
Depot Management System
A web-based management system for a family-owned drinking water depot, covering customers, transactions, stock, products, and courier payroll.
Overview
Depot Management System is a web application built for my family's drinking water depot, a small family-run business. It brings the depot's day-to-day records into one system: customer data, customer transactions, stock, and the product and payroll settings managed by the owner.
I built it as a personal project from August 21 to August 30, 2026, using a Laravel REST API, a PostgreSQL database, and a React front end.
My Role
This was a solo project. I handled it end to end, from gathering requirements through database design, back end, front end, and testing.
- Requirements analysis with the depot owners
- Database design in PostgreSQL
- REST API with CRUD operations in Laravel
- Front-end development in React
- Testing
Technology Stack
The React front end communicates with a Laravel REST API, which handles CRUD operations on data stored in PostgreSQL.
- React front end
- Laravel REST API
- PostgreSQL database
Key Features
The system has two levels of access. Regular admin use doesn't require a login, while owner features sit behind a separate owner login.
Transaction Recording
Records customer transactions for both delivery orders and customers who pick up their order at the depot.
Stock Management
Records incoming stock and calculates the available stock.
Dashboard
Brings the depot's information together in one view.
Owner Controls
After logging in as owner, the owner can set the price of each product, add new products when needed, remove products, and manage the salaries of the gallon delivery couriers.
Development Process
-
Requirements
Gathered requirements by talking with my parents, the depot's owners.
-
Database Design
Designed the PostgreSQL database for the system's data.
-
Laravel API
Built the REST API and its CRUD operations.
-
React Front End
Built the user interface on top of the API.
-
Testing
Tested the system's features.
Project Status
Developed and tested; not yet deployed.
Key Takeaway
Building a system for my family's business meant the requirements came directly from the people who would use it. Working solo, I took it from database design through the API and front end to testing.