Insurance Company Website Development on 1C-Bitrix

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Insurance Company Website Development on 1C-Bitrix
Complex
from 1 week to 3 months
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1356
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    943
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    693
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    828
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    731
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1073

A typical scenario: an insurance company spends up to 40% of managers' time manually calculating and issuing policies. Clients leave without waiting for a response, and agents lose motivation due to complex processes. We automate these tasks with an online insurance calculator and integration of accounting systems. A client calculates the cost, selects options, and pays for the policy in 5 minutes — without calls or office visits. We are certified specialists with 10+ years of experience, having implemented over 50 projects for insurance companies. Our expertise covers the full stack — from setting up information blocks to custom business logic for calculations.

The central element of such a site is a multi-step form with tariff logic that recalculates the premium in real time. Below we examine the architecture of all key components: from the catalog to integration with 1C:Insurance and AIS. Get a consultation on your project — we will help determine the optimal configuration.

Online Calculator for Insurance Policies

Insurance products are information blocks with sections by line of business:

  • Auto insurance — OSAGO, CASCO
  • Medical insurance — VHI for individuals and companies
  • Property — apartment, house, commercial real estate
  • Travel — international, domestic tourism
  • Life and health — accident insurance, endowment

Properties of the information block element:

Property Type Purpose
COVERAGE_LIST HTML List of covered risks
EXCLUSIONS HTML Exclusions from coverage
SUM_INSURED_MIN number Minimum insured sum
SUM_INSURED_MAX number Maximum insured sum
CALCULATOR_LINK string Link to the calculator for this product
DOCUMENTS file (multiple) Insurance rules, sample policy (PDF)
TARGET_AUDIENCE enumeration Individuals / Legal entities / Both

Each product has a detailed page describing the terms, coverage, and claim procedure. The insurance client carefully reads this information before purchasing.

Calculator Architecture with Tariff Logic

The calculator is the most complex component. Each product has its own form and calculation formula. Let's examine CASCO — the most loaded in terms of parameters.

Step 1: Vehicle data. Make, model, year of manufacture, engine power, VIN (optional), vehicle cost, presence of anti-theft system.

Step 2: Driver data. Age, experience, number of permitted drivers (or multi-drive). For each driver, their own BMR coefficient is calculated.

Step 3: Insurance parameters. Insured sum, deductible (unconditional, from 0 to 1000), inclusion of additional risks (GAP, personal accident, courtesy car), insurance period.

Step 4: Premium calculation. Base premium formula for CASCO:

Premium = Insured_Sum × Base_Tariff × BMR × EM × SP × FD × AS × TR

Coefficient values:

  • Base_Tariff — depends on make/model (theft risk) and year of manufacture
  • BMR — bonus-malus coefficient (minimum of all drivers)
  • EM — engine power coefficient
  • SP — insurance period coefficient (half a year ≠ half of annual)
  • FD — franchise (deductible) coefficient (the higher the franchise, the lower the coefficient)
  • AS — anti-theft system coefficient
  • TR — territorial coefficient

Highload blocks in 1C-Bitrix allow efficient storage of directories with arbitrary structure. The tariff directory is implemented via Highload blocks:

InsuranceBaseTariff — base tariffs:

Field Type Example
UF_PRODUCT_TYPE enumeration CASCO
UF_CAR_BRAND string Toyota
UF_CAR_MODEL string Camry
UF_YEAR_FROM integer start year
UF_YEAR_TO integer end year
UF_BASE_RATE float 0.035 (3.5%)
UF_RISK_GROUP enumeration Low / Medium / High (theft)

InsuranceCoefficient — coefficients:

Field Type Purpose
UF_COEFF_TYPE enumeration BMR / EM / SP / FD / AS / TR
UF_PARAM_FROM float Lower bound of parameter
UF_PARAM_TO float Upper bound of parameter
UF_VALUE float Coefficient value
UF_PRODUCT_TYPE enumeration For which product

Example entries for BMR:

UF_COEFF_TYPE UF_PARAM_FROM (age) UF_PARAM_TO Experience from Experience to UF_VALUE
BMR 18 21 0 2 1.87
BMR 22 25 3 5 1.04
BMR 30 65 10 99 0.93

For BMR, two parameters (age and experience) are needed, so additional fields are added to the Highload block or a separate InsuranceCoefficientBMR is created.

Example server-side calculation

The calculator sends an AJAX request to a custom controller. The server finds the base tariff and coefficients, multiplies them, and returns a JSON with a breakdown.

$baseTariff = InsuranceBaseTariffTable::getRow([
    'filter' => [
        'UF_PRODUCT_TYPE' => 'kasko',
        'UF_CAR_BRAND' => $brand,
        'UF_CAR_MODEL' => $model,
        '<=UF_YEAR_FROM' => $year,
        '>=UF_YEAR_TO' => $year,
    ],
]);

