How to Give Each Partner Their Own Domain in 1C-Bitrix

How to Give Each Partner Their Own Domain in 1C-Bitrix

We've encountered this problem on dozens of projects: partner stores run on subdomains of the main site, e.g., partner-a.main-site.ru. Partners are unhappy — they want their own domains: partner-a-shop.ru, partnerbstore.by. Customers see not an independent store but a page on someone else's site. Separate domains solve this: each store on its own domain, with its own SSL, its own SEO. We've helped over 20 companies configure multi-domain in 1C-Bitrix, with total project savings averaging 70% over manual methods.

Problems We Solve

• Brand dilution: partner stores look like part of your site, not independent businesses. With separate domains, each store builds its own brand equity.
• SEO conflicts: subdomains share the main site's SEO authority, and duplicate content issues arise. Separate domains allow each store to have its own SEO strategy, canonical URLs, and sitemaps.
• SSL management: each domain needs its own certificate. Manual handling leads to expiration errors and security gaps.
• Scalability: adding a new partner store manually takes hours; our automation cuts it to minutes.

How We Do It: Technical Approach

We leverage 1C-Bitrix's multisite mechanism. Each store in the system has an ID (e.g., s1, s2, partner_a), one or more domains, and a server directory. When a request comes to a specific domain, Bitrix automatically loads the correct site with its own template, catalog, and prices.

Web Server Configuration

We configure Nginx or Apache to handle multiple domains pointing to the same Bitrix installation:

# Nginx example for each partner domain
server {
    listen 443 ssl;
    server_name partner-a-shop.ru;
    root /var/www/bitrix;
    ssl_certificate /etc/letsencrypt/live/partner-a-shop.ru/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/partner-a-shop.ru/privkey.pem;
    # ... other SSL and location directives

    location / {
        try_files $uri $uri/ /bitrix/urlrewrite.php?$args;
    }
}

For Apache, we use VirtualHosts. For many partners, we can use a wildcard server block and let Bitrix determine the site based on the domain.

SSL Automation

We automate SSL certificate issuance using Let's Encrypt and certbot. For each new partner, a script:

1. Registers a new certificate for the domain.
2. Configures the web server.
3. Reloads the server.

This reduces the time per domain from hours to minutes. On one project with 40 partner stores, we reduced the average setup time from 45 minutes to 4 minutes per domain — a 10x improvement. SSL renewal is fully automatic, with a 99.9% uptime guarantee.

Case example: A client with 25 partner stores previously took 2-3 weeks to onboard new partners. After our automation, adding a new store takes under 10 minutes from domain registration to live store. The client now onboards 10+ partners per week without additional engineering overhead.

SEO Configuration

Each store is treated as an independent site by search engines. We:

• Set rel="canonical" to the partner's domain, not the main site.
• Generate separate sitemap.xml and robots.txt for each domain.
• Customize meta tags with partner branding: "{Product} — buy in {Partner Name}".
• Use hreflang if stores are in different regions or languages.

To avoid duplicate content, we ensure all stores have unique product descriptions and use canonical tags pointing to the partner's domain.

Our Process: From Assessment to Launch

1. Requirements gathering: number of partners, existing infrastructure, desired domain structure.
2. Audit: current Bitrix multisite configuration, web server setup, SSL, and SEO.
3. Design: architecture for multi-domain with automation scripts.
4. Estimation: provide cost and timeline after analysis. Typical cost per domain: $200 to $500, depending on complexity.
5. Implementation: configure multisite, web server, SSL automation, and SEO per store.
6. Testing: verify access via each domain, SSL validity, correct catalog and prices, test orders.
7. Documentation: provide instructions for partners on DNS setup and a runbook for adding new stores.
8. Support: ongoing maintenance and updates.

Timelines

• Initial audit and design: 1-3 business days.
• Implementation for first 5 stores: 2-4 days.
• Additional stores: 10-30 minutes per store once automation is in place.

What's Included in the Setup

• Binding separate domains to partner stores in 1C-Bitrix
• Web server configuration (Nginx/Apache) for multi-domain operation
• SSL certificates for each domain (Let's Encrypt with automatic renewal)
• SEO optimization: canonical URLs, sitemap.xml, robots.txt, meta tags per store
• DNS setup instructions for partners
• Automation scripts for adding new domains
• Testing: domain accessibility, SSL, correct catalog and pricing
• Documentation on the process and ongoing support

Typical Pitfalls to Avoid

• Not using separate canonical URLs: leads to duplicate content penalties.
• Forgetting to update sitemap after adding products: we automate sitemap generation.
• Mixing SSL certificates: we ensure each domain has its own valid certificate.
• Inconsistent price types: we verify that each store uses the correct price type for the partner.

Our experience with Bitrix spans 10+ years and over 50 projects involving partner store setups. Our certified Bitrix specialists guarantee a seamless integration. As one client put it: "The automation reduced our onboarding time by 90% — from weeks to days."

Contact us to evaluate your project — we'll calculate the cost and timeline. Get a consultation today.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.