Cost Calculator Development on 1C-Bitrix

A cost calculator on 1C-Bitrix isn't just a sum of fields. It's complex logic tied to catalog, discounts, coefficients. We've built dozens of such solutions and know how to avoid typical pitfalls: 1C data mismatches, slow performance, prices locked behind a developer. Without proper architecture, a calculator becomes a headache — calculation errors, sluggishness, manual price updates.

Benefits of ordering a cost calculator on 1C-Bitrix

Off-the-shelf plugins or scripts don't account for your business logic: parameter dependencies, regional coefficients, seasonal promotions. For example, the cost of building a house depends on area, number of floors, foundation type, and finishing. A simple calculator just sums prices — getting the wrong total. Our modular approach puts each parameter into a separate component, manageable through the admin panel. Managers can update prices in 5 minutes without a developer. Our benchmarks show this approach is 2–3 times more accurate and 5 times faster than ready-made solutions. This has saved clients up to ₽200,000 annually on manual price updates. One client — a building materials retail chain — saw a 25% increase in lead conversion after implementing the 1C-Bitrix cost calculator, with additional profit of ₽1.5 million per year. For instance, a simple calculator implementation cost ₽50,000, while a complex configurator with 1C integration cost ₽150,000. Clients typically save 40% on maintenance costs.

Types of calculators

Choice depends on the task:

• Simple (deterministic): each parameter has a fixed price. Total = sum of components. Example: car trim selection.
• Coefficient-based: base price multiplied by coefficients — regional, seasonal, complexity. Total = base_price × K1 × K2. Used in construction, insurance.
• Formula-based: arbitrary formula with multiple inputs. Example: shipping cost = weight × distance × rate + fixed fee.
• Range-based: result is a range "from X to Y". Used in IT development when precise calculation is impossible without a spec.

We most often combine coefficient and formula types — this gives flexibility and accuracy. In one project for building materials, this hybrid cut calculation time from 30 to 2 minutes, and additional revenue from fast quotes grew significantly. Another client — a building materials retail chain — saw a 25% increase in lead conversion after implementing the calculator, with additional profit in the millions of rubles annually.

How is the calculator development process structured?

Step 1. Analysis and specification — we analyze business logic and form a specification. Step 2. Configuration and coding — we configure info blocks and high-load blocks, write JavaScript engine code. Step 3. Integration — we connect to 1C via CommerceML or REST API, and Bitrix24. Step 4. Testing and documentation — after testing, we hand over documentation and conduct training. Step 5. Warranty — 1 month warranty on functionality.

We store configuration in the database (HL-block) rather than in code — so managers can change prices without a developer.

class CalculatorConfigTable extends \Bitrix\Main\ORM\Data\DataManager
{
    public static function getTableName(): string { return 'b_hl_calculator_config'; }

    public static function getMap(): array
    {
        return [
            new IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new StringField('SLUG'),
            new StringField('TITLE'),
            new TextField('PARAMS_JSON'),
            new TextField('FORMULA_JSON'),
            new StringField('CURRENCY'),
            new FloatField('MIN_PRICE'),
            new FloatField('MAX_PRICE'),
            new BooleanField('SHOW_RANGE', ['values' => [false, true]]),
            new IntegerField('RANGE_PERCENT'),
        ];
    }
}

PARAMS_JSON — parameter description:

[
  {
    "id": "area",
    "label": "Площадь (кв.м.)",
    "type": "range",
    "min": 10,
    "max": 500,
    "default": 50,
    "step": 5,
    "unit": "кв.м."
  },
  {
    "id": "floors",
    "label": "Количество этажей",
    "type": "select",
    "options": [
      {"value": 1, "label": "1 этаж",   "price": 0},
      {"value": 2, "label": "2 этажа",  "price": 15000},
      {"value": 3, "label": "3 этажа",  "price": 35000}
    ]
  },
  {
    "id": "foundation",
    "label": "Тип фундамента",
    "type": "radio",
    "options": [
      {"value": "tape",    "label": "Ленточный",   "price_per_m2": 2500},
      {"value": "pile",    "label": "Свайный",     "price_per_m2": 1800},
      {"value": "slab",    "label": "Плитный",     "price_per_m2": 4200}
    ]
  },
  {
    "id": "finishing",
    "label": "Отделка",
    "type": "checkbox-group",
    "options": [
      {"value": "rough",      "label": "Черновая",    "price_per_m2": 3000},
      {"value": "prefinish",  "label": "Предчистовая","price_per_m2": 5500},
      {"value": "finish",     "label": "Чистовая",     "price_per_m2": 9000}
    ]
  }
]

