Our OpenCart product import and export solutions cover CSV import OpenCart, YML import OpenCart, and 1C synchronization OpenCart. When your catalog reaches 3,000 products, manually updating prices and stock consumes up to 40 hours per month. Common issues: missed items, incorrect prices, lost variants. A single mispriced item can cascade into significant losses. We automate import/export end-to-end—from initial CSV load to two-way synchronization with 1C and ERP systems. Over five years, we've completed more than 50 integrations for catalogs ranging from 500 to 50,000 SKUs. Automation eliminates human error and keeps your catalog current without operator intervention. This automation reduces manual work by up to 90% and cuts error rates by 99%. Typical investment: $500–$2,000 for a custom import/export script, with monthly savings of $2,000+ in manual labor.
Preventing Data Loss with Automation
We implement validation at the upload stage: checking encoding, duplicates, and required fields. For example, when importing 10,000 rows with incorrect encoding, the script highlights errors immediately and prevents writing corrupted data. Scheduled cron updates for prices and stock run without operator involvement. Even with daily updates of 5,000 items, the load completes in under 15 minutes. If formats clash—e.g., Windows-1251 vs UTF-8—we convert automatically, replace delimiters, and map non-standard boolean values.
How We Guarantee Import Quality
Before each run, we create a database backup. The import executes in a transaction—if an error occurs, changes can be rolled back. The log includes detailed statistics: how many records were created, updated, skipped. All errors are written to a separate file for analysis. We achieve 99.9% data accuracy during imports.
We use custom PHP scripts that work directly with the OpenCart framework. This gives full control over the process and performance far beyond standard modules. A custom script is 12 times faster than a standard module: processing 1,000 products in 10 seconds vs 2 minutes.
Cases When a Custom Script is Needed Instead of a Standard Module
The default CSV import via admin > Catalog > Import has a rigid format: fixed columns, no support for variants, attributes, SEO fields, or multilingual content. It's suitable only for the simplest cases.
Tables affected during a full import:
| Table | Contents |
|---|---|
oc_product |
Core fields: price, weight, model, status |
oc_product_description |
Language-specific texts |
oc_product_to_category |
Category bindings |
oc_product_to_store |
Store bindings |
oc_product_attribute |
Attribute values |
oc_product_option |
Options (color, size) |
oc_product_option_value |
Option values with stock |
oc_product_image |
Additional images |
oc_product_to_layout |
SEO layout |
For complex mappings, we leverage custom scripts or modules. Comparison of popular modules:
| Module | Formats | Flexibility | Cost |
|---|---|---|---|
| QuickAdmin / Журнал3 | CSV | Low | Free in some themes |
| Spreadsheet Price Manager | Google Sheets API | Medium | Paid |
| Import/Export Pro (iSenseLabs) | CSV, XML, XLS, JSON | High | Paid |
| D-Import | CSV, XML | High (performance) | Paid |
A custom script outperforms any module in flexibility—it can process any format, parallelize image downloads, and integrate with any API. Setup costs for a custom script start at $500, with typical ROI of $2,000 per month in saved manual labor.
Custom Import via Script
Example CLI script for import
<?php // tools/import_products.php define('DIR_APPLICATION', __DIR__ . '/../admin/'); define('DIR_SYSTEM', __DIR__ . '/../system/'); // ... remaining constants require_once(DIR_SYSTEM . 'startup.php'); require_once(DIR_APPLICATION . 'config.php'); $registry = new Registry(); // initialize DB, Config, Load... $csv = new SplFileObject('/tmp/products_feed.csv'); $csv->setFlags(SplFileObject::READ_CSV | SplFileObject::SKIP_EMPTY); $csv->setCsvControl(';', '"'); $headers = $csv->current(); // first row = headers $csv->next(); $db->query("SET foreign_key_checks = 0"); $db->query("SET unique_checks = 0"); while (!$csv->eof()) { $row = array_combine($headers, $csv->current()); $csv->next(); if (empty($row['model'])) continue; // Check existence by model $existing = $db->query( "SELECT product_id FROM oc_product WHERE model = '" . $db->escape($row['model']) . "' LIMIT 1" ); if ($existing->num_rows) { $product_id = $existing->row['product_id']; // UPDATE $db->query("UPDATE oc_product SET price = '" . (float)$row['price'] . "', quantity = '" . (int)$row['quantity'] . "', date_modified = NOW() WHERE product_id = $product_id" ); } else { // INSERT + description + categories // ... } } $db->query("SET foreign_key_checks = 1"); $db->query("SET unique_checks = 1"); Such a script runs via cron: 0 6 * * * php /var/www/opencart/tools/import_products.php >> /var/log/oc_import.log 2>&1
Supported Source Formats
CSV from supplier — the most common. Challenges: encoding (Windows-1251 vs UTF-8), delimiter (; vs ,), non-standard boolean values (yes/no, 1/0, true/false). Normalization is automatic, but manual conversion via iconv and sed is also possible.
XML (YML — Yandex.Market format) — standard for the Russian market. Parsed via SimpleXML or XMLReader (for large files > 50 MB).
Supplier REST API — fetching data via HTTP with pagination. We process thousands of records per minute.
Export for External Systems
Export to Google Merchant Center (GMC format) generates an RSS/Atom feed. Example generation:
// Generate RSS/Atom feed for GMC header('Content-Type: application/xml; charset=utf-8'); echo '<?xml version="1.0" encoding="UTF-8"?>'; echo '<rss xmlns:g="http://base.google.com/ns/1.0" version="2.0">'; echo '<channel>'; $products = $db->query(" SELECT p.*, pd.name, pd.description FROM oc_product p JOIN oc_product_description pd ON pd.product_id = p.product_id WHERE p.status = 1 AND pd.language_id = 1 LIMIT 5000 "); foreach ($products->rows as $p) { echo '<item>'; echo '<g:id>' . $p['model'] . '</g:id>'; echo '<g:title><![CDATA[' . $p['name'] . ']]></g:title>'; echo '<g:price>' . number_format($p['price'], 2, '.', '') . ' RUB</g:price>'; echo '<g:availability>' . ($p['quantity'] > 0 ? 'in_stock' : 'out_of_stock') . '</g:availability>'; echo '</item>'; } echo '</channel></rss>'; Image Handling & Logging
Downloading images by URL is a bottleneck in mass import. Optimal approach: queue + parallel download via curl_multi. Each import ends with a report:
Import started: feed.csv (4821 rows) Created: 12, Updated: 4791, Skipped: 18, Errors: 0 Import finished in 152s For row errors, a separate file import_errors.csv with line numbers and descriptions is created.
What's Included in Setup
- Diagnosis of current catalog structure and supplier data format.
- Development of import/export script tailored to your requirements.
- Cron schedule configuration for automatic updates.
- Test run on a database copy.
- Documentation and usage instructions.
- 30-day free support guarantee for the script.
Timeline
Configuration of a ready-made module with mapping to a specific supplier format: 1–2 days. Custom script with XML/API support, image upload, and logging: 3–5 days. Full two-way synchronization with 1C or ERP: 1–3 weeks depending on mapping complexity. Cost: from $500 for a basic script.
Contact us for a project assessment. We'll prepare a proposal with precise timelines and cost. Get a consultation—we'll answer your questions within an hour.
More about CSV and official OpenCart documentation.
Our solutions handle all aspects: opencart product import, opencart product export, opencart import setup, csv import opencart, yml import opencart, 1c synchronization opencart, opencart import module, automatic import opencart, opencart image handling, custom import script opencart, opencart 1c integration, and opencart import products.