01 / THE PROBLEM
Connecting the workflow
A dealership needs more than a vehicle gallery: it needs searchable stock, incoming enquiries, seller submissions, follow-ups, viewings, and records of completed sales.
PROJECT CASE STUDY
Edwin’s Auto Hub
A dealership and multi-category catalogue for cars, parts, land, and houses. Includes search, saved listings, enquiries, seller submissions, inventory management, customer follow-ups, viewing schedules, and sales reports.
JavaScript · Node.js · Express · SQLite
View source on GitHub ↗
02 / MY CONTRIBUTION
What I built
I developed a responsive catalogue and protected admin workspace, later extending the inventory to car parts, land, and houses with category-specific fields.
03 / DESIGN DECISIONS
How the system fits together
- Keep inventory, enquiries, customers, viewings, and sales in one SQLite-backed workspace.
- Review seller submissions as private drafts before publishing them.
- Deduct parts quantities transactionally and reject overselling; treat vehicles and properties as single-unit listings.
- Browse catalogue
- Send enquiry
- Manage viewing
- Record sale
04 / CURRENT STATUS
Implemented scope & next steps
Implemented local application. Preview stock is illustrative; launch needs verified inventory, business details, persistent HTTPS hosting, and backups. Payments and checkout are outside the implemented scope.