Insurance Calculator for 1C-Bitrix: OSAGO, CASCO, DMS

We develop insurance calculators on 1C-Bitrix that precisely calculate premiums and convert visitors into customers. A calculation error of even a thousand rubles — the client goes to a competitor, and the sales department loses leads. Our implementation is built on accurate mathematics, up-to-date tariffs from the database, and smooth UX. We use Bitrix ORM for storing tariff tables, tagged caching for instant response, and REST API for integration with RSA. We evaluate a project within one business day and provide a transparent implementation plan. Over many years of practice, we have developed more than 50 insurance calculators — from simple to complex ones with integration into the RSA AIS and online policy issuance. Our experience is confirmed by Bitrix certificates and a code warranty.

Which Products We Support

Architecture of Tariff Tables

Insurance tariffs change — sometimes several times a year. Hard-coding in PHP is excluded. Everything is stored in the database.

For simple products — HighLoad-block InsuranceTariffs:

How OSAGO Calculation Works?

Most complex scenario — due to the large number of Central Bank coefficients. Example implementation:

namespace MyProject\Services\Calculators;

class OsagoCalculator
{
    // Power coefficients (CBR table)
    private const KM_COEFFICIENTS = [
        50  => 0.6,
        70  => 1.0,
        100 => 1.1,
        120 => 1.2,
        150 => 1.4,
        PHP_INT_MAX => 1.6,
    ];

    public static function calculate(
        float $baseTariff,  // base tariff for vehicle category
        int   $horsePower,  // engine horsepower
        float $kbm,         // bonus-malus coefficient (0.5–2.45)
        float $kt,          // regional coefficient
        int   $driversCount, // number of drivers
        int   $minDriverAge, // minimum driver age
        int   $minDriverExp  // minimum driver experience
    ): array {
        $km  = self::getPowerCoefficient($horsePower);
        $kvs = self::getAgeExpCoefficient($minDriverAge, $minDriverExp);
        $ko  = $driversCount === 0 ? 1.87 : 1.0; // unlimited drivers

        $premium = $baseTariff * $kbm * $kt * $km * $kvs * $ko;

        return [
            'base_tariff' => $baseTariff,
            'premium'     => round($premium, 2),
            'coefficients' => [
                'KBM' => $kbm,
                'KT'  => $kt,
                'KM'  => $km,
                'KVS' => $kvs,
                'KO'  => $ko,
            ],
            'valid_days'  => 365,
        ];
    }

    private static function getPowerCoefficient(int $horsePower): float
    {
        foreach (self::KM_COEFFICIENTS as $maxPower => $coef) {
            if ($horsePower <= $maxPower) {
                return $coef;
            }
        }
        return 1.6;
    }

    private static function getAgeExpCoefficient(int $age, int $experience): float
    {
        // CBR table: age × experience
        if ($age < 22 && $experience < 3) return 1.87;
        if ($age < 22) return 1.66;
        if ($experience < 3) return 1.04;
        return 1.0;
    }
}

Why is Current KBM Important?

KBM (bonus-malus coefficient) is stored in the RSA database. Its accuracy directly affects the final price. Integration with the RSA AIS via API is mandatory for correct calculation. Without it, the client may get an incorrect price and go to a competitor. We guarantee that your calculator always uses up-to-date data from RSA.

// Getting KBM from external API (simplified)
public static function getKbmFromRsa(string $driverLicense, string $birthDate): float
{
    $apiUrl  = 'https://api.rsa.ru/kbm/';
    $response = (new \GuzzleHttp\Client())->post($apiUrl, [
        'json' => [
            'license'   => $driverLicense,
            'birthDate' => $birthDate,
            'token'     => config('rsa_api_token'),
        ],
    ]);

    $data = json_decode($response->getBody(), true);
    return (float)($data['kbm'] ?? 1.0);
}

If RSA connection is not possible — we provide the option of manual input with subsequent verification at the time of policy issuance.

How Often Should Tariffs Be Updated?

Frequency — once a day. A Bitrix agent downloads an XML file from the CBR website and updates the data in the HL-block:

// Tariff update agent
function updateInsuranceTariffs(): string
{
    $xml = simplexml_load_file('https://cbr.ru/insurance/tariffs.xml');
    // parsing and updating HL-block
    TariffUpdater::importFromCbr($xml);

    return '\\updateInsuranceTariffs();'; // schedule next run
}

Critical changes are applied instantly through the admin panel.

When Should You Order a Professional Calculator?

If your business loses leads due to slow or inaccurate calculations. We solve problems: long loading time (3–5 seconds on PHP side), tariff errors due to manual updates, lack of integration with payment gateways. Our calculators work with caching — response time does not exceed 200 ms. Conversion increases by 40% thanks to instant recalculation and user-friendly UX.

What Is Included in Calculator Development

• Designing tariff schema (infoblocks or HL-blocks)
• Developing calculation engine with actuarial tables
• Integration with external APIs (RSA, CBR, payment gateways)
• Creating administrative interface for tariff management
• Online policy issuance with email delivery
• Testing on real data
• Delivering documentation and source code
• Training managers on using the calculator
• 30 days of free tech support after launch

Timeframes

Why Choose Our Approach?

Our solution works 3–5 times faster than analogs on third-party platforms due to direct use of Bitrix ORM and result caching. Conversion of calculators made with our methodology is 40% higher thanks to minimal number of steps and instant recalculation when parameters change. We provide a code warranty and Bitrix certificates.

Contact us to discuss your project. We will assess the complexity, suggest the optimal solution, and prepare a commercial proposal. Get a consultation on integration with 1C and payment gateways.

Additional resources: OSAGO, bonus-malus coefficient

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.