Social Commerce on 1C-Bitrix: Reviews, Wishlists, Referrals

Your online store runs on 1C-Bitrix, but reviews are not verified, sharing doesn't convert, referrals are absent? A typical situation: the base platform provides reviews and vote components, but they are insufficient for real social commerce. Without verification, reviews lack trust; without wishlists, customers leave; without referrals, traffic is expensive. We extend Bitrix for social commerce tasks—turning your site into a platform where every customer works as a brand ambassador.

Why Verified Reviews Increase Conversion by 1.5x?

The built-in review module in Bitrix does not verify purchases or support photos. According to Wikipedia, users trust purchase-verified reviews 40% more. We extend the component: when adding a review, we check b_sale_order_basket for the PRODUCT_ID in completed orders of the current user. Photos are uploaded via \CFile::SaveFile(), sorting by usefulness via \Bitrix\Vote\VoteTable. As a result, conversion increases 1.5x compared to unverified reviews. Customer acquisition cost savings from trust reach 30%.

How a Referral Program Reduces Customer Acquisition Cost

A referral program generates low-cost traffic: you pay only for results. The user gets a unique link; when a referred customer makes a purchase, the referrer receives a 5% bonus of the order amount. Customer acquisition through referrals is 3x cheaper than contextual advertising. Payback occurs in 2–3 months at an average conversion rate of 10%.

// Генерация реферальной ссылки
$refCode = base64_encode($userId . '-' . crc32($userId . SITE_SECRET));
$refLink = 'https://' . SITE_SERVER_NAME . '/?ref=' . $refCode;

// Обработчик входящего трафика (в init.php или компоненте)
$refCode = $_GET['ref'] ?? null;
if ($refCode && !isset($_SESSION['ref_code'])) {
    $_SESSION['ref_code'] = $refCode;
    setcookie('ref_code', $refCode, time() + 86400 * 30, '/');
}

// При создании заказа — начисление бонуса рефереру
AddEventHandler('sale', 'OnSaleOrderSaved', function(\Bitrix\Sale\Order $order) {
    $refCode = $_COOKIE['ref_code'] ?? null;
    if ($refCode) {
        $referrerId = ReferralService::getUserIdByCode($refCode);
        if ($referrerId && $referrerId !== $order->getUserId()) {
            BonusService::credit($referrerId, $order->getPrice() * 0.05); // 5% от покупки
        }
    }
});

Bonuses can be accumulated and spent in the store. Integration with Bitrix24 via REST OAuth allows tracking in CRM.

Wishlists and Group Buying

We implement wishlists on custom tables. The user creates a wishlist and can make it public. The public link is indexed by search engines and becomes a viral channel: another user can add items from the wishlist to cart. In gifting categories, conversion increases 3x.

class WishlistService
{
    public static function addItem(int $userId, int $productId, ?string $wishlistName = null): void
    {
        $wishlistId = self::getOrCreateDefault($userId, $wishlistName);
        $exists = WishlistItemTable::getRow([
            'filter' => ['WISHLIST_ID' => $wishlistId, 'PRODUCT_ID' => $productId],
        ]);
        if (!$exists) {
            WishlistItemTable::add([
                'WISHLIST_ID' => $wishlistId,
                'PRODUCT_ID'  => $productId,
                'ADDED_AT'    => new \Bitrix\Main\Type\DateTime(),
            ]);
        }
    }

    public static function shareWishlist(int $wishlistId): string
    {
        $token = bin2hex(random_bytes(16));
        WishlistTable::update($wishlistId, ['SHARE_TOKEN' => $token, 'IS_PUBLIC' => 1]);
        return '/wishlist/shared/' . $token;
    }
}

Group buying: the user creates a group order; when the required number of participants is reached, the price drops. Tables bl_group_purchases and bl_group_purchase_members. When current_qty >= target_qty, an agent changes the status and sends notifications. Each participant pays their share at a reduced price—a separate order is created with a discount.

Open Graph and Social Sharing

We add "Share" buttons with AJAX event capture in bl_share_events. In the catalog.element template, we include Open Graph meta tags:

<meta property="og:title"       content="<?= htmlspecialchars($arResult['NAME']) ?>"/>
<meta property="og:description" content="<?= htmlspecialchars($arResult['PREVIEW_TEXT']) ?>"/>
<meta property="og:image"       content="https://<?= SITE_SERVER_NAME ?>/<?= \CFile::GetPath($arResult['PREVIEW_PICTURE']) ?>"/>
<meta property="og:price:amount"   content="<?= $arResult['CATALOG_PRICE_1']['PRICE'] ?>"/>
<meta property="og:price:currency" content="RUB"/>

Sharing with UTM tags provides sales attribution: we know which customer brought traffic.

Comparison of Social Commerce Mechanics

What's Included in the Work

• Full audit of your current database schema and components
• Design: table structure, event handlers, agents
• Development of modules with caching and tagged cache
• Integration with existing catalog, infoblocks, and HL-blocks
• Load testing (up to 1000 simultaneous users)
• API documentation and description of modifications
• Administrator training on system usage
• 1-year warranty on all code

Timeline Estimates

Accurate timeline is determined after analyzing your Bitrix environment. We work with PHP 8.1+, MySQL/MariaDB, and infoblocks v2.0.

How We Work

1. Analysis — study current functionality and business processes
2. Design — define architecture and module set
3. Development — write code using ORM, tagged caching, events
4. Testing — unit tests and load testing
5. Deployment — push to production server, configuration
6. Support — bug fixes and modifications during warranty period

We specialize in Bitrix for over 8 years and have completed 30+ projects with social modules. Our engineers are certified 1C-Bitrix developers.

Order turnkey development — get a consultation and accurate project estimate within one day. Contact us to discuss details and launch social mechanics that will increase your conversion and customer LTV.

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.