1C-Bitrix Custom Service Calculator Module Development

1C-Bitrix Custom Service Calculator Module Development

A client enters the area, selects finishing — and leaves. Without a price. Without an application. Familiar? A service calculator on Bitrix solves this: the user gets an instant cost and submits an application. We develop custom modules that integrate into your site and work with CRM. No ready-made solutions — only tailored to your business logic and formulas.

Ready-made calculators in the Bitrix marketplace are practically nonexistent, or they are too primitive. For serious business — an insurance company, a construction contractor, a print shop — a module with flexible formulas and CRM integration is required. Our experience shows that a properly built calculator increases conversion by 2–3 times: the client understands pricing and trusts the company.

When Is a Custom Calculator Needed?

If your business uses non-standard rates, regional coefficients, or depends on data from 1C, a ready-made plugin won't suffice. A custom module gives full control over formulas and integrations. Compare: ready-made solutions handle only linear dependencies, while a custom module handles branching and external directories. Lead conversion with such a calculator is 2 times higher — proven on projects.

How the Formula Engine Works

The formula is stored in a JSON structure interpreted both on the server (PHP) and client (JavaScript). Synchronization is critical: the final amount in the interface must match the amount in CRM. The PHP interpreter FormulaEvaluator::evaluate($formula, $fieldValues) recursively traverses the tree and calculates the result. The frontend uses an identical JS interpreter.

{
  "type": "add",
  "operands": [
    {
      "type": "multiply",
      "operands": [
        {"type": "field", "name": "area"},
        {"type": "field", "name": "work_type_price"}
      ]
    },
    {
      "type": "if",
      "condition": {"type": "gt", "left": {"type": "field", "name": "area"}, "right": 100},
      "then": {"type": "multiply", "operands": [{"type": "ref", "name": "subtotal"}, -0.1]},
      "else": 0
    }
  ]
}

Comparison: Ready-Made vs Custom Module

Module Architecture: Tables and Field Types

The vendor.calculator module includes four main tables:

• b_vendor_calc_calculator — calculators: id, name, slug, config (JSON of fields and steps), formula (JSON calculation tree), crm_target (lead/deal), is_active
• b_vendor_calc_field — calculator fields: id, calculator_id, type, name, label, options (JSON), depends_on, validation_rules, sort
• b_vendor_calc_result — saved calculations: id, calculator_id, session_id, user_id, params (JSON), result (JSON sum), created_at
• b_vendor_calc_lead — link between calculation and CRM lead/deal: result_id, crm_type, crm_id

Field types:

• number — numeric field with min/max/step
• slider — slider with range
• select — dropdown with coefficient binding
• checkbox — flag with additional cost
• radio — single choice
• area — two-dimensional input (width × height)
• catalog_product — select product from infoblock with auto-substitution of price

Why Reactive Recalculation Matters

On the frontend — reactive recalculation without page reload. On any field change:

1. Current values of all fields are collected
2. A local copy of the formula is computed in JS (same logic as PHP)
3. The result is instantly updated in the interface
4. Additionally: an AJAX request to the server for precise calculation using actual database prices

// Recalculation on field change
document.querySelectorAll('.calc-field').forEach(field => {
    field.addEventListener('change', () => {
        const values = collectFieldValues();
        const localResult = evaluateFormula(calculatorConfig.formula, values);
        updateResultDisplay(localResult);
        debounce(() => fetchServerResult(values), 500)();
    });
});

Dependent Fields

Dependency is described in the field configuration:

{
  "name": "material_type",
  "type": "select",
  "depends_on": {
    "field": "work_type",
    "map": {
      "painting": ["latex", "acrylic", "oil"],
      "wallpaper": ["paper", "vinyl", "non-woven"],
      "tile": ["ceramic", "porcelain", "mosaic"]
    }
  }
}

When work_type = 'painting' is selected, the material list filters to ["latex", "acrylic", "oil"]. The logic works both on the client and is validated on the server upon form submission.

CRM Submission

After calculation, the user fills in contact details and submits the application. The module creates a lead or deal:

$leadFields = [
    'TITLE'       => 'Calculation from calculator: ' . $calculator['NAME'],
    'NAME'        => $formData['name'],
    'PHONE'       => [['VALUE' => $formData['phone'], 'VALUE_TYPE' => 'WORK']],
    'EMAIL'       => [['VALUE' => $formData['email'], 'VALUE_TYPE' => 'WORK']],
    'COMMENTS'    => $this->buildCalculatorComment($result),
    'UF_CALC_SUM' => $result['total'],
    'SOURCE_ID'   => 'CALCULATOR',
];

$leadId = \Bitrix\Crm\LeadTable::add($leadFields)->getId();

Calculation parameters are written to the lead comment and to the custom field UF_CALC_PARAMS (JSON).

What's Included

• Database architecture and module installer
• Field builder and configurator with admin interface
• Formula engine PHP + JavaScript
• Reactive recalculation and dependent fields
• Integration with trade catalog prices
• CRM application submission (leads/deals)
• Component for page placement
• Documentation and training of your employee
• 30-day warranty after delivery

Development Timeline

Total: 13 business days. Non-standard formulas with external references (rate grids, regional coefficients) — add 2–3 days.

Contact us to estimate your project. Over 10 years of Bitrix development experience — we guarantee quality and transparency. Get a consultation to discuss your task and prepare a commercial proposal. Learn more about CRM systems and Bitrix24 REST API.

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.