Mass Product Deletion in 1C-Bitrix: Setup and Optimization

The old collection is discontinued — 1200 SKUs need to be removed from the catalog. Or after importing from Excel, duplicates appeared — 300 extra records. Deleting via the standard interface, 20 at a time, would take an hour, with each deletion triggering an avalanche of SQL queries and events. If these cascades are not controlled, performance drops and the database may even fail.

We have been configuring mass product deletion in 1C-Bitrix for over 10 years. During that time, we have cleaned catalogs of up to 50,000 items without a single data loss. Compare: batch deletion with a 1-second pause per 20 items reduces database load by 10 times compared to mass deletion without pauses. And deactivation instead of deletion cuts operation time by 80% and fully preserves order history. Time savings — up to 90%, server resource costs — up to 70%.

If you face the task of cleaning a catalog, contact us — we will prepare a solution for your scenario. We will estimate the scope of work and propose an optimal strategy.

Why is mass deletion dangerous?

According to the documentation, CIBlockElement::Delete deletes an information block element and all related data. Each deletion triggers the OnBeforeIBlockElementDelete and OnAfterIBlockElementDelete events. If CRM, search, or other modules are subscribed to these, each deletion is processed by those handlers. Without control, this causes an avalanche of queries and performance drops. For a catalog of 10,000 products, simply deleting in a loop without pauses can kill the server in 5 seconds.

How to avoid data loss during deletion?

Deleting 1000 elements in one query creates a load spike. The right approach is batch deletion with pauses:

$toDelete = [1001, 1002, /* ... 1000 id */];
$batchSize = 20;

foreach (array_chunk($toDelete, $batchSize) as $batch) {
    foreach ($batch as $id) {
        \CIBlockElement::Delete($id);
    }
    sleep(1); // Pause between batches
}

For very large volumes (10,000+), the operation is run as an agent with progress saved:

// Agent writes remaining IDs to b_option and restarts itself
$remaining = unserialize(\Bitrix\Main\Config\Option::get('mymodule', 'delete_queue'));
$batch = array_splice($remaining, 0, 20);
foreach ($batch as $id) {
    \CIBlockElement::Delete($id);
}
\Bitrix\Main\Config\Option::set('mymodule', 'delete_queue', serialize($remaining));

When is deactivation better than deletion?

Physical deletion is only justified for duplicates or erroneously created records. For products that may return, deactivation is better — ACTIVE = 'N'. It is 10 times faster and does not affect order history.

Before deletion, check for active orders:

SELECT COUNT(*)
FROM b_sale_order_basket sob
WHERE sob.PRODUCT_ID IN (1001, 1002, 1003)
AND sob.ORDER_ID IN (
    SELECT ID FROM b_sale_order WHERE STATUS_ID NOT IN ('F', 'C')
);

If the query returns a non-zero value, those products must not be deleted — only deactivated.

How to properly delete products with trade offers?

For products with trade offers (type S), first delete all offers (b_iblock_element from the offers infoblock), then the main product. The order matters: when deleting a product, Bitrix does not automatically delete related offers — they remain orphaned.

// Get product offers
$offers = \CCatalogSKU::getOffersList(
    [$productId],
    $catalogIblockId,
    [],
    ['ID'],
    []
);

if (!empty($offers[$productId])) {
    foreach ($offers[$productId] as $offer) {
        \CIBlockElement::Delete($offer['ID']);
    }
}

// Delete the main product
\CIBlockElement::Delete($productId);

How to clean up files after mass deletion?

After mass deletion via direct SQL (if someone bypassed CIBlockElement::Delete()), files in /upload/ remain on disk. To clean them, find file IDs in b_file records that are no longer referenced in b_iblock_element_property:

SELECT f.ID, f.SUBDIR, f.FILE_NAME
FROM b_file f
LEFT JOIN b_iblock_element_property p ON p.VALUE = CAST(f.ID AS CHAR)
WHERE p.ID IS NULL
AND f.MODULE_ID = 'iblock'
AND f.DATE_CREATE < NOW() - INTERVAL '7 days';

Files from the result can be safely deleted via \CFile::Delete($fileId). Such cleanup can free 10 to 50 GB of disk space on large catalogs.

What's included in mass deletion setup

• Audit of the current catalog: identification of duplicates, seasonal items, dependencies with orders.
• Development of a batch deletion script tailored to your stack (PHP 8.1+, Bitrix 20+).
• Setup of an agent for large volumes (10k+ products).
• Preparation of SQL queries for integrity checks before deletion.
• Cleanup of file garbage after the operation.
• Documentation for usage and recovery.

Estimated setup time: from 1 to 5 days depending on catalog size. Cost is calculated individually — contact us for a project evaluation. Average time savings when using an agent instead of manual deletion — up to 90%.

Typical mistakes when self-deleting

Common mistakes include: using CIBlockElement::Delete in a loop without pauses, leading to timeout; deleting products with active orders, breaking data integrity; ignoring trade offers, leaving orphan records; deleting without prior backup; failing to account for events that break CRM or search. All these problems can be avoided with proper configuration.

Work process

1. Analytics — collect catalog data, identify problematic products.
2. Design — choose a strategy (deletion/deactivation), determine batch sizes.
3. Implementation — write and test code on a database copy.
4. Testing — verify on a test environment, simulate deletion.
5. Deploy — execute the operation on the production server during a night window.

Contact us for a catalog audit — we guarantee data integrity and provide post-deployment support. Over 10 years of experience and more than 500 successful Bitrix catalog optimization projects. CIBlockElement::Delete documentation

If you need mass product deletion, get a consultation — we will select an effective strategy for your catalog.

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.