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.