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).