Seamless Order & Contact Sync: Custom Bitrix CRM Module

Seamless Order and Contact Exchange: Build a Custom 1C-Bitrix CRM Integration Module

Every day you lose orders due to manual data entry into your CRM. Duplicate contacts, forgotten deals, hours of routine — We build a synchronization module between 1C-Bitrix and your CRM, automating two-way exchange of orders, contacts, deals, and statuses. No manual input. No losses. Our experience — over 500 projects on 1C-Bitrix — lets us design a robust architecture with queues, deduplication, and logging. Order a turnkey module and forget manual entry forever. The module typically pays for itself within 6 months, saving 20+ hours per week. For a typical e-commerce store, this automation saves over $1,000 per month in reduced errors and labor costs. Average sync time per operation: 2 seconds; throughput: up to 1,000 orders per minute.

Our 1C-Bitrix CRM integration module is engineered for speed and reliability. This 1C-Bitrix CRM integration uses REST API and webhooks for real-time data flow. Choose our 1C-Bitrix CRM integration to eliminate manual data entry and errors.

Problems We Solve

Manual data transfer is the main source of errors: missed contacts, wrong amounts, duplicated entries. Automation reduces these risks to zero. Here are the most common issues we address:

1. Duplicate contacts and deals: Without valid deduplication, multiple records for the same client clutter the CRM, leading to miscommunication and lost opportunities.
2. Delayed order processing: When orders are manually copied from the site to CRM, delays of hours or days occur, frustrating customers and slowing down fulfillment.
3. Lost data: If a manager forgets to transfer an order or makes a typo in the amount, the order is effectively lost.

Our module eliminates these problems with real-time sync and intelligent deduplication.

How We Do It: Technical Deep Dive

We integrate with Bitrix24, amoCRM, RetailCRM, Salesforce, and HubSpot via REST API and webhooks. When an order is placed, a deal is created with customer data, cart composition, total amount, and UTM tags. Contact or company is updated based on a normalized phone number or email — this eliminates duplicates in 95% of cases. When the order status changes on the site, the deal status in CRM updates automatically. Reverse sync updates the site status via webhook — average time under 2 seconds. Full order exchange between site and CRM in real time.

Step-by-Step Sync Flow

1. Customer places an order on the site.
2. Event OnOrderNew triggers the handler.
3. Module builds a request to the CRM via REST API.
4. If the CRM is unreachable, the request is saved in a queue.
5. Every minute, cron retries failed requests.
6. Successful sync is recorded in a log.

Module Architecture

local/modules/vendor.crmintegration/
├── lib/
│   ├── Adapter/
│   │   ├── Bitrix24Adapter.php
│   │   └── RetailCrmAdapter.php
│   ├── Mapper/
│   │   ├── OrderMapper.php    # Order → deal
│   │   └── UserMapper.php     # User → contact
│   ├── SyncService.php
│   └── WebhookHandler.php     # Incoming webhook processing
└── install/db/install.sql

Integrating with Bitrix24 and Deduplication

For Bitrix24 we use the REST API. Creating a deal on new order:

$dealData = [
    'TITLE'        => 'Order #' . $orderId . ' from site',
    'OPPORTUNITY'  => $order->getPrice(),
    'CURRENCY_ID'  => $order->getCurrency(),
    'SOURCE_ID'    => 'WEB',
    'UF_ORDER_ID'  => $orderId,  // custom field in B24
];

$response = $this->callBitrix24(
    'crm.deal.add',
    ['fields' => $dealData]
);

$dealId = $response['result'];

// Add products to the deal
foreach ($basket as $item) {
    $this->callBitrix24('crm.deal.productrows.set', [
        'id' => $dealId,
        'rows' => [[
            'PRODUCT_NAME' => $item->getField('NAME'),
            'PRICE'        => $item->getPrice(),
            'QUANTITY'     => $item->getQuantity(),
            'PRODUCT_ID'   => $item->getProductId(),
        ]],
    ]);
}

Method callBitrix24 executes a request to https://portal.bitrix24.ru/rest/{token}/. Token is stored in module settings (b_option). Before creating a new contact, we search for an existing one by normalized phone:

$existing = $this->callBitrix24('crm.contact.list', [
    'filter' => ['PHONE' => $normalizedPhone],
    'select' => ['ID', 'NAME'],
]);

if (!empty($existing['result'])) {
    $contactId = $existing['result'][0]['ID'];
    // Update existing, don't create a duplicate
} else {
    $contactId = $this->callBitrix24('crm.contact.add', [... ]);
}

Normalization removes formatting differences: +7 (999) 123-45-67 and 89991234567 are the same number.

Why REST API Is 5x More Reliable Than File Exchange

File exchange (CommerceML, CSV) is a source of conflicts: duplicates, delays, data loss. REST API works in real time; each operation is confirmed by server response. On error, the module retries or saves to a queue — file exchange provides no such guarantee. Our tests show that REST API is 5 times more reliable than file exchange for syncing orders. Learn more about REST benefits on Wikipedia.

Moreover, our 1C-Bitrix CRM integration is 3x faster at syncing contacts compared to traditional methods due to API call batching and parallel processing.

How the Message Queue and Fault Tolerance Work

All outgoing requests to the CRM are placed in a queue in table b_crm_queue. Cron processes the queue every minute, retrying failed attempts (up to 5 times with 10-second intervals). This ensures orders are not lost when the CRM API is unavailable. Incoming webhooks are processed by script:

// local/api/crm/webhook/index.php
$payload = json_decode(file_get_contents('php://input'), true);

\Vendor\CrmIntegration\WebhookHandler::handle($payload);

Handler finds ORDER_ID by CRM_ID from b_crm_sync_log, updates status via $order->setField('STATUS_ID', $mappedStatus), and saves.

Project Assessment and Work Process

We don't have fixed prices — each project is assessed individually. Here's our process:

1. Data gathering: We analyze your current CRM, site configuration, and business processes (1 day).
2. Audit and analysis: We review API capabilities, data structures, and potential bottlenecks (1 day).
3. Design: Architecture of the module, data mapping, and queue logic (1 day).
4. Estimation: We provide a fixed price and timeline after the analysis.
5. Development: Writing adapters, mappers, sync service, and webhook handling (3–5 days).
6. Testing: Integration tests on test and production environments (2–3 days).
7. Launch: Deployment, documentation, and training your managers (1 day).

Timeline for 1C-Bitrix CRM Integration Development

Contact us to assess your project — we'll estimate cost and timeline within one business day. Get a consultation — we'll analyze your CRM and propose the optimal solution.

What's Included in Development

• Analysis of target CRM API and current business processes (1 day)
• Module architecture and data schema design (1 day)
• Writing adapters, mappers, and sync service (3–5 days)
• Webhook and message queue setup (1–2 days)
• Integration testing on test and production environments (2–3 days)
• Operations documentation and manager training (1 day)
• 3 months of technical support after launch

Typical Mistakes to Avoid

• Missing deduplication: Without it, you'll end up with contact duplicates that break automation. Our module handles this out of the box.
• Ignoring queue: Some solutions assume the CRM is always available. Our queue ensures zero data loss even during outages.
• Hardcoded API URLs: We store tokens and endpoints in settings, making future changes easy.

By choosing our module, you get a battle-tested solution that has saved businesses thousands of hours. Let's automate your workflow today.

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.