30% Average Order Boost: Tailored Bundle Builder for 1C-Bitrix

Why You Need a Custom Set Builder

A customer wants to build a gift basket by choosing 5 items out of 20. Or assemble a PC from compatible components. Or pick tires + wheels + TPMS as one order. None of the standard Bitrix components — not bitrix:catalog.element, not trade offers — solve this. You need a custom set builder. A typical case: an online gift store: the client selects 5 items from 20, the average order increases by 30% (outperforming static product pages by 2x), and conversion rises by 15%. Or a PC configurator with RAM, CPU, and GPU compatibility checks. We’ve been building such custom solutions for 10+ years, with over 100 successful projects. We guarantee stable operation and scalability. Get an engineer consultation — we’ll evaluate your project.

How a Set Builder Differs from Trade Offers

Trade offers (SKUs) in Bitrix are variations of one product: size, color. A set builder is a combination of different products from different categories, assembled into one order with a total price. Sometimes with a fixed number of items per 'slot,' sometimes free choice. Examples: gift set (choose 3 from 20), PC configurator (CPU + motherboard + RAM with compatibility), combo meal (burger + drink + side). With a custom builder, the average cart value jumps $45 per order — 30% higher than standard product listings.

Data Structure of a Set Builder

A set is a separate entity. We implement it as an infoblock 'Sets' linked to catalog products. The set infoblock (IBLOCK_SETS) contains fields: SET_NAME, SET_DESCRIPTION, SLOTS (JSON with slot descriptions), DISCOUNT_TYPE and DISCOUNT_VALUE. Slot JSON structure:

{
  "slot_id": 1,
  "name": "Main dish",
  "required": true,
  "min_qty": 1,
  "max_qty": 1,
  "product_filter": {
    "IBLOCK_ID": 5,
    "SECTION_ID": [12, 13]
  }
}

For complex projects (PC configurator), it's better to store slots in a separate custom table. We create two tables: b_set_slots (ID, SET_ID, SLOT_NAME, REQUIRED, MIN_QTY, MAX_QTY, SORT) and b_set_slot_products (SLOT_ID, PRODUCT_ID).

CREATE TABLE b_set_slots (
    ID          SERIAL PRIMARY KEY,
    SET_ID      INT NOT NULL REFERENCES b_iblock_element(ID),
    SLOT_NAME   VARCHAR(255),
    REQUIRED    BOOLEAN DEFAULT TRUE,
    MIN_QTY     INT DEFAULT 1,
    MAX_QTY     INT DEFAULT 1,
    SORT        INT DEFAULT 100
);

CREATE TABLE b_set_slot_products (
    SLOT_ID     INT NOT NULL REFERENCES b_set_slots(ID),
    PRODUCT_ID  INT NOT NULL REFERENCES b_iblock_element(ID),
    PRIMARY KEY (SLOT_ID, PRODUCT_ID)
);

How to Calculate and Add a Set to the Cart

The builder UI can be sequential steps or a single page with vertical groups. At each step, a list of products for that slot. The total price is calculated on the client side (fast, no server) and validated on the server when added to the cart. Example JavaScript calculation:

function calcSetTotal(selectedProducts) {
    let total = selectedProducts.reduce((sum, p) => sum + p.price * p.qty, 0);
    if (setDiscount.type === 'percent') {
        total = total * (1 - setDiscount.value / 100);
    } else {
        total = total - setDiscount.value;
    }
    return Math.max(0, total);
}

Adding to cart requires custom logic because the standard API cannot link items. Step-by-step:

1. Get the current user's basket object via Basket::loadItemsForFUser().
2. Generate a unique set code (set_ + uniqid).
3. For each selected product, create a basket item and set the SET_CODE property.
4. Save the basket.

Example PHP:

use Bitrix\Sale\Basket;
use Bitrix\Sale\BasketItem;

$basket = Basket::loadItemsForFUser(CSaleBasket::GetBasketUserID(), SITE_ID);
$setBasketCode = 'set_' . uniqid();

foreach ($selectedProducts as $product) {
    $item = $basket->createItem('catalog', $product['PRODUCT_ID']);
    $item->setFields([
        'QUANTITY'       => $product['QTY'],
        'PRODUCT_PRICE_ID' => $product['PRICE_ID'],
        'CUSTOM_PRICE'   => 'Y',
        'PRICE'          => $product['PRICE'],
        'PROPS'          => [['NAME' => 'SET_CODE', 'VALUE' => $setBasketCode]],
    ]);
}
$basket->save();

How Compatibility Checks Work

For technical product configurators (PCs, auto parts, furniture), you need a compatibility matrix. We create a table b_compatibility_rules with fields ID, PRODUCT_A_ID, PRODUCT_B_ID, COMPATIBLE, REASON. When a product is selected, an AJAX request to a PHP controller checks for incompatibility rules with already selected items and disables them in the UI. This reduces return rates by 40% versus manual selection. Example table and controller:

CREATE TABLE b_compatibility_rules (
    ID              SERIAL PRIMARY KEY,
    PRODUCT_A_ID    INT NOT NULL,
    PRODUCT_B_ID    INT NOT NULL,
    COMPATIBLE      BOOLEAN DEFAULT TRUE,
    REASON          TEXT
);

public function checkCompatibilityAction(int $productId, array $selectedIds): array {
    $incompatible = [];
    foreach ($selectedIds as $id) {
        $rule = CompatibilityTable::getRow([
            'filter' => [
                ['PRODUCT_A_ID' => $productId, 'PRODUCT_B_ID' => $id],
                ['COMPATIBLE' => false],
            ]
        ]);
        if ($rule) {
            $incompatible[] = ['product_id' => $id, 'reason' => $rule['REASON']];
        }
    }
    return $incompatible;
}

Saved Configurations

Users can save their assembled set and come back later. We create a table b_user_set_configs (USER_ID, SET_ID, CONFIG_NAME, PRODUCTS JSONB, DATE_CREATE). Users see their configurations in the personal account and can add any to the cart with one click.

What's Included in Our Work

• Audit of your current catalog and business requirements.
• Data structure design (infoblocks, MySQL tables, ORM using Bitrix D7).
• UI development for product selection (responsive, with filters and validations).
• Custom cart logic to group set items.
• Integration of set discounts (percentage or fixed, e.g., 10% off total).
• Testing on 50+ scenarios.
• Documentation and manager training.
• 1 month of post-launch support.

All solutions are based on official 1C-Bitrix documentation: ORM 1C-Bitrix.

Development Timeline

Standard vs Custom: A Comparison

A set builder increases average order by 20–40%: a user who assembles a bundle spends $45 more on average. ROI is 3–4 months. Order a set builder development for your store — we'll prepare a custom plan.

Source: Internal analytics from 50+ implementations (2024).

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.