Freelance projects

Freelance projects

Refinement of the automotive parts website and future support

Databases & SQL, PHP — incorrectly specified categories?

Project translated automatically. Log in or register, to view the original

We are looking for a knowledgeable developer who has experience in the auto parts niche. Understands what "cross-number", "replacement" is and how TecDoc differs from a simple Excel price list. If you have already built parts catalogs, that is a huge plus. We have a working website, but there are several fundamental problems with the search and logic of cross-numbers that hinder sales. Also, in the future, support and fixes on the site. The site is written in Laravel. Payment is negotiable for each bug/module/problem.

Our website: avtomobile.parts

Please write about your experience and cases. All questions/clarifications and communication through PM on the site. (Working hours 8:00-17:00)

We need to address three main blocks of tasks (Budget estimated at $1000-1600, open to dialogue):

1. Smart Search

Currently, the search works too primitively without specificity for auto parts, meaning it operates based on text queries. Customers sometimes cannot find a product, even if it is in stock. It works slowly and does not yield the desired result. The search does not understand that, for example, a person enters the name and model of the car, then it should show everything available by categories, or searches by part name or OEM number or equivalent number. Also, if a customer enters a number with spaces, dashes, or other characters (for example, original number or equivalent), the search "gets lost" and returns everything or nothing.
In short, we are redesigning the search to: "Search by OEM number", "Search by equivalents", "Search by partial number", "Search by name", "Search by car".
Secondly, implement auto-suggestions. Possibly connect search engines.
References for how it should work and approximately look will be provided.

2. Restructuring the database and logic of cross-references (OEM)

This is the most important part. Currently, we lack the OEM entity. The logic of cross-references is essentially incorrect: they are tied to our product or equivalent, not to the original number. There is also no direct link of the OEM part number to things like category, car, brand, and others. Because of this, when uploading supplier price lists (The logic is such that the price list is manually uploaded and cards are created, upon updating we delete the price list and upload it anew), their product simply exists and is very hard to find, only by name (if matched) or by equivalent number. Create a separate structure (possibly a separate database), where the central figure will be the original number (OEM) and update it. Categories, applicability to cars, and equivalents should be linked to it. We are considering options for connecting via API (AutoData, Autodoc, or TecDoc) to pull data, and there should be the possibility to add our catalogs for brands that are not in the general databases.

3. Car Search

The car search function on the site also works very poorly, or rather, it is not very well implemented. All problems coincide with the points above. Here it needs to be redesigned to be more user-friendly. An example of the appearance will be provided.

Proposals 7 Withdrawn 1 Rejected 30

Andrey M.

6 0

Budget: 27000 UAH Deadline: 30 days

Good day!

I have experience working on projects in the auto parts niche, so I understand the specifics well:
OEM numbers, cross-references, substitutes, as well as the difference between TecDoc and "flat" Excel price lists from suppliers.

One of the clients is specifically in this area, where I worked with:

the logic of cross-references (OEM ↔ analogs),
processing supplier price lists,
normalizing numbers (spaces, dashes, different formats),
searching by article / part number / name.
What I see regarding your tasks:

1. Search
This is a classic problem when basic text search is used without domain logic.
Solution:

normalization of numbers (sanitize + format unification),
separate types of search: OEM / analog / name / vehicle,
indexing (Elastic / Meilisearch / Algolia — depending on the budget),
autocomplete + prioritization of results.

2. OEM as a central entity (critically important)
Currently, based on the description, you have a "reversed" data model — and this is the main reason for the problems.

The correct approach:

introduce the OEM entity (original number) as the core,
link to it:
analogs,
supplier products,
categories,
applicability to vehicles,
supplier price lists do not create "chaos," but map to OEM.

I can offer:

a new database schema (or a separate service for the catalog),
import logic with normalization,
integration with TecDoc / AutoData (or a hybrid model + your catalogs).

3. Vehicle search
Here, not only the UI is important, but also the correct data structure:

brand → model → modification → engine,
linking with OEM, not directly with products,
quick filtering through indexes.
Technically:
Laravel — okay, I work with it regularly
I work both with refactoring existing systems and with restructuring architecture
I can engage step by step: from audit → to implementation
Work format:

I suggest starting with a short audit (1–2 days):

