Optimization of data structure, attributes, and filters based on OpenCart/ocStore

1. Purpose of Work

Bringing the database of products, attributes, and filters to a unified appearance to ensure the correct operation of user filtering and further integration with the automated content management system.

2. Stages and Scope of Work

2.1. Global Audit (Read-only)

• 
  

  Categories: Checking the availability of products in categories and subcategories. Identifying categories without configured filters or with incorrect display logic.

  
  

  
  

• 
  

  Attributes: Searching for duplicates and meaningful synonyms (for example, "Power" and "Rated Power").

  
  

  
  

• 
  

  Connections: Checking the integrity of chains: Category → Filter, Product → Filter, Product → Attribute.

  
  

  
  

2.2. Organizing Attributes and Filters

• 
  

  Deduplication: Removing duplicates of attributes and filters while preserving values in products.

  
  

  
  

• 
  

  Normalization of Values: Bringing units of measurement to a single canonical format (for example, converting "7000 W", "7000 watt" to "7 kW").

  
  

  
  

• 
  

  Mandatory Minimum: Checking the presence of 3 basic attributes for each product: Type, Brand, Key Feature.

  
  

  
  

• 
  

  Sorting Logic: Arranging filters in order of priority for the user (most important characteristics at the top).

  
  

  
  

2.3. Correction of Commercial Logic

• 
  

  Processing Technical Prices: For products with prices in the range of 0.01 to 10 UAH (which are often technical placeholders), set the status to "Out of stock" or "Unavailable" to hide from display.

  
  

  
  

3. Technological Constraints (Strict Constraints)

The performer is strictly prohibited from:

• Changing system identifiers: product_id, category_id, attribute_id, filter_id.

  
  

  
  

• Interfering with the operation of the SimplePars module and its tables (oc_pars_* ), changing import rules or the logic of SKU/Model.

  
  

  
  

• Creating new subcategories or deleting current ones without written approval from the Customer.

  
  

  
  

• Running Cron or performing mass data cleaning without creating a current backup.

  
  

  
  

4. Security Regulations

Before starting the active phase of work, the Performer must:

1. Before starting any work, the Performer must create a complete backup of the database.

2. Provide a list of tables subject to modification.

3. After completing the audit, provide a "Change Plan" for the Customer's approval.

4. Any changes are made only after conducting a read-only audit and agreeing on the "Change Plan" with the Customer.
   
   
   

4.1 Responsibility for Recovery:

In case of malfunction of the SimplePars parser, product import, or disruption of system identifiers (product_id), the Performer is obliged to independently and at their own expense restore the full functionality of the system to its original state as a priority (immediately).

The Performer is responsible for the accuracy of the data. If the structure of the URL (SEO) is disrupted as a result of the work, the Performer is obliged to correct this within 48 hours.

5. Criteria for Successful Completion of Work (KPI)

• 
  

  Correctness of Filtering: When selecting a value in the filter, all relevant products are displayed in the catalog without loss.

  
  

  
  

• 
  

  Cleanliness of the Database: Absence of duplicate attributes with the same content.

  
  

  
  

• 
  

  Integrity: Maintaining the functionality of the SimplePars parser and all current import settings.

  
  

  
  

• 
  

  Reporting: Providing a brief report listing merged attributes and changed connections.