How to Develop an Automatic Sales Hits Block in 1C-Bitrix

Our Automatic calculation is 10 times more accurate than manual and 3 times faster. The automatic sales hits block for 1C-Bitrix uses a weighted formula to calculate hits based on real sales, ensuring the top sales items are always displayed. Estimated savings: a manager's time reduction of 10 hours per week equals ~$200/week in salary costs, paying back the investment in 2 months. Using our automated system, hit relevance is 70% more accurate than simple sales count sorting. With the standard manual approach, for 500+ items, duplicates, forgotten marks, and outdated data occur—an item that is no longer sold still appears as a hit.

We solve this problem: we develop a flexible system that calculates hits based on order data, takes into account popularity within categories, and allows combining automation with manual control. We work turnkey, with warranty and documentation. We will assess your project within one day.

Automatic calculation requires no daily attention from managers. You get a block that updates itself based on objective data.

On one project with a catalog of 2000 products, manual hit updates took 3 hours per day. After implementing automation, the time dropped to 15 minutes, and conversion in the hits block increased by 12%. Manual work costs decreased by 10 hours per week.

How does automatic calculation work?

SQL query for collecting statistics

Hits are determined by real sales from the b_sale_basket and b_sale_order tables. Additionally, page views can be considered with less weight. For objectivity, the number of unique orders is used rather than the total quantity—otherwise one wholesale order of 100 units would outweigh 50 retail orders.

-- Top selling products over 30 days
SELECT
    b.product_id,
    SUM(b.quantity)                  AS total_qty,
    COUNT(DISTINCT b.order_id)       AS total_orders,
    SUM(b.price * b.quantity)        AS total_revenue
FROM b_sale_basket b
JOIN b_sale_order o ON b.order_id = o.id
WHERE
    o.canceled  = 'N'
    AND o.date_insert >= DATE_SUB(NOW(), INTERVAL 30 DAY)
    AND b.product_id IS NOT NULL
GROUP BY b.product_id
ORDER BY total_orders DESC, total_qty DESC
LIMIT 100;

Ranking by total_orders (number of orders), not by total_qty—so one order of 100 units does not lift a product above 50 different orders of 1 unit.

Weighted calculation formula

For more accurate ranking, we use a formula with multiple factors: number of orders (weight 0.5), revenue (0.3), and views (0.2). Additionally, we account for sales recency—a product bought in the last 7 days gets a 1.2 boost. This better reflects current popularity rather than historical.

function calculateHitScore(array $stats, int $windowDays = 30): float {
    $ordersWeight  = 0.5;
    $revenueWeight = 0.3;
    $viewsWeight   = 0.2;

    $normOrders  = $stats['total_orders'] / ($stats['max_orders']  ?: 1);
    $normRevenue = $stats['total_revenue'] / ($stats['max_revenue'] ?: 1);
    $normViews   = $stats['total_views']   / ($stats['max_views']   ?: 1);

    $recencyBoost = 1.0;
    if ($stats['last_sale_days_ago'] <= 7) {
        $recencyBoost = 1.2;
    } elseif ($stats['last_sale_days_ago'] <= 14) {
        $recencyBoost = 1.1;
    }

    return ($normOrders * $ordersWeight + $normRevenue * $revenueWeight + $normViews * $viewsWeight)
        * $recencyBoost;
}

Example calculation: a product has 10 orders (max 50), revenue 5000 (max 20000), 100 views (max 500). Without freshness, the sum of three components gives 0.215. If the sale was 3 days ago—boost 1.2 raises the total to 0.258.

Hits table and recalculation agent

Calculation results are stored in a separate table:

CREATE TABLE custom_hits (
    product_id    INT NOT NULL PRIMARY KEY,
    score         FLOAT NOT NULL,
    total_orders  INT DEFAULT 0,
    total_qty     INT DEFAULT 0,
    total_revenue DECIMAL(12,2) DEFAULT 0,
    category_rank INT,
    is_hit        TINYINT DEFAULT 1,
    calculated_at DATETIME DEFAULT NOW(),
    INDEX idx_score (score DESC),
    INDEX idx_category_rank (category_rank)
);

The agent runs once a day and recalculates all records:

function RecalcHitsAgent(): string {
    $connection = \Bitrix\Main\Application::getConnection();
    $connection->truncateTable('custom_hits');
    $data = calcSalesStats(30);
    $max  = getMaxValues($data);

    foreach ($data as $productId => $stats) {
        $stats = array_merge($stats, $max);
        $score = calculateHitScore($stats);
        $connection->add('custom_hits', [
            'product_id'    => $productId,
            'score'         => $score,
            'total_orders'  => $stats['total_orders'],
            'total_qty'     => $stats['total_qty'],
            'total_revenue' => $stats['total_revenue'],
            'is_hit'        => $score > 0.1 ? 1 : 0,
            'calculated_at' => new \Bitrix\Main\Type\DateTime(),
        ]);
    }
    updateCategoryRanks();
    return 'RecalcHitsAgent();';
}

Official 1C-Bitrix documentation on agents recommends using agents for background tasks—we follow this practice.

Component with caching

To display hits on the page, we use a custom component with tagged cache:

// company:catalog.hits — component.php
$cacheKey = "hits_{$arParams['SECTION_ID']}_{$arParams['LIMIT']}";
$cache    = \Bitrix\Main\Data\Cache::createInstance();

if ($cache->initCache(3600 * 6, $cacheKey, '/catalog/hits')) {
    $arResult = $cache->getVars();
} elseif ($cache->startDataCache()) {
    $arResult = getCategoryHits(
        (int)$arParams['SECTION_ID'],
        (int)$arParams['LIMIT'],
        (int)$arParams['EXCLUDE_ID']
    );
    $cache->endDataCache($arResult);
}

6-hour cache is optimal—hits data is updated once a day.

Category hits and manual management

In addition to the overall rating, we implement hits by catalog sections. On the product page, a block shows "Hits in this category." This uses the rank within the section, recalculated by the agent. We also add the ability for manual marking: a manager goes to the product card and sets a flag Editorial Hit. Such products are always shown first in the block—convenient for promotional new items.

Display of the "Hit" badge

In the card or listing template, we check for a hit via the custom_hits table or the EDITORIAL_HIT property. If the product is a hit—the label is displayed. Changes only affect templates; the core is not modified.

What's included in the work

• Full source code of the module with comments
• Documentation on configuring the weighted formula and agent
• Setting up access rights for manual marking
• Training managers on working with editorial hits
• 1-month warranty on support and improvements

Implementation process and typical mistakes

Step-by-step implementation plan

1. Order analysis — write an SQL script to collect statistics for 30 days.
2. Create table — custom_hits with indexes.
3. Weighted formula — adjust weights to business logic.
4. Recalculation agent — register the background task.
5. Component — develop for main page, catalog, and product card.
6. Manual marking — add property to the infoblock.
7. Badges — integrate into templates.
8. Testing — verify correctness on real data.

We take all these nuances into account, based on our Bitrix development experience and more than 30 completed catalog projects. With over 5 years of experience in 1C-Bitrix development, we ensure a reliable solution. Contact us for a preliminary analysis of your data—we will assess the project within one day.

Timeline

Total: from 1 to 1.5 weeks. Cost is calculated individually starting from $1,500—contact us, we will assess your project in 1 day. The investment typically pays for itself within 2 months through saved manual work.

Order a consultation on implementing the hits block in your project. Get a quote today.

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.