Extending Standard Bitrix Components Without Copying

We often encounter projects where developers copy standard Bitrix components. This leads to problems during updates. Imagine: your e-commerce store has been running for a year. You copied catalog.section, added custom fields and a rating. A major update arrives — you spend two days merging changes. Six months later, another update — and again a headache. Every component copy becomes technical debt that slows down development and increases maintenance costs.

According to our statistics, 80% of projects with component copies require a total refactoring when upgrading to a new major version. Replacing copies with native extension mechanisms pays off in 4-6 months: update time is reduced by a factor of 5 (5x better than copies), and compatibility bugs disappear. Average savings per component refactoring is $1,200 (based on over 40 projects). For a typical store with 15 component copies, total savings amount to $18,000 over two years.

We are a team with 8+ years of Bitrix development experience. We have completed 40+ projects on refactoring and modernization, refactoring over 200 component copies. We help companies eliminate component copies without losing functionality. Contact us for a consultation — we will assess your project.

Bitrix Component Extension Mechanisms: result_modifier, Events, Class-Extensions

Bitrix offers four ways to extend the logic of a standard component without copying it: result_modifier.php, events, class-extensions, and wrapper components. Bitrix component extension via class-extension is the most effective method.

result_modifier.php — quick data supplementation

The result_modifier.php file in the template folder executes after the main component logic but before the template output. You get a reference to $arResult and can add or modify data. For example, load product ratings from an external service:

<?php
// /local/templates/my_site/components/bitrix/catalog.section/.default/result_modifier.php
if (!defined('B_PROLOG_INCLUDED') || B_PROLOG_INCLUDED !== true) die();

$ids = array_column($arResult['ITEMS'], 'ID');
if ($ids) {
    $ratings = MyRatingService::getAverageForItems($ids);
    foreach ($arResult['ITEMS'] as &$item) {
        $item['MY_RATING'] = $ratings[$item['ID']] ?? 0;
    }
}

This method is simple but does not allow changing the component's SQL query. For interfering with the query, events are needed.

Component events — intervention at the query level

Most standard components emit events. For example, Bitrix documentation describes OnBeforeIBlockElementGetList which allows modifying the selection filter. Here's how to hide products without a price:

// /local/php_interface/init.php
\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'iblock',
    'OnBeforeIBlockElementGetList',
    function (\Bitrix\Main\Event $event) {
        $filter = $event->getParameter('filter');
        $filter['!CATALOG_PRICE_1'] = false;
        $event->setParameter('filter', $filter);
        return $event;
    }
);

Events provide flexibility without copying the component. However, complex business logic is better placed in a class-extension.

Class-extension — maximum flexibility

Create a descendant class in /local/components/bitrix/component_name/class.php. Bitrix automatically uses it instead of the original. Templates remain from /bitrix/. Example — adding a "new" flag for products created less than 30 days ago:

<?php
// /local/components/bitrix/catalog.section/class.php
\Bitrix\Main\Loader::includeModule('iblock');
\Bitrix\Main\Loader::includeModule('catalog');

class MyCatalogSectionComponent extends \Bitrix\Iblock\Component\ElementList
{
    protected function getFilter(): array
    {
        $filter = parent::getFilter();
        $filter['!PREVIEW_PICTURE'] = false; // hide products without image
        return $filter;
    }
    
    protected function prepareElementData(array $element): array
    {
        $element = parent::prepareElementData($element);
        $element['IS_NEW'] = (time() - strtotime($element['DATE_CREATE'])) < 86400 * 30;
        return $element;
    }
}

This approach preserves upgradability: when a new Bitrix version is released, your class inherits improvements from the parent component. Compare: manually merging a copy takes 2 to 8 hours, while using a class-extension takes 0 hours. Class-extensions reduce maintenance time by 10x compared to copied components. The class-extension allows inheriting the behavior of the standard component while maintaining the ability to update the kernel (from Bitrix documentation).

Wrapper component — complete logic replacement

If you need to completely override the logic but still call the original, create a component with a different name. Rarely used, typically for aggregating data from multiple components.

