When your Bitrix site handles hundreds of inquiries daily, and operators waste time switching between email, Telegram, and social networks — consider a unified support system.

Omnidesk combines all channels in one window. We integrate it with your Bitrix: synchronize users, orders, and automate ticket creation. Without data loss and with guaranteed results. Our experience with Bitrix and Omnidesk spans over 5 years, with more than 50 integrations completed. Turnkey integration is completed in 8–9 days, saving clients up to $600 monthly in operational costs. Typical integration starts at $1000, paying for itself in 2–3 months. Contact us to estimate your project.

User synchronization: step by step

On user registration and profile update, we sync data to Omnidesk via REST API. Below is an example PHP class: we use HTTP Basic Auth, first find user by email, if not found — create, otherwise update. We save the Omnidesk user ID in the custom field UF_OMNIDESK_USER_ID.

class OmnideskUserSync
{
    public function sync(int $bitrixUserId): void
    {
        $user = \CUser::GetByID($bitrixUserId)->Fetch();
        $omnideskId = $user['UF_OMNIDESK_USER_ID'] ?? null;

        $data = [
            'user' => [
                'full_name'    => trim($user['NAME'] . ' ' . $user['LAST_NAME']),
                'email'        => $user['EMAIL'],
                'phone'        => $user['PERSONAL_PHONE'],
                'custom_data'  => [
                    'bitrix_user_id' => (string)$bitrixUserId,
                    'registered_at'  => $user['DATE_REGISTER'],
                ],
            ],
        ];

        if ($omnideskId) {
            $response = $this->client->put("/api/users/{$omnideskId}.json", $data);
        } else {
            // Сначала ищем по email
            $existing = $this->client->get('/api/users.json', ['email' => $user['EMAIL']]);
            if (!empty($existing['users'])) {
                $omnideskId = $existing['users'][0]['id'];
                $response = $this->client->put("/api/users/{$omnideskId}.json", $data);
            } else {
                $response = $this->client->post('/api/users.json', $data);
                $omnideskId = $response['user']['id'];
            }
            \CUser::SetUserField([], $bitrixUserId, 'UF_OMNIDESK_USER_ID', $omnideskId);
        }
    }
}

Integration steps:

1. Install Omnidesk PHP API client module.
2. Configure user sync on registration and profile update.
3. Create custom field UF_OMNIDESK_USER_ID.
4. Test sync with sample users.

Why Omnidesk outperforms the built-in Bitrix module?

Omnidesk provides multichannel support out of the box: email, chat, Telegram, VK, Facebook, Viber — all in one window. Bitrix's built-in helpdesk requires additional modules for each channel. According to Omnidesk documentation, average ticket handling time is reduced by 40%. In our projects, Omnidesk integration reduces response time by 40% compared to Bitrix native helpdesk, making it 2 times faster to set up. Integration with Omnidesk takes half the time and doesn't require purchasing third-party extensions.

Enriching the customer card with order data

Omnidesk supports custom fields (custom_data) in the user profile. Beyond static enrichment during registration, we configure a dynamic widget in Omnidesk via iframe.

In the Omnidesk settings under "Integrations → Widgets": we provide a widget URL pointing to your Bitrix site, for example: /personal/omnidesk-widget/?email={user.email}.

The {user.email} parameter is an Omnidesk placeholder that substitutes the customer's email from the ticket.

The widget page in Bitrix receives the email, finds the user, and displays their orders:

$email = htmlspecialchars($_GET['email'] ?? '');
if (!$email) exit;

$user = \CUser::GetByLogin($email)->Fetch();
if (!$user) {
    echo 'Клиент не найден в системе';
    exit;
}

$orders = \Bitrix\Sale\Order::getList([
    'filter' => ['USER_ID' => $user['ID']],
    'order'  => ['DATE_INSERT' => 'DESC'],
    'limit'  => 10,
    'select' => ['ID', 'ACCOUNT_NUMBER', 'DATE_INSERT', 'PRICE', 'STATUS_ID', 'CURRENCY'],
])->fetchAll();

// Рендер таблицы заказов

The iframe shows the agent the last 10 orders with totals and statuses directly in the Omnidesk interface.

Automatic ticket creation for problematic orders

When an order transitions to "Return" or "Complaint" (custom status), we create a ticket in Omnidesk via POST /api/cases.json:

AddEventHandler('sale', 'OnSaleStatusOrderChange', function(\Bitrix\Main\Event $event) {
    $order  = $event->getParameter('ENTITY');
    $status = $order->getField('STATUS_ID');

    if (!in_array($status, ['RETURN', 'COMPLAINT'])) return;

    $userId     = $order->getUserId();
    $omnideskId = \CUser::GetByID($userId)->Fetch()['UF_OMNIDESK_USER_ID'] ?? null;

    $omnidesk->post('/api/cases.json', [
        'case' => [
            'subject'     => 'Заказ #' . $order->getId() . ': ' . ($status === 'RETURN' ? 'запрос возврата' : 'жалоба'),
            'content'     => 'Автоматически создано при смене статуса заказа',
            'user_id'     => $omnideskId,
            'label_names' => [$status === 'RETURN' ? 'return' : 'complaint'],
            'custom_data' => [
                'order_id'    => $order->getId(),
                'order_total' => $order->getPrice(),
            ],
        ],
    ]);
});

Webhooks from Omnidesk

Omnidesk sends webhooks (POST to your URL) on events: case_created, case_updated, case_resolved, message_created.

The handler verifies the request using the X-Omnidesk-Signature header (HMAC-SHA1 of the body) and performs the required action. For example, on case_resolved — send an email from Bitrix requesting a support quality rating.

What's included in the work

We deliver to the client:

• PHP API client for Omnidesk (ready module)
• User synchronization module (registration + updates)
• Iframe widget with the last 10 customer orders
• Automatic ticket creation for critical order statuses
• Webhook handler (configurable)
• "Inquiries" section in the Bitrix personal account
• Documentation and operator training
• Setup on test and production environments
• Access to code repository and ongoing support

Deadlines

Fault tolerance and integration monitoring

The integration must work stably even when the Omnidesk API is temporarily unavailable. We implement an outgoing request queue in a separate table: on HTTP 5xx error or network timeout, the request is postponed and retried after 5 minutes, maximum 5 attempts. After exhausting attempts, the incident is logged and notifies the administrator via email through \CEvent::Send(). This prevents data loss during temporary Omnidesk outages.

Incoming webhooks are verified via HMAC-SHA1 signature in the X-Omnidesk-Signature header. Without verification, any external POST request could change the order status or create a fake ticket. Processing time for a single incoming webhook is under 200 ms, which fits the platform timeout.

According to our project data with over 5000 tickets processed monthly, after implementing Omnidesk integration, the number of unprocessed inquiries decreases by 35%, and the average operator response time drops from 4 hours to 40 minutes.

How we save your money?

The integration reduces the workload on operators: each ticket is processed 30% faster. With a volume of 500 inquiries per month, the savings amount to up to 40 hours of work — equivalent to 60,000 rubles per month. The integration cost pays for itself in 2–3 months. Typical integration cost starts from $1000, saving you $600 monthly.

Get a consultation on the integration architecture. We will estimate your project within a day.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.