Vehicle Inventory Management System
Custom Online Inventory Pipeline
A custom inventory workflow for adding, storing, and displaying vehicles for sale on an automotive business website.
Implementation Focus
What I implemented
Designed and built a custom vehicle inventory system that allowed an automotive business to add, store, and display vehicles for sale on its website.
Problem
HEM had expanded into used vehicle sales but had no digital way to showcase available vehicles. Without an inventory system, each vehicle would have required manual page creation or would remain invisible to online shoppers.
Approach
Built a MERN-based inventory pipeline with admin vehicle intake, image uploads, cloud storage, API-driven data delivery, and dynamic frontend listing pages.
Outcome
Enabled the business to display vehicles online for the first time through an inventory overview page and individual vehicle detail pages.
Constraints
- This was the first system built beyond a basic CRUD application.
- The business needed it delivered quickly.
- Image ordering depended on strict file naming.
- Editing did not work from the frontend and required manual database updates.
- Image aspect ratio and count were rigid in the first version.
Tradeoffs
- Prioritized speed over a complete sales workflow.
- Built a listing system instead of a full vehicle sales platform.
- Deferred pricing logic, deposits, online purchase flow, and customer lifecycle tracking.
Ownership
What I owned
Execution Breakdown
How the work was implemented
Inventory Intake System
Created an admin-side workflow for adding vehicles and making them visible on the public website.
Vehicle Creation
Added vehicle details through an admin workflow instead of manually building new pages for each listing.
Vehicle Status
Supported basic lifecycle status such as available and sold so vehicles could be shown or removed from public inventory.
Image Uploads
Supported multiple images per vehicle using Multer, with media stored through DigitalOcean.
Frontend Inventory Display
Built public-facing inventory pages that dynamically rendered vehicle data from the backend.
Inventory Overview
Created a page showing all available vehicles in a browsable layout.
Vehicle Detail Pages
Created templated individual pages for each vehicle using backend data.
Website Integration
Connected inventory data to the existing HEM website so vehicle listings became part of the public customer experience.
Backend & API Design
Built the inventory system as an API-driven MERN application.
MongoDB Storage
Stored vehicle metadata such as year, make, model, description, status, and image references.
API Gateway
Routed inventory requests through a custom API gateway.
Rate Limiting
Added request limits to control how often vehicle pages could be accessed within a short time window.
Media Handling
Managed vehicle photography as part of the listing workflow.
Image Count
Supported up to 40 images per vehicle in the first version.
Aspect Ratio Requirement
Images needed to follow a consistent 3:4 aspect ratio to display correctly.
Ordering Constraint
Image display order depended on file naming, which exposed the need for better media ordering controls in future versions.
Workflow
System flows
Vehicle Intake to Public Listing Flow
- 1Vehicle is repaired, cleaned, and photographed.
- 2Admin enters vehicle details into the inventory system.
- 3Admin uploads vehicle images.
- 4Vehicle metadata is stored in MongoDB.
- 5Images are stored through DigitalOcean.
- 6Frontend fetches vehicle data through the API.
- 7Vehicle appears on the public inventory overview page.
- 8Customer can open an individual vehicle detail page.
Vehicle Status Flow
- 1Vehicle is created as available.
- 2Vehicle displays publicly on the website.
- 3When sold, vehicle status is changed to sold.
- 4Sold vehicles are removed or hidden from the public available inventory.
Results
Impact and outcomes
Online Inventory Visibility
Gave the business a way to show available vehicles online for the first time.
Repeatable Listing Pipeline
Replaced manual vehicle page creation with a reusable intake and display workflow.
Foundation for Vehicle Sales Systems
Created an early system that later informed Skynetrix vehicle sales and inventory concepts.
Visual Proof
Screens and artifacts
Vehicle Inventory Pages
Screenshots showing the public inventory overview and individual vehicle listing pages.
Reflection
What I learned
What worked
- The system solved the immediate visibility problem by getting vehicles onto the website.
- The API-driven structure made the inventory reusable across frontend pages.
- Building media uploads forced a better understanding of file handling, storage, and frontend rendering.
What I’d improve
- Add full frontend editing support.
- Remove manual database update requirements.
- Decouple image order from file naming.
- Allow flexible image aspect ratios and more flexible image limits.
- Improve vehicle detail page URLs for SEO.
- Integrate VIN Vision to automate VIN-based vehicle data entry.
- Add online deposits and payment support.
- Connect vehicle inventory to customer and sales records.
- Add pricing logic or AI-assisted pricing recommendations.
Key takeaway
The Vehicle Inventory Management System showed how a simple business need can quickly become a systems problem involving media handling, data modeling, API design, frontend rendering, and future sales workflows.