Why Standard 1C-Bitrix Notifications Fall Short?

\Bitrix\Main\Mail\Event::send() — the basic mechanism that handles emails after registration or order confirmation. But when the business demands push notifications, Telegram, WhatsApp, SMS — all with a unified delivery log, statuses, and retries — the built-in tool stops meeting the needs. According to official Bitrix documentation, the standard mail mechanism is not designed for more than 1000 emails per minute. As a result, up to 30% of critical alerts are lost, and debugging takes days. For example, on a project with a load of 8000 events per hour, we recorded 2000 SMTP errors per day.

Each new channel connects differently, logs are scattered, testing is complex. We specialize in developing custom notification modules for 1C-Bitrix that solve these problems centrally. Our module is designed for high-load projects and processes up to 100,000 notifications per day with guaranteed delivery of 99.5%.

How We Build the Module Architecture

The vendor.notifications module is built on the concepts of a channel and an event. An event is something that happens in the system. A channel is the delivery method. One event can be sent through multiple channels simultaneously. For data storage, we use four ORM tables optimized for high loads:

• b_vendor_notif_event — event types: id, code, name, description, default_channels (JSON), is_active
• b_vendor_notif_template — message templates: id, event_code, channel, subject, body, body_html, lang, variables_schema
• b_vendor_notif_queue — send queue: id, event_code, channel, recipient, payload (JSON), status (pending/sent/failed), attempts, created_at, sent_at, error
• b_vendor_notif_subscription — user subscriptions: id, user_id, event_code, channel, is_active

Each channel implements the ChannelInterface:

interface ChannelInterface
{
    public function getName(): string;
    public function send(Notification $notification): SendResult;
    public function supports(string $recipient): bool;
}

Implementations:

• EmailChannel — via \Bitrix\Main\Mail\Mail::send() with custom SMTP settings or through PHPMailer. Email via SMTP is 3-5 times faster and more reliable than the built-in mail().
• SmsChannel — adapters for different providers (SMS.ru, SMSC, Twilio): unified interface, provider is a configuration parameter.
• TelegramChannel — Telegram Bot API, sendMessage method, Markdown and inline buttons support.
• PushChannel — web push via Web Push Protocol (library web-push-php), subscriptions stored in b_vendor_notif_push_subscription. Web Push ensures delivery even with the browser closed.
• InternalChannel — internal notifications in the personal account, stored in b_vendor_notif_inbox, displayed on the site via AJAX.

How the Event Dispatcher and Async Queue Work

Sending a notification from code is one line:

\Vendor\Notifications\Dispatcher::dispatch('order_paid', [
    'user_id'      => $userId,
    'order_id'     => $orderId,
    'order_sum'    => $order->getPrice(),
    'order_number' => $order->getField('ACCOUNT_NUMBER'),
]);

The dispatcher determines which channels to use (based on event settings), produces messages from templates, substitutes variables, and puts tasks into b_vendor_notif_queue.

How Async Sending Improves Performance

Immediate sending at the moment of the event is bad practice: an HTTP request to Telegram might hang, blocking order saving. The queue is processed by a Bitrix agent. The async approach with retries reduces notification loss by 90% compared to synchronous sending (based on our measurements on projects with a load of 10,000 events/day).

// In the module installer
\CAgent::AddAgent(
    '\\Vendor\\Notifications\\QueueProcessor::run();',
    'vendor.notifications',
    'N',
    60, // every 60 seconds
);

public static function run(): string
{
    $items = NotifQueueTable::getList([
        'filter' => ['STATUS' => 'pending', '<=ATTEMPTS' => 3],
        'limit'  => 50,
        'order'  => ['CREATED_AT' => 'ASC'],
    ])->fetchAll();

    foreach ($items as $item) {
        $channel = ChannelRegistry::get($item['CHANNEL']);
        $result  = $channel->send(Notification::fromQueue($item));

        if ($result->isSuccess()) {
            NotifQueueTable::update($item['ID'], ['STATUS' => 'sent', 'SENT_AT' => new DateTime()]);
        } else {
            NotifQueueTable::update($item['ID'], [
                'ATTEMPTS' => $item['ATTEMPTS'] + 1,
                'STATUS'   => $item['ATTEMPTS'] >= 3 ? 'failed' : 'pending',
                'ERROR'    => $result->getError(),
            ]);
        }
    }

    return '\\Vendor\\Notifications\\QueueProcessor::run();';
}

After 3 failed attempts, the task is moved to failed status and appears in the dashboard for manual review. The log shows the reason for the error, simplifying debugging. When a delivery error occurs, the specific reason is displayed, for example: Telegram API returned 403 Forbidden: blocked by user or SMTP server is unreachable. The administrator can manually resend the notification or reset the attempt counter.

Managing User Subscriptions

In the personal account, the user sees a list of available events and can disable individual channels. Settings are stored in b_vendor_notif_subscription. The dispatcher checks before enqueuing whether the user has unsubscribed from that event type on that channel.

Why We Use Twig for Templates

The message body is generated using Twig. Variables are passed from the event payload. According to official Twig documentation, the template engine ensures strict isolation of templates from logic, increasing security when handling user content. Templates support filters: |price for amount formatting, |date for localized dates. HTML emails support inline styles via Emogrifier.

Administrative Interface

• List of events with default channel settings
• Template editor with preview (test variable substitution)
• Send log with filtering by status, channel, date, recipient
• Delivery statistics per channel
• Test notification sending to a specified address

What Is Included in Module Development

Development Timeline

Total: 14 working days. Adding extra channels (Viber, VK, WhatsApp Business API) — 1–2 days per channel. The cost is calculated individually based on complexity and number of channels. We will estimate your project in 1 day.

How to Add a New Notification Channel

1. Implement a class that implements ChannelInterface.
2. Register the channel in ChannelRegistry via the OnBuildChannels event.
3. Create a template for the new channel in the admin panel.
4. Configure default subscriptions for events.

Contact us — we will analyze your load and propose an architecture for your project. Order development and receive a ready-made module with full documentation and a month of support. Get a consultation on integration with your system — we will discuss details and timelines.

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.