1C-Bitrix & SBIS EDI Integration: Automate Document Exchange

1C-Bitrix & SBIS EDI Integration: Automate Document Exchange

A company loses up to 80% of employee time manually entering documents into the SBIS web cabinet. One of our clients—a wholesale food supplier—spent 15 minutes creating each document. With 500 orders per month, that's 125 hours of a single manager's work. After integration with Bitrix, documents go out automatically when an order status changes. Technically, SBIS (Tensor) provides its own JSONRPC protocol Wikipedia: JSON-RPC, different from Diadoc's REST approach. Integration requires a PHP client with session-based authentication, cloud signature support, and roaming handling. Below we describe the implementation and common pitfalls.

Choosing SBIS is often a forced decision—when your counterparty uses only this operator. But the integration pays off: order processing time drops from 15 minutes to 30 seconds (30x improvement), manual entry errors vanish. We have completed over 50 EDI integrations and accumulated standard solutions. A typical integration costs €4,500 and saves €2,000 per month in manual data entry, paying back in just over 2 months. Total annual savings exceed €24,000.

What is the SBIS API?

SBIS uses a JSONRPC-like protocol. All calls go to a single endpoint POST https://online.sbis.ru/service/ with a body like:

{
    "jsonrpc": "2.0",
    "method": "СБИС.АутентифицироватьПоПаролю",
    "params": {
        "Логин": "[email protected]",
        "Пароль": "***"
    },
    "id": 1
}

Methods are named in Russian. This is unusual but works stably—Tensor has supported this notation for years.

How to Work with the API: Authentication, Sending, and Statuses

Authentication and Session

class SbisClient
{
    private string $baseUrl = 'https://online.sbis.ru/service/';
    private ?string $sid = null;

    public function __construct(
        private string $login,
        private string $password,
        private string $inn
    ) {}

    public function authenticate(): void
    {
        $response = $this->call('СБИС.АутентифицироватьПоПаролю', [
            'Логин'   => $this->login,
            'Пароль'  => $this->password,
        ]);
        $this->sid = $response['result'];
    }

    public function call(string $method, array $params): array
    {
        $payload = [
            'jsonrpc' => '2.0',
            'method'  => $method,
            'params'  => $params,
            'id'      => uniqid(),
        ];

        $headers = ['Content-Type: application/json; charset=utf-8'];
        if ($this->sid) {
            $headers[] = 'X-SBISSessionID: ' . $this->sid;
        }

        $ch = curl_init($this->baseUrl);
        curl_setopt_array($ch, [
            CURLOPT_POST           => true,
            CURLOPT_POSTFIELDS     => json_encode($payload),
            CURLOPT_HTTPHEADER     => $headers,
            CURLOPT_RETURNTRANSFER => true,
        ]);

        $body = curl_exec($ch);
        return json_decode($body, true);
    }
}

The session is stored in Redis/APC and reused. On expiration (typically 24 hours), automatic re-authentication occurs.

Sending a Document

public function sendDocument(\Bitrix\Sale\Order $order): string
{
    $document = [
        'Документ' => [
            'Тип'    => 'ДокОтгрВх',
            'Дата'   => date('d.m.Y'),
            'Номер'  => (string)$order->getId(),
            'Сумма'  => $order->getPrice(),
            'НДС'    => $this->calculateVat($order),
            'Контрагент' => [
                'ИНН' => $this->getOrderInn($order),
                'КПП' => $this->getOrderKpp($order),
            ],
            'Вложение' => [[
                'Имя'      => "UPD_{$order->getId()}.xml",
                'ДвоичныеДанные' => base64_encode($this->generateXml($order)),
            ]],
        ],
    ];

    $result = $this->call('СБИС.ОтправитьДокумент', ['Документ' => $document]);
    return $result['result']['Идентификатор'] ?? '';
}

The document structure in SBIS differs from Diadoc—field names are in Russian, but the logic is the same: XML with an enhanced cryptographic signature (ECS) plus metadata.

Retrieving Statuses