$coefficients = [];
$bmr = InsuranceCoefficientTable::getRow([
    'filter' => [
        'UF_COEFF_TYPE' => 'bmr',
        '<=UF_PARAM_FROM' => $driverAge,
        '>=UF_PARAM_TO' => $driverAge,
        '<=UF_PARAM2_FROM' => $driverExperience,
        '>=UF_PARAM2_TO' => $driverExperience,
    ],
]);
$coefficients['bmr'] = $bmr['UF_VALUE'];
// Similarly for EM, SP, FD, AS, TR
$premium = $insuredSum * $baseTariff['UF_BASE_RATE'];
foreach ($coefficients as $coeff) {
    $premium *= $coeff;
}

The breakdown for the client shows what the price consists of: base tariff 3.5%, BMR 1.04, franchise reduces by 15% — transparency builds trust.

On one project, we optimized the coefficient lookup queries, reducing calculation time from 8 seconds to 1.2 seconds.

Importance of Server-Side Insurance Tariff Calculation

The calculator works via an AJAX request to a custom Bitrix controller. The client side collects form parameters and sends a POST request. Server-side calculation is 3-5 times faster than a full page reload, allows dynamic coefficient loading, and provides a detailed quote.

Online Policy Purchase

After calculation, the client clicks "Issue Policy". An order is created via the sale module. The product is the insurance item with a dynamic price from the calculator. Order properties contain all policy parameters. Payment is through payment gateways (ERIP, bank cards) integrated via sale.paysystem. After payment, the OnSaleOrderPaid handler generates a PDF policy (TCPDF or mPDF) and sends it to the email.

Policyholder Personal Account

Personal account functionality:

  • My Policies — list of active and expired policies with PDF
  • Notifications 30 days before policy expiry (Bitrix agent + email/SMS)
  • Renewal — "Renew" button pulls data into the calculator
  • Claim submission — form with document upload (photos, certificates). Files via CFile::SaveFile(), claim saved in the "Insurance Cases" information block
  • Claim status: submitted → under review → documents requested → decision → payment

Integration with 1C:Insurance and AIS

Main options:

1C:Insurance. Exchange via 1C HTTP services. New policies and claims are sent from the site; statuses and tariffs are received from 1C.

Insurer's AIS. Via SOAP or REST. For OSAGO, KBM verification via an external API is mandatory, along with sending policy data and receiving a number.

CommerceML governs data exchange with 1C, but for insurance systems, custom HTTP services are more often used.

Agent Portal (B2B)

Insurance agents get authorized access with a calculator showing agent commission, a client pipeline (via a custom "Agent Requests" information block), and reporting in XLSX (via PhpSpreadsheet). Access is restricted by Bitrix user groups.

Implementation Timeline

Scale Composition Timeline
Single product (OSAGO or travel) Calculator, online purchase, basic personal account 8-10 weeks
3-5 products (auto + property + VHI) + multiple calculators, integration with 1C, claim submission 14-20 weeks
Full-featured website + agent portal, integration with AIS, renewal, mobile personal account 22-30 weeks

When estimating, we consider the volume of tariff directories and the number of unique formulas. Each new product requires separate implementation of calculator business logic. Contact us for an accurate estimate of your project.

What Is Included in the Work

  • Requirements analysis and audit of current processes
  • Architecture design and prototyping
  • Implementation of calculators and tariff directories
  • Integrations with 1C:Insurance, AIS, payment systems
  • Development of personal account and agent portal (if required)
  • Testing, deployment, and 6-month warranty support
  • Training of employees to work with the Bitrix admin panel
  • Transfer of technical documentation and access rights

Request an audit of your site — get a roadmap and cost estimate.

How to properly design infoblocks?

When developing a 1C-Bitrix website, we see dozens of projects where poor infoblock structure slows down the site. Typical scenario: the client asks for a "product catalog." The developer creates one infoblock catalog, puts 15 properties in it. Six months later – 40 properties, 8 of which are used only for one category. The filter lags, the b_iblock_element_property table grows to millions of rows, CIBlockElement::GetList runs for 3 seconds. Consequences – conversion drop, loss of customers, additional optimization costs. In one project after catalog refactoring, page generation time dropped from 4.2 to 0.8 seconds, and annual support costs were reduced by over $10,000 through eliminated redundant queries and agents.

Our approach: design infoblocks before writing a single line of code. Separate infoblocks for entities (products, categories, brands), dictionary properties via highload blocks, trade offers for SKUs. This builds performance for years. If you want a preliminary audit of your infoblock schema, contact us for a free review of common mistakes and recommendations.

Why 1C-Bitrix outperforms most CMS for business

