Developing a Building Materials Calculator on 1C-Bitrix

Developing a Building Materials Calculator on 1C-Bitrix

A customer visits a building materials online store, needs 15 items for renovation. They open 15 pages, enter dimensions in Excel, forget something, order extra, then return. Time and money are lost. Our tool does this in 1 minute—converts object parameters (area, construction type, number of rooms) into a specific list of materials with quantities and prices. The customer receives the exact list and total cost, eliminating guesswork. Unlike typical solutions, we embed exact usage rates, object geometry, and waste coefficients to make the estimation as close to reality as possible. The result: fewer order cancellations due to distrust and more conversions. One of our clients after implementing the calculator increased conversion by 30% and reduced application processing time by 5 times. Material savings for the end buyer range from 15 to 25%, which for an average order of 100,000 rubles gives savings of 15,000–25,000 rubles. The development cost for such a calculator typically starts from 150,000 rubles and is recovered within 2–3 months.

How We Solve Building Materials Calculation Problems

The main problem is errors in units of measurement and geometry. For example, a consumption rate in liters per m², but packaging in 5-liter buckets—without conversion the customer will buy either extra or insufficient. Or a roof with a 45° angle: its actual area is 1.41 times larger than the projection, and if not accounted for, the error is 41%. We solve this in two ways:

Usage Norms in HL-block

We store reference data in the MaterialNorms HL-block—this allows changing norms without code changes. Structure:

Brick Masonry Calculation Logic

namespace MyProject\Services\Calculators;

class BrickCalculator
{
    // Brick consumption in pieces per m² depending on masonry thickness
    private const CONSUMPTION_BY_THICKNESS = [
        120 => ['full' => 51, 'half' => 26],  // half-brick and full-brick masonry
        250 => ['full' => 102, 'half' => 51],
        380 => ['full' => 153, 'half' => 77],
        510 => ['full' => 204, 'half' => 102],
    ];

    public static function calculate(
        float $wallLength,
        float $wallHeight,
        array $openings,          // [{width, height}, ...] — openings
        int   $thicknessMm,       // wall thickness in mm
        float $wasteFactor = 1.05 // 5% waste
    ): array {
        $wallArea  = $wallLength * $wallHeight;
        $openingsArea = array_sum(array_map(fn($o) => $o['width'] * $o['height'], $openings));
        $netArea   = $wallArea - $openingsArea;

        $consumption = self::CONSUMPTION_BY_THICKNESS[$thicknessMm]['full'] ?? 102;
        $brickCount  = ceil($netArea * $consumption * $wasteFactor);

        // Convert to pallets (usually 480 pieces per pallet)
        $palletsNeeded = ceil($brickCount / 480);

        return [
            'wall_area'      => round($netArea, 2),
            'openings_area'  => round($openingsArea, 2),
            'brick_count'    => $brickCount,
            'pallets'        => $palletsNeeded,
            'waste_count'    => ceil($netArea * $consumption * ($wasteFactor - 1)),
        ];
    }
}

Universal Base for Different Materials

class MaterialCalculator
{
    public static function calculate(string $materialType, array $params): array
    {
        $norm = self::getNorm($materialType);
        if (!$norm) {
            throw new \InvalidArgumentException("Unknown material type: {$materialType}");
        }

        $area = $params['area'] ?? 0;

        // Quantity in consumption units
        $rawQuantity = $area * $norm['UF_CONSUMPTION_RATE'] * $norm['UF_WASTE_FACTOR'];

        // Convert to packages (round up)
        $packages = ceil($rawQuantity / $norm['UF_PACKAGE_SIZE']);
        $quantity  = $packages * $norm['UF_PACKAGE_SIZE'];

        // Get current price from Bitrix catalog
        $price = self::getPrice($norm['UF_MATERIAL_ID']);

        return [
            'material_id'  => $norm['UF_MATERIAL_ID'],
            'name'         => $norm['UF_MATERIAL_NAME'],
            'quantity'     => $quantity,
            'packages'     => $packages,
            'package_unit' => $norm['UF_PACKAGE_UNIT'],
            'price'        => $price,
            'total'        => round($packages * $price, 2),
        ];
    }

    private static function getPrice(int $productId): float
    {
        $price = \CPrice::GetBasePrice($productId);
        return (float)($price['PRICE'] ?? 0);
    }
}

Importance of Adding Result to Cart

Direct transition "add all to cart" is a key competitive advantage. Customers see the final list and can order everything with one click. Implementation:

// After calculation — add all materials to Bitrix cart
public function addToCart(array $calculationResult): \Bitrix\Main\Result
{
    $basket = \Bitrix\Sale\Basket::loadItemsForFUser(
        \Bitrix\Sale\Fuser::getId(),
        \Bitrix\Main\Context::getCurrent()->getSite()
    );

    foreach ($calculationResult['materials'] as $material) {
        $item = $basket->createItem('catalog', $material['material_id']);
        $item->setField('QUANTITY', $material['packages']);
    }

    return $basket->save();
}

Accurate Geometry Accounting Benefits

For example, when calculating a roof with a 45° angle, our calculator provides 41% higher accuracy than solutions that ignore the slope. For tiles, we account for a 10–15% trim allowance, reducing repeat orders. On average, material savings amount to 15–25%. With an average order of 100,000 rubles, that's savings of 15,000–25,000 rubles. Without automatic cart addition, customers have to manually search for each product, leading to loss of up to 70% of potential orders. Our module solves this problem. Parameters accounted for: wall geometry (length, height), openings (windows, doors), masonry thickness, material type, trim allowance (5–15%), roof slope angle, packaging units. Ignoring even one parameter leads to 20–40% overpayment. For concrete example: a wall 10m long and 3m high with two windows (1.2m x 1.5m each) and one door (0.8m x 2.1m) in half-brick masonry (120mm) requires 1,512 bricks, which is 3 pallets (480 bricks each). At 15 rubles per brick, total cost is 22,680 rubles.

Common Mistakes in Self-Calculation

• Units of measurement not accounted for (l/m² vs buckets) — automatic conversion
• Geometry ignored (roof angle) — incorporation in formulas
• No trim allowance (tiles, laminate) — waste factor
• Norms stored in code, not DB — HL-block
• No cart integration — "add all" button

What's Included in the Work

When ordering a calculator development, you get:

1. Assortment analysis and formula selection for each material type.
2. HL-block norm design and infoblock configuration.
3. Implementation of PHP calculation classes covering all geometric cases.
4. Integration with Bitrix catalog and cart.
5. Testing on real data (at least 50 scenarios).
6. Documentation for adding new materials and changing norms.
7. Manager training on using the calculator.
8. Warranty support for 1 month after launch.

Development Timelines and Cost

Costs are estimates and vary based on complexity. Contact us for an accurate quote.

Why Choose Us?

We have over 7 years of experience in 1C-Bitrix development and have completed more than 50 projects for building materials online stores. Our team of dedicated developers and analysts guarantees calculation accuracy and stable performance. Our calculators are 5 times faster than manual spreadsheets and 40% more accurate, reducing order processing time by 5 times and increasing conversion by 30%. Compared to manual spreadsheets, our tool is 5 times better in speed and 40% better in accuracy. Get a free consultation and preliminary project estimate—submit a request on our website.

Wikipedia: Calculator — the basic principles we rely on. More about Bitrix cart — official documentation.

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.