White-Label Solution Development on 1C-Bitrix

White-Label Solution Development on 1C-Bitrix

A development company creates a product that clients sell under their own brand—this is white-label. A tour aggregator, payment gateway, CRM system, or marketplace: all can be built as white-label on 1C-Bitrix. One codebase, dozens of installations with different branding—or a single installation with multi-tenancy. We specialize in such solutions and guarantee an architecture that scales from 5 to 500 clients without rewriting the core.

The key technical question at the start is choosing between a single codebase for all clients or a separate instance for each. This choice determines the future architecture, maintenance cost, and deployment speed. Below we analyze both models.

Two Architectural Models

Bitrix Multi-Site (single instance, multiple sites). Bitrix supports multiple sites within a single installation. Each site is a record in b_lang, a separate template in /local/templates/{SITE_ID}/, its own settings in b_option. Data (products, users, orders) can be shared or separated by site. Suitable when there are few clients (up to 20–30 sites), data is partially shared, and one team administers all sites. License cost savings can reach 30%.

Separate Installations. Each client gets an independent Bitrix installation. The common codebase is delivered as a module or via Git. Updates are rolled out separately to each instance. Suitable when clients want independence (their own data, their own backups), require different configurations, or have strict data isolation requirements (GDPR, healthcare).

How Multi-Tenancy Works in a Single Installation?

For aggregators and SaaS products on Bitrix, a multi-tenant architecture is built:

• b_lang table—each site (tenant) with a unique LID
• Templates—a common base template (/local/templates/base/) + overrides in /local/templates/{TENANT_ID}/
• Tenant settings—custom table b_tenant_settings with pairs TENANT_ID / KEY / VALUE
• Users—common b_user table, separation by groups and SITE_ID

Branding for each tenant:

// In init.php or in the template header
$tenantId   = SITE_ID;
$tenantConf = TenantSettingsTable::getByTenantId($tenantId);

define('TENANT_PRIMARY_COLOR', $tenantConf['PRIMARY_COLOR'] ?? '#0052cc');
define('TENANT_LOGO_URL',      $tenantConf['LOGO_URL'] ?? '/logo.svg');
define('TENANT_DOMAIN',        $tenantConf['DOMAIN']);

CSS variables are generated dynamically via PHP and cached at the page level:

$css = ":root { --primary: " . TENANT_PRIMARY_COLOR . "; --brand-font: " . $tenantConf['FONT'] . "; }";

Developing the Product Core as a Bitrix Module

If the product code is delivered to multiple clients, it's best to package it as a Bitrix module. The module is installed via /bitrix/admin/partner_modules.php and registered in b_module:

/local/modules/vendor.whitelabel/
├── install/
│   ├── index.php
│   └── db/install.sql
├── lib/
│   ├── TenantManager.php
│   ├── BrandingService.php
│   └── ...
├── options.php
└── include.php

Advantage: the module updates via Bitrix's standard mechanism (ModuleManager::isModuleInstalled(), ModuleManager::install()), similar to standard modules. In practice, this reduces deployment time by 50%.

Feature Gating by Tier

White-label often involves tiered plans: basic, standard, premium. Each tier unlocks or restricts functionality.

Feature availability check:

public static function hasFeature(string $feature, string $tenantId = SITE_ID): bool {
    $plan = self::getTenantPlan($tenantId);
    $features = self::PLAN_FEATURES[$plan] ?? [];
    return in_array($feature, $features, true);
}

if (!TenantLicenseManager::hasFeature('advanced_analytics')) {
    // Stub or redirect to upgrade page
}

The feature matrix is stored in code or database. Tier changes take effect without deployment.

Admin Interface for Clients

The client of a white-label product needs to manage their instance. This is not the standard Bitrix admin panel—it's excessive and insecure. A separate "partner dashboard" is built:

• Branding management (upload logo, choose colors)
• User management for their tenant
• Statistics and analytics
• Notification and integration settings

Implementation: a separate site section with authorization by the TENANT_ADMIN group. Components in /local/components/vendor.whitelabel/tenant.admin.*.

Why Data Isolation Between Tenants Matters?

A critical security issue: tenant A's data must not be visible to tenant B. In all infoblock queries, a mandatory filter by SITE_ID or a custom TENANT_ID field is added:

$filter = array_merge($userFilter, ['=PROPERTY.TENANT_ID' => CURRENT_TENANT_ID]);
$res = CIBlockElement::GetList([], $filter, ...);

For critical data (payment info, personal data), database separation between tenants is recommended—each tenant works with its own PostgreSQL schema. Bitrix does not support this out of the box, but it is achievable by switching the $DB object at the start of each request.

How to Update the Codebase with Many Clients?

Managing multiple installations is the most complex operational task. With separate instances, an automatic update deployment system is needed:

• Git repository with the module/templates code
• CI/CD (GitLab CI, GitHub Actions) for rollout to each server via SSH or Ansible
• Versioning: the module has a VERSION in install/index.php, and compatibility with the client's Bitrix version is checked before updating

With a single installation, updates are simpler—one deployment.

What Is Included in Our Work?

We provide a complete package: architecture documentation, CI/CD setup, client team training, technical support at launch, and update maintenance. The exact scope is clarified during project definition.

Estimated Timelines

Architecture Comparison

A Real-World Example

We recently helped a B2B aggregator client build a white-label marketplace on Bitrix. The initial prototype for their first tenant took 5 weeks. After adding multi-tenant logic and tiered plans, they onboarded 12 tenants in the first quarter. The system handles 50+ tenants today with full data isolation and automated CI/CD. Performance metrics show page load times below 2 seconds even with 200 concurrent requests at the database level.

White-label on Bitrix is a non-standard use of the platform requiring deep understanding of its architecture. With proper design, the system scales from 5 to 500 clients without rewriting the core. Our 10+ years of experience and certified specialists ensure a reliable solution. Order a prototype today. Contact us for a consultation on your product architecture.

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.