Custom Product Configurator on 1C-Bitrix – Turnkey Development

With a catalog of over 10,000 option combinations, standard trade offers SKU no longer suffice. The site slows down, adding a new option becomes problematic, and prices are calculated with errors. A typical case is a PC builder or kitchen configurator where parameters intersect with compatibility constraints. In such situations, a custom configurator on 1C-Bitrix is the only adequate solution. We have implemented over 30 such projects and know all the pitfalls. 1C-Bitrix official documentation recommends using trade offers only for simple combinations. The development cost is determined after analyzing your project complexity; contact us for a preliminary consultation.

When Standard Trade Offers Are Not Enough

Standard trade offers work for up to 4–5 parameters. With 6+ interdependent options or complex compatibility rules, the b_catalog_product_offer table becomes inefficient. A configurator with its own rule matrix solves this. In our projects, matrices reach 500,000 combinations — we know how to maintain this. Operational savings from caching optimization amount to up to 30%, which at an average turnover of 5 million rubles gives savings of up to 1.5 million rubles per year.

Data Storage: Infoblock or Custom Table?

The choice of storage method is critical for performance. Compare both options:

In practice, we combine: main data in the infoblock, compatibility rules in a separate table. This provides both speed and manageability. On a matrix of 100,000 combinations, a custom table with indexes performs 10 times faster than nested infoblock properties. This can reduce server hardware costs by 200,000–400,000 rubles per year.

Technical Implementation

Compatibility Table in Action

Each step of the configurator is a set of options. Selection at step N dynamically limits options at step N+1. We use a simple SQL structure:

CREATE TABLE custom_configurator_rules (
    id          SERIAL PRIMARY KEY,
    product_id  INT NOT NULL,
    param_key   VARCHAR(100) NOT NULL,
    param_value VARCHAR(255) NOT NULL,
    depends_key VARCHAR(100) NOT NULL,
    depends_val VARCHAR(255) NOT NULL,
    available   TINYINT DEFAULT 1
);
CREATE INDEX idx_rules_product ON custom_configurator_rules (product_id, param_key, param_value);

When a user selects a parameter, an AJAX request is sent to /bitrix/services/main/ajax.php with action custom:configurator. The handler reads the rule table and returns available options for the next step and the current price.

Real-Time Price Calculation

Configuration price = base product price + markups for selected options. Markups are stored in a separate table:

CREATE TABLE custom_configurator_price_mod (
    id          SERIAL PRIMARY KEY,
    product_id  INT NOT NULL,
    param_key   VARCHAR(100) NOT NULL,
    param_value VARCHAR(255) NOT NULL,
    price_mod   DECIMAL(12,2) NOT NULL,
    price_pct   DECIMAL(5,2)  DEFAULT 0
);

The handler sums markups, applies discounts via \Bitrix\Catalog\Discount\DiscountManager, and returns the total. The client sees how the price changes with each selection.

Integration with Cart and Orders

After the user completes the configuration, the product is added to the cart, and the JSON configuration is attached as a custom basket property:

\Bitrix\Sale\Basket::create(SITE_ID);
$basketItem = $basket->createItem('catalog', $productId);
$basketItem->setFields([
    'QUANTITY' => 1,
    'PROPS'    => [
        ['NAME' => 'Configuration', 'CODE' => 'CONFIGURATION', 'VALUE' => json_encode($config)],
    ],
]);

The configuration is displayed in the admin order card and in the confirmation email via the order_new template. Integration with 1C via CommerceML for stock and price synchronization is available on request.

Rule Management via Admin Panel

For content managers, we develop an interface in /bitrix/admin/ using standard CAdminList and CAdminForm classes. This allows adding new options, compatibility rules, and price markups without writing code. All changes are logged and revertible.

Process for adding a new option:

1. In the admin panel, select the product and the "Configurator Parameters" section.
2. Click "Add Step" and specify the name (e.g., "Case Color").
3. List the option values and markups for each.
4. In the "Compatibility Rules" section, link the new option to existing steps.
5. Save — changes take effect immediately without cache reload thanks to agents.

Process and Timeline

Stages and Timelines

Total: from 2.5 to 4 weeks depending on the number of parameters and matrix complexity. We provide an accurate estimate after analyzing your catalog. The multi-step configuration process with compatibility checks is implemented at each stage.

What's Included in Deliverables

• Project documentation: DB schema, API description, use cases.
• Configured access for content managers (roles in Bitrix).
• Manual for managing rules and price modifiers.
• Post-release support: 2 weeks of free consultations.
• Code warranty: 6 months from the date of signing the acceptance certificate.

Common Mistakes and How to Avoid Them

• Lack of caching. Without cache, AJAX requests for each step load the database — the site slows down even with 50 concurrent users.
• Storing rules in infoblock properties. With 50,000 combinations, queries to b_iblock_element_property become unbearably slow.
• Ignoring stock. If you don't check availability of each component, the configurator will sell a configuration that cannot be assembled.
• Flat JSON in cart without verification. If the price changes, an attacker could tamper with parameters, so we recalculate the cost server-side.

A configurator is ideal for e-commerce stores with customizable products. Get a preliminary assessment of your project — contact us. Request a consultation — we will evaluate your project and propose an optimal plan.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.