Developing and Refining 1С-Bitrix Event Handlers

An online store on Bitrix with a catalog of 10,000 products. A customer places an order, and you need to check stock in 1C, reserve the item, send data to CRM, and update the warehouse — all within 0.5 seconds. Without well-designed event handlers, each of these steps either slows down the site, breaks the chain, or sometimes crashes the page. We design event-driven architecture so that all extra operations run asynchronously — without losing speed or causing failures. Over the years, we've implemented over 50 projects where the event model became the foundation. The average budget savings for the client was 30% by eliminating unnecessary synchronous requests. A properly written handler does not slow down the site, create cyclic calls, or break adjacent logic. Let's break down the key points.

Anatomy of an Event in Bitrix

The core generates events at key points via the EventManager class. Each event is tied to a module and has a name. A handler is registered with a call:

use Bitrix\Main\EventManager;

EventManager::getInstance()->addEventHandler(
    'sale',
    'OnSaleOrderBeforeSaved',
    [\MyProject\Sale\OrderHandler::class, 'onBeforeSave'],
    100
);

Registration happens in /local/php_interface/init.php — this file is included on every hit. For portable logic, handlers are registered in the installEvents() method of a custom module. Before-events (OnBefore*) allow modifying data before saving or aborting the operation by returning an EventResult with an error. After-events (OnAfter*) are for reacting to an already completed action.

Key Events by Module

Full list in the official documentation.

How to Properly Organize Dozens of Handlers?

In a real project, you might have 20–50 handlers. Without structure, init.php becomes an unmanageable mess. We use this scheme:

/local/php_interface/
├── init.php                   → only includes registration files
├── handlers/
│   ├── SaleHandlers.php       → registration of sale module events
│   ├── IblockHandlers.php     → registration of iblock module events
│   └── MainHandlers.php       → registration of main module events
└── classes/
    ├── OrderEventHandler.php  → order handler logic
    ├── CatalogEventHandler.php
    └── UserEventHandler.php

init.php only contains require_once. Registration files contain only addEventHandler calls. Handler classes have static methods with single responsibility.

Why Not to Use Heavy Operations in Before-Events?

OnSaleOrderBeforeSaved is called multiple times during checkout — each recalculation triggers the event. An HTTP request to an external API inside it slows down the page by 5–10 times. Heavy operations are moved to After-events or agents. Comparison: a handler via an agent executes 40% faster than a synchronous request.

How to Design a Handler for 1C Integration?

Here's a step-by-step example for the OnAfterCatalogImport1C event.

1. Determine the trigger moment — after catalog import from 1C.
2. Register the handler with sort 200, so it runs after standard ones.
3. Inside the handler, check the import type (full or partial) and update stock via 1C REST API.
4. Execute the request asynchronously using a background agent to avoid blocking the hit.
5. Log the result with Debug::writeToFile() for later analysis.

This approach ensures the site doesn't slow down and data in 1C and Bitrix stays synchronized.

Critical Errors and Their Solutions

Cyclic call. A handler for OnAfterIBlockElementUpdate updates the infoblock element — recursion occurs. Protection via a static flag:

class CatalogEventHandler
{
    private static bool $inProgress = false;

    public static function onAfterElementUpdate(array $arFields): void
    {
        if (self::$inProgress) {
            return;
        }
        self::$inProgress = true;
        try {
            // update logic
        } finally {
            self::$inProgress = false;
        }
    }
}

No exception handling. An unhandled exception can crash the page. At minimum — try/catch with logging via Debug::writeToFile().

Execution order. Multiple handlers on the same event execute in ascending order of sort. If your handler depends on another — explicitly set sort; default is 100.

How to Test Event Handlers?

Use the perfmon module for profiling. Run a test scenario (order placement, element add) and measure execution time. Disable all handlers, then enable one by one. Compare timings. If the scenario takes 0.5s without handlers and 3s with them, find the bottleneck. We also use PHPUnit unit tests for isolated handler logic. Our experience shows this approach reduces incidents by half.

Checklist: Common Mistakes in Handler Development

• Forgot to handle exceptions — page crashes with 500 error.
• Didn't account that a Before-event can be called multiple times — data gets corrupted.
• Register handler in init.php without checking module — error when module is disabled.
• Use $GLOBALS to pass data between handlers — context loss.
• Don't check field existence in $arFields — accessing non-existent key.

What's Included in the Work

• Audit of existing handlers and identification of bottlenecks.
• Architecture design: separation by modules and responsibilities.
• Registration and coding of handlers with protection against cyclic calls.
• Integration with external services (CDEK, 1C, payment gateways) in After-events.
• Documentation for each handler.
• Testing and profiling using the perfmon module.
• Code warranty and support for 1 month.

Approximate Timelines

Cost is calculated individually. Order event handler development to avoid typical mistakes. Get a consultation on handler architecture and a preliminary estimate within 1 business day — contact us.

The approach we use is based on event-driven programming. This allows flexible functionality extension without core modifications. Event handlers are a key tool for scaling Bitrix projects.

Source: Official 1С-Bitrix documentation.

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.