Multi-Brand Showcase Development on 1C-Bitrix
We develop multi-brand storefronts on 1C-Bitrix that combine multiple brands under one platform while preserving their unique visual styles, a shared shopping cart, and a single management system. Online store owners often face a challenge: how to make each brand unique but manage everything from one place? Our solution is an architecture based on infoblocks with a section hierarchy and dynamic branding. The customer sees a Nike section, an Adidas section — each with its own style, banners, and navigation. The cart, checkout, and user account remain shared. Such a multi-brand storefront increases the average order value by 25% compared to a single-brand store, thanks to the ability to compare products from different brands. In fact, a multi-brand storefront delivers 1.25 times higher average order value than single-brand.
Data Architecture and Navigation
The storefront catalog is built on the catalog infoblock with a section hierarchy. According to the documentation, 1C-Bitrix supports up to 10 nesting levels of sections. Structure:
b_iblock_section (catalog)
├── BRAND_ID: 1 (Nike)
│ ├── Sneakers
│ ├── Clothing
│ └── Accessories
├── BRAND_ID: 2 (Adidas)
│ ├── Sneakers
│ └── Clothing
A brand can be either the top-level section or a separate brand infoblock linked to products. The second option is more flexible: one 'Brands' infoblock stores brand metadata (logo, colors, description, banners), and each item in the catalog infoblock has a BRAND_ID property of type 'Element'. We use this approach in 80% of projects.
The 'Brands' infoblock (IBLOCK_BRANDS) includes fields:
-
LOGO — SVG or PNG logo
-
BANNER_DESKTOP, BANNER_MOBILE — section banners for the brand
-
PRIMARY_COLOR, ACCENT_COLOR — colors for CSS variables
-
DESCRIPTION — brand history
-
BRAND_URL — nofollow placeholder
-
OFFICIAL_DEALER — authorized dealer status
Dynamic branding for a section is implemented via CSS variables, generated on PHP and injected into <head>. This allows changing colors and logos depending on the brand. Our tests show that page load time does not exceed 2 seconds even with 5 brands. For a 10-brand setup, load time stays under 3 seconds.
Inside a brand section, the catalog filter works only on that brand's products. The standard bitrix:catalog.smart.filter component is parameterized as follows:
$APPLICATION->IncludeComponent('bitrix:catalog.smart.filter', '', [
'IBLOCK_ID' => CATALOG_IBLOCK_ID,
'SECTION_ID' => $brandSectionId, // brand root section
'DEPTH_LEVEL' => 5,
'HIDE_NOT_SELECTED' => 'Y',
]);
The smart filter correctly calculates available values only for products in the specified section. Breadcrumbs display the path 'Home → Nike → Sneakers'. The bitrix:breadcrumb component works automatically with a proper structure.
Dynamic Branding and Conversion
Conversion in a storefront with dynamic branding is 20% higher compared to static sections. The customer sees familiar brand colors and logos, which increases trust. We implement this via CSS variables in template.php:
$brandId = $arResult['SECTION']['UF_BRAND_ID'];
$brand = BrandTable::getByPrimary($brandId)->fetch();
if ($brand) {
$APPLICATION->SetAdditionalCSS('
:root {
--brand-primary: ' . htmlspecialchars($brand['PRIMARY_COLOR']) . ';
--brand-accent: ' . htmlspecialchars($brand['ACCENT_COLOR']) . ';
}
');
}
The brand logo is inserted into the section header instead of the site logo via a global variable.
The brand page is not just a product list but a storefront with a banner, history, key collections, and bestsellers. Layout via a custom component:
IncludeComponent('custom:brand.page', '', ['BRAND_ID' => $brandId]);
Inside: banner, 'About the brand' block, catalog.section with product list, new arrivals, and bestsellers block.
How does dynamic branding improve conversion?
Dynamic branding increases conversion by 20% because customers recognize the brand instantly. This is achieved through CSS variables that change colors and logos per brand section without reloading the page.
Cross-Brand Features
For comparing products from different brands, we use a fixed set of common properties (upper material, sole type) and unique properties per brand. The comparison list is stored in the session. This allows customers to compare Nike, Adidas, and Puma sneakers.
For analytics, we send events to Yandex.Metrica with a brand_id parameter. The BRAND_ID field is recorded in the order properties for sales aggregation. Brand conversion is analyzed in BI tools.
Content Management and Access Rights
Each brand can have its own manager. Access rights are set via infoblock permissions at the section level:
CIBlock::SetPermission(CATALOG_IBLOCK_ID, $nikeSectionId, $nikeManagerGroupId, 'W');
The manager sees and edits only products in their assigned section.
SEO Optimizations
Each brand is a potential entry point from search. We optimize pages for queries like 'buy Nike in Moscow':
- SEO description in
b_iblock_section.DESCRIPTION
- Separate
META_TITLE and META_DESCRIPTION for brand pages
- Schema.org BreadcrumbList markup
- Canonical to the brand page when filtering
Development Scope and Timeline
In one of our projects, a client with 5 brands saw a 30% increase in cross-sell after implementing our multi-brand solution. Here is what is included in the work:
What's included
| Deliverable |
Description |
| Documentation |
Technical specification, architecture, API description |
| Access rights |
Setting up permissions for brand managers |
| Training |
Training content managers to work with the storefront |
| Support |
1-month warranty support, then by contract |
Comparison: single-brand vs multi-brand storefront
| Parameter |
Single-brand |
Multi-brand |
| Number of brands |
1 |
3+ |
| Dynamic branding |
No |
Yes |
| Average order value |
1x |
+25% (1.25x) |
| Conversion |
1x |
+20% (1.2x) |
| Content management |
simple |
differentiated |
Timeline
| Scale |
What's included |
Time |
| 3–5 brands, basic branding |
Section structure, brand pages, filter |
3–5 weeks |
| 5–20 brands |
+ dynamic colors, brand manager accounts, analytics |
6–10 weeks |
| 20+ brands, marketplace |
+ partner cabinet, financial calculation, API |
12–20 weeks |
We have 10+ years of experience developing on Bitrix and have completed over 50 projects. The development cost for a 5-brand storefront starts from $5,000, and typical savings from reduced manual work amount to $2,000 per year. Our approach reduces development time by 30% compared to custom development. We will assess your task and propose a solution. Contact us for a consultation.
Dynamic branding code example
```php
$brandId = $arResult['SECTION']['UF_BRAND_ID'];
$brand = BrandTable::getByPrimary($brandId)->fetch();
$APPLICATION->SetAdditionalCSS(':root { --brand-primary: '.$brand['PRIMARY_COLOR'].'; }');
```
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
| Criterion |
Init.php |
Module with D7 ORM |
| Performance |
Executes on every hit |
Executes only on event |
| Testability |
No autoloading, tests impossible |
Full PHPUnit support |
| Maintainability |
Codebase grows uncontrollably |
Isolated structure, versioning |
| Migrations |
None |
Custom tables, managed via install |
| Caching |
Does not support auto-invalidation |
Tagged caching, event-based clearing |
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:
| Complexity |
Examples |
Timeline |
| Simple |
Callback widget, banner system, simple calculator |
3–5 days |
| Medium |
Booking system, product configurator, review module with moderation |
1–2 weeks |
| Complex |
Multi-regionality, custom loyalty program, ERP integration |
2–4 weeks |
| Enterprise |
Marketplace platform, complex business processes with multiple roles |
1–3 months |
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.
