Setting Up a Loyalty Program in 1C-Bitrix: From Discounts to Points

Imagine an e‑commerce store on 1C-Bitrix with a catalog of several thousand products and an above-market average order value. Customers rarely return, purchase frequency stays below two times per year. Without a well‑designed motivation system, LTV growth is nearly impossible. You need not just a discount but a smart mechanic that retains buyers and encourages repeat orders.

We have been configuring loyalty programs in Bitrix for over 7 years. During this time we have delivered more than 50 projects: from simple cumulative discounts to multi‑level systems with bonus points and integration with professional loyalty platforms. Our approach is engineering‑driven, devoid of marketing templates. We rely on official documentation and proven patterns. For a deeper understanding of the principles, we recommend reading the article on loyalty programs on Wikipedia.

Why Built-in Tools Are Not Enough

Bitrix does not have a dedicated "loyalty program" module. The available functionality:

• User groups — different levels with prices and access rights.
• Cumulative discounts — automatic transfer between groups based on purchase total (field DISCOUNT_VALUE).
• Order discounts — condition "sum of previous orders" in the rule designer of the sale module.
• Coupons — personal promo codes.

For bonus points (accrual of N points per purchase, redemption on the next order) there is no built-in mechanism. A custom module or integration with an external loyalty system is required.

Approach Comparison

Custom development gives full control over logic but requires time. An external system is faster to integrate but locks you into a vendor. Our experience shows: for online stores with a monthly turnover of half a million rubles or more, a custom solution pays off.

How to Implement a Tier Program?

A three‑tier program (Basic / Silver / Gold) via user groups can be done in 1–2 days:

1. Create three groups with corresponding price groups.
2. Set up automatic transfer using the OnSaleOrderSaved event.
3. Display the current level and progress to the next in the personal account.

Data for progress calculation:

$userSaleData = \Bitrix\Sale\Internals\UserTable::getList([
    'filter' => ['=USER_ID' => $userId],
    'select' => ['DISCOUNT_VALUE'],
])->fetch();

$currentTotal = (float)$userSaleData['DISCOUNT_VALUE'];

For progress use purchase total, order count, or average check — depending on business logic. Show progress in the personal account using a custom template of the bitrix:sale.personal component.

How to Add Bonus Points?

If you need a points system, a custom module is unavoidable. Implementation includes:

• Creating your own table bonus_account with fields USER_ID, BALANCE.
• Handler for the OnSaleOrderSaved event — accruing points as a percentage of the order amount.
• Handler for OnSaleOrderStatusChange — deducting points when the order is cancelled.
• Cart component — a field for entering the number of points to redeem.

According to 1C-Bitrix documentation, the OnSaleOrderSaved event is triggered when an order is saved and can be used for custom logic.

Typical Implementation Mistakes

• Not handling deductions on order cancellation — points remain on the balance, going negative.
• Conflict with tagged caching — progress does not update in the personal account.
• Lack of points expiration filtering — points never expire, breaking the economy.

Integration with External Loyalty Systems

If bonus points are needed, we connect an external platform via REST API. Integration points:

• OnSaleOrderSaved — accruing points when an order is placed.
• OnSaleOrderStatusChange — accruing when the status changes to "paid".
• Cart component — adding a points deduction field.

Example for Mindbox: sending order data via REST API, retrieving the number of points, and storing them in the database. We support asynchronous processing through agents — no slowdown on checkout.

What Is Included in the Work

• Audit of the current site configuration and product catalog.
• Selection of loyalty mechanics considering 54-FZ and OFD.
• Development of a module or configuration of an off‑the‑shelf solution.
• Integration with payment systems and delivery services.
• Testing all scenarios (accrual, redemption, order cancellation).
• API documentation and administrator manual.
• Employee training on program operation.
• One month of post‑release support.

Timeline and Guarantees

Estimated timelines:

• Basic tier program — 1 to 2 business days.
• Program with bonus points without integration — 3 to 5 days.
• Full integration with an external system — 5 to 10 days.

Cost is calculated individually after an audit and clarification of requirements. We provide a 12‑month warranty on the code. Over 7 years of Bitrix experience — you get a predictable result. Contact us for a consultation — we will evaluate your project and propose the optimal architecture. Place an order and get first results within a week.

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.