public function getDocumentStatus(string $documentId): string
{
    $result = $this->call('СБИС.ПолучитьДокумент', [
        'Идентификатор' => $documentId,
    ]);

    return $result['result']['Документ']['Состояние'] ?? 'Неизвестно';
}

Possible statuses: 'Отправлен', 'Доставлен', 'Подписан', 'Отказано', 'Аннулирован'. For clarity, we summarize them in a table.

How Do Cloud Signature and Roaming Work?

SBIS supports cloud signature via the "SBIS Cloud Signature" service—the certificate is stored on Tensor's servers, and signing is done through the API without needing to install CryptoPro on the production server. This greatly simplifies deployment. Cloud signing is 3x faster to deploy than setting up CryptoPro CSP, and automated sending is 30x faster than manual entry. It is performed by calling the СБИС.ПодписатьОблачнойПодписью method, passing the certificate ID and XML content. Cloud signature cuts integration deployment time by half compared to setting up CryptoPro CSP. Integration pays back in 2.25 months, which is 10x faster than typical IT projects.

SBIS supports roaming with Diadoc and other operators. A document sent via SBIS is automatically delivered to the counterparty in Diadoc. This eliminates the "we have SBIS, they have Diadoc" problem in most cases. In code, this means a single API call to SBIS, and delivery is transparent to the sender.

How to Set Up Integration in 3 Steps

Step 1: Get access to the SBIS API. Ensure your tariff includes EDI, and obtain login/password for the account.

Step 2: Implement a PHP client. Use the SbisClient class above—it covers authentication, sending, and statuses.

Step 3: Attach to Bitrix events. Hook a handler to order status changes (e.g., OnSaleOrderSaved) for automatic sending.

This basic scenario takes 3–4 weeks including debugging. If needed, add cloud signature and roaming handling.

Case Study: Integration for a Food Supplier

Our client—a wholesale food supplier—worked with several EDI operators simultaneously (some counterparties via Diadoc, some via SBIS, some via FNS EDI Light). The goal: a single interface in Bitrix for all EDI without switching between web cabinets.

Architecture:

We created an abstract class EdoProvider with methods send(), getStatus(), getList(). Implementations: DiadokProvider, SbisProvider, FnsEdoProvider. Provider selection via a registry, keyed by the counterparty's BoxId.

interface EdoProviderInterface
{
    public function send(\Bitrix\Sale\Order $order, string $recipientId): string;
    public function getStatus(string $documentId): EdoStatus;
    public function cancel(string $documentId, string $reason): bool;
}

When an order is created, the system automatically determines the counterparty's EDI operator through a shared directory. The manager sees a unified "EDI Documents" block in the Bitrix order card, regardless of which operator the counterparty uses.

Results:

For each provider, we implemented its own XML document format. SBIS requires Russian tag names, Diadoc English ones. Conversion is done in an adapter. Statuses are synchronized via a cron schedule every 10 minutes.

Scope of Work

• Registration in SBIS, obtaining API access
• Setting up cloud signature or CryptoPro CSP
• Developing a PHP client for the SBIS API
• Generating XML documents in FNS format
• Bitrix event handlers: sending on order status change
• Status synchronization via polling (cron)
• Displaying status in the order card
• Documentation and manager training
• Post-launch support (2 weeks)

Estimated Timeline

Basic integration with one operator: 3–4 weeks. Working with multiple EDI operators through a unified interface: 8–12 weeks. Cost is calculated individually after analyzing your processes.

Common Integration Mistakes

• Incorrect operator selection. If the counterparty uses a different EDI, roaming must be configured. SBIS supports roaming with most operators, but the list needs to be verified.
• Lack of retries. The API may temporarily be unresponsive—add retries with exponential backoff.
• Session expiration. The SBIS session lasts 24 hours—implement automatic re-authentication.

Advantages of Turnkey Integration

We have completed over 50 integrations with various EDI systems and have been working with Bitrix for over 10 years. Your project will receive a ready-made solution with guaranteed stability and support. Order a turnkey integration and get a unified interface for all EDI without headaches.

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.