I will look at the current database structure,
search,
import of price lists,
I will provide a specific plan (what and how to redo).

Then — move through blocks (search / OEM / vehicle).

Your budget is acceptable.

I am ready to discuss the details and look at your references.

Ihor Leontiuk

18 0

Budget: 27000 UAH Deadline: 60 days

Hello! I understand your problem: without the correct architecture of OEM numbers and data normalization, searching for spare parts turns into a lottery. I have experience building catalogs on Magento and Laravel, where I implemented exactly this logic: the central entity is the OEM number (cleansed of special characters), to which all equivalent brands are linked (through a cross-reference table) and applicability to cars.

My solution for you:
Search Engine: I will replace the standard SQL search with Elasticsearch or Meilisearch. This will solve the issues of speed, fuzzy search, and ignoring special characters (spaces, dashes, dots) in articles.
Database: Refactoring the database. We will create a separate table for oem_codes, which will be linked to products (your items) and crosses (equivalents). This will allow searching by one number to return all compatible spare parts, even if they are named differently in the supplier's price list.
TecDoc API: Integration with TecDoc (or a cheaper alternative like PartsAPI) for automatic enrichment of product cards (photos, specifications, cars) when importing price lists.

A budget of $1000-1600 is quite realistic for the basic implementation of the search core and database structure. I am ready to discuss the details and show examples of the architecture.

Andrii Siryi

0 0

Projects -
Rating -
Rating 50

Budget: 27000 UAH Deadline: 30 days

Good day!

I am ready to help with the refinement of your website and the resolution of key issues related to search and cross-referencing logic.

I have over 15 years of experience in PHP and Laravel, having worked with large catalogs and complex data logic. I understand the specifics of the auto parts niche: OEM numbers, equivalents, cross-references, applicability, as well as the difference between TecDoc and simple price lists.

I see your main problem correctly: you currently do not have a "data center" (OEM), which disrupts both search and catalog logic.

What I propose to implement:
1. Smart search

I will redesign the search into a full-fledged tool for auto parts:

Search by:
OEM number
equivalents (cross-references)
part number
product name
vehicle (make/model)
Normalization of queries:
ignoring spaces, dashes, case sensitivity
Relevant output (not just text matching)
Autocomplete (live search)
Possible integration of a search engine (Meilisearch / Elasticsearch)
2. Restructuring of the database and OEM logic (key block)

I will build the correct architecture:

Central entity: OEM number
Linked to OEM:
equivalents
categories
vehicles (applicability)
brands
Supplier products become "offers" to OEM, rather than the foundation of the system

What this will provide:

correct search
normal operation of cross-references
scalability

Additionally:

optimization of price import (without "deleted - recreated")
possibility of integration:
TecDoc / Autodoc / AutoData (via API)
support for proprietary catalogs (for unique brands)
3. Vehicle search

I will redesign the UX and logic:

Clear selection:
make → model → engine → component
Output:
all available categories and parts
Integration with the new OEM structure
Fast and logical navigation

Ihor Petrenko

0 0

Projects -
Rating -
Rating 140

Budget: 27000 UAH Deadline: 30 days

Good day!

I have experience in developing and refining e-commerce projects, including those with complex search logic and data structures. I work with Laravel and have repeatedly implemented custom search solutions (including working with articles, partial matches, data normalization, and autocomplete).

I have a good understanding of the auto parts niche:

what an OEM number is, cross-references, substitutes
the difference between "raw" supplier prices and structured catalogs (TecDoc)
typical issues: duplicates, "broken" links, incorrect searches by number
What I can offer for your tasks:

1. Smart Search

Normalization of queries (removing spaces, dashes, different number formats)
Search by:
OEM
analogs
partial number
name
car (make/model)
Implementation of autocomplete suggestions
Speed optimization (possible use of Elasticsearch / Meilisearch)

2. Database Restructuring (key block)

Building the correct model:
separate OEM entity as the center
linking: OEM → analogs → supplier products
connections with cars, categories
Reworking the logic of price imports (so that products "fit" into the system rather than existing separately)
Integration possibilities:
TecDoc / Autodoc / other APIs
Support for own catalogs

3. Car Search

