Bitrix24-ERP Integration: Design, Development, Support

Bitrix24-ERP Integration: Design, Development, Support

You're launching production, but your managers see inventory that's three days old in CRM. Accounting issues invoices in ERP, but the sales team doesn't know about payments. This is the result of a disconnect between front-office (Bitrix24) and back-office (ERP). We design and implement seamless synchronization so that data flows without manual entry.

Typical synchronization scenarios cover counterparty directories, product catalogs with stock levels, orders, and financial documents. For counterparties, the key is TIN; for products, it's XML_ID from 1C. Mapping errors lead to duplicates and data loss, so analytics gets special attention. Each scenario requires configuring an exchange mechanism: via REST API, files, or message queues.

Choosing the architecture is a key step. Direct point-to-point connection is an anti-pattern—it doesn't scale and breaks when APIs change. We use an integration bus (RabbitMQ or Kafka), a microservice adapter, or file exchange. The choice depends on the number of integrated systems, budget, and performance requirements. Our comparison shows that a bus is 3–5 times more reliable than direct connection, with a payback period of 2–3 months. The budget for adapter development varies, but in most cases it doesn't exceed half a year's salary of one developer and pays off by eliminating manual labor.

Typical Synchronization Scenarios

• Counterparty directories: client from lead → company in CRM → counterparty in ERP. Link key: TIN in a custom field.
• Product catalog and stock: ERP is the source of truth. Bitrix24 receives current stock and prices via API or queues.
• Orders: deal in "Contract signed" status → order in ERP. Execution status from ERP updates the deal stage.
• Financial documents: invoices from CRM → ERP for accounting, payments from ERP → CRM for closing deals.

How to Choose Integration Architecture?

Direct point-to-point connection is an anti-pattern. It breaks quickly when APIs change and doesn't scale. According to Bitrix24 REST API documentation, the recommended approach is using webhooks and external handlers. We apply three proven patterns:

1. Integration bus (ESB/iPaaS). Bitrix24 and ERP communicate via RabbitMQ or Apache Kafka. The bus normalizes formats, guarantees delivery, and stores history. Enterprise standard.
2. Microservice adapter. A lightweight PHP service that knows both APIs. It receives events, transforms them, and calls endpoints. Simpler to implement but less scalable than a bus when integration grows.
3. File exchange via FTP/S3. For ERPs without API (legacy SAP versions, specific 1C configurations). The ERP exports XML/CSV on a schedule, the adapter parses and writes to Bitrix24. Latency is a few minutes.

Our comparison shows that a bus is 3–5 times more reliable and faster to debug than direct connection. Integration payback is 2–3 months by eliminating manual data entry.

Integration with 1C:ERP

The most common request in the CIS market. Technical options:

• Via REST API from Bitrix24 + HTTP service in 1C. 1C publishes endpoints, the adapter initiates requests for synchronous operations (e.g., stock check). For asynchronous events, 1C sends a webhook to Bitrix24.
• Via standard CommerceML. We extend the protocol for CRM scenarios: counterparties, orders, invoices. A compromise option.
• Via an intermediate database. 1C writes changes to a separate PostgreSQL, the adapter reads and publishes. Slower but isolates ERP from direct load.

Similar approaches apply to integration with SAP, Odoo, and other ERPs.

Why Data Transformation Matters?

Data models don't match. Example: in ERP, a counterparty is a legal entity with TIN/KPP and contracts. In Bitrix24, it's crm.company with fields and contacts. Mapping looks like:

Keys are stored in custom fields UF_*—this ensures idempotency.

How to Build Integration: Step-by-Step Plan

1. Analytics and data map: define flows, mapping, master system.
2. Architecture selection: bus, adapter, or file exchange.
3. Prototype development: one scenario to test connectivity.
4. Implement all scenarios, including transformation and error handling.
5. Testing with real data: edge cases, load, conflicts.
6. Historical data migration and pilot run.
7. Monitoring and post-launch support.

Conflict Management

In bidirectional sync, conflicts are inevitable. Strategies:

• Master system: for each data type, assign a source of truth. Prices and stock—from ERP, comments—from Bitrix24.
• Timestamp-based merge: the later record wins. Simple but breaks on simultaneous changes.
• Locking: a field is marked as "in sync" until confirmation is received. Reliable but complex to implement.

What's Included in the Work

• Analytics and data map (flow diagram, field mapping)
• Adapter development or bus setup
• Testing with real data (edge cases, load)
• Documentation and team training
• 3 months of post-launch support

When to Replace Standard 1C Exchange?

Standard CommerceML works for e-commerce, but for CRM scenarios its functionality is often insufficient. We either extend it or implement a separate adapter via 1C HTTP services and Bitrix24 REST API. This provides flexibility and removes CommerceML limitations.

Monitoring and Debugging

Integration is a long-lived system. You need control:

• Message queue size, number of failed messages
• Transformation errors (type mismatch, missing directories)
• Sync lag (time from source change to target arrival)
• Dashboard in Grafana or Bitrix24 standard reports

Project Phases

An integration project is not a one-time task, but a long-term system that needs support when any platform is updated. Factor this into your budget from the start.

Contact us for a preliminary audit and roadmap. Order integration development—we'll assess your architecture for free.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.