Configuring Discounts and Marketing Rules in Bitrix

Have you encountered uncontrolled stacking of discounts?

Typical scenario: three promotions sum up, giving 70% discount instead of expected 15%. Or a promo code triggers together with a general promotion, and the customer gets the product almost for free. In one project, incorrect LAST_DISCOUNT configuration led to significant losses. The root cause is incorrect priority and LAST_DISCOUNT flag setup. We configure rules so that each promotion applies strictly according to its conditions, and stacking control eliminates losses.

Our experience: 7+ years working with Bitrix, over 50 marketing configuration projects. According to the 1C-Bitrix documentation, LAST_DISCOUNT is a key mechanism to prevent multiple discount application. Additionally, we use custom OnSaleDiscountRuleAction events for non-standard mechanics. Proper configuration can save substantial revenue.

Why may promotions in Bitrix stack incorrectly?

The problem arises when several discount rules have the same priority and the 'Stop further processing' flag is not set. For example, a '10% off first order' promotion and a '5% off entire catalog' promotion apply together, giving 14.5% instead of 10%. The solution: set priority 100 for the main promotion and enable LAST_DISCOUNT. If stacking is desired, use joint application in settings. In complex cases, we add a check in the OnSaleDiscountCondition event to programmatically control applicability.

// event OnSaleDiscountCondition
class MyCondition extends \Bitrix\Sale\Discount\Condition\Base
{
    public static function getClassName()
    {
        return __CLASS__;
    }

    public static function getControlId()
    {
        return 'MyCondition';
    }

    public static function checkCondition(array $params, array $arOrder)
    {
        // Check if basket contains product from desired category
        $basket = $arOrder['BASKET_ITEMS'];
        foreach ($basket as $item) {
            if ($item['IBLOCK_SECTION_ID'] == 42) {
                return true;
            }
        }
        return false;
    }
}

How to distinguish a catalog discount from a marketing rule?

Catalog discounts (table b_catalog_discount) work at the product price level before the basket. Marketing rules (section 'Basket rules') operate in the basket, allowing gifts, shipping discounts, conditional chains. According to Wikipedia, catalog discounts are classic price discounts, while marketing rules are a more complex mechanism. Using marketing rules gives 30% more flexibility than catalog discounts because you can combine conditions and impose restrictions.

Creating a promotion via the builder

Store → Marketing → Discounts and promotions → Add:

1. Conditions — AND/OR builder:

   • Order total greater than X
   • Basket contains product from section N
   • User in group G
   • Promo code used

2. Actions:

   • Discount on order (percent, fixed)
   • Discount on basket items
   • Shipping discount
   • Add gift (product with zero price)

3. Application settings:

   • Priority
   • 'Stop further processing' — important for mutually exclusive promotions
   • Joint application with other discounts

Custom OnSaleDiscountRuleAction events allow implementing mechanics 2-3 times faster than creating a custom module. For example, we added a discount on the second product in the basket — it took 2 hours instead of a week of development.

Promo codes: common, unique, and user-specific

In promotion settings, enable coupon (Store → Marketing → Coupons). Coupon types:

Coupons are stored in b_sale_discount_coupon. When activated, the coupon is checked via \Bitrix\Sale\DiscountCouponsManager::add. If a promo code doesn't apply, check coupon activity, expiration date, and type — the issue is often in basket data caching.

What to do if promotions don't trigger?

First, check the error log in Store → Marketing → Discounts and promotions → Application report. If a promotion is not applied, ensure it is active and conditions match the basket. Also check the condition grouping: maybe an 'AND' condition instead of 'OR' is blocking execution. Enable debug mode in bitrix/php_interface/dbconn.php to view SQL queries: $DB->showSqlStat = true;. This helps find caching problems or incorrect relations.

What's included?

• Audit of current promotions and rules
• Design of discount application logic
• Implementation via builder or custom code
• Testing on a test order
• Documentation and staff training
• Support for one month after launch

Contact us for an audit of your marketing rules. Order a consultation to avoid losses from incorrect discounts. Setup of 3-5 standard promotions with promo codes — 3-5 hours. Complex mechanics with gifts and custom actions — 1-2 working days. Cost is calculated individually after analyzing the specification. Additionally, you get a guarantee on correct promotion operation for 30 days.

Get a detailed audit and optimization plan — just write to us.

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.