Developing a Custom Partner Cabinet on 1C-Bitrix

When an online store's monthly turnover exceeds 1 million rubles, managing partners manually becomes unsustainable. You need a dedicated partner cabinet that handles registration, referral tracking, multi-level commissions, and automated payouts. We have built such systems for clients with hundreds of active partners and thousands of orders per day. With over 10 years of experience and 40+ successful Bitrix projects, we deliver stable, scalable solutions. Typical development takes 2 to 4 months depending on integrations.

How the Built-In Bitrix Affiliate System Works and Its Limitations

The sale module includes the "Affiliates" subsystem (\Bitrix\Sale\Affiliate). Basic features: partner registration via bitrix:sale.affiliate.register, generation of referral links with partner_id, tracking of clicks and orders, fixed-percentage commission calculation, and the bitrix:sale.affiliate.cabinet component for statistics.

Limitations: single-level referral only, flat commission without flexible conditions, minimal interface (no charts), no payout management, and no marketing materials. For a real partner program, the built-in module serves as a foundation, but the business logic must be extended with custom handlers and entities.

Partner Registration: What You Need to Consider

Partner registration differs from normal user registration. The partner fills out an extended form: full name or company name, INN (for legal entities), business area, promotion channels, and payout details. The request goes to moderation. The manager reviews the data and approves or rejects. On approval, the partner is assigned to the "Partners" group and an initial level.

Technical implementation: extended form using bitrix:main.register with custom UF_* fields, an OnAfterUserRegister handler that creates a record in a partner highload-block, and a notification to the manager.

Building a Referral System: Attribution Models and Implementation

The partner gets a unique link like https://site.ru/?partner_id=XXX or https://site.ru/?ref=PROMO_CODE. The partner ID is saved in a cookie with a configurable lifetime (usually 30–90 days).

Attribution models:

The built-in module only supports last click. For other models, we create a custom click table that records the full chain, and an OnSaleOrderPaid event handler applies the required logic. A custom level system can boost partner conversion by 2–3 times compared to the built-in one.

Promo codes are an alternative to referral links. The partner gets a unique code; the customer enters it at checkout. The code is linked to the partner via a basket rule (\Bitrix\Sale\Discount) and simultaneously attributes the sale. For more on attribution models, see Wikipedia.

Why Partner Levels Matter

A multi-level program motivates partners to increase volumes. Levels are stored in a separate highload-block with parameters:

Level recalculation runs via an agent (\CAgent) – daily or on each paid order. On level change, the partner receives a notification and the commission percentage updates for future orders.

Additional reward models: fixed amount per order (for services), percentage of first order + repeat order LTV, threshold bonuses, and multi-level marketing (implemented via recursive parent_partner_id).

The Partner Dashboard: Key Metrics and Tools

The main screen shows:

• Statistics: referral clicks (daily/weekly/monthly), attracted customer registrations, orders (count, amounts, average check), conversion rates (click → registration → order), accrued commissions, current balance.

Data is aggregated in a statistics highload-block. Charts are built with Chart.js or ApexCharts, data loaded via AJAX to a custom controller (\Bitrix\Main\Engine\Controller).

• Tools: referral link generator with UTM tags, promo code list (with limited creation based on level), payout history filtered by period and status.

Commission Calculation: From Order Payment to Balance

Calculation occurs when the order status changes to "Paid" via the OnSalePayOrder handler. Algorithm:

1. Identify the partner via partner_id cookie or promo code linked to the order.
2. Load the current level and commission percentage.
3. Compute the base: order amount minus delivery, coupons, and VAT (configurable).
4. Accrue commission to the partner's internal balance.
5. If multi-level marketing is enabled, recursively accrue commissions to upstream partners with a diminishing percentage.
6. Create a record in the accrual log (highload-block: partner_id, order_id, amount, type, date).

Cancellations and returns: When an order is canceled or refunded, the commission is reversed with a negative entry in the log. If already paid, a debt is recorded and deducted from the next payout.

Payout Management: From Request to Payment

The payout system uses a request-based approach. The partner submits a payout request once the minimum threshold (configurable) is reached. Steps:

• Partner clicks "Withdraw funds", enters amount and payout details.
• Request goes to moderation.
• Manager reviews and confirms.
• After actual payment, status changes to "Paid".

For legal entities, an invoice is generated from a template, the partner signs it, and accounting processes the payment.

Providing Marketing Materials

A section with:

• Banners in various formats with embedded referral links (HTML code for insertion).
• Logos and brand guidelines for co-branding.
• Email templates.
• Product/service descriptions partners can use on their sites.
• PDF presentations.

Materials are stored in an infoblock linked to partner levels. Starter partners see basic materials; upgraded levels unlock more advanced options.

Common Pitfalls in Partner Cabinet Development

• Missing cookie verification – transitions may be lost if cookies are blocked.
• Non-optimal highload queries with many partners – use tagged caching.
• Ignoring returns and reversals – leads to accounting discrepancies.
• No moderation process for payout requests – creates chaos.

Our Process and Timeline

We follow a structured approach:

1. Data gathering – understand your business, partner volumes, integrations.
2. Audit/analysis – review existing Bitrix setup and identify gaps.
3. Design – propose solution architecture, UI mockups, data model.
4. Estimation – provide a fixed price after analysis (no hidden costs).
5. Development – build custom modules, handlers, and integration.
6. Testing – unit tests, integration testing, UAT with sample partners.
7. Launch – deploy, train managers, monitor.

Timeline: typically 2 to 4 months from project start to go-live.

A Case from Our Practice

For a major electronics retailer with 150 existing partners and a monthly turnover of 5 million rubles, we implemented a multi-level partner program. The client was managing payouts manually via spreadsheets, taking 2 days per payout cycle. We automated the entire lifecycle: registration with document upload, multi-level commission calculation, and integrated payout requests with 1C. Result: partner onboarding time dropped from 3 days to 1 hour, and active partners grew by 40% in the first quarter. Payout processing time reduced to 4 hours. Official Bitrix sale module documentation: dev.1c-bitrix.ru.

Contact us to discuss your partner program. We'll assess your needs and propose an optimal solution.

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.