The Motobai Inventory and Sales System was one of the most significant projects I worked on during my time in university. It was developed as part of our Systems Analysis and Development (SAD) course, and it marked the first time I participated in building a complete system from start to finish.
Looking back at it now, the project represents an important step in my development as a programmer.
The Team
This project was built as a collaborative effort among three people:
- Christian Nacar – Frontend Developer
- Me – Backend Developer
- Thaddeus Domingo – Documentation
Each of us had clear roles, which helped organize the development process and allowed the project to progress more smoothly.
First Time Building a Full System
Before this project, most of the things I built were relatively small. This was the first time I worked on a full system intended to solve a real business problem.
Because of that, it introduced many concepts that felt new at the time: structuring a backend properly, connecting a frontend to an API, managing database relationships, and thinking about how users would actually interact with the system.
Technology Stack
The system was built using a modern web stack:
- React for the frontend interface
- Django for the backend
- REST API to connect the frontend and backend
- A relational database for storing system data
This setup allowed the frontend and backend to remain separate while communicating through API requests.
The tools we used were:
- mySQL for the database
- VSCode for the IDE
- Figma for the design UI
- Lucidchart for the ERD
The Business: Motobai
Motobai is a small local business that sells motor oil and motorcycle parts. Like many small businesses, much of their inventory and sales tracking was done manually.
Our task was to develop a system that could help them manage two main aspects of their operations:
- Inventory tracking
- Sales tracking
The goal was to reduce manual record keeping and make it easier for the business to monitor stock levels and transactions.
The Project Timeline
The project took approximately one year to complete, spanning:
- Second semester of second year
- First semester of third year
During that time, we went through the full development process: planning, designing, implementation, testing, and presentation.
We also had to complete two formal defenses, where the system was presented and evaluated.
System Features
The system included several features designed to support the business’s daily operations.
Some of the core functionalities included:
Inventory Management
- Stock-in and stock-out tracking
- Monitoring product quantities
Sales Management
- Walk-in orders
- Delivery orders
- Order tracking
User Management
- Creating and managing employees
- Creating customer records
Receipts
- Printable receipts for completed transactions
Together, these features allowed the system to function as both an inventory system and a sales system.
Limitations and Things to Improve
Looking back at the project now, there are several areas that could be improved.
One of the biggest limitations was within the inventory module. A typical inventory system often includes features such as supplier management and more detailed product sourcing information. These were originally considered but were ultimately not included based on the client's decision.
If the system were to be expanded in the future, adding these features would make the inventory component more complete.
There are also technical improvements I would consider today, such as:
- Improving the overall UI/UX
- Optimizing API structure
- Adding better validation and error handling
- Expanding reporting and analytics
Projects like this tend to reveal their weaknesses only after they are finished.
Looking Back
Despite its limitations, the Motobai Inventory and Sales System remains an important project for me. It was the first time I experienced what it was like to build something closer to a real-world application.
Working through planning, development, and defenses over the course of a year made the experience both challenging and rewarding.
More importantly, it helped me understand how many moving parts are involved in creating a complete system.
Project Links
Demo Video
[Watch on YouTube]
Source Code
[View on GitHub]