Development of an industry-specific solution based on Bitrix24

Developing an Industry-Specific Solution on Bitrix24

Out-of-the-box Bitrix24 configurations cover 60–70% of generic business needs. The remaining 30–40% is industry-specific functionality that cannot be addressed through standard configuration: specialized entities (real estate property, insurance policy, medical case), non-standard pipelines, deep integrations with industry-specific systems, and domain-specific calculations and automations.

An industry-specific solution is a layer built on top of standard Bitrix24, implemented through a combination of the platform's low-code tools, custom REST applications, and server-side logic. Developing such a solution is fundamentally different from standard configuration — this is where real engineering work begins.

Architectural Choice: Extension vs. Integration

The first decision in an industry solution project is determining what belongs in Bitrix24 and what belongs in external systems. Both extremes are equally problematic:

Everything in Bitrix24 — creates a monolith where the platform is overloaded with functions it was not designed for. Financial accounting, warehouse logistics, production planning — these are not CRM tasks.

Bitrix24 as a thin client — then why pay for the license? The entire value of a unified workspace is lost.

The optimal boundary: Bitrix24 handles client communications, deal and task management, and visualization of data from external systems. Industry-specific systems (1C, MIS, ERP, WMS) handle the subject domain.

Technical Stack for an Industry Solution

Smart Processes (SPA) — the foundation for custom entities in Enterprise and higher plans. They allow you to create "Construction Project", "Insurance Policy", "Medical Case" entities with custom fields, pipelines, access rights, and robots. With the REST API in version 22.x, Smart Processes became a viable replacement for custom modules.

// Creating a Smart Process item via REST
CRest::call('crm.item.add', [
    'entityTypeId' => 138, // your SPA ID
    'fields' => [
        'title'          => 'Project: Residential Complex North',
        'ufCrm138_1234'  => 'Residential Complex',  // custom field
        'ufCrm138_5678'  => '2025-12-31',            // planned deadline
        'assignedById'   => 42,
    ],
]);

REST application on Bitrix24 Marketplace — for solutions intended for distribution. Application registration, OAuth 2.0, webhooks on CRM events. This path is more complex, but provides the ability to sell the solution to other clients.

Embeddable Apps — iframe insertions of custom UI into CRM cards. Implemented via placement.bind, they allow displaying external system data in the deal card side panel: order status from 1C, support ticket history, technical specifications from an ERP.

Case Study: Industry Solution for a Real Estate Agency

Task: an agency with 50 agents, primary and secondary market, partner programs with developers.

Problem with standard Bitrix24: no "Property" entity with characteristics (type, area, floor, price per m², sale status), no property ↔ multiple deals from different agents relation, no agent commission calculation.

Solution architecture:

Smart Process "Property"
  ├── Fields: type, area, floor, price, status (available/reserved/sold)
  ├── Relation: Developer (Company in CRM)
  └── Relation: Deals (Standard entity)

Smart Process "Commission"
  ├── Relation: Deal
  ├── Fields: percentage, amount, payment status
  └── Robot: auto-calculation when deal moves to "Won"

REST Application "Property Catalog"
  ├── Embedded page in contact card
  ├── Display available properties matching client criteria
  └── "Reserve" button → creates Deal + updates Property status

Delivered in 6 weeks:

Result: time from client inquiry to presenting options was reduced from 2 hours to 15 minutes (manual searching across databases replaced by catalog search directly from the client card).

Integration with Industry Systems

For most industries, two-way synchronization with an accounting or ERP system is critical. Common patterns:

1C → Bitrix24 (accounting data to CRM): invoice payment statuses, warehouse stock levels, shipment data. Implemented via the 1C connector or via REST API with a cron agent in 1C.

Bitrix24 → 1C (deals to orders): when a deal is won, an order is automatically created in 1C. Triggered via the ONCRMDEALSTAGEIDCHANGE webhook, transferred via COM object or 1C REST.

External APIs: for insurance — insurer policy information systems; for healthcare — MIS via FHIR protocol; for logistics — carrier APIs (transport companies).

Version Control and Deployment

An industry solution is code that must be versioned. Mandatory stack:

• Git repository for the REST application and server-side scripts
• Staging environment (separate Bitrix24 portal or test On-Premise instance)
• CI/CD for automated deployment of changes

Without versioning, within six months no one will remember why a particular field was added to a Smart Process, and changes will start breaking each other.

An industry solution is a long-term product that lives and evolves with the business. Design the architecture with change in mind: modularity, documentation, and clear boundaries of responsibility between Bitrix24 and external systems.