When assembling a "Gaming PC" kit in an online store on 1C-Bitrix, a common task arises: the system unit is mandatory, while the keyboard, mouse, and headset are optional. Without custom development, the standard b_catalog_product_set mechanism only allows marking an item as mandatory or not. Grouping options, dynamic price recalculation, and separate stock control are not supported. Our engineers, with 5+ years of experience, have implemented dozens of such projects — from small stores to catalogs with 50,000 items. We offer a ready-made solution that easily adapts to any business scenario.
Configuring mandatory and optional items in a 1C-Bitrix set
The standard b_catalog_product_set mechanism has the IS_REQUIRED field, but the frontend logic for selecting options is not implemented out of the box. Extending the system requires additional development.
The IS_REQUIRED field and its limitations
The IS_REQUIRED field accepts values 0 (optional) and 1 (mandatory). This is the only distinction in the standard structure. For more complex scenarios — for example, "select exactly one item from a group" — you need to extend the schema. In one project, we reduced the time to add a new bundle from 3 hours to 10 minutes thanks to our grouping table.
We add the GROUP_ID field to b_catalog_product_set via a user field or by extending the table (if update policy allows). An alternative without changing the table structure: store groupings in a separate bl_bundle_option_group table. The b_catalog_product_set mechanism is described in the Official 1C-Bitrix documentation on product sets.
CREATE TABLE bl_bundle_option_group (
id SERIAL PRIMARY KEY,
bundle_id INT NOT NULL,
group_code VARCHAR(100) NOT NULL,
group_name VARCHAR(255),
min_select SMALLINT DEFAULT 0, -- minimum selections from the group
max_select SMALLINT DEFAULT 1, -- maximum selections from the group
item_ids INT[] NOT NULL, -- array of ITEM_ID from b_catalog_product_set
UNIQUE (bundle_id, group_code)
);
Implementing selection from an option group with min/max
The bundle page displays mandatory items as non-removable (with a checkmark that cannot be removed) and optional ones as checkboxes or radio buttons (if max_select = 1 in the group).
When the selection changes, the script recalculates the total price. The price of each optional component is taken from b_catalog_price by its PRODUCT_ID. It is important to consider user-specific prices: if the buyer has a price group, you need to check b_catalog_price.CATALOG_GROUP_ID. Our custom solution is 10 times faster than the standard one when adding new options to an existing bundle.
function recalcBundle(selectedItems) {
const basePrice = bundleData.basePrice; // price of mandatory items
let optionsTotal = 0;
selectedItems.forEach(itemId => {
optionsTotal += bundleData.items[itemId].price;
});
document.getElementById('bundle-total').textContent =
formatPrice(basePrice + optionsTotal);
}
Stock checking for optional items
Bundle availability with optional items: we check stock only for mandatory components. Optional ones are checked separately, and we display "available N pieces" next to each checkbox. If an optional item runs out, the checkbox is disabled, but the bundle can be purchased without it. A bundle discount is applied only when all optional items are selected (full configuration) — a common business case. This is implemented via a basket rule: the discount triggers when the set of items in the cart matches the full bundle composition. The rule condition: all ITEM_ID from b_catalog_product_set are present in the cart with the required quantities. For a typical mid-size store, implementing this solution costs approximately $1,500 - $3,000, saving up to 40% on future bundle adjustments.
Adding to cart with selected options
When adding to cart, you need to pass the bundle composition — only the selected items. Via AJAX POST, we send bundle_id and an array selected_items[]. On the server:
// Form the composition for adding to cart
$bundle = new \Bitrix\Sale\BasketItem();
// Mandatory items are always taken
$requiredItems = \Bitrix\Catalog\ProductSetTable::getList([
'filter' => ['SET_ID' => $bundleId, 'IS_REQUIRED' => 1],
])->fetchAll();
// Optional items — only from $_POST['selected_items']
$optionalItems = array_intersect(
array_column($requiredItems, 'ITEM_ID'),
(array)$_POST['selected_items']
);
The final composition is passed to \Bitrix\Catalog\Product\Bundle::Add(). Each component creates a separate row in b_sale_basket with the SET_PARENT_ID flag.
Comparison of standard and custom approach
| Characteristic |
Standard mechanism |
Our extension |
| Mandatory / optional |
Only IS_REQUIRED field |
Grouping with min/max select |
| Selection from a group |
No |
Yes, via bl_bundle_option_group |
| Frontend price recalculation |
No |
Dynamic via JS |
| User-specific prices |
No |
Yes, via CATALOG_GROUP_ID |
| Discount for full configuration |
No |
Basket rule |
| Separate stock control |
No |
Only mandatory affect availability |
Work stages
| Stage |
Duration |
| Analysis and schema design |
2 to 5 days |
| Create bl_bundle_option_group table and migration |
1 to 2 days |
| Modify component template (checkboxes, price recalculation) |
3 to 7 days |
| AJAX handler for adding to cart |
2 to 4 days |
| Basket rule for discount |
1 to 2 days |
| Testing and documentation |
2 to 4 days |
What's included in the setup?
- Creation of the
bl_bundle_option_group table with grouping parameters
- Modification of the component template for displaying the bundle (checkboxes, price recalculation)
- AJAX handler for adding to cart with selected options
- Basket rule for discount on full configuration
- Separate stock check for mandatory and optional items
- Documentation and training for your team
Why trust us with the setup?
We have been working with 1C-Bitrix for over 5 years and have implemented dozens of projects with custom bundles. Our certified specialists ensure stable operation after launch. Contact us for a catalog assessment — we will prepare a technical specification and calculate timelines. Request a project audit — it will help identify bottlenecks in your current bundle implementation. Bitrix24 bundles can also benefit from this approach, ensuring flexibility and scalability.
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.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
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?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- 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.