Developing D7 API Classes for 1C-Bitrix — Modern Approach

We integrate D7 API into Bitrix projects, creating classes with namespaces instead of global functions, Result objects instead of bool and error strings, and using Application as the entry point instead of global variables. Such code doesn't break on updates, is easily testable and reusable. Our experience: over 5 years working with Bitrix, over 30 projects fully migrated to D7. Get your project assessed — contact us!

Problems We Solve

Typical pains: legacy code using CModule and $_POST breaks on updates, can't be covered by tests, errors are lost (return false without context), and cache is invalidated only by time. D7 API solves this through strict typing, exceptions, and tagged cache. As a result, production errors decrease by 2–3 times, and time to deploy new features is reduced by 40%.

Why Migrate to D7 API?

Migrating to D7 API is not a trend but a necessity for projects that live longer than a year. Instead of CIBlockElement::GetList() with a ton of parameters, you get ORM queries with method chains. Instead of $_POST['field'] — a Request object with typed access. Your code becomes predictable and documented. Let's compare legacy and D7 code volume: for 1000 lines of legacy, D7 takes about 800 lines, but D7 code is 60% easier to maintain.

How We Develop D7 Classes

Let's take a real case: an e-commerce store on Bitrix with 50,000 products. The old basket code worked via CSaleBasket::Add and was scattered across templates. We rewrote it into a BasketService service class with D7:

namespace MyProject\Services;

use Bitrix\Main\Result;
use Bitrix\Main\Error;
use Bitrix\Sale\Basket;

class BasketService
{
    public function __construct(
        private readonly int $userId
    ) {}

    public function addItem(int $productId, int $quantity): Result
    {
        $result = new Result();
        $basket = Basket::loadItemsForUser($this->userId);
        if (!$basket) {
            $result->addError(new Error('Failed to load basket', 'BASKET_LOAD_FAIL'));
            return $result;
        }
        $item = $basket->createItem('catalog', $productId);
        $item->setFields(['QUANTITY' => $quantity]);
        $saveResult = $basket->save();
        if (!$saveResult->isSuccess()) {
            $result->addErrors($saveResult->getErrors());
        }
        return $result;
    }
}

Now the basket is fully covered by unit tests, and when Bitrix updates, you only need to replace one class, not rewrite all templates. This reduced update time from 3 days to 2 hours.

How D7 API Improves Caching

Tagged caching is one of D7's strong points. Instead of global cache flush by time, you invalidate only the data that changed. For example, when a product price is updated, only that product's cache is flushed, not the entire catalog. This reduces database load by 30–50%.

Architectural Patterns: Factories and Repositories

For complex logic, we use factories to create objects and repositories to work with storage. For example, an order factory creates Order instances with pre-filled dependencies, and a product repository encapsulates ORM queries with tagged cache. This approach isolates business logic from infrastructure and makes it easy to swap implementations during testing.

Our Process

1. Audit current code — identify places using legacy API.
2. Design architecture — define services, repositories, factories.
3. Implement classes — write code with Result, Application, tagged cache.
4. Write unit tests — cover critical scenarios.
5. Integration and deployment — replace old modules piece by piece, maintaining backward compatibility.

What's Included

• Full set of D7 classes (services, repositories, factories, Result objects)
• API documentation in PHPDoc
• Unit tests (on request)
• Adaptation of existing code to work with new classes
• Installation and maintenance instructions

D7 API vs Legacy API

Timelines

Code on D7 API lives long. It can be updated piece by piece, tested, and reused. Order turnkey D7 class development — we'll assess your project in one day. Guaranteed compatibility with latest Bitrix versions.

Learn more about D7 API in the official documentation and Wikipedia on PHP namespaces.

Contact us for a consultation — we'll help with the migration to D7. Get a commercial proposal and cost estimate within a day.

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.