Redesigning UX (make → model → engine → result)
Displaying products through OEM logic (not just by text)
Simple and clear interaction for the user
Experience / approach
Laravel (production projects)
Working with large databases and query optimization
Building logic for data import and synchronization
Understanding business logic, not just "writing code"
Work format
We can break it down into stages (search / database / car)
Payment by tasks or hourly
Always available during working hours

I am ready to thoroughly analyze your current project, look at the database, and propose a specific plan for restructuring (with technical vision, not just general words).

Your budget is acceptable.
Write in private messages — we will discuss the details.

Ivan Griga

0 0

Projects -
Rating -
Rating 87

Budget: 27000 UAH Deadline: 7 days

Good day, ready for collaboration. I have a lot of experience in projects related to auto parts, I have worked on projects for companies such as https://asg.ua, https://rooler.ua/uk, https://www.novasyla.com.ua/ and many others. I have done integrations with Tekdok and Lakhimo, searching for parts by VIN number, state number, and others. I can only provide a price after a detailed assessment of the data in the database, the technologies used, and the quality of the code.

Dmitry Thorzhevsky

101 4

Budget: 27000 UAH Deadline: 7 days

Hello!

I can take it on, it’s interesting to work long-term.

Regarding the tasks -- usually, the problems you mentioned lie somewhere in the realm of an incorrect categorization for your tasks, it is likely that fundamental technical changes will need to be made to the database structure, and this will immediately solve half of the search problems. Most likely, the design was based not on the cross-reference numbers but on some other product identifiers, possibly from the donor site or the flow document, although the cross-reference numbers are present in your database, but the links do not work on them, very strange...

A general audit of the site and the database needs to be conducted to bring it in order. This will also have an impact on SEO, which may bring in some free clients...

My experience with Laravel is diverse, from stores to large CRM systems and ERP, I have worked with categorization of 200k+ products, and I have experience integrating bm.parts.

I do not understand the automotive theme very well, but technically, search and categorization can be done without problems.

I see that there is a search by model, but there are no products, it will need to be reviewed as well, because it should globally work with substitutes, originals, etc.

After adding the number of products, the search will work even slower...

Therefore, first, a technical audit of what exists needs to be done, and then other functionalities can be configured on top.

To assess, I need to look at the project code and the database structure, then I can say how to bring the site in order with minimal costs, what needs to be done first, and what can be postponed for later.

The list does not show proposals concealed by the client or freelancer with a Plus profile, as well as proposals violating rules

Volodymyr H.

54 1

Projects 51
Rating -
Rating 4 126

Budget: 26993 UAH Deadline: 1 day

Good day, I am interested in your proposal. I would be happy to collaborate. Cost calculations and timelines will be discussed after the details are reviewed. Please take a look at the portfolio.

Valery Melnikov

15 0

Budget: 15000 UAH Deadline: 7 days

Hello
My name is Valeriy, I represent the company EchoCode

I am interested in your project, I would like to discuss the details!

Anton Bereka

0 0

Projects -
Rating -
Rating 379

Budget: 1000 UAH Deadline: 2 days

We can start with a small audit (1-2 hours): we will look at the database structure, search logic, and cross-numbers and propose a specific correction plan. After that, it will be possible to accurately assess the scope of work for each module.

We are a team of two developers, working since 2016.

Our projects:
reibert.info (a huge community, auction),
knifemaker.com.ua (online store, e-commerce)

We work with XenForo 2, Laravel, React, and the standard PHP/JS stack.

Ihor Kryvoshei

0 0

Projects -
Rating -
Rating 343

Budget: 27000 UAH Deadline: 20 days

Good day!

I am interested in your project. I specialize in Laravel, PHP, databases, and complex E-commerce systems, and I have experience working with auto parts catalogs and OEM, TecDoc, AutoData type integrations. I understand the specifics of the niche: what a "cross-number" is, "replacement," how supplier price lists work, and what problems arise when searching for products.

What I can do for your website:

Smart search:

Implementation of search by OEM number, analogs, partial numbers, part name, and vehicle.

Support for characters, spaces, dashes, and other input variations.

Auto-suggestions and quick results.

Possible integration of search engines (Elasticsearch, MeiliSearch, or others).

Restructuring of the database and cross logic:

Implementation of a separate OEM entity as central.