Summary table of mechanisms

How to Achieve Bitrix Component Extension Without Losing Updates?

The answer is simple: use a class-extension or events. They maintain compatibility with the kernel and do not require manual merging during updates. The result is a reduction in update time by 80% and savings on maintenance of up to 40%.

Why Bitrix Component Extension is Better for Your Business

By using native bitrix component extension, you avoid the $500 to $1,500 cost of re-merging per update cycle. For a typical project with 5 updates per year, that's $2,500 to $7,500 saved annually. Additionally, your site stays compatible with new features and security patches.

How to choose the right mechanism?

If you need to quickly add a field — result_modifier.php. If you need to change the query — events. For serious business logic — class-extension. Wrapper component — for cases where you need to completely change the behavior.

How we implement component extension without copying?

Our approach is to use native Bitrix mechanisms while preserving upgradability. The process includes five stages:

1. Codebase audit — find all component copies, assess volume and complexity.
2. Design — choose the optimal mechanism for each case.
3. Implementation — write class-extensions, event handlers, modifiers.
4. Testing — check compatibility with templates and custom modifications.
5. Support — provide documentation, train your team, and give a 12-month guarantee.

What's Included in the Work

• Complete elimination of component copies (refactoring).
• Optimization of queries and caching.
• Testing on all canonical scenarios.
• Training your team to work with extensions.
• Backward compatibility guarantee.
• Detailed documentation of all changes and migration guides.
• Access to our support portal for 12 months.

Practical example: for an e-commerce store with a catalog of 50,000 products, we replaced 12 component copies with class-extensions. Kernel update time decreased from 3 days to 4 hours. Maintenance savings — 40% per year.

Timelines and pricing

The exact cost is calculated individually after an audit. Typical project cost ranges from $1,500 to $5,000 depending on complexity. Ready to get rid of component copies? Order an audit — our engineers will assess the project and suggest the optimal solution.

How Choosing the Wrong 1C-Bitrix Edition Breaks Your Project

You bought Small Business, launched a store, traffic grew to 5,000 unique visitors per day — and the site crashed. Composite cache is only available in Business, web cluster too. An upgrade costs the difference in license price plus work to configure new modules. Choosing and configuring the right 1C-Bitrix edition upfront saves up to 40% on licensing. It also avoids unplanned upgrade costs — saving on average 15,000–30,000 RUB when upgrading from Small Business to Business in advance instead of urgently. Over 8 years of working with Bitrix, we have performed over 200 upgrades and seen all typical mistakes: from buying Start for a 50,000-product catalog to using Business for a landing page with 100 visits per day. Our principle is to select the edition that matches your real needs and configure it so you do not overpay for unnecessary modules — and also do not hit a ceiling at the first traffic spike.

1C-Bitrix Editions: Site Management

Four editions, and the difference lies not in the number of features but in the available core modules. The official 1C-Bitrix documentation states that composite cache is only available in Business and above.

Start is minimal, only content modules: iblock, form, basic SEO. For business card sites and landing pages. No sale module — cannot build a store.

Standard adds communication: blog, social network, forum, extended tech support. For corporate sites and portals with user-generated content.

Small Business is the first edition with e-commerce: the sale module appears. Comfortable ceiling is up to about 10,000 products without serious optimization. For small stores and catalogs with ordering.

Business is the full set: composite cache (TTFB drops from 800 ms to 50–80 ms — 10–15 times faster), web cluster, multisite, multi-warehouse, REST API. For large stores, marketplaces, projects with 10,000+ visitors per day.

How Does Composite Cache Reduce Server Load?

Composite cache (main.composite) speeds up page loading 10–15 times compared to dynamic generation. For a store with 3,000+ visitors per day, without composite the server starts struggling: average response time increases, database overload, checkout pages time out. Composite solves this radically — HTML is served by nginx without running PHP. It is important to correctly configure exclude masks for cart, personal account, and pages requiring real-time data. We configure this on every upgrade to Business.

