Social proof for 1C-Bitrix: turnkey development

A product card without reviews, ratings, and real customer photos converts 15–30% worse — this is confirmed by A/B tests on dozens of e-commerce projects. Users trust other buyers' opinions more than advertising: reviews and ratings increase the likelihood of purchase by 58% (data from PowerReviews). The technical implementation of such elements on Bitrix requires a deep understanding of infoblock architecture, caching, and the event model.

The problem isn't a lack of desire, but complexity: you need to design review storage, configure aggregated data caching, avoid breaking catalog performance, and simultaneously protect against spam and vote rigging. In 5 years, we have implemented social proof for 50+ projects on 1C-Bitrix and developed architectural solutions that work without compromise. Each project delivered an average of 20% conversion growth, and some up to 45%.

One of our clients (an electronics online store) after implementing a custom review system saw a 32% conversion increase in two months.

Which social proof elements actually affect conversion?

The set of blocks depends on the business type, but a typical list includes:

• rating and reviews with stars and text;
• view and purchase counter — "This product purchased 127 times";
• recent purchase notifications — a popup without personal data;
• Q&A section on the product card;
• user photos (UGC gallery);
• badges like "Best Seller" or "Customer's Choice".

A custom approach outperforms ready-made modules: page load speed is 2 times faster, and configuration flexibility is unlimited. Out-of-the-box solutions are overloaded with unnecessary features and slow down due to poor caching. For example, one client switched from a module to a custom solution and reduced the product card load time from 3.2 to 1.1 seconds.

How do we design the reviews and rating architecture?

The built-in vote module in Bitrix is only suitable for simple voting. For a full-fledged system, we build custom tables:

CREATE TABLE b_product_reviews (
    ID          SERIAL PRIMARY KEY,
    PRODUCT_ID  INT NOT NULL,
    USER_ID     INT,
    AUTHOR_NAME VARCHAR(255),
    RATING      SMALLINT CHECK (RATING BETWEEN 1 AND 5),
    TITLE       VARCHAR(500),
    BODY        TEXT,
    PROS        TEXT,
    CONS        TEXT,
    STATUS      VARCHAR(20) DEFAULT 'pending',
    DATE_CREATE TIMESTAMP DEFAULT NOW(),
    HELPFUL_YES INT DEFAULT 0,
    HELPFUL_NO  INT DEFAULT 0
);
-- Review photos are stored in a separate table b_review_photos

The aggregated rating is cached in an infoblock property and updated via an event handler when a new review is approved. This eliminates computations on every request. In a project with 10,000 products, the load decreased by 60%.

Purchase counters and notifications without N+1

A direct query to b_sale_basket for each product creates an N+1 problem. The solution is a separate cache table that updates when an order is placed:

CREATE TABLE b_product_social_counters (
    PRODUCT_ID      INT PRIMARY KEY,
    PURCHASE_COUNT  INT DEFAULT 0,
    VIEW_COUNT      INT DEFAULT 0,
    WISHLIST_COUNT  INT DEFAULT 0,
    LAST_PURCHASED  TIMESTAMP
);

Update via the OnSaleOrderSaved event:

AddEventHandler('sale', 'OnSaleOrderSaved', function($event) {
    $order = $event->getParameter('ENTITY');
    foreach ($order->getBasket() as $item) {
        $productId = $item->getField('PRODUCT_ID');
        $db->query("UPDATE b_product_social_counters SET purchase_count = purchase_count + 1,
                    last_purchased = NOW() WHERE product_id = $productId");
    }
});

Recent purchase notifications are loaded via AJAX and displayed only when real data exists — fake numbers undermine trust. We set a 3–5 second delay and limit to 1 notification per 10 seconds per user.

UGC gallery and Schema.org markup

Customer photos are a powerful trust signal. Images uploaded via the review form are resized to 800px on the longer side, go through moderation, and are displayed in the gallery. For search results, we add Product + AggregateRating with JSON-LD:

$schema = [
    '@context' => 'https://schema.org',
    '@type'    => 'Product',
    'name'     => $arResult['NAME'],
    'aggregateRating' => [
        '@type'       => 'AggregateRating',
        'ratingValue' => $arResult['RATING'],
        'reviewCount' => $arResult['REVIEW_COUNT'],
        'bestRating'  => 5,
    ],
    'review' => array_map(fn($r) => [
        '@type'        => 'Review',
        'reviewRating' => ['@type' => 'Rating', 'ratingValue' => $r['RATING']],
        'author'       => ['@type' => 'Person', 'name' => $r['AUTHOR_NAME']],
        'reviewBody'   => $r['BODY'],
    ], $reviews),
];
echo '<script type="application/ld+json">' . json_encode($schema, JSON_UNESCAPED_UNICODE) . '</script>';

Data-driven badges

Badges like "Best Seller", "High Rating", or "Almost Out" are computed by an agent once per day and saved in an infoblock property. This approach doesn't load visits and guarantees up-to-date data. For a large catalog with 50,000 products, the agent runs in 4–6 minutes.

Why a custom solution is more effective than ready-made modules?

Comparison of approaches: marketplace module vs custom development

How to implement social proof step by step

1. Audit the current catalog. Determine load, database size, existing review mechanisms (if any).
2. Design the schema. Create tables for reviews, counters, photos. Optimize indexes.
3. Develop the module. Write 2.0 components, event handlers, agents.
4. Integrate markup. Add JSON-LD for Schema.org.
5. Testing. Conduct load testing simulating 1000 simultaneous users.
6. Deploy and monitor. Enable error logging, monitor performance.

Protecting reviews from manipulation

Without protection, both ratings and counters are manipulated. We implement: reviews only from verified purchasers, one review per product per user, rate limiting on the view counter API (max 10 requests per minute per IP), captcha or honeypot on forms. This ensures data authenticity and business peace of mind. In one project, after implementing protection, the number of fake reviews dropped from 200 per month to 0. Savings on advertising amounted to up to 800,000 rubles per month due to increased trust.

What's included in the work

• Documentation: storage architecture description, database schemas, caching logic.
• Access: to the review moderation admin panel, to social signal statistics.
• Training: instructions for content managers on moderation and editing.
• Support: 2 weeks of free maintenance after launch, fixing possible bugs.

Development timelines

Social proof is not a decoration, but part of the conversion funnel. Investment in proper implementation pays off through product card conversion growth, easily measurable via A/B test. On average, payback is under 3 months, and the average order value increases by up to 500 rubles. Get a consultation for your project — we will select the optimal set of blocks and calculate timelines. Contact us to discuss details.

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.