Custom 1C-Bitrix Modules: Architecture, ORM, Events, Marketplace

Custom 1C-Bitrix Modules: Architecture, ORM, Events, Marketplace

Made a mistake—modified the core? After an update everything broke, and a year later nobody remembers what was changed or why. A familiar situation? A custom module solves this problem once and for all. We develop modules that never touch the core, are easy to update, and are thoroughly documented. Our experience: over 10 years of 1C-Bitrix development, dozens of successful projects across various industries.

Support cost reduction can reach 40%, and investment in a module pays back in 3–6 months. We guarantee quality and deadline compliance. Contact us to evaluate your project—we will prepare a commercial proposal.

Why avoid core modifications?

A custom module is not just a set of files. It is an architectural solution that must be resilient to updates, maintainable, and secure. Direct SQL queries in code are an outdated approach. Bitrix D7 ORM is better in terms of security and flexibility: it prevents SQL injections and makes data structure changes easy. We use modern patterns: Repository, Service, Event-driven. Certified specialists with experience writing modules for Marketplace ensure your module passes moderation and works stably.

How is the module architecture structured?

A 1C-Bitrix module is a directory in /bitrix/modules/<vendor>.<modulename>/ with a strictly defined structure. Bitrix uses the naming convention <vendor>.<name>, where vendor is the developer's short name.

vendor.modulename/
├── install/
│   ├── index.php          # Installer class (extends CModule)
│   ├── db/
│   │   └── mysql/
│   │       ├── install.sql   # SQL to create tables
│   │       └── uninstall.sql # SQL to drop tables
│   └── files/             # Files copied during installation
│       └── bitrix/
│           └── components/
├── lib/                   # Classes in namespace Vendor\Modulename\
│   ├── Repository.php
│   ├── Service.php
│   └── Orm/
│       └── EntityTable.php  # ORM entity (D7)
├── lang/
│   ├── ru/
│   │   └── install/
│   │       └── index.php    # Language labels
│   └── en/
├── options.php            # Module settings page
└── include.php            # Included via \Bitrix\Main\Loader::includeModule()

How does ORM D7 work in a module?

Modern modules use Bitrix D7 ORM instead of direct SQL queries. The table class is declared by inheriting from \Bitrix\Main\ORM\Data\DataManager:

namespace Vendor\Modulename\Orm;

use Bitrix\Main\ORM\Data\DataManager;
use Bitrix\Main\ORM\Fields\{IntegerField, StringField, DatetimeField, BooleanField};

class RequestTable extends DataManager
{
    public static function getTableName(): string
    {
        return 'vendor_modulename_requests';
    }

    public static function getMap(): array
    {
        return [
            new IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new StringField('NAME', ['required' => true, 'size' => 255]),
            new StringField('EMAIL', ['size' => 255]),
            new BooleanField('ACTIVE', ['default_value' => true]),
            new DatetimeField('CREATED_AT'),
        ];
    }
}

Usage:

// Get records
$result = RequestTable::getList([
    'filter' => ['ACTIVE' => true],
    'select' => ['ID', 'NAME', 'EMAIL'],
    'order'  => ['CREATED_AT' => 'DESC'],
]);

// Add a record
RequestTable::add(['NAME' => 'Test', 'EMAIL' => '[email protected]']);

ORM D7 automatically escapes values, preventing SQL injections, and supports tagged caching. This is important for high-load catalogs.

Events and their registration

A module can subscribe to platform events and generate its own. Registration of an event handler:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale',                    // module
    'OnSaleOrderBeforeSaved',  // event
    ['\Vendor\Modulename\EventHandlers', 'onOrderBeforeSaved']
);

Generating a custom event for extensibility:

$event = new \Bitrix\Main\Event('vendor.modulename', 'OnRequestAdded', ['REQUEST' => $request]);
$event->send();

Events allow integrating the module with other systems without changing core code. For example, you can subscribe to an order added event and send data to 1C via CommerceML.

How does module installation work?

The installation process includes several steps:

1. Copy the module to /bitrix/modules/<vendor>.<name>/.
2. Go to admin panel → "Marketplace" → "Installed Solutions".
3. Click "Install". The system runs the installer script (creates tables, copies files).
4. Configure access rights and module parameters via options.php.

Administrative interface

The section in the admin panel is registered via a menu item (/bitrix/menu.php or automatically through the menu.php file in the module folder). Admin section pages reside in /bitrix/admin/vendor_modulename_*.php. For modern projects, the admin interface is implemented as an Inertia/React SPA or as classic Bitrix admin pages using CAdminList, CAdminForm.

Versioning and Marketplace

A module can be distributed through 1C-Bitrix Marketplace. Publication requires: error-free code, language files for ru/en, documentation, compatibility with current PHP and platform versions.

Development process

Estimated timelines

What's included in development?

Within the project, we provide:

• Architectural documentation (ER-diagrams, API description).
• Source code with comments and PHPDoc.
• Language files for ru/en.
• Access to the repository and task management system.
• Administrator training on module operation.
• Warranty support (bug fixes) for 1 month.

Typical mistakes during development and installation

• Incorrect permissions on the module folder (must be 755).
• Missing required dependencies (e.g., sale module).
• Errors in SQL scripts—duplicate indexes.
• Forgot to add an agent for background tasks.

Agents are another powerful mechanism: you can schedule code execution. This is useful for synchronization with external services or cleaning up outdated data.

Get a consultation—we'll show you how to solve your task optimally and save your budget. Learn more about the platform on the official 1C-Bitrix site.

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.