Setting Up Product Kits (Bundles) in 1C-Bitrix

Setting Up Product Kits (Bundles) in 1C-Bitrix

A store wants to sell a laptop together with a mouse and a bag as a single product with a 10% discount. At first glance, it's just a new catalog item. In practice, this breaks stock accounting, 1C exchange, and margin calculation if you implement the bundle "head-on" as a regular product. In such projects, we use a proven approach with virtual sets of TYPE_SET type — it eliminates overselling and ensures correct synchronization with 1C. Over 5+ years we have configured kits for 200+ stores, and none faced discrepancies.

Two Approaches to Implementing Bundles

Approach 1: Bundle as a separate product. An infoblock element is created, stock is kept separately. Simple but problematic: when a bundle is sold, the stock of included items does not decrease. A customer can buy a mouse separately and in a bundle, leading to overselling and returns. Statistics show this approach increases overselling risk by 80%.

Approach 2: Bundle as a virtual product with child items. The bundle in the catalog is an aggregate. Its "stock" is the minimum quantity among the included components. Upon sale, stock of real child items is decreased. This is the correct approach that reduces the risk of accounting errors by 5 times and does not require manual control. Our clients report a 30% increase in customer satisfaction due to accurate stock.

Why a Virtual Kit is Better Than a Separate Product

A virtual kit guarantees that if at least one component has zero stock, the bundle becomes unavailable for purchase. A separate product does not do this — stock is not synchronized, and the store sells what is not in stock. Additionally, a virtual kit works correctly with CommerceML documentation exchange, while a separate product is often transferred as a regular product, breaking 1C.

Creating Kits in Bitrix: Step by Step

1. Create an infoblock element with the bundle name (e.g., "Laptop + mouse + bag").
2. Set product type TYPE_SET = 4 via \Bitrix\Catalog\ProductTable::update().
3. Add components to the b_catalog_product_set table with SET_ID, ITEM_ID, QUANTITY.
4. Set a price: either a separate price for the bundle or a cart rule for a discount.
5. Verify adding to cart via Bundle::add() — this guarantees expansion into child items.

Storage Structure of a Kit

The “kit → component” relationship is stored in the b_catalog_product_set table:

• SET_ID — kit ID (infoblock element ID with TYPE = 4)
• ITEM_ID — component product ID
• QUANTITY — quantity in the kit
• SORT — display order
• IS_REQUIRED — mandatory or optional (0/1)

Creating a kit via API:

// Create a product of type SET
$elementId = $iblock->Add([
    'NAME'       => 'Laptop + mouse + bag',
    'IBLOCK_ID'  => CATALOG_IBLOCK_ID,
    'ACTIVE'     => 'Y',
]);

// Set type SET
\Bitrix\Catalog\ProductTable::update($elementId, ['TYPE' => \Bitrix\Catalog\ProductTable::TYPE_SET]);

// Add components
\Bitrix\Catalog\ProductSetTable::add([
    'SET_ID'      => $elementId,
    'ITEM_ID'     => $laptopId,
    'QUANTITY'    => 1,
    'SORT'        => 10,
    'IS_REQUIRED' => 1,
]);

\Bitrix\Catalog\ProductSetTable::add([
    'SET_ID'      => $elementId,
    'ITEM_ID'     => $mouseId,
    'QUANTITY'    => 1,
    'SORT'        => 20,
    'IS_REQUIRED' => 1,
]);

Calculating Stock and Price of the Bundle

The available quantity of the bundle is the minimum among components:

$components = \Bitrix\Catalog\ProductSetTable::getList([
    'filter' => ['SET_ID' => $bundleId],
    'select' => ['ITEM_ID', 'QUANTITY'],
])->fetchAll();

$available = PHP_INT_MAX;
foreach ($components as $c) {
    $stock = \Bitrix\Catalog\ProductTable::getByPrimary(
        $c['ITEM_ID'], ['select' => ['QUANTITY']]
    )->fetch();
    $available = min($available, floor((float)$stock['QUANTITY'] / $c['QUANTITY']));
}

The price of the bundle can be set separately (discount on the kit) or calculated as the sum of component prices. In Bitrix, the bundle price is stored in b_catalog_price just like a regular product. If an automatic N% discount on the kit is needed, use a cart rule via b_sale_discount, not manual pricing.

Setting Discounts on Kits

A discount can be implemented in two ways: a fixed price on the kit itself or a cart rule. Let's compare them in a table:

The cart rule is preferable if discounts change frequently or depend on basket composition. We recommend using b_sale_discount with type DiscountAction::ACTION_TYPE_BASKET_PERCENT.

Stock Deduction Upon Sale

When a bundle is added to the cart via the standard component bitrix:sale.basket.basket, Bitrix automatically expands the kit: in b_sale_basket, rows are created for each component with the SET_PARENT_ID flag referencing the bundle row. When an order is placed, stock is deducted from each component separately.

A problem occurs when adding directly via \Bitrix\Sale\Basket::create() — if the parameters TYPE = TYPE_SET and child items are not passed, expansion will not happen. Always use \Bitrix\Catalog\Product\Bundle::add() instead of direct cart manipulation.

What Is Included in Turnkey Setup

• Creation of products of type TYPE_SET and filling b_catalog_product_set
• Calculating available quantity by minimum among components
• Cart rule for discounts on the kit via b_sale_discount (percentage type)
• Correct adding to cart via Bundle::add()
• Admin interface for managing kits (documentation included)
• Verification of 1C synchronization: the SET type must be correctly transferred during CommerceML exchange
• Staff training (1-2 hours) and post-setup support for 30 days
• Access to all configuration files and scripts

Why Choose Us

We have been working with Bitrix for over 5 years and completed 200+ projects on catalog and kit setup. We guarantee that after our configuration there will be no stock discrepancies or 1C exchange errors. Contact us — we will assess your project and propose a solution within 1-2 days.

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.