Build Custom B2B & B2C Personal Accounts on 1C-Bitrix

Build Custom B2B & B2C Personal Accounts on 1C-Bitrix

We are a team of certified 1C-Bitrix developers with over 7 years of experience. During this time, we delivered more than 50 personal account projects for B2B and B2C. Every day clients call the manager: "What's the status of my order?" "Send me the reconciliation report for last quarter." "I need a duplicate invoice." The manager then dives into 1C, generates the document, and emails it. Five minutes per request. Twenty such calls a day — that's an hour and a half of pure time spent on work a personal account should handle. On 1C-Bitrix, the personal account is built from ready-made components. But a full-fledged B2B account with multi-user access and 1C integration always requires customization. We guarantee your personal account will run without failures and scale as your business grows. Our multi-user B2B account reduces manager workload by 3x compared to manual processing, and clients typically save 40% on support costs.

Architecture of the Personal Account

A typical personal account is the /personal/ section of the site. It includes a set of subsections, each implemented by a Bitrix component or custom page.

Standard components:

• bitrix:main.profile — view and edit profile
• bitrix:sale.personal.order — order list with details
• bitrix:sale.personal.order.cancel — cancel order
• bitrix:catalog.viewed — viewed products
• bitrix:main.feedback — feedback form

In practice, this set suffices for an online store with a simple model. An individual buys, tracks the order, downloads a receipt. For B2B, where multiple people from one organization work with different roles, an overlay is needed.

Routing inside the personal account uses SEF rules in .urlrewrite.php or a complex component with SEF mode. The second option is more convenient. All personal account pages are managed from one place.

Access Rights Differentiation

The rights system in Bitrix is based on user groups. For a personal account it looks like this:

• Registered user — basic access: profile, own orders
• Wholesale client — wholesale prices, additional sections (accounts receivable, reconciliation reports)
• Counterparty — documents and settlements for their organization
• Partner — referral statistics, marketing materials

Groups are assigned during registration via the OnAfterUserRegister handler or manually by the manager. Rights are checked at two levels: file system (/personal/b2b/ — accessible only to the "Wholesalers" group) and inside components (data filtering by $USER->GetID()).

Deep-dive: B2B Account with Multi-User Access

A standard personal account has one user, one account, their orders. In B2B, an organization has a purchaser, an accountant, a manager. Each needs their own set of data and rights. This is the main architectural challenge.

Entity "Organization". Created via a highload block or infoblock with fields: name, TIN, KPP, legal address, payment terms, credit limit. Users are linked to the organization via the user property UF_COMPANY_ID.

Roles within the organization:

The organization's administrator adds employees via the personal account interface. They send an invitation by email. The new user registers and is automatically linked to the organization with the specified role. No need to call the manager to add a new purchaser.

Technical implementation:

• User-to-organization binding stored in UF_COMPANY_ID or in a separate link table (to support multi-organization access when one person works with multiple legal entities)
• Roles — a separate highload block: user_id, company_id, role
• Upon login, the organization context and user role are loaded into the session
• Components filter data by company_id: the purchaser sees their orders, the administrator sees all orders of the organization
• Switching between organizations — a selector in the personal account header

Order approval. In large organizations, the order does not go directly to the supplier:

1. Purchaser creates an order (status "Draft")
2. The procurement manager receives a notification, checks the content and budget
3. Approves or returns for revision with a comment
4. After approval, the order moves to status "Confirmed" and goes into processing

Implemented via custom order statuses in the sale module and event handlers OnSaleOrderBeforeSaved, OnSaleStatusOrder.

What Is Included in Personal Account Development?

Deliverables:

• Architecture design and role model
• Configuration of standard components and custom development
• Integration with 1C via CommerceML or REST API
• Security setup (HTTPS, two-factor authentication, logging)
• Load testing up to 1000 concurrent users
• Administration and usage documentation
• Training for the client's employees (up to 5 people)
• Warranty support for 3 months after delivery

Personal Account Sections

Orders

Component sale.personal.order — list with filtering by status, date, amount. Details: composition, payment and delivery statuses, tracking number. Extensions:

• Repeat order — copy the composition to the cart with one button
• Complaint — a claim form linked to a specific order and item
• Print forms — generation of invoice, act, waybill via \Bitrix\Sale\Order::getDocuments()

Documents

Section for downloading closing documents: invoices, acts, invoices, UPD. Documents are generated from the sale module or uploaded from 1C via integration. Storage — linked to the order or to the user via a highload block.

For B2B it's critical that the accountant sees all documents of the organization, not just their own. Filtering by company_id, not by user_id.

Tickets

Ticket system: the user creates a ticket, attaches files, sees history and status. Implementation — via the support module (tech support) or custom on an infoblock / CRM smart process. The second option is more convenient if tickets should go into CRM and be processed by the manager in a familiar interface.

Balance and Settlements

For B2B clients: current balance, payment history, accounts receivable. Data comes from 1C via REST or file exchange. A reconciliation statement is generated on request — the user clicks a button, the request goes to 1C, the PDF returns within a few minutes.

Integration with 1C

Linking a personal account with 1C is mandatory for B2B. The standard exchange module sale + catalog synchronizes the catalog and orders, but a full-fledged personal account requires extended exchange.

From 1C to the personal account:

• Order history, including those placed by phone or through the manager
• Accounts receivable by counterparty
• Reconciliation statements in PDF
• Personal prices and discounts according to the counterparty's price list
• Shipment and payment statuses

Exchange — via REST API (module rest), SOAP services, or CommerceML with an extended schema. Official 1C-Bitrix documentation recommends using REST for new projects. For high-load systems, data is cached in highload blocks: when the user requests, the personal account reads the local cache rather than waiting for a response from 1C. Synchronization — on schedule (cron agent) or by event (webhook when data changes in 1C).

Security

The personal account handles personal data and financial information. Minimum set of measures:

• HTTPS for the entire /personal/ section
• CAPTCHA or rate-limiting on the authorization form — protection against brute force
• Two-factor authentication via the security module (OTP)
• Logging of user actions in the "Proactive Protection" module
• Automatic session termination on inactivity (configured in the security module)
• For B2B — optional IP-based session restriction

Development Stages and Pricing

Cost is calculated after requirements analysis. Contact us for a free project assessment.

Why Order Development from Us?

• Over 7 years of experience and 1C-Bitrix certification
• More than 50 implemented personal account projects
• Full documentation and training
• Warranty on work up to 12 months
• Individual approach: we do not use template solutions

Get a consultation — we will assess your project for free.

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.