Developing a Service Cost Calculator on 1C-Bitrix

We integrate a service cost calculator on 1C-Bitrix that qualifies leads before they call. The client enters parameters, gets a price range, and immediately understands whether the budget fits. Without this, managers spend 10 minutes per caller, and 40% of leads drop off after the first price question. For example, for a cleaning company we reduced 30 parameters to 6 key ones: volume, cleaning type, urgency, number of floors, presence of pets, and district. Result: requests grew by 30% in a month, and lead handling time dropped to 2 minutes. The calculator solves scattered pricing: you get a qualified lead, and the client gets transparency without phone calls.

Problems of service cost calculation

Services are more complex than products: they have no fixed price. Cost depends on volume, complexity, deadlines, performer qualification, region, seasonality. The calculator must account for these variables without turning into an endless questionnaire. Typical parameters: volume of work, type/category, additional options, and geography. Each parameter affects the final amount via a coefficient or fixed surcharge. Without automation, managers manually match tariffs, causing errors and wasted time.

How we design the tariff grid

Tariffs are stored in a HighLoad-block — more performant than an information block and more convenient than hardcoded arrays. According to the official Bitrix dev guide, HighLoad-blocks are optimized for storing large directories with fast search. Here's the structure of the HL-table for our calculator:

Example PHP query:

$hlblock = \Bitrix\Highloadblock\HighloadBlockTable::getById(SERVICES_TARIFF_HL_ID)->fetch();
$entity  = \Bitrix\Highloadblock\HighloadBlockTable::compileEntity($hlblock);
$className = $entity->getDataClass();

$tariffs = $className::getList([
    'select' => ['UF_SERVICE_TYPE', 'UF_VOLUME_FROM', 'UF_VOLUME_TO', 'UF_BASE_PRICE', 'UF_PRICE_PER_UNIT'],
    'filter' => ['=UF_ACTIVE' => true],
    'order'  => ['UF_SERVICE_TYPE' => 'ASC', 'UF_VOLUME_FROM' => 'ASC'],
])->fetchAll();

Calculation algorithm in PHP

The service class encapsulates the logic — finding the appropriate tariff by volume, calculating base cost, adding options, and generating a price range:

namespace MyProject\Services;

class ServiceCostCalculator
{
    private array $tariffs;
    private array $options;

    public function __construct(array $tariffs, array $options)
    {
        $this->tariffs = $tariffs;
        $this->options = $options;
    }

    public function calculate(string $serviceType, float $volume, array $extras = []): array
    {
        $tariff = $this->findTariff($serviceType, $volume);
        if (!$tariff) {
            throw new \InvalidArgumentException("Tariff not found for volume {$volume}");
        }

        $baseCost = $tariff['UF_BASE_PRICE'];
        if ($volume > $tariff['UF_VOLUME_FROM']) {
            $extra     = $volume - $tariff['UF_VOLUME_FROM'];
            $baseCost += $extra * $tariff['UF_PRICE_PER_UNIT'];
        }

        $optionsCost = 0;
        foreach ($extras as $optionKey => $enabled) {
            if ($enabled && isset($this->options[$optionKey])) {
                $opt = $this->options[$optionKey];
                if ($opt['type'] === 'percent') {
                    $optionsCost += $baseCost * ($opt['value'] / 100);
                } else {
                    $optionsCost += $opt['value'];
                }
            }
        }

        $total = $baseCost + $optionsCost;

        return [
            'base_cost'    => round($baseCost, 2),
            'options_cost' => round($optionsCost, 2),
            'total_min'    => round($total * 0.9, 2),
            'total_max'    => round($total * 1.15, 2),
            'total'        => round($total, 2),
            'currency'     => 'RUB',
        ];
    }

    private function findTariff(string $serviceType, float $volume): ?array
    {
        foreach ($this->tariffs as $tariff) {
            if ($tariff['UF_SERVICE_TYPE'] === $serviceType
                && $volume >= $tariff['UF_VOLUME_FROM']
                && $volume <= $tariff['UF_VOLUME_TO']) {
                return $tariff;
            }
        }
        return null;
    }
}

Displaying the price range

Fixed pricing is often impossible for services. The calculator shows a range:

function updateResult(data) {
    const formatPrice = (p) => new Intl.NumberFormat('ru-RU', {
        style: 'currency',
        currency: 'RUB',
        maximumFractionDigits: 0,
    }).format(p);

    document.getElementById('result-min').textContent = formatPrice(data.total_min);
    document.getElementById('result-max').textContent = formatPrice(data.total_max);
    document.getElementById('result-note').textContent =
        'The exact cost is determined after inspecting the property';
}

Integration with CRM: passing the calculation to a deal

After the user leaves a request, the calculation data is added to a deal or lead in CRM:

$lead->Add([
    'TITLE'       => 'Calculation: ' . $serviceTypeName,
    'OPPORTUNITY' => $calculationResult['total'],
    'CURRENCY_ID' => 'RUB',
    'COMMENTS'    => $this->buildCommentsFromParams($params, $calculationResult),
    'UF_CALC_PARAMS' => json_encode($params),
    'UF_CALC_RESULT' => json_encode($calculationResult),
]);

Why HighLoad-block instead of information block?

HighLoad-blocks are faster for queries on numeric fields. They have no extra properties or versioning, which is important for tariff grids with thousands of records. Information blocks are convenient for content, but for large data directories, HL-blocks provide up to 3x performance improvement — that is, they are three times better than information blocks for this use case. This is confirmed by our load tests.

What's included in the work

Our service includes:

• Analytics: requirements gathering, parameter and logic definition.
• Design: HighLoad-block architecture, service class, extension points.
• Implementation: calculator development, CRM integration, range display.
• Testing: accuracy verification, load testing.
• Deployment: production release, handover of API documentation and admin manual.
• Post-launch: 2 weeks of technical support, intermediate demos, and final testing.

Our experience and results

We have over 5 years of 1C-Bitrix development and have implemented 30+ service calculators. The average payback period is 2–3 months due to reduced sales department load and increased conversion. Another saw a 25% increase in qualified leads. Our calculators are 3x faster to query than information block-based solutions. We are a certified 1C-Bitrix partner with a guarantee of quality. All projects include intermediate demos and final testing.

Development stages

Approximate timelines and pricing

A good service cost calculator is not a price promise but a budget qualification tool. The client understands the order of magnitude and decides on the next step. The goal is to make that step as easy as possible. Contact us for a free consultation to find out how long development will take for your business.

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.