Build a Custom Product Rating in 1C-Bitrix with ORM & AJAX

We integrate a custom product rating system into 1C-Bitrix using a separate ORM table, AJAX voting, and fraud protection. Unlike the standard vote module, our approach stores ratings in b_product_vote and aggregates results into infoblock properties, enabling smooth catalog integration and sorting. With over 10 years of Bitrix development experience and 50+ deployed projects, we guarantee stable operation under load. Typical project cost: €600-1200, with a development timeline of 3-7 days.

Why the standard vote module is not suitable for product ratings?

The vote module in Bitrix is designed for abstract polls and cannot directly bind to infoblock elements. For products, a lot of custom logic is needed: duplicate checking, aggregation recalculation, and order linking. Moreover, vote uses its own tables and components, complicating catalog sorting. Our scheme with a separate b_product_vote table and infoblock properties eliminates these shortcomings. Furthermore, Bitrix rating optimization in our approach is achieved through direct SQL queries and caching.

Rating storage architecture

Table b_product_vote for individual ratings:

ORM class ProductVoteTable extends \Bitrix\Main\ORM\Data\DataManager.

In the product infoblock, two numeric properties are added:

• RATING_AVG — average rating (float, updated after each vote)
• RATING_COUNT — number of ratings

This allows sorting and filtering by rating through standard CIBlockElement::GetList() without JOINs.

How we implement ratings: step-by-step process

1. Audit the current store architecture on 1C-Bitrix: assess load, product types, and existing modules.
2. Design the ORM model: create b_product_vote table, write ProductVoteTable class.
3. Develop an AJAX voting controller with duplicate protection.
4. Integrate aggregation into infoblock properties using SetPropertyValuesEx.
5. Create a star widget with partial fill (SVG, CSS-clip).
6. Configure catalog sorting by rating.
7. Load test: simulate 10,000 votes, measure response time.
8. Document API and components, train administrators.

Voting algorithm

Voting is done via an AJAX request. The component outputs a star form; a click sends a POST to the controller:

// local/ajax/product_vote.php
\Bitrix\Main\Loader::includeModule('main');
\Bitrix\Main\Loader::includeModule('catalog');

$productId = (int)($_POST['product_id'] ?? 0);
$rating    = (int)($_POST['rating'] ?? 0);

if ($rating < 1 || $rating > 5 || $productId <= 0) {
    echo json_encode(['success' => false, 'error' => 'invalid_data']);
    exit;
}

$userId = $GLOBALS['USER']->GetID() ?: null;
$ip     = \Bitrix\Main\Context::getCurrent()->getRequest()->getRemoteAddress();

// Check: already voted?
$existing = ProductVoteTable::getList([
    'filter' => ['=PRODUCT_ID' => $productId, '=USER_ID' => $userId ?: false, '=IP' => $ip],
    'limit'  => 1,
])->fetch();

if ($existing && $userId === null) {
    echo json_encode(['success' => false, 'error' => 'already_voted']);
    exit;
}

For authorized users, we check by USER_ID. For guests, by IP. An authorized user can change their rating (update the existing record instead of creating a new one).

Aggregated rating recalculation

After each vote, we update the aggregates. More details on SetPropertyValuesEx in the official documentation:

function updateProductRating(int $productId): void
{
    $conn = \Bitrix\Main\Application::getConnection();
    $row = $conn->query(
        "SELECT AVG(RATING) as AVG_RATING, COUNT(*) as CNT
         FROM b_product_vote
         WHERE PRODUCT_ID = {$productId}"
    )->fetch();

    \CIBlockElement::SetPropertyValuesEx($productId, false, [
        'RATING_AVG'   => round((float)$row['AVG_RATING'], 2),
        'RATING_COUNT' => (int)$row['CNT'],
    ]);
}

SetPropertyValuesEx works faster than Update() of the whole element — it updates only the specified properties.

Star widget implementation

On the frontend, the rating is displayed as a set of SVG stars. Partial fill logic: for a rating of 4.2, four stars are fully filled, the fifth is 20% filled. Implemented via CSS-clip or SVG gradient with width proportional to the fractional part.

Component for displaying rating in product card and listing accepts parameters:

$APPLICATION->IncludeComponent('custom:product.rating', '', [
    'PRODUCT_ID'    => $arResult['ID'],
    'SHOW_FORM'     => $USER->IsAuthorized() ? 'Y' : 'N',
    'CURRENT_RATING' => $arResult['PROPERTIES']['RATING_AVG']['VALUE'],
    'VOTE_COUNT'    => $arResult['PROPERTIES']['RATING_COUNT']['VALUE'],
]);

How to protect ratings from fraud?

IP restrictions are good for guests but not for organized attacks:

• For authorized users — one rating per product (strict check via USER_ID + PRODUCT_ID).
• Restriction: cannot vote for a product that has never been viewed (check via b_stat_session or custom view table).
• Optionally: allow voting only to users who purchased the product (similar to verification in review systems).

Thanks to this approach, we block up to 99% of fraud in real projects. Experience shows that the combination of USER_ID + IP reduces fake votes to almost zero. In one electronics store project (catalog of 10,000 products, load 500 votes per hour), implementing the rating increased conversion by 18% in the first month — products with a score above 4.0 sold twice as often. The average score across the store was 4.2. Rating update time after a vote is less than 0.3 seconds.

What is included in the work

• Audit of the current store architecture on 1C-Bitrix
• Design of the ORM model for storing ratings
• Development of AJAX voting controller with protection
• Integration of aggregation into infoblock properties
• Creation of a star widget with partial fill
• Configuration of catalog sorting by rating
• Load testing and debugging
• API and component documentation
• Training administrators on the system
• Post-release support for one month

Experimentally confirmed: product rating increases conversion by 15–20%.

Development timeline and cost

Contact us for a free project assessment. Order a turnkey rating system development — increase trust in your catalog. Get a consultation on your project.

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.