Developing Bitrix24 Integration with Logistics Systems

When a manager closes a deal in CRM, and logistics staff manually transfer data to TMS, up to 30 minutes are lost per request — amounting to hundreds of hours of operational time per month.

Manual entry errors (wrong address, incorrect weight) lead to re-sorting and repeat deliveries, producing extra expenses. We develop integration between Bitrix24 and your logistics system — from request creation to tracking and notifications. A request is automatically generated upon a deal stage change, recipient data is pulled from the contact, and items from the deal. Processing time drops from hours to seconds, and errors to zero. Turnkey, with stable performance guarantees and up to 60% savings in the delivery department's time. Our delivery automation solution covers all key processes: from request to return.

What logistics systems and APIs do we integrate?

1C:TMS Logistics. 1C HTTP services, data format — JSON or XML. Main operations: creating a transport request, getting status, attaching documents.

MySklad. REST API with OAuth 2.0. Rich documentation, sandbox. Supports order management, shipments, stock, returns.

CDEK API v2. REST API, JWT authentication. Cost calculation, order creation, tracking, pickup point list.

Yandex.Delivery / DPD / Boxberry / PEK. Each has its own REST API, differing in data structure and authentication mechanisms. For universal integration with multiple carriers, we use the adapter pattern: a single interface inside the application, with a separate implementation for each carrier.

WMS systems (Manhattan, SAP Extended Warehouse Management, 1C:WMS). Typically SOAP or proprietary API. Integration is more complex due to legacy protocols.

According to CDEK API documentation, version v2 handles up to 100 requests per minute with an average response time of 1.5 seconds.

Why is asynchronous processing critical for integration?

Logistics APIs are unstable: rate limits, timeouts, unavailability. Therefore, we build an async queue (Redis + Bitrix built-in agents). The webhook from Bitrix24 is accepted instantly, while the logistics API call and status updates are executed asynchronously. This is 2-3 times more reliable than a synchronous approach and does not block managers' work. For example, with a 30-second timeout, a synchronous request would block the interface, while an asynchronous approach simply retries after 30 seconds.

Integration scenarios

Deal → delivery request. A deal in Bitrix24 moves to the "Sent for shipment" stage — a webhook fires, the adapter creates a request in the logistics system. The deal card gets the request ID (UF_LOGISTICS_ORDER_ID) and tracking number.

Delivery statuses in CRM. The logistics system sends a webhook on status change: "Accepted at warehouse", "In transit", "Delivered", "Return". The adapter updates the deal stage via crm.deal.update and adds a timeline comment via crm.timeline.comment.add.

Delivery cost calculation. At order creation (in a deal or online store) — request to the carrier API for cost calculation by weight, dimensions, and address. Result saved in deal or invoice fields.

Pickup point selection. For integrations with CDEK, Boxberry, Russian Post — a pickup point chooser on a map inside the deal card. Implemented as a Bitrix24 embedded application with a map (Leaflet + pickup point data from the carrier's API).

Returns. The customer initiates a return — a smart process "Return" is created in CRM, triggering the procedure in the logistics system: pick-up from customer, warehouse acceptance, item inspection status.

Adapter architecture

We build a PHP application that:

1. Listens to Bitrix24 webhooks (deal stage change event)
2. Maps deal data to the logistics system format
3. Calls the logistics API
4. Writes the response back to Bitrix24

Bitrix24 (stage change webhook)
  ↓
Adapter (validation, data transformation)
  ↓
Logistics system API
  ↓ (async — via callback or polling)
Adapter (status processing)
  ↓
Bitrix24 REST API (crm.deal.update, crm.timeline.comment.add)

Example webhook handler in PHP:

function handleBitrixWebhook($event) {
    $dealId = $event['data']['FIELDS']['ID'];
    $deal = CRest::call('crm.deal.get', ['id' => $dealId]);
    $address = $deal['UF_DELIVERY_ADDRESS'];
    $phone = $deal['UF_DELIVERY_PHONE'];
    // Call CDEK API
    $cdek = new CdekApiClient();
    $order = $cdek->createOrder([
        'recipient' => ['name' => $deal['CONTACT_NAME'], 'phone' => $phone],
        'address' => $address,
        'items' => $deal['PRODUCTS']
    ]);
    CRest::call('crm.deal.update', [
        'id' => $dealId,
        'fields' => ['UF_CDEK_ORDER_ID' => $order['uuid']]
    ]);
}

Field mapping

Typical set of fields to pass to the logistics system:

Weight and dimensions are a separate challenge. In Bitrix24, they are stored in the product card (catalog), but in a CRM deal they are taken from crm.product.list by PRODUCT_ID. If integration with a warehouse or 1C is not set up, weight characteristics may be missing — a fallback is needed (default values by product category or manual input). For exchange with 1C via CommerceML, we additionally configure nomenclature synchronization.

Tracking and customer notifications

After receiving the tracking number, we build a notification chain. A Bitrix24 robot sends an SMS or email to the customer (via integration with a mailing service): "Your order has been handed over for delivery, tracking number: XXX". On each status change — similarly. This reduces call center load by 4 times and increases customer satisfaction. The status check agent runs every 15 minutes, and notifications are sent within 5 minutes of a status change.

For automatic delivery status retrieval, we use two approaches:

• Webhook from carrier — the carrier notifies on status change. Best option, but not supported by all.
• Polling — a Bitrix agent queries the status every N minutes by tracking number. Works with any carrier, creates API load.

What to do when the logistics API fails?

Logistics APIs are unstable and have specific limitations:

• Rate limiting — we pause between requests, cache reference data (pickup point list, tariffs). For example, CDEK limits 100 requests per minute.
• Address errors — the carrier cannot determine delivery zone by address. A UI for manual correction with manager notification is needed.
• Blocked requests — if logistics blocks a request (incorrect data), the manager must see this in CRM, not learn from the customer.

For exception handling, we use a queue with retries (exponential backoff up to 5 times: 1, 2, 4, 8, 16 minutes) and CRM notifications. If after all retries the API is unavailable, a task is created for the operator with full error context.

What's included in the work

• Analysis of your logistics system APIs and scenario selection
• Adapter development with async queue and retries
• Configuration of deal fields, smart processes, and Bitrix24 business processes (Bizproc) for automatic logistics
• Creation of a pickup point selection widget (if required)
• Automatic customer notifications via SMS and email based on statuses
• Testing on real requests in a test environment
• Technical documentation and employee training
• 6-month warranty on integration after delivery

Development stages

A completed integration reduces the time from deal creation to delivery request from hours to seconds — and eliminates manual data entry errors. Order integration — get a working solution with a 6-month warranty. Contact us for a project assessment: we'll select the optimal turnkey solution.

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.