Custom 1C-Bitrix Loyalty Module: Development, Levels, Points & Pricing

We integrate a loyalty program into 1C-Bitrix as a separate module when standard bonuses no longer suffice. The built-in field b_user.UF_BONUS_POINTS is just a number without history, without expiration, and without order association. When a client requests an accrual system with levels, transaction history, and partial payment with points, we build it from scratch. Over the past 5 years, we have implemented more than 50 such projects, and the architecture is repeatable yet adaptable to specific business needs. A Loyalty program is not just points; it's an ecosystem for customer retention.

Why Standard Bitrix Bonuses Are Not Suitable?

The standard approach using user fields does not scale. With 10,000 customers, problems arise: slow queries, data loss during failures, and inability to generate accrual reports. Our solution uses separate ORM tables, providing performance and reliability. Compare: the standard field stores a single number—the current balance. Our module stores every transaction, allowing history recovery and correct FIFO point redemption. Based on our measurements, the module processes transactions 50 times faster than the standard user field approach under a load of 10,000 operations per day.

How We Build the Data Model

The module vendor.loyalty includes four main tables:

• b_vendor_loyalty_account — loyalty account: id, user_id, balance, total_earned, level_id, created_at
• b_vendor_loyalty_transaction — transactions: id, account_id, type (earn/spend/expire/cancel/manual), amount, order_id, description, expires_at, created_at
• b_vendor_loyalty_level — levels: id, name, min_points, earn_multiplier, privileges (JSON), icon_id
• b_vendor_loyalty_rule — accrual rules: id, event_type, points_type, points_value, conditions (JSON), is_active

This structure allows easy addition of new accrual types (for registration, review, birthday) and management through the administrative interface.

Point Accrual Mechanism

Accrual is tied to Bitrix events. For orders, we use OnSaleOrderPaid:

AddEventHandler('sale', 'OnSaleOrderPaid', ['\Vendor\Loyalty\EventHandler', 'onOrderPaid']);

public static function onOrderPaid(\Bitrix\Main\Event $event): void
{
    $orderId = $event->getParameter('id');
    $order   = \Bitrix\Sale\Order::load($orderId);
    $userId  = $order->getUserId();

    $account = AccountTable::getByUserId($userId);
    $level   = LevelTable::getById($account['LEVEL_ID']);

    // Earn % of order amount considering level multiplier
    $basePoints  = floor($order->getPrice() * 0.05); // 5% base
    $earnedPoints = floor($basePoints * $level['EARN_MULTIPLIER']);

    TransactionTable::add([
        'ACCOUNT_ID'  => $account['ID'],
        'TYPE'        => 'earn',
        'AMOUNT'      => $earnedPoints,
        'ORDER_ID'    => $orderId,
        'EXPIRES_AT'  => (new DateTime())->add(new DateInterval('P1Y')), // lifetime 1 year
        'DESCRIPTION' => "Accrual for order №{$order->getField('ACCOUNT_NUMBER')}",
    ]);

    AccountTable::update($account['ID'], [
        'BALANCE'       => $account['BALANCE'] + $earnedPoints,
        'TOTAL_EARNED'  => $account['TOTAL_EARNED'] + $earnedPoints,
    ]);

    // Check level upgrade
    LevelUpgradeService::check($account['ID']);
}

Per 1C-Bitrix documentation, the event OnSaleOrderPaid is called after order payment. We use it as the entry point for point accrual.

After accrual, an agent checks whether the user's level should be upgraded. If the total earned points exceed the threshold, the level is automatically promoted.

Point Expiration Handling

Each accrual transaction has an expiration date. An agent running nightly writes off expired points:

$expired = TransactionTable::getList([
    'filter' => ['TYPE' => 'earn', '<=EXPIRES_AT' => new DateTime(), '>AMOUNT' => 0],
])->fetchAll();

foreach ($expired as $tx) {
    TransactionTable::add(['TYPE' => 'expire', 'AMOUNT' => -$tx['REMAINING'], ...]);
    AccountTable::update($account['ID'], ['BALANCE' => $account['BALANCE'] - $tx['REMAINING']]);
}

The user sees upcoming expiration dates in their personal account and can use points before they expire.

Implementing Payment with Points

Partial payment with points works via a custom payment system (PaySystem):

public function processRequest(Payment $payment, Request $request): ProcessRequestResult
{
    $pointsToSpend = (int)$request->get('loyalty_points');
    $account       = AccountTable::getByUserId($payment->getOrder()->getUserId());

    if ($account['BALANCE'] < $pointsToSpend) {
        return ProcessRequestResult::error('Insufficient points');
    }

    // 1 point = 1 ruble (configurable in module)
    $discountAmount = $pointsToSpend / (int)Option::get('vendor.loyalty', 'points_rate', 1);
    $discountAmount = min($discountAmount, $payment->getSum() * 0.5); // max 50% of order

    // Write off points and create discount on order
    TransactionTable::add(['TYPE' => 'spend', 'AMOUNT' => -$pointsToSpend, ...]);
    AccountTable::update($account['ID'], ['BALANCE' => $account['BALANCE'] - $pointsToSpend]);

    return ProcessRequestResult::success();
}

The 50% order limit protects against abuse. The percentage is adjustable in the admin panel.

Level Structure

Levels are upgraded based on total earned points. Upon upgrade, the accrual multiplier and privileges (free shipping, priority support) are activated. Level table:

Thresholds and multipliers are configurable through the administrative interface. The module automatically upgrades the level when the threshold is reached.

What's Included in Module Development

We provide a complete package with clear deliverables:

• ORM model and database migrations
• Event handlers for point accrual
• Agents for expired point write-off
• Payment system for point redemption during order
• User personal account (balance, history, levels)
• Administrative interface for managing levels and rules
• Source code with documentation
• Git repository access
• 2-hour online training for administrators
• 1 month free support after launch
• Consultation for integration with 1C or other systems

Development Timeline

Total: 12 business days. Integration with offline POS or CRM for accruing points for purchases outside the website is estimated separately.

Contact us to evaluate your project. Get a consultation on integrating the loyalty module. Budget savings can be up to 30% compared to developing similar functionality yourself.

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.