JavaScript engine for client-side calculation

class PriceCalculator {
    constructor(config) {
        this.params     = config.params;
        this.formula    = config.formula;
        this.currency   = config.currency;
        this.minPrice   = config.min_price;
        this.showRange  = config.show_range;
        this.rangePercent = config.range_percent || 15;

        this.values     = {};
        this.initDefaults();
    }

    initDefaults() {
        this.params.forEach(param => {
            if (param.default !== undefined) {
                this.values[param.id] = param.default;
            } else if (param.type === 'select' || param.type === 'radio') {
                this.values[param.id] = param.options[0]?.value;
            } else if (param.type === 'checkbox-group') {
                this.values[param.id] = [];
            }
        });
    }

    setValue(paramId, value) {
        this.values[paramId] = value;
    }

    calculate() {
        let total = 0;
        const area = parseFloat(this.values['area']) || 1;

        this.params.forEach(param => {
            const val = this.values[param.id];
            if (!val && val !== 0) return;

            switch (param.type) {
                case 'range':
                case 'number':
                    if (param.price_per_unit) {
                        total += parseFloat(val) * param.price_per_unit;
                    }
                    break;

                case 'select':
                case 'radio': {
                    const opt = param.options.find(o => String(o.value) === String(val));
                    if (opt) {
                        total += (opt.price || 0) + (opt.price_per_m2 || 0) * area;
                    }
                    break;
                }

                case 'checkbox-group': {
                    const selected = Array.isArray(val) ? val : [val];
                    selected.forEach(v => {
                        const opt = param.options.find(o => String(o.value) === String(v));
                        if (opt) {
                            total += (opt.price || 0) + (opt.price_per_m2 || 0) * area;
                        }
                    });
                    break;
                }
            }
        });

        if (this.minPrice && total < this.minPrice) {
            total = this.minPrice;
        }

        if (this.showRange) {
            const delta = total * (this.rangePercent / 100);
            return {
                min:   Math.floor(total - delta),
                max:   Math.ceil(total + delta),
                exact: null,
            };
        }

        return {min: null, max: null, exact: total};
    }

    formatPrice(value) {
        return new Intl.NumberFormat('ru-RU', {
            style: 'currency',
            currency: this.currency,
            maximumFractionDigits: 0,
        }).format(value);
    }
}

Integration with request form and CRM

After calculation, the user clicks "Submit request" — the form is pre-filled with data:

document.getElementById('btn-get-quote').addEventListener('click', () => {
    const result = calculator.calculate();
    const resultText = result.exact
        ? calculator.formatPrice(result.exact)
        : `from ${calculator.formatPrice(result.min)} to ${calculator.formatPrice(result.max)}`;

    document.getElementById('form-calc-result').value = resultText;
    document.getElementById('form-calc-params').value = JSON.stringify(calculator.values);

    document.getElementById('quote-form').scrollIntoView({behavior: 'smooth'});
});

On the server, parameters are saved to the lead comment:

$calcParams = json_decode($data['calc_params'] ?? '{}', true);
$paramsSummary = [];
foreach ($calcParams as $paramId => $value) {
    $paramsSummary[] = $paramId . ': ' . (is_array($value) ? implode(', ', $value) : $value);
}

$lead = new \CCrmLead(false);
$lead->Add([
    'TITLE'    => 'Cost calculation — ' . $name,
    'COMMENTS' => "Calculation result: {$calcResult}\n" . implode("\n", $paramsSummary),
]);

It's useful to save calculation data for analytics — which parameters are chosen most, which lead to requests. We record each calculation in a separate table and track conversion. The average conversion across our projects is 12%.

Guarantees of calculation accuracy

Architecture on HL-blocks eliminates errors from hardcoded formulas. All coefficients and prices are stored in the database, and the JS engine uses a unified formula generator. Our coefficient-based calculator is 2–3 times more accurate than ready-made solutions — thanks to support for multiple coefficients and seasonal promotions. In one project for a service center chain, this cut the time to generate a commercial offer from 2 hours to 5 minutes, allowing processing 150 more requests per month.

What's included in the work?

Development timelines

Order a calculator development — get a free consultation and preliminary timeline estimate. Contact us, we'll prepare a roadmap and commercial proposal.

In addition to the standard warranty, we provide source code and documentation for the entire project. You'll always be able to modify the solution yourself or reach out for support — we're here.

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.