1C-Bitrix official documentation: "Composite cache is available only in Business edition and higher."

Avoiding Common Mistakes in Edition Selection

Typical Mistakes

• Buying Start for an online store — no sale module, you either need to upgrade immediately or hack a custom ordering system.
• Choosing Small Business for a project that will grow to 10,000 products in six months — composite cache cannot be enabled, upgrading to Business costs the license difference plus configuration work.
• Using Business for a landing page — overpaying for features that will never be used.

Choosing an Edition for an Online Store

Hard Criteria for Edition Selection

By modules:

• 1C exchange (catalog) → at least Small Business
• Composite cache (main.composite) → only Business
• Web cluster (cluster) → only Business
• Multisite → only Business
• REST API → only Business

By load:

• Up to 1,000 unique visitors/day — any edition can handle
• 1,000–10,000 unique visitors/day — Small Business with nginx/php-fpm tuning hits a ceiling. Business with composite cache is the right choice
• 10,000+ unique visitors/day — only Business with composite and cluster

By budget:

• The price difference between editions is 2-5x
• Upgrade at any time — pay the difference in license cost
• Our principle: take the minimum sufficient. But if you know you will need composite in six months, get Business immediately, because an upgrade also involves configuration work. The total upgrade cost (license difference + setup) typically ranges from 10,000 to 50,000 RUB.

What Happens If You Ignore License Renewal?

An active license provides updates — new versions, security patches, bug fixes, marketplace access, and vendor tech support. When it expires, the site continues to work but remains without updates. For stores this is dangerous — security patches fix vulnerabilities in sale, catalog, main modules. Data leaks from b_sale_order or b_user are just a matter of time. Renewal costs a fraction of buying a new license — typically 20–30% of the full price. Regular renewal is insurance against unpatched CVEs.

Cost Benefits of Planned Edition Upgrades

1C-Bitrix allows upgrading without reinstallation — data is preserved. Process:

1. Pay the difference in license cost
2. Activate new key: Settings → Updates → Registration
3. Install newly available modules via admin panel
4. Configure new functionality
5. Test compatibility

What we do during an upgrade:

• Check custom code for conflicts with new modules — especially custom event handlers like OnBeforeOrderAdd, OnSaleBasketSaved
• Enable and configure composite cache — correct exclude masks for dynamic pages (cart, checkout, personal account)
• Configure multi-warehouse if needed — b_catalog_store, warehouse selection rules
• Run full functional testing on staging
• Document changes

As a result, you get:

• A working site on the new edition with no data loss
• Configured composite cache (if upgraded to Business)
• Testing report and recommendations for further optimization
• Access to staging and documentation of changes

Integrating Site Management with Bitrix24

A common scenario: site on 1C-Bitrix + CRM in Bitrix24. Orders from b_sale_order automatically become leads or deals, unified authorization, client base synchronization. Site forms (form or custom) feed into the CRM funnel. These are two separate licenses and two separate products — integration between them is standard and stable.

Practical Recommendations

• Do not skimp on the edition if you know the functionality will be needed in six months. Upgrading costs the same difference plus configuration and testing.
• Business for projects with growth ambitions — composite cache pays for the price difference at the first traffic spike. Without composite, 3,000+ unique visitors/day will strain the server.
• Bitrix24 and Site Management are different products with different licenses. Confusion here costs money.
• Renew your license annually — renewal is much cheaper than buying a new one, and without updates you risk unpatched CVEs.

What We Offer: Turnkey Selection and Configuration

We do not just consult — we handle the full cycle: analyze your current project, select the edition, purchase the license (if needed), migrate, configure all modules, and train your team. As part of the service, you get:

• An edition selection report with justification
• Migration plan (if upgrading)
• Fully set up staging with the new edition
• Composite cache and cluster configuration (if necessary)
• Documentation of the new configuration
• Guarantee of site functionality after the transition

Contact us today — we can assess your project within one business day and propose the optimal configuration. Receive a personalized cost estimate for selecting and configuring your 1C-Bitrix edition right now.