1C-Bitrix Price Rules Module Development

Imagine: a manager wants to set a promotion "15% off all brand X items for customers from Moscow whose order sum over the last 30 days exceeds 10,000 rubles, but only if the cart contains no items from category Y." The built-in Bitrix discount module (sale) handles straightforward cases, but combined conditions involving order history or regional logic either require hacky code in the cart template or a separate module. We specialize in building such modules turnkey—this avoids bulky core modifications and preserves compatibility with system updates.

Why the built-in discount module falls short

Built-in discounts in sale operate through the b_discount table and predefined condition types: user group, order total, product set. The OnGetDiscountConditionTypes event allows adding custom conditions, but its capabilities are limited—you cannot flexibly combine conditions or add order history dependencies through standard means. Moreover, performance suffers: with 5–10 rules, a query to b_discount_condition can take 0.2–0.5 seconds per check, and with 50 rules up to 2 seconds, critical for high-load stores. In the 1C-Bitrix documentation, the event is described as an extension point but does not guarantee performance for complex chains.

Features of the Price Rules Module

Our custom module is built on top of sale, without touching the core—a key decision that ensures compatibility with 1C synchronization and third-party integrations. We use tagged caching for conditions to minimize database load. For example, a basic module costs from $2,500 and can save up to $15,000 annually, with payback in under six months.

The rules engine stores configurations in its own table myvendor_price_rules. Each rule is a JSON structure with conditions and actions:

{
  "conditions": [
    {"type": "user_group", "value": [5, 8]},
    {"type": "region", "value": ["RU-MOW"]},
    {"type": "order_history_sum", "period_days": 30, "min_sum": 10000}
  ],
  "condition_operator": "AND",
  "actions": [
    {"type": "percent_discount", "value": 15, "target": "brand_X_items"}
  ],
  "priority": 100,
  "stackable": false
}

The condition evaluator is a set of strategy classes implementing ConditionInterface::check(). Conditions requiring database queries (order history) are cached within a single request using a static array.

Detailed: order history condition

This is the most expensive condition. Without optimization, an aggregation query on b_sale_order over 30 days can be slow. We use this approach:

$cacheKey = "order_history_{$userId}";
if (!isset($_SESSION['price_rules_cache'][$cacheKey])) {
    $sum = \Bitrix\Sale\OrderTable::getList([
        'filter' => [
            '=USER_ID'      => $userId,
            '>=DATE_INSERT' => (new \Bitrix\Main\Type\DateTime())->add('-30D'),
            '=CANCELED'     => 'N',
        ],
        'runtime' => [
            new \Bitrix\Main\Entity\ExpressionField('TOTAL', 'SUM(%s)', 'PRICE'),
        ],
    ])->fetch()['TOTAL'] ?? 0;
    $_SESSION['price_rules_cache'][$cacheKey] = (float)$sum;
}

Excluding conditions (block when a category Y item is present) are implemented via a separate ExclusionCondition type.

How to ensure performance with many rules?

The key element is tagged caching of check results for each rule. We also introduce priorities: rules with simple conditions (e.g., by group) are checked first to eliminate most buyers before heavy queries. As a result, even with 100+ rules, cart check time does not exceed 0.3 seconds. More about caching in 1C-Bitrix can be found in the official documentation.

Deliverables

Each project includes the following deliverables:

1. Analysis of current discounts in b_discount and import of existing rules.
2. Design of condition and action architecture (up to 10 types in the basic version).
3. Module implementation with tagged caching and event handlers.
4. Integration with the cart via OnSaleOrderBeforeSaved and OnBeforeBasketAdd events.
5. Administrative interface: visual rule constructor, applicability preview, history of firings.
6. Full documentation (user guide, API reference, technical specification) and manager training session.
7. Access to complete source code (Git repository).
8. 3 months of technical support and module warranty.

Performance comparison

Our module processes rules up to 5 times faster than the standard one due to session-level caching and lightweight queries.

Development timeline and cost

The cost of module development is calculated individually, depending on complexity and required functionality. Automation of manual promotions can save up to $15,000 annually, with payback period less than six months.

Before starting, we conduct an audit of your current discounts—often importing existing rules takes longer than expected. We also evaluate database performance and help optimize indexes.

We have 10 years of experience in 1C-Bitrix development and over 50 successful projects in this field. Contact us for a free consultation and get an estimate for your project. Order the development of a price rules module—we will help implement any promotional logic.

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.