Custom email module for 1C-Bitrix with queues and tracking

Standard email module in 1C-Bitrix starts failing with a database of over 10,000 contacts. Clients complain about missed emails—the default subscribe becomes a bottleneck. Without queues and tracking, scaling email marketing is impossible. Our team with 10 years of experience builds custom subscription and email modules turnkey: with queues, tracking, and flexible segmentation. Estimated development time—from 2 weeks. Contact us to discuss your project.

Why the standard subscribe module doesn't work for large mailings?

The standard module stores subscribers in the b_subscribe_subscr_addr table and email templates in b_subscribe_posting. Sending logic uses CAgent agents that run synchronously during HTTP requests. With over 10,000 contacts, this leads to timeouts and missed emails. Additionally: no built-in open tracking, no retry queue for SMTP errors, no support for transactional emails with dynamic content via API. In one project, we replaced the standard module with a custom one and reduced email marketing costs by 35% by abandoning expensive third-party services. The custom module processes 3 times more emails per unit time and reduces spam complaints by 5 times, ensuring up to 95% deliverability.

How does a custom module improve deliverability?

The module registers in the standard way via /bitrix/modules/vendor.mailer/install/index.php with the class vendor_mailer. Namespace is \Vendor\Mailer.

Key components

• SubscriberTable — ORM table b_vendor_mailer_subscriber (id, email, name, status, groups, created_at, unsubscribed_at)
• CampaignTable — b_vendor_mailer_campaign (id, name, subject, template_id, status, scheduled_at, sent_count, open_count)
• QueueTable — b_vendor_mailer_queue (id, campaign_id, subscriber_id, status, attempts, last_error, sent_at)
• EventTable — b_vendor_mailer_event (id, subscriber_id, type, payload, created_at) — open and click tracking

Tables are created via \Bitrix\Main\ORM\Data\DataManager with full D7-ORM support. For reliability, we use tagged cache for information blocks—this speeds up work with large data volumes.

// Enqueue when campaign starts
public function enqueue(int $campaignId): void
{
    $subscribers = SubscriberTable::getList([
        'filter' => ['=STATUS' => 'active', '=GROUPS' => $this->campaign->getGroups()],
        'select' => ['ID', 'EMAIL', 'NAME'],
    ]);

    while ($row = $subscribers->fetch()) {
        QueueTable::add([
            'CAMPAIGN_ID'   => $campaignId,
            'SUBSCRIBER_ID' => $row['ID'],
            'STATUS'        => 'pending',
            'ATTEMPTS'      => 0,
        ]);
    }
}

Transports: SMTP and API providers

Transport abstraction is implemented via MailTransportInterface:

interface MailTransportInterface
{
    public function send(Message $message): SendResult;
}

Concrete implementations: SmtpTransport (via PHPMailer or native mail()), SendGridTransport (REST API v3), MailgunTransport, AmazonSesTransport. The transport is selected in module settings (b_option, namespace vendor.mailer).

On send error, status changes to failed, attempts counter increments. When attempts >= 3, the record is marked as dead and not retried.

Open and click tracking

A transparent 1×1 pixel is inserted into the email:

<img src="https://site.ru/mailer/track/open/?uid=UNIQUE_TOKEN" width="1" height="1">

On GET request, the controller logs the event in b_vendor_mailer_event and returns a 1×1 GIF. Clicks are tracked via redirect: all links in the email are replaced with https://site.ru/mailer/track/click/?uid=TOKEN&url=ENCODED_URL.

Event handler:

EventTable::add([
    'SUBSCRIBER_ID' => $subscriberId,
    'CAMPAIGN_ID'   => $campaignId,
    'TYPE'          => 'open', // or 'click'
    'PAYLOAD'       => json_encode(['url' => $url, 'ip' => $_SERVER['REMOTE_ADDR']]),
    'CREATED_AT'    => new \Bitrix\Main\Type\DateTime(),
]);

Subscriber segmentation

Groups are stored in b_vendor_mailer_group, links to subscribers via b_vendor_mailer_subscriber_group. Segmentation supports conditions based on Bitrix user profile fields (b_user) via JOIN.

Dynamic segments are built using a filter builder in the admin interface—the same approach as in Bitrix CRM: a set of conditions with AND/OR operators that are translated into an ORM filter when enqueuing.

Transactional emails

For system emails (email confirmation, password reset, order notifications), the module provides an event API:

// Send transactional email
\Vendor\Mailer\Transactional::send('order_confirmed', [
    'USER_ID'    => $userId,
    'ORDER_ID'   => $orderId,
    'ORDER_SUM'  => $orderSum,
    'ITEMS'      => $orderItems,
]);

Transactional email templates are stored in b_vendor_mailer_template and editable via the admin section with support for variables like {{ORDER_ID}}.

Admin interface

The module adds sections in /bitrix/admin/:

• vendor_mailer_subscribers.php — subscriber list and management
• vendor_mailer_campaigns.php — campaigns, status, statistics
• vendor_mailer_templates.php — template editor
• vendor_mailer_settings.php — transport settings, DKIM, limits

The interface uses standard CAdminList, CAdminForm classes—full compatibility with the Bitrix theme.

Unsubscribe and GDPR

An unsubscribe link in every email leads to https://site.ru/mailer/unsubscribe/?token=TOKEN. On click, subscriber status changes to unsubscribed, and unsubscribed_at is filled. Re-enqueuing such records is blocked at the filter level.

For GDPR compliance: export subscriber data on request (GET /mailer/export-personal/?token=TOKEN), full deletion via SubscriberTable::delete() with cascading deletion from all related tables.

What is included?

• Documentation: architecture description, DB schema, installation manual.
• Module source code with license.
• Training: 2-hour webinar for administrators.
• Support: 30 days after launch (bug fixes, consultations).
• Compatibility guarantee with Bitrix 20.0+ and PHP 8.1+.

Comparison of standard and custom modules

Typical mistakes when developing an email module

• Ignoring queues—sending in a loop freezes the site. Always use an async queue.
• Lack of retries—if an email fails, must retry up to 3 times, otherwise you lose subscribers.
• No tracking—cannot evaluate campaign effectiveness. Build in statistics collection from the start.
• Rigid binding to one SMTP—if the provider goes down, mailing stops. Use failover transports.

Timeline and cost

Total: from 11 working days for a basic version. Connecting additional API providers (Mailchimp, UniSender) — +1 day each.

Development cost is calculated individually after analyzing your requirements. Order module development today. Get a consultation—we will help you choose the optimal solution.

For an in-depth understanding of Bitrix ORM, we recommend studying the official documentation. Also useful to read about SMTP protocol and REST API.

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.