Audit of parsers and their settings - OpenCart

Budget: 3000 UAH Deadline: 1 day

Hello!

I have reviewed the task description. As I understand it, the goal is not just to eliminate the current duplicates of categories, filters, and attributes, but to find the root cause of their appearance and to select a solution that will prevent the problem from recurring.

Before proposing an implementation, I believe it is appropriate to conduct an audit of the current import scheme: analyze the settings of SimplePars, the logic of the parsers and sub-parsers, check the mechanism for forming categories, filters, and attributes, and also assess whether the problem is indeed related to the limitations of the parser itself or if the cause lies in the existing configuration.

Based on the audit results, I will be able to propose the most rational solution with an explanation of why it will be optimal in your case, and if necessary, evaluate the implementation.

For an accurate assessment of costs and timelines, I need to clarify a few technical details in personal correspondence.

Budget: 12000 UAH Deadline: 3 days

The budget of 1000 UAH for such a task will likely not even cover a normal audit - the issue is not just with one filter, but with the logic of import, mapping of categories, attributes, and rules for cleaning before writing to OpenCart.

I can conduct an audit of SimplePars and the catalog structure - in 2-3 days we will check the settings of the parsers, duplicates of filters, unnecessary categories, rules for auto-replacements, and points where data is contaminated again. In the end, I will provide not just a list of errors, but a solution - what to correct in the settings, where a cron module is needed, and where it is better to normalize data before it enters the catalog.

Look, there is a nuance - if the parsers are already broken down into sub-parsers and auto-replacements do not work, then a one-time cleanup is almost meaningless. It is necessary to create a layer of rules - standard categories, a dictionary of attributes, duplicate checks, change logs, and safe updates without recreating garbage. Overall, it’s a normal situation; we just need to treat the cause, not the symptoms =)

I will clarify 2 points:
> how many sources are currently being parsed through SimplePars
> is there access to the OpenCart admin panel, SimplePars settings, and the database for analysis

Similar tasks based on Ingello's experience:
> https://business.ingello.com/prime-eva - e-commerce and systematic work with product data
> https://business.ingello.com/eva - retail, process automation, and scaling catalog logic
> https://business.ingello.com/forma-crm - an example of an approach to accounting systems, roles, and data

The main page for system development - https://systems-fl.ingello.com Expand

Budget: 1000 UAH Deadline: 4 days

Duplicates in your filters are almost certainly not due to settings, but because SimpleParse writes attribute values to the database as they are, without normalization. The supplier in the feed gives "черный," "Чёрный," and "black" - for OpenCart, these are three different filter values, and each run of the parser generates new ones. The same goes for categories: the feed changes structure, the mapping in sub-parsers remains old, and extra branches grow in the menu. Your programmer is right in the main point - auto-replacements at the parsing stage won't resolve this; it needs to be processed after import, not during.

What I will do as part of the audit. First, I will take a real picture of the database: using SQL queries, I will find all duplicated filter values, orphaned categories, and broken bindings, and quantify the scale of the junk in numbers. Next, I will analyze the settings of the parsers and sub-parsers - where exactly the mapping diverged from the supplier's feed. In the end, you will receive an analysis with specific reasons and examples from your database, plus the architecture of a fundamental solution: a post-processing module on a cron job that normalizes values through a correspondence table after each run (all variations of "чёрный" collapse into one canonical with the transfer of product bindings), removes empty filters, and cleans up junk categories. This is a standard, solvable task on OpenCart, not an eternal struggle.

I have been programming since 2013, and for several years I have run my own store on OpenCart with Journal3, so I know the ins and outs of categories, filters, and imports - including how parsers break the catalog structure.

One question to assess the volume: how many filter and category values are there currently in the system? This will determine whether a one-time cleanup is sufficient or if we should immediately plan for incremental processing after each parsing.

Write to me - we will discuss the details. For the audit, minimal access is sufficient: database read and admin panel.

Budget: 20000 UAH Deadline: 21 days

I can conduct an audit of the OpenCart + SimplePars integration: check sub-parsers, product distribution rules, category creation, filters and attributes, auto-replacements, cron tasks, and database work to identify the specific source of duplicates and structure resets.

Do I understand correctly that you need not just a one-time cleanup of current duplicates, but a system that maintains the approved structure of categories and attributes after each parsing and does not create duplicate or unnecessary values?

The budget, timelines, and fundamental solution options will be discussed in private correspondence after reviewing the OpenCart admin panel, SimplePars settings and logs, the list of sub-parsers, database structure, examples of problematic products, current cron tasks, and the availability of a backup or test environment.

Budget: 1000 UAH Deadline: 2 days

I have been working with the SimplePars module since its development and continue to do so... I have implemented many different tasks, feel free to reach out.

Budget: 2000 UAH Deadline: 1 day

Hello. I wrote a special script that removes duplicates, junk, etc., in an already filled database. Feel free to reach out, we will run it and see what gets fixed. Regarding the simple cases, if there are many parsers, this is a natural outcome. Either rewrite everything with separate parsers or fix what exists.

Budget: 3500 UAH Deadline: 3 days

Hello.

I am interested in the task. I will conduct an audit of OpenCart and SimplePars settings: I will check the logic of product distribution by categories, creation of filters and attributes, sub-parsers, auto-replacements, and reasons for duplicates.

As a result, I will provide:

— the exact cause of the problem;
— a safe plan for cleaning duplicates and unnecessary categories;
— a fundamental solution to prevent data from being recreated;
— recommendations for the cron module, if it is indeed necessary;
— a separate assessment of the implementation. Expand

Budget: 6000 UAH Deadline: 3 days

We already have an almost ready scheme for a similar solution with import auditing, catalog normalization, and duplicate checking; it can be quickly adapted for your OpenCart and SimplePars.

In terms of timing, the audit will take 3 days, and the budget for this stage is 6000 UAH.

From the description, it seems that the bottleneck is likely not only in the parser but also in the rules for matching categories, filters, and attributes before or after recording in the catalog via cron.

We shouldn't complicate things - first, we need to find out where exactly the extra entities are being generated, and only then decide if a separate module, normalization reference, or adjustment of the import scheme is needed.

I will also check the SimplePars settings, category structure, filters, attributes, and the current logic of auto-replacements, and provide a plan on how to eliminate the recurrence of the problem, rather than just cleaning up the consequences.

We need to clarify whether duplicates appear after each run of the parser or have accumulated from old rules.

It's also important to understand if there is access to the admin panel, SimplePars settings, and 2-3 examples of products where the category, filter, or attribute were incorrectly assigned.

https://business.ingello.com/prime-eva - is close in e-commerce logic, product data, and systematic work with the catalog.

https://business.ingello.com/eva - is an example of working with retail and complex processes around product data.

Our profile for such tasks on Freelancehunt is https://systems-fl.ingello.com.

I am available here on the marketplace; we can discuss the details and choose the shortest path to a proper solution. Expand

Budget: 1000 UAH Deadline: 1 day

Good day. I am ready to set it up. I am an official module developer on the forum and I configure Simple Parser.

Budget: 1000 UAH Deadline: 1 day

Hello, Yaroslav! I am interested in your project and ready to help solve the issues with duplicate subcategories, filters, and attributes in OpenCart. First, I will analyze the current structure, utilize the SimpleParser files, and wait to identify the configuration file with unnecessary entries. Then, I will create a module that will correct the names, categories, and attributes, and finally, I will set up a cron job to make the process autonomous.

My experience working with OpenCart and SimpleParser shows that this approach effectively resolves similar issues, so I am prepared to work this way. I propose to conduct an audit and adjustments for 1000 UAH, with a deadline of one working day, after which I will send the results and offer one more pleasant bonus – a short instruction on setting up the cron without unnecessary restarts.

Budget: 1000 UAH Deadline: 1 day

Good day, I am ready to complete your task quickly and efficiently. I have extensive experience in creating various parsers. Please write to me in private messages to discuss the details. I will be happy to help :)