Installment Calculator Development for 1C-Bitrix

A visitor adds a laptop worth 120,000 rubles to the cart, sees the total, and leaves — a typical situation for online stores without installment options. The psychological barrier of the full price reduces conversion by 20–30%. We are a team of certified 1C-Bitrix developers with more than 5 years of experience. We have developed calculators for 15+ online stores, from small niche shops to large catalogs. In this article, we'll break down how to implement a tool that not only shows "from 5,000 RUB/month" but also correctly handles hidden commissions, annuity schemes, and bank integration.

Annuity payment — Wikipedia.

Why is an Installment Calculator Critical for E-commerce?

Instead of a price of 120,000 RUB, the customer sees "from 5,000 RUB/month." The psychological barrier drops, and the average order value increases. A calculator on the product page increases checkout conversion by 20–30% according to our data — this is 2-3 times more effective than just showing a banner with a promotion. The annuity formula provides accuracy down to a penny, while a simplified method can be off by 5–10% for programs with variable rates (see Wikipedia: Annuity).

How Does the Installment Mechanism Work?

In classic zero-interest installment, the monthly payment = product cost / number of months. The seller compensates the bank for the difference through their margin or a special agreement with the partner bank. In "0–0–24" installment (0% down payment, 0% rate, 24 months), hidden conditions often include mandatory insurance or account maintenance fees. The calculator must show the real total amount.

Pitfalls of 0% Installment

Challenges we face during implementation:

• Multiple partner banks with different conditions (term, down payment, commission). Storing in an HL block is optimal.
• Hidden commissions in "interest-free" programs (insurance, account maintenance). The calculator must display the total amount.
• Integration with 1C via CommerceML — you need to pass the selected program into the order and accounting.

Some banks charge a one-time connection fee for installment — up to 10% of the purchase amount. Instead of stating it explicitly, they mask it as "service fee." The calculator should break down the total: product cost + commissions + interest (if any).

How to Develop an Installment Calculator: Step-by-Step Plan

1. Collect partner bank conditions: terms, rates, commissions, minimum and maximum amounts.
2. Design the highload block InstallmentPrograms for storing programs.
3. Implement the InstallmentCalculator class with support for annuity and differentiated schemes.
4. Embed the widget on the product page and in the cart with a comparison table.
5. Set up caching of calculation results and integration with 1C.

How We Do It: Stack and Approach

At the core is the InstallmentCalculator class with annuity calculation. We support all popular schemes: classic zero-interest installment, installment with an actual rate (compensated by the seller), variations with different down payments.

namespace MyProject\Services;

class InstallmentCalculator
{
    /**
     * @param float  $amount      Product/service cost
     * @param int    $months      Installment term
     * @param float  $downPayment Down payment (0 if none)
     * @param float  $bankRate    Actual bank rate (compensated by the seller)
     * @param float  $commission  One-time commission (0 if none)
     */
    public static function calculate(
        float $amount,
        int   $months,
        float $downPayment = 0,
        float $bankRate    = 0,
        float $commission  = 0
    ): array {
        $loanAmount      = $amount - $downPayment;
        $commissionFixed = $amount * ($commission / 100);

        if ($bankRate == 0) {
            // Classic zero-interest installment
            $monthlyPayment = $loanAmount / $months;
            $totalPayment   = $loanAmount + $commissionFixed;
            $overpayment    = $commissionFixed;
        } else {
            // Installment with actual rate (paid by seller, not buyer)
            $monthlyRate    = $bankRate / 12 / 100;
            $monthlyPayment = $loanAmount * $monthlyRate
                * pow(1 + $monthlyRate, $months)
                / (pow(1 + $monthlyRate, $months) - 1);
            $totalPayment   = $monthlyPayment * $months + $commissionFixed;
            $overpayment    = $totalPayment - $loanAmount;
        }

        return [
            'down_payment'    => round($downPayment, 2),
            'loan_amount'     => round($loanAmount, 2),
            'monthly_payment' => round($monthlyPayment, 2),
            'commission'      => round($commissionFixed, 2),
            'total_payment'   => round($totalPayment, 2),
            'overpayment'     => round($overpayment, 2),
            'months'          => $months,
            'is_zero_percent' => ($overpayment == 0 || $overpayment == $commissionFixed),
        ];
    }
}

Installment Options Configuration

Stores work with multiple partner banks, each offering different conditions. Storing in the HL block InstallmentPrograms:

When the amount is selected, the calculator automatically displays available programs.

UX: Displaying Options

The interface shows a comparison table. Implementation in JavaScript:

function renderInstallmentTable(programs, amount) {
    const rows = programs
        .filter(p => amount >= p.min_amount && amount <= p.max_amount)
        .map(p => {
            const calc = calcInstallment(amount, p.months, p.down_pct, p.commission_pct);
            return `
                <tr>
                    <td>${p.bank_name}</td>
                    <td>${p.months} mo.</td>
                    <td>${formatMoney(calc.down_payment)} (${p.down_pct}%)</td>
                    <td>${formatMoney(calc.monthly_payment)}/mo.</td>
                    <td>${calc.overpayment > 0 ? formatMoney(calc.overpayment) : '0 RUB'}</td>
                    <td><button onclick="selectProgram(${p.id})">Select</button></td>
                </tr>
            `;
        });

    document.getElementById('installment-table').innerHTML = rows.join('');
}

Integration with Bitrix Cart

For online stores, the calculator is embedded on the product page and in the cart. The selected option is saved in the order properties. Integration example:

// Saving the selected installment program in the order property
$order = \Bitrix\Sale\Order::load($orderId);
$propertyCollection = $order->getPropertyCollection();

$installmentProp = $propertyCollection->getItemByOrderPropertyCode('INSTALLMENT_PROGRAM');
if ($installmentProp) {
    $installmentProp->setValue(json_encode([
        'bank'    => $bankName,
        'months'  => $months,
        'payment' => $monthlyPayment,
    ]));
}

$order->save();

// In the product template: minimum payment
$minMonthlyPayment = InstallmentCalculator::getMinMonthlyPayment(
    $arResult['ITEM_PRICES'][0]['PRICE'],
    $availablePrograms
);

if ($minMonthlyPayment) {
    echo "from {$minMonthlyPayment} RUB/month in installments";
}

How to Ensure Calculation Accuracy?

The annuity formula provides accuracy down to a penny, while a simplified method can be off by 5–10% for programs with variable rates. This is critical when connecting a real bank API — calculation errors lead to returns and complaints. Always use decimal types for financial operations, and tagged caching to reduce database load during batch calculations.

Typical Mistakes in Calculator Development

• Incorrect interest calculation — forgetting to account for commission or rounding. Use BigDecimal equivalents.
• Lack of caching — calculation for each product page can load the database. Add tagged caching of results.
• Rigid binding to a bank — abstract through interfaces to easily add new partners.

What's Included in the Development?

• Analysis of your partner banks and their terms
• Designing highload tables and business logic
• Implementing the calculation class and cart integration
• UI widget with comparison table and program selection
• Documentation and manager training
• Code warranty and post-launch support

Timeframes for Implementation

The cost is calculated individually. Contact us for a consultation and commercial proposal. Leave a request — we'll evaluate the project in one day and tell you how an installment calculator can increase your store's conversion.

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.