The choice of CMS is dictated by business needs, not preferences. Native 1C exchange via catalog.import.1c provides two-way synchronization of products, prices, balances, and orders through CommerceML without third-party modules — five times faster than developing custom exchange on OpenCart or WordPress, saving hundreds of thousands of rubles. Proactive security module includes WAF, file integrity control, SQL injection protection, and two-factor authentication; it's certified for FSTEK requirements. Modular architecture lets you enable only needed modules — iblock, catalog, sale, search — reducing DB queries per hit. Regular patches close vulnerabilities faster than open-source projects (average CVE fix time two weeks). Official documentation is maintained on the vendor's site.

What highload blocks are and how they speed up the catalog

Highload blocks are an alternative to extended infoblock properties when the list of values can grow to thousands of entries. Typical example: manufacturers, countries, colors. If stored as list properties in an infoblock, each filter triggers a full scan of b_iblock_property_enum table. With HL-blocks, selection uses indexes – filter response time drops from 1–2 seconds to 50 ms. We use HLB component and custom queries via Bitrix\Highloadblock\DataManager. This is critical for catalogs with 100,000+ items.

From our practice: an online store with 500,000 items. Standard filter by brand took 4 seconds. The server couldn't handle 50 concurrent requests – pages crashed. We moved the brand directory to an HL-block, added tagged caching for 15 minutes, and set up an agent to clear cache on change. After optimization, filter time was 120 ms, average LCP was 1.8 seconds. The project runs stable without failures.

What integrations are critical for 1C-Bitrix stores

Each e‑commerce project requires reliable connections with payments, fiscalization, logistics, and CRM. We integrate YooKassa, CloudPayments, Tinkoff, Apple Pay, Google Pay for payments; ATOL and OrangeData for 54-FZ compliance via sale.cashbox; CDEK, Boxberry, PEC, Russian Post, Yandex.Delivery for logistics; Bitrix24, amoCRM, Roistat, Calltouch, Mindbox for analytics and CRM. All integrations are configured with proper error handling and fallback logic.

What's included in 1C-Bitrix website development

Each project includes a full set of documentation and artifacts to prevent knowledge loss after handover.

  • Technical specification – user stories, infoblock diagrams, integration schemas.
  • Source code in Git – with commit history, release tags, branching rules.
  • Administrative documentation – description of custom components, deployment instructions, list of agents and events.
  • Staff training – up to a 3-hour webinar: admin panel, order management, price settings. Recorded for later review.
  • Access to staging during development – test before production deployment.
  • Warranty support – bug fixes for 30 days after launch. Post-warranty support packages with SLA (response 2 hours, resolution 8 hours).

Our process and technologies

Project type Timeline Complexity Key features
Corporate website from 1 month Medium Catalog, news, forms, CRM integration
Online store from 2 months High 54-FZ, marketplaces, 1C exchange, SKU
B2B portal from 3 months Very high Personal prices, document flow, Bizproc
Landing page from 2 weeks Low LCP < 2s, composite cache, static
Multisite structure from 1.5 months High Separate content, shared catalog, hreflang

Tech stack: mobile-first markup, tested on physical devices (iPhone, iPad, Android). Use BrowserStack for Safari on iOS. Performance goals: LCP < 2.5 s, FID < 100 ms, CLS < 0.1. Enable composite site (composite module), CDN, tagged caching, WebP/AVIF, lazy loading. SEO: Schema.org via JSON-LD, auto-generation of sitemap.xml via seo module, canonical and hreflang for multilingual versions. robots.txt blocks /bitrix/ from indexing. CI/CD: Git, auto-deploy via GitLab CI, staging. DB migrations: sprint.migration module with versioning.

Process:

  1. Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
  2. Design – UI/UX with design system. Components are reusable.
  3. Development – write components with custom templates in local/templates/. Business logic in local/modules/.
  4. Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
  5. Launch – deploy to production, monitoring via UptimeRobot, alerts in Telegram. Fixes for first 48 hours.

Multilingual support and redesign

Full localization via language files lang/ and SITE_ID mechanism. hreflang for each version. Regional versions with different prices and content – IP detection (main.geo) or manual selection. Multidomain – unified management of multiple domains.

Redesign without losing rankings: performance audit (PageSpeed, WebPageTest), SEO (Screaming Frog). New template in local/templates/ with preserved URL structure. 301 redirects only if URL changes significantly. Kernel update, migration to D7 ORM, infoblock restructuring, migration via sprint.migration with Git.

Guarantee and support

We have been working with 1C-Bitrix for 12+ years, completed 500+ projects. Certified developers on staff. Fixed price in contract – no surprises. Warranty period covers code errors. After warranty, subscription packages with SLA (response time 2 hours, resolution 8 hours). 24/7 availability monitoring, alerts in Telegram. Get a consultation and preliminary estimate: contact us via the form on the website or chat – we'll respond within an hour. Order turnkey development – we'll design infoblocks, integrate 1C, and speed up the catalog. If you already have a site on another CMS, order a performance audit and migration to Bitrix.