Streamline Support: Integrating 1C-Bitrix with Usedesk

What happens when support tickets live separately from orders?

Operators have to jump between Usedesk and Bitrix to understand a client's history. This slows responses, increases error rates, and reduces LTV. Our solution links tickets with orders in real time, automatically passes client data, and personalizes the widget. Result — the operator sees the full picture in one window, and the client gets a quick answer without extra questions. With 5 years of experience and over 100 successful integrations, our team ensures seamless operation. We integrate your Usedesk helpdesk with Bitrix via REST API — operator time savings up to 80%. This 1C-Bitrix Usedesk integration syncs tickets and orders in real time, providing all key features: sync clients Usedesk Bitrix, personalize Usedesk widget, handle webhooks Usedesk Bitrix.

Problems the integration solves

• Data gap: the order exists in Bitrix, but it's not visible in the ticket. The client writes asking about their order — the operator searches for the number manually. Every third client repeats the request, losing up to 15% LTV. For a store with 1500 orders per month, that's 225 lost customers.
• Manual transfer: operators copy email, phone, history from one system to another — wasting up to 30 seconds per ticket. At 200 tickets per day, that's 100 minutes of wasted work. The cost of errors is estimated at 50,000 rubles monthly.
• Lack of context: without integration, it's impossible to automatically offer a discount to a repeat client or send a survey after ticket closure.

Benefits of API integration over manual import

API integration processes requests 10 times faster than manual data import. Data errors are reduced to zero, whereas with manual transfer, the error rate reaches 5%. For a store with 1000 orders per day, manual import takes up to 2 hours of operator work — versus 5 minutes for automatic synchronization. Our clients report an average saving of 50,000 rubles per month after integration. Integration cost typically ranges from 40,000 to 80,000 rubles depending on complexity. The integration pays for itself within a few months, with average monthly savings of 50,000 rubles.

Real-time linking of tickets with orders

We use custom fields in Usedesk. For each ticket, you can specify the Bitrix order ID. A webhook when a ticket is created updates this field. The operator sees a link to the order in the Usedesk interface and can go to Bitrix with one click. Reverse flow: when the order status changes, we send a comment to the ticket.

Linking tickets with orders: synchronization and data transfer

We use the REST API of Usedesk and 1C-Bitrix events (OnAfterUserRegister, OnSaleOrderSaved). Everything works on standard mechanisms: agents for background tasks, tagged caching for the ticket list. Stack: PHP 8.1+, information blocks v2.0, MySQL. Full Usedesk API documentation is available at their developer portal. For cloud editions of Bitrix24, integration is available via REST API with daily request limits sufficient for a typical store; On-Premise versions have no limits.

Client synchronization

When a user registers in Bitrix (event OnAfterUserRegister), we create or find the client in Usedesk. We store the mapping in the user field UF_USEDESK_CLIENT_ID:

AddEventHandler('main', 'OnAfterUserRegister', function(&$fields) {
    $email = $fields['LOGIN']; // In Bitrix, login is often the email

    // Look for an existing client by email
    $response = $usedesk->get('/clients', ['email' => $email]);
    if (!empty($response['clients'])) {
        $udClientId = $response['clients'][0]['id'];
    } else {
        // Create a new one
        $response = $usedesk->post('/clients', [
            'name'  => $fields['NAME'] . ' ' . $fields['LAST_NAME'],
            'email' => $email,
            'phone' => $fields['PERSONAL_PHONE'] ?? '',
            'custom_fields' => [
                ['id' => USEDESK_CF_BITRIX_USER_ID, 'value' => $fields['ID']],
            ],
        ]);
        $udClientId = $response['client']['id'];
    }

    // Save the mapping
    \CUser::SetUserField([], $fields['ID'], 'UF_USEDESK_CLIENT_ID', $udClientId);
});

Passing order data into the ticket

When a new order is created (event OnSaleOrderSaved), we write data into the client's custom fields in Usedesk. This enriches the client card with purchase history:

