Auto Parts Marketplace Web App
Budget / Salary$250–750
TypeFreelance project
LocationRemote
Posted1 hour ago
Automotive Spare Parts Platform
Create a responsive web application, accessible from both smartphones and computers, that connects customers with multiple automotive spare parts shops.
1. Vehicle Identification
The customer has 3 options:
* Take a photo/upload a photo of the vehicle registration card
* Enter the VIN + vehicle model
* Select the vehicle manually, but in this case all required fields must be completed: make, model, year, engine, etc.
2. Finding a Spare Part
The customer selects one category:
* Front suspension / front axle
* Rear suspension / rear axle
* Engine
* Bodywork
* Interior
Then the customer searches for the required part.
The catalogue displays only:
* Part name
* Part reference
No prices are displayed in the catalogue.
If the required part is not available in the catalogue, the customer can use “Request a Part”, describe what they need and optionally add a photo.
3. Partner Spare Parts Shops
Each shop has its own account.
Requests are sent to shops that match the requested brand/part.
The shop can:
* Confirm availability
* Reject the request
* Propose a price
* Offer pickup or delivery
Several shops can respond to the same request.
4. Comparing Offers
The customer receives the different offers and can compare them.
Before accepting an offer, the customer can see:
* Proposed price
* Availability
* The shop’s region/locality, so the customer can evaluate its proximity
However, the customer cannot yet see:
* Shop name
* Phone number
* Exact address
* Direct contact information
5. Accepting an Offer
Once the customer accepts an offer:
* The shop name becomes visible
* The phone number becomes visible
* The address/location becomes visible
* The order is created
* A unique order number + code/QR code are generated
For delivery, the necessary customer contact details are shared with the shop after the offer is accepted.
6. Shop Pickup
To collect the part, the customer presents their code or QR code.
The shop uses this code to:
* Identify the order
* Confirm the customer’s arrival
* Validate the sale
The system records the different steps:
Request → Offer → Acceptance → Customer arrived → Sale completed
Other possible statuses:
* Rejected
* Cancelled
* Customer did not show up
* Sale not completed
The customer can also confirm that the sale was actually completed.
7. Administration
The administrator can manage:
* Shops
* Brands
* Models
* Parts
* References
* Requests
* Offers
* Orders
* Sales
* History
The system should also allow the administrator to track sales generated by each shop and generate monthly reports.
8. Business Model
* Customer: Free
* Shop: Free
* No online payment at the beginning
* No centralized inventory
* Each shop keeps and manages its own stock
* Shops handle pickup and/or delivery
* The platform earns a commission from sales generated through the platform
9. Initial Version
I want to start with a very simple, low-cost and scalable MVP.
No need initially for:
* Native iPhone application
* Native Android application
* Online payment
* Unnecessary complex features
A responsive web application is sufficient.
10. Development Quote Required
Please provide:
1. Total development cost
2. Estimated development time
3. Technologies to be used
4. Annual hosting cost
5. Domain name cost
6. Maintenance cost
7. Detailed list of everything included in the quotation
Objective: Build a simple, reliable, secure and scalable first version without unnecessary expenses.
Create a responsive web application, accessible from both smartphones and computers, that connects customers with multiple automotive spare parts shops.
1. Vehicle Identification
The customer has 3 options:
* Take a photo/upload a photo of the vehicle registration card
* Enter the VIN + vehicle model
* Select the vehicle manually, but in this case all required fields must be completed: make, model, year, engine, etc.
2. Finding a Spare Part
The customer selects one category:
* Front suspension / front axle
* Rear suspension / rear axle
* Engine
* Bodywork
* Interior
Then the customer searches for the required part.
The catalogue displays only:
* Part name
* Part reference
No prices are displayed in the catalogue.
If the required part is not available in the catalogue, the customer can use “Request a Part”, describe what they need and optionally add a photo.
3. Partner Spare Parts Shops
Each shop has its own account.
Requests are sent to shops that match the requested brand/part.
The shop can:
* Confirm availability
* Reject the request
* Propose a price
* Offer pickup or delivery
Several shops can respond to the same request.
4. Comparing Offers
The customer receives the different offers and can compare them.
Before accepting an offer, the customer can see:
* Proposed price
* Availability
* The shop’s region/locality, so the customer can evaluate its proximity
However, the customer cannot yet see:
* Shop name
* Phone number
* Exact address
* Direct contact information
5. Accepting an Offer
Once the customer accepts an offer:
* The shop name becomes visible
* The phone number becomes visible
* The address/location becomes visible
* The order is created
* A unique order number + code/QR code are generated
For delivery, the necessary customer contact details are shared with the shop after the offer is accepted.
6. Shop Pickup
To collect the part, the customer presents their code or QR code.
The shop uses this code to:
* Identify the order
* Confirm the customer’s arrival
* Validate the sale
The system records the different steps:
Request → Offer → Acceptance → Customer arrived → Sale completed
Other possible statuses:
* Rejected
* Cancelled
* Customer did not show up
* Sale not completed
The customer can also confirm that the sale was actually completed.
7. Administration
The administrator can manage:
* Shops
* Brands
* Models
* Parts
* References
* Requests
* Offers
* Orders
* Sales
* History
The system should also allow the administrator to track sales generated by each shop and generate monthly reports.
8. Business Model
* Customer: Free
* Shop: Free
* No online payment at the beginning
* No centralized inventory
* Each shop keeps and manages its own stock
* Shops handle pickup and/or delivery
* The platform earns a commission from sales generated through the platform
9. Initial Version
I want to start with a very simple, low-cost and scalable MVP.
No need initially for:
* Native iPhone application
* Native Android application
* Online payment
* Unnecessary complex features
A responsive web application is sufficient.
10. Development Quote Required
Please provide:
1. Total development cost
2. Estimated development time
3. Technologies to be used
4. Annual hosting cost
5. Domain name cost
6. Maintenance cost
7. Detailed list of everything included in the quotation
Objective: Build a simple, reliable, secure and scalable first version without unnecessary expenses.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.