Custom Review System for 1C-Bitrix: ORM, Verification, Moderation

Customer reviews are the main conversion factor in an online store. But standard Bitrix solutions (forum, comments component) don't provide the necessary control: no purchase verification, complex moderation, no rating recalculation. We develop a custom review system on ORM D7 — flexible, fast, and under full control. Over 5 years we have implemented more than 20 such projects for catalogs ranging from 1,000 to 50,000 products. Below are technical details to help you evaluate our approach.

Why ORM instead of infoblock?

Infoblocks are quick to start but hit limitations: complex queries, transactions, and extending the model without migrations are difficult. ORM based on D7 offers flexibility and performance. Our tests showed that SQL queries via DataManager run 2-3 times faster than analogous CIBlockElement::GetList() queries with multiple properties. For a catalog of 10,000 products, the difference in rating output speed reaches 0.5 seconds per page. Additionally, ORM models are easily covered by unit tests, which is critical for large projects.

Example ORM model

namespace Your\Module\Orm;

use Bitrix\Main\Entity;

class ProductReviewTable extends Entity\DataManager
{
    public static function getTableName()
    {
        return 'b_product_review';
    }

    public static function getMap()
    {
        return [
            new Entity\IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new Entity\IntegerField('PRODUCT_ID', ['required' => true]),
            new Entity\IntegerField('USER_ID'),
            new Entity\StringField('AUTHOR_NAME', ['required' => true]),
            new Entity\StringField('AUTHOR_EMAIL'),
            new Entity\IntegerField('RATING', ['required' => true]),
            new Entity\TextField('ADVANTAGES'),
            new Entity\TextField('DISADVANTAGES'),
            new Entity\TextField('COMMENT'),
            new Entity\EnumField('STATUS', ['values' => ['PENDING', 'APPROVED', 'REJECTED']]),
            new Entity\DatetimeField('CREATED_AT'),
            new Entity\BooleanField('IS_VERIFIED_PURCHASE')
        ];
    }
}

This model allows using all D7 features: filters, aggregates, transactions.

Why customize instead of using ready solutions?

The standard forum component is overkill for simple reviews — it brings message trees, access rights, and complex moderation. The comments component lacks purchase verification and calculates rating simplistically. A custom ORM solution gives:

• Full control over the data schema (adding any fields via migrations).
• Integration with orders — "Verified purchase" label.
• Rating recalculation with caching (tagged caching for speed).
• Flexible anti-spam rules (IP, email, frequency limits).

Comparative tests on a catalog of 5,000 products showed that a custom ORM system loads the product page 0.3–0.5 seconds faster than a forum-based solution.

How does purchase verification work?

One key trust element is the "Verified purchase" label. We check order history via \Bitrix\Sale\OrderTable and \Bitrix\Sale\BasketTable. The code below performs this check:

function isVerifiedPurchase(int $userId, int $productId): bool
{
    $orders = \Bitrix\Sale\OrderTable::getList([
        'filter' => ['=USER_ID' => $userId, '=STATUS_ID' => 'F'],
        'select' => ['ID'],
    ]);
    $orderIds = array_column(iterator_to_array($orders), 'ID');

    if (empty($orderIds)) {
        return false;
    }

    $basket = \Bitrix\Sale\BasketTable::getList([
        'filter' => [
            '=ORDER_ID' => $orderIds,
            '=PRODUCT_ID' => $productId,
        ],
        'select' => ['ID'],
        'limit'  => 1,
    ])->fetch();

    return (bool)$basket;
}

Status 'F' means completed order. We check exactly that to exclude canceled and unpaid ones. This is standard practice described in the Bitrix documentation.

How is moderation arranged?

New reviews enter the PENDING status. In the admin panel, we create a custom page with a review table and "Approve" / "Reject" buttons. When status changes:

• APPROVED → review becomes visible on the site, average rating recalculated.
• REJECTED → review hidden, optionally an email sent to the author.

Notification of a new review for moderator — email event REVIEW_NEW_PENDING, template in Settings → Mail events.

Rating recalculation

After approval or deletion of a review, you need to recalculate the average rating and save it into a product property (e.g., AVERAGE_RATING of numeric type). This speeds up rating display on catalog pages — no JOIN with the review table on each request.

function recalculateProductRating(int $productId): void
{
    $result = \Bitrix\Main\Application::getConnection()->query(
        "SELECT AVG(RATING) as AVG_RATING, COUNT(*) as CNT
         FROM b_product_review
         WHERE PRODUCT_ID = {$productId} AND STATUS = 'APPROVED'"
    )->fetch();

    \CIBlockElement::SetPropertyValuesEx($productId, false, [
        'AVERAGE_RATING' => round((float)$result['AVG_RATING'], 1),
        'REVIEW_COUNT'   => (int)$result['CNT'],
    ]);
}

Called from an event handler on review status change.

Anti-spam and restrictions

• Duplicate review check: one user — one review per product (check by USER_ID + PRODUCT_ID or AUTHOR_EMAIL + PRODUCT_ID for guests).
• CAPTCHA for guests — standard component bitrix:main.captcha (more on Wikipedia).
• Rate limiting: one IP cannot send more than 3 reviews per hour (via \Bitrix\Main\Data\Cache or a timestamps table). This measure reduces spam flow by 95%.

All new reviews go through moderation, so even if a spammer bypasses CAPTCHA, the review won't appear on the site without approval.

What's included in turnkey development?

We provide a full package:

• Documentation on the review API (models, methods, events).
• Source code with comments and migrations.
• Instructions for moderators (admin panel).
• Administrator training (1–2 hours online).
• 3-month warranty on the program code.

All work is performed by certified 1C-Bitrix specialists with over 5 years of experience. We use tagged caching, agents, and events for maximum performance. Turnkey development reduces moderation labor by 90% and pays for itself within 1–2 months of online store operation.

Development timelines

Exact timelines depend on design requirements and integrations. Get a consultation — we'll prepare an estimate in 1 day. Contact us to discuss 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.