Automated bulk price update for 1C-Bitrix catalogs

A supplier sends a price list with 3000 new purchase prices. Your retail markup is fixed at 40%. You need to update retail prices by morning. Manual update is unrealistic: 8–10 hours of tedious work with rounding errors. Import via 1C is not always available. Bulk price update via Bitrix API is the solution we set up in hours. A PHP script using D7 ORM processes 3000 records in 2–3 minutes. Price types, infoblock bindings, quantity dependencies, tagged cache clearing—all require precise code. Our team has 10+ years of experience with such tasks and delivers stable results. Certified 1C-Bitrix developers offer a turnkey solution. Contact us to discuss your catalog.

Problems mass price update solves

Manual editing of thousands of products takes days; a script handles it in minutes. Rounding errors when calculating markup manually—automation eliminates typos. Dependency on 1C—when CommerceML exchange is not configured or temporarily unavailable, the API saves the day. Catalogs up to 100,000 products are processed without downtime.

How mass update works via D7 ORM

Prices are stored in b_catalog_price. Key fields: PRODUCT_ID, CATALOG_GROUP_ID (price type), PRICE, CURRENCY, QUANTITY_FROM, QUANTITY_TO (for price ranges). Price types are in b_catalog_group: BASE is the base, others are additional (retail, wholesale, purchase). CATALOG_GROUP_ID = 1 usually means base price, but it depends on the specific setup.

Comparison of update methods

Direct API update is 50 times faster than CommerceML for one-off updates—key advantage for urgent tasks.

Working with PriceTable API

Get price type ID by name:

$priceType = \Bitrix\Catalog\GroupTable::getList([
    'filter' => ['NAME' => 'Retail'],
    'select' => ['ID'],
])->fetch();
$priceTypeId = $priceType['ID'];

For more details, see the official documentation.

Implementation: from loading price list to cache clearing

Loading from Excel/CSV and markup calculation

Supplier price lists usually come in Excel or CSV. For parsing Excel, we use PhpSpreadsheet:

$spreadsheet = \PhpOffice\PhpSpreadsheet\IOFactory::load('/path/to/price.xlsx');
$sheet = $spreadsheet->getActiveSheet();

foreach ($sheet->getRowIterator(2) as $row) { // from second row (skip header)
    $cells = $row->getCellIterator();
    $cells->setIterateOnlyExistingCells(false);

    $rowData = [];
    foreach ($cells as $cell) {
        $rowData[] = $cell->getValue();
    }

    $articul     = $rowData[0]; // A: SKU
    $newPurchase = (float)$rowData[3]; // D: purchase price

    // Find product by SKU
    $productId = findProductByArticul($articul);
    if ($productId) {
        updatePrice($productId, PURCHASE_PRICE_TYPE_ID, $newPurchase);
        updatePrice($productId, RETAIL_PRICE_TYPE_ID, calcRetailPrice($newPurchase, 40.0));
    }
}

Retail price calculation based on markup:

function calcRetailPrice(float $purchasePrice, float $markup): float {
    return round($purchasePrice * (1 + $markup / 100), 2);
}

Cache clearing and change log

After a mass price update, catalog pages show old cached prices. Clear cache for the entire catalog:

\Bitrix\Main\Application::getInstance()->getTaggedCache()->clearByTag('catalog');
// or clear by infoblock
\Bitrix\Main\Application::getInstance()->getTaggedCache()->clearByTag('iblock_id_' . $iblockId);

Alternatively, don't clear cache globally and wait for natural TTL expiry. But if prices changed for a time-limited promotion, clearing is mandatory.

For audit purposes, we recommend saving old prices before the update in a custom table catalog_price_history with fields (product_id, price_type_id, old_price, new_price, changed_by, changed_at). This allows rolling back erroneous updates and analyzing price dynamics.

Step-by-step update process

1. Prepare the price list in Excel or CSV format.
2. Parse the file with PhpSpreadsheet, extract SKUs and prices.
3. Validate and map SKUs to product IDs in the infoblock.
4. Run a batch loop of 100 records with a 50ms pause to update prices via PriceTable API.
5. Calculate retail price based on markup and write both price types.
6. Clear the tagged cache of the catalog.
7. Write change log to the catalog_price_history table.

How to avoid errors during mass update

Test the script on a copy of the catalog before production. Enable error logging in PHP and use MySQL transactions for atomicity. We include all these elements in the standard scope of work.

Typical errors

• Wrong price type identifier—prices go to the wrong place.
• No batching—MySQL crashes on 10,000 products.
• Missing cache clearing—old prices remain on the storefront.
• No transaction—partial update on failure.

If the update fails, restart the script—it skips already updated records if there is an updated flag. Or roll back using the catalog_price_history table if created.

What's included in mass update setup and what guarantees we provide

• Analysis of the current catalog structure and price types.
• Development of an import script from Excel/CSV with automatic markup calculation.
• Implementation of batching for large volumes (up to 100,000 products).
• Configuration of tagged cache clearing.
• Creation of a change log table.
• Testing on a copy of the catalog.
• Script documentation and run instructions.
• 30-day stable operation guarantee.

Contact us for a project assessment. On average, we reduce update time from hours to minutes for catalogs of 10,000+ items.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.