AddEventHandler('sale', 'OnSaleOrderSaved', function(\Bitrix\Main\Event $event) {
    $order = $event->getParameter('ENTITY');
    if ($order->isNew()) {
        $userId = $order->getUserId();
        $udClientId = \CUser::GetByID($userId)->Fetch()['UF_USEDESK_CLIENT_ID'] ?? null;
        if (!$udClientId) return;

        // Add a note to the client in Usedesk
        $usedesk->post("/clients/{$udClientId}/comments", [
            'message' => sprintf(
                'New order #%d for %s RUB. Status: %s',
                $order->getId(),
                number_format($order->getPrice(), 2, ',', ' '),
                $order->getField('STATUS_ID')
            ),
            'type' => 'note',
        ]);
    }
});

Usedesk widget and personal account

Widget personalization

Usedesk provides a JS widget. For personalization with an authorized user, we pass their data:

(function(d, w, c) {
    w.usedeskSettings = {
        company_id: "<?= USEDESK_COMPANY_ID ?>",
        <?php if ($USER->IsAuthorized()): ?>
        user: {
            name: "<?= htmlspecialchars($USER->GetFullName()) ?>",
            email: "<?= htmlspecialchars($USER->GetEmail()) ?>",
            fields: {
                custom_id: "<?= $USER->GetID() ?>"
            }
        },
        <?php endif; ?>
    };
    var s = d.createElement("script");
    s.type = "text/javascript"; s.async = true;
    s.src = "https://secure.usedesk.ru/widget.js";
    d.getElementsByTagName("head")[0].appendChild(s);
})(document, w, c);

This allows Usedesk to automatically link the chat session with the client card by email.

Displaying tickets in the personal account

In the Bitrix personal account, we add a "My Requests" section. The component fetches the client's tickets through the Usedesk API by client_id:

$udClientId = $USER->GetParam('UF_USEDESK_CLIENT_ID');
$tickets = $usedesk->get('/tickets', [
    'client_id' => $udClientId,
    'per_page'  => 20,
    'page'      => (int)$_GET['page'] ?: 1,
]);

The list of tickets is cached for 60 seconds (\Bitrix\Main\Data\Cache).

Handling webhooks from Usedesk

// /api/usedesk-webhook.php
$payload = json_decode(file_get_contents('php://input'), true);

// Verify signature
$sig = hash_hmac('sha256', file_get_contents('php://input'), USEDESK_WEBHOOK_SECRET);
if (!hash_equals($sig, $_SERVER['HTTP_X_USEDESK_SIGNATURE'] ?? '')) {
    http_response_code(403); exit;
}

if ($payload['event'] === 'ticket.resolved') {
    $email = $payload['ticket']['client']['email'] ?? '';
    if ($email) {
        \Bitrix\Main\Mail\Event::send([
            'EVENT_NAME' => 'SUPPORT_RESOLVED_REVIEW_REQUEST',
            'LID'        => SITE_ID,
            'C_FIELDS'   => ['EMAIL' => $email, 'TICKET_ID' => $payload['ticket']['id']],
        ]);
    }
}

Comparison: API integration vs manual import

What's included

1. Setting up the API client — creating a PHP library to work with Usedesk (Guzzle or cURL).
2. Client synchronization — mapping Bitrix users to Usedesk via registration events.
3. Order transfer — automatically enriching the client card with purchase history.
4. Personalized widget — passing the user's name, email, and ID to the widget.
5. Webhook handler — receiving events from Usedesk (ticket statuses, new messages).
6. Personal account — a component for displaying tickets on the Bitrix site.
7. Documentation and training — architecture description, instructions for operators.

Process and timeline

We work in iterations: analysis → design → implementation → testing → deployment.

The estimated timeline is 7 to 9 working days. The cost is calculated individually for your project. We guarantee stable operation of the integration and provide post-project support: bug fixes, modifications, consultations.

Order the integration now — contact us for a consultation. Get a personalized estimate of timeline and cost.

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.