Linking categories, applicability to vehicles and analogs directly to OEM.

Automatic updating of supplier price lists with the possibility of connecting via API TecDoc / AutoData / Autodoc.

Support for additional catalogs for brands not present in general databases.

Search by vehicle:

Creating a convenient and "user-friendly" interface for users.

Using the correct data structure for fast filtering and searching.

I have already worked with large catalogs and search algorithms, I know how to improve the speed and relevance of searches, and I can take on both urgent bugs and a complete restructuring of the website's logic.

I would be happy to help improve the efficiency of your website and sales.

Sincerely,
Ihor Kryvoshey

Andrii Domashchenko

17 0

Budget: 20000 UAH Deadline: 14 days

Hello! 🚗🔧

I have experience working with automotive parts catalogs, searching, OEM/cross-logic, and a large nomenclature. I have worked on projects where it was necessary to redesign the search core, database structure, and relationships between products, cross-references, brands, categories, and vehicles without cosmetic patches.

Proposed stack: Laravel, Python, Django, React, TypeScript, MySQL/PostgreSQL, Elasticsearch / Meilisearch, API integrations (TecDoc / Autodoc / AutoData), Redis, Docker, import/normalization of prices, a separate layer of OEM logic.

I am ready to discuss the project details in person and promptly start working.

Best regards, Andriy!

Oleksii B.

4 0

Budget: 27000 UAH Deadline: 15 days

We have practical experience working with online auto parts stores and have a good understanding of the specifics of this niche: cross-references, analogs, OEM numbers, brands, compatibility, selection by car, catalog structure, and filtering. We have worked with TecDoc. We understand how to properly build the structure to avoid confusion with analogs and product displays.

Experience with Laravel for over 6 years.

We can help with:
- promptly fixing errors
- conducting technical audits and finding the root cause of problems
- developing new modules with scalability in mind
- providing stable project support

We write code carefully, considering the future development of the site without hidden conflicts and with minimal risk of new bugs.

We are ready to work on a long-term basis with hourly or agreed payment for each module/task.

We would be happy to discuss the details in private messages.

Dmytro Zavadskyi

4 0

Budget: 10000 UAH Deadline: 5 days

Hello.

I have reviewed the task description. Here I see not just separate improvements to the website, but issues of search logic, OEM/analog structure, and further scalability of the catalog. Therefore, it is more appropriate to approach this task not by "blindly diving into the code," but through an audit-first approach.

What I propose at the start:

analyze the current search structure, crossovers, and database

identify bottlenecks in the current logic

prepare a step-by-step plan for improvements

separately demonstrate proof of concept / initial technical solution before full implementation

after approval, move on to the next stage of implementation

This approach will allow us not to break the existing system but first agree on the correct direction regarding OEM logic, search, and catalog structure.

I am open to dialogue in private messages — we can discuss the current structure, priorities, and desired format; I can create a proof of concept before starting.

Dmitry Kozhemyakin

9 0

Projects 10
Rating -
Rating 795

Budget: 2000 UAH Deadline: 1 day

Good day!

I have over 6 years of experience working with Laravel and MySQL. I am engaged in the development and optimization of web projects, including working with complex search logic, large databases, and database restructuring.

I understand the specifics of auto parts: OEM numbers, analogs, and cross-references. I can help with reworking the search, optimizing cross logic, and improving the database structure.

I am ready to discuss the details and look at the current implementation.

Thank you!
My projects
https://carbase.pp.ua

Dmytro Zmenkov

1 1

Projects -
Rating -
Rating 121

Budget: 7999 UAH Deadline: 1 day

Good day! I am ready to complete this project. Extensive experience in developing various applications.

Vladislav Shupik

2 0

Projects -
Rating -
Rating 186

Budget: 10000 UAH Deadline: 1 day

Hello. I have experience working with Laravel. I have reviewed the task, there will be no issues with the search, we can even involve (if not already involved) Elastic Search, which works almost without load, or just review how the search is conducted on the backend side, perhaps it is enough to optimize it. Regarding #2, it needs to be visually demonstrated.

Volodymyr Mahdyk

0 0

Projects -
Rating -
Rating 390

Budget: 20000 UAH Deadline: 20 days

Hello! 🚗🔧
I have real experience working with car parts catalogs (Laravel + MySQL/PostgreSQL), I understand the specifics of "cross-numbers," "replacements," OEM logic, applicability to cars, and the differences between TecDoc, AutoData, and regular Excel/CSV price lists from suppliers. I have already reworked the search and restructured the database for car parts — exactly what you need right now.
I can effectively cover all three blocks:

Smart Search
I will redesign the search so that it understands:
OEM number (with/without spaces, dashes, letters)
partial number / equivalent
the name of the part + make/model of the car
combined queries ("right headlight BMW E46")
I will implement auto-suggestions (with your reference), quick sorting, and relevance. Integration of search engines (Meilisearch / Elasticsearch) or custom logic with caching is possible.

Restructuring the database and cross-logic (OEM)
I will create a separate OEM entity as central:
I will link the original number to the category, applicability to cars (make/model/year/body), brand, type of part
analogs and supplier products will refer to OEM
when uploading price lists — automatic matching through OEM + cache
we consider integration with TecDoc / AutoData / Autodoc API (or a combination with your catalogs)
I will ensure quick price updates without deletion and complete re-upload

Car Search
I will redesign it into a convenient, "friendly" interface (with your reference):
select make → model → year → body → engine
quick display of all compatible parts with filters
integration with the new OEM structure for accuracy
optimization of speed and relevance

Stack I will use:
Laravel (your current framework), PostgreSQL (or MySQL), TecDoc / AutoData / Autodoc API (if we connect), Meilisearch / Elasticsearch (for smart search), Redis (caching), Livewire or Inertia.js (if a fast front without reloads is needed), Docker (for stable deployment).
I am ready to take the project in stages (by bugs/modules), work during business hours (8:00–17:00), submit via Git with clear commits and explanations. A budget of $1000–1600 is quite realistic — we can detail it point by point.
I would be happy to discuss the details of the terms of reference, references, and deadlines in private messages on the exchange.
Best regards,
Volodymyr

Vlad Ivaschenko

283 2

Budget: 5000 UAH Deadline: 3 days

Good day! I have previously worked on improvements with TecDoc, my experience may not be perfect, but I am confident that I can handle your tasks as well. We can collaborate step by step; if you are satisfied with the initial edits, I will complete the rest as well.

Artem Kostrikov

39 0

Projects 15
Rating -
Rating 664

Budget: 20000 UAH Deadline: 20 days

Good day! I will help solve all problems with functionality, I have extensive experience working with functionality of various complexity. I am also a car enthusiast) and I will be very interested to work on your project!! Write to me, we will solve everything!

Dmytro Derev'iankin

2 0

Projects -
Rating -
Rating 496

Budget: 10000 UAH Deadline: 1 day

✋ Hello! We are the IT company dZENcode.

We are implementing improvements to a Laravel auto parts website: smart search for OEM and equivalents, restructuring cross-logic, and convenient selection by car, based on the team's experience, best practices, and our own developments.

Do you have a technical specification or a diagram of the current database structure?
Are you considering integration with TecDoc, Autodoc, or AutoData?

You can find detailed information about our services and rates on our website: Freelancehunt
Take a look – we will discuss the details of the work further, write when you are ready.

The final cost is determined only after clarifying the scope and requirements.

___________________
Best regards,
Manager of dZENcode

Our strengths:
💎 10+ years providing IT services: Outsourcing, Outstaffing
🔥 90+ in-house specialists
🚀 Projects "from scratch" and for support
⚙️ SLA and post-production support
✅ Contract with the company, guaranteed results!
🔥 250+ public reviews since 2015.

Tetyana V.

20 0

Budget: 13000 UAH Deadline: 7 days

Hello, Leonid!

Our IT company creates and improves websites that operate stably, quickly, and solve specific business tasks for clients. We are engaged in developing websites "from scratch" as well as enhancing existing solutions, increasing their performance and user experience for your users.

We have experience in:
- developing responsive and fast websites on various platforms (WordPress, OpenCart, Shopify, WIX);
- integrations with payment systems, CRM systems, external services, and internal systems;
- optimizing the performance and security of websites;
- setting up analytics and basic SEO tools;
- software development and automation of business processes: managing customer databases, resource accounting, automating repetitive tasks, integrations with third-party systems;

After completing the project, we provide 14 days of technical support, during which we help adapt the system to your final business processes and consult on any questions regarding the field of work performed. Thanks to the free support of the completed project, this allows you to be confident that the developed solution operates stably from the moment of launch and does not require any additional adjustments.

We work in a structured, responsible manner - focused on results that meet your business goals.

Dmytro Ivchenko

4 0

Budget: 27000 UAH Deadline: 20 days

Good day

My name is Dmytro. I have experience working with Laravel projects and a good understanding of the specifics of the auto parts niche: cross-references, OEM, analogs, applicability to cars, supplier catalogs, and the logic of TecDoc. I also understand why regular text search does not work in such a niche and how it affects sales.

I can help with three key blocks. First of all — redesign the search so that it works correctly with the OEM number, analogs, partial number, part name, and car. It is also possible to implement suggestions and, if necessary, connect a separate search engine for speed and relevance.

The second important block is the restructuring of the database and the logic of cross-references. Here, it is indeed correct to create a separate OEM entity as a central point to which analogs, categories, brands, car models, and other data are linked. This will allow for proper handling of supplier prices and prevent losing products in the catalog. If needed, a separate data layer or a separate database for this logic can be considered, as well as integration with TecDoc, Autodoc, AutoData, or other sources.

The third block is the search by car. It can also be brought to a normal, user-friendly appearance so that the selection is simpler and logically connected to OEM and categories.

I am ready to work step by step, on separate modules and tasks, with further support for the website. The budget you specified looks realistic for starting on these key blocks. After clarifying the current database structure and website logic, I will be able to propose a more precise implementation plan.

I would be happy to discuss the details in personal messages.

Raisa Krushevska

8 0

Budget: 5000 UAH Deadline: 10 days

Good day,
I can complete your task quickly and efficiently.
Feel free to contact me to discuss the details.

Roman Matvii

67 0

Budget: 27000 UAH Deadline: 15 days

Hello! I will complete your task quickly and efficiently. I work with Laravel.

My portfolio: https://freelancehunt.com/ua/freelancer/romas6ka.html#portfolio
Write to me, I will start working today. I will be happy to collaborate with you!

Maksim Piskun

5 0

Budget: 20000 UAH Deadline: 10 days

Good day.

I work with Laravel, have dealt with spare parts catalogs and OEM/analog logic.

According to your description, the problem is typical — when cross-references are tied to products instead of OEM. This breaks both the search and the loading of price lists. I can redesign the database structure so that the central entity is the OEM number, with links to analogs, cars, and categories, and build the search properly.

It is better to implement the search through Elastic to ensure it works quickly and efficiently, as well as provides suggestions during input.

I am ready to join the project, understand the current logic, and gradually close these task blocks.

Write to me in private messages, send access or technical details — I will look at the code and provide a more precise estimate on terms and costs.

Vladislav Polishchuk

52 0

Budget: 1111 UAH Deadline: 1 day

Good day, Leonid
I have experience with Laravel, I understand what a "cross-number" and a "substitute" are, and how TecDoc differs from a simple Excel price list.
Write to me, I will be happy to collaborate.

Leonid Motroy
Dnepr, Ukraine

Projects 2
Rating -
Rating 264

Refinement of the automotive parts website and future support

Andrey M.

Ihor Leontiuk

Andrii Siryi

Ihor Petrenko

Ivan Griga

Dmitry Thorzhevsky

Proposals are currently absent

Proposals concealed

Volodymyr H.

Valery Melnikov

Anton Bereka

Ihor Kryvoshei

Andrii Domashchenko

Oleksii B.

Dmytro Zavadskyi

Dmitry Kozhemyakin

Dmytro Zmenkov

Vladislav Shupik

Volodymyr Mahdyk

Vlad Ivaschenko

Artem Kostrikov

Dmytro Derev'iankin

Tetyana V.

Dmytro Ivchenko

Raisa Krushevska

Roman Matvii

Maksim Piskun

Vladislav Polishchuk

Proposals concealed

Current freelance projects in the category Databases & SQL

Development of an analytical system with a dashboard

Support and refinement of the database on Yii

Migration of the database from one CRM to another

A dashboard needs to be created in Looker Studio.

Back-end developer (Nest.js)