Unified Online and Offline Loyalty Program Setup in Bitrix

We've encountered this situation: a customer accumulated 500 bonuses on the website, comes to the store — the cashier doesn't see them. Or an in-store purchase doesn't accrue points on the online account. The gap between online and offline loyalty programs is not just a UX problem — it's a direct loss of repeat sales. We configure a unified loyalty system turnkey: integration of the site and cash registers, real-time bonus synchronization, full transparency for the customer.

How loyalty works in Bitrix

The sale module implements discount system through b_sale_user_discount (personal discounts) and bonus system through b_sale_discount (basket rules). A full-fledged loyalty program with accumulative points requires either a separate module or integration with an external system. Bitrix24 has a CRM module with bonuses (b_crm_loyalty_bonus_transaction), but for an online store without Bitrix24, either the marketingcrm module or a custom transaction table is more often used. Based on our experience, a custom implementation provides the greatest flexibility and reliability — you are not tied to the limitations of a typical module.

Bonus storage structure: tables and transactions

Minimum structure for a unified program:

CREATE TABLE bl_loyalty_account (
    id          SERIAL PRIMARY KEY,
    user_id     INT UNIQUE,           -- b_user.ID (online)
    card_number VARCHAR(20) UNIQUE,   -- card number for offline
    balance     NUMERIC(10,2) DEFAULT 0,
    created_at  TIMESTAMP DEFAULT NOW()
);

CREATE TABLE bl_loyalty_transaction (
    id          SERIAL PRIMARY KEY,
    account_id  INT NOT NULL REFERENCES bl_loyalty_account(id),
    amount      NUMERIC(10,2) NOT NULL,  -- positive=accrual, negative=deduction
    type        VARCHAR(20) NOT NULL,    -- 'earn_online', 'earn_offline', 'spend', 'expire'
    order_id    INT,                     -- b_sale_order.ID or external offline receipt ID
    source      VARCHAR(20) NOT NULL,    -- 'web', 'pos', 'mobile'
    created_at  TIMESTAMP DEFAULT NOW()
);

A transactional model with history is the only reliable way to store bonuses. Never update balance directly without recording a transaction. balance is either a denormalized aggregate (updated by a DB trigger) or calculated as SUM(amount) from the transaction table. The latter approach is safer but slower under frequent balance queries.

How to identify a customer at an offline cash register?

The key task: the cashier must find the customer account. Identification methods:

• Loyalty card number (physical card or barcode in a mobile app)
• Phone number (most common)
• QR code with token (generated in personal account on the site)

When identifying by phone, the cash register software sends a request to the Bitrix API:

// /local/ajax/loyalty/find-account.php
$phone     = normalizePhone($_POST['phone']);
$bitrixUser = \CUser::GetList([], ['PERSONAL_PHONE' => $phone])->Fetch();

if ($bitrixUser) {
    $account = getLoyaltyAccount($bitrixUser['ID']);
    echo json_encode(['balance' => $account['balance'], 'account_id' => $account['id']]);
}

Bonus accrual on online orders

Handler for order status change — after delivery/completion:

AddEventHandler('sale', 'OnSaleStatusOrderChange', function(\Bitrix\Main\Event $event) {
    $order  = $event->getParameter('ENTITY');
    $status = $order->getField('STATUS_ID');

    if ($status !== 'F') return; // Only completed orders

    $userId = $order->getUserId();
    $bonus  = round($order->getPrice() * BONUS_RATE); // BONUS_RATE = 0.05 (5%)

    addLoyaltyTransaction($userId, $bonus, 'earn_online', $order->getId(), 'web');
});

Bonus deduction on online payment

Bonuses are applied through a basket rule or a custom payment method. A basket rule (b_sale_discount) can give a fixed amount discount. For a more flexible scheme — a custom "payment method" like "Pay with bonuses", which when the order is completed deducts a transaction from bl_loyalty_transaction.

Why transactional deduction is critically important?

An offline cash register calls three endpoints:

1. GET /loyalty/balance?phone=... — check balance
2. POST /loyalty/spend — deduct bonuses at sale (must be transactional: start sale → reservation → confirmation)
3. POST /loyalty/earn — accrue bonuses after sale

Reservation during deduction is a critical step. Without it, two parallel requests from different cash registers could simultaneously read a balance of 500 bonuses and each deduct 500, going negative. Reservation via SELECT ... FOR UPDATE in PostgreSQL or through a strict UPDATE with result check:

UPDATE bl_loyalty_account
SET balance = balance - :amount
WHERE id = :account_id AND balance >= :amount
RETURNING balance;
-- If 0 rows updated — insufficient bonuses

This approach is more reliable than using application-level locks.

Approach comparison: custom table vs Bitrix module

A custom table loses to modules in implementation speed, but is 2-3 times more reliable under high loads and non-standard business logic.

What's included in the work

• Designing table structures bl_loyalty_account and bl_loyalty_transaction
• Developing a REST API for cash register systems (balance, accrual, deduction)
• Creating event handlers OnSaleStatusOrderChange for online accruals
• Customer identification mechanism by phone/card
• Transactional deduction with race condition protection
• Administrative interface for viewing and canceling transactions
• API documentation and cashier instructions
• Testing and 30-day warranty

Timelines and budget

Setting up a unified loyalty program takes from 5 to 15 working days depending on complexity (number of cash registers, need for integration with 1C, reporting requirements). Cost is calculated individually after an audit of the current system. We'll assess your project in 1 day.

Common mistakes in setup

• Updating balance directly without a transaction — data loss on failure.
• Lack of locks during deduction — double deduction.
• Ignoring API logging — difficult to debug.
• Using only the marketingcrm module for offline — does not support reservation.

Avoiding these mistakes requires experience — we have implemented over 30 loyalty projects on Bitrix, including chains with 50+ cash registers.

Contact us for a consultation: we'll tell you how to unite online and offline loyalty in your business.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.