Bitrix to MoeDelo Integration: Order Exchange Automation

Imagine: every order from your Bitrix online store needs to be manually entered into MoeDelo — as a sales, create a counterparty, issue an invoice. This takes 10–15 minutes per order. With 50 orders per day, that's up to 12 hours of routine per month. Errors in details, incorrect VAT, missed payments — typical consequences. We automate this process turnkey, reducing processing time by 80% and minimizing errors. For a store with 200 orders per month, this saves approximately $300–$500 monthly on manual labor. Our experience with MoeDelo integrations spans over 15 projects, guaranteeing stable 24/7 synchronization. We'll assess your project for free — just contact us.

What Problems We Solve

Manual Counterparty Entry

Each new customer requires creating a card in MoeDelo: TIN, name, address. With repeat orders, duplicates easily appear. Our algorithm automatically searches for a counterparty by email or TIN and creates one only if not found.

VAT Calculation Errors

VAT rates vary: 0%, 10%, 20%. Manual transfer leads to mistakes, causing discrepancies with tax authorities. The integration takes the rate from the product properties in Bitrix — eliminating human error.

Lost Payments

A paid order is not always reflected in MoeDelo as a receipt. We hook into the OnSalePaymentPaid event — payment is automatically recorded as an incoming payment. This is especially important for 54-FZ and shift closure.

How to Integrate Bitrix with MoeDelo?

We use the public MoeDelo API with token-based authorization. On the Bitrix side, we write a PHP client (8.1+), use infoblocks v2.0 and ORM. Each order goes through the chain: counterparty → sales document → invoice (optional) → payment. For returns, we create a return document.

Here is an example of creating a counterparty (code snippet):

class MoeDeloClient
{
    private string $apiKey;
    private string $baseUrl = 'https://api.moedelo.org';

    public function request(string $method, string $endpoint, array $body = [], array $query = []): array
    {
        $url = $this->baseUrl . $endpoint;
        if ($query) {
            $url .= '?' . http_build_query($query);
        }

        $ch = curl_init($url);
        curl_setopt_array($ch, [
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_CUSTOMREQUEST  => $method,
            CURLOPT_HTTPHEADER     => [
                'Content-Type: application/json',
                "X-DM-Auth-Token: {$this->apiKey}",
            ],
            CURLOPT_POSTFIELDS => in_array($method, ['POST', 'PUT', 'PATCH'])
                ? json_encode($body) : null,
        ]);

        $json     = curl_exec($ch);
        $httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
        curl_close($ch);

        if ($httpCode >= 400) {
            throw new \RuntimeException("MoeDelo API {$httpCode}: {$json}");
        }

        return json_decode($json, true) ?? [];
    }
}

Counterparties

For individuals (B2C orders without details), we create a counterparty of type individual:

public function findOrCreateContragent(\Bitrix\Sale\Order $order): int
{
    $props  = $order->getPropertyCollection();
    $email  = $props->getUserEmail();
    $name   = $props->getBuyerName();
    $phone  = $props->getPhone();
    $inn    = $props->getItemByOrderPropertyCode('INN')?->getValue();

    // Search by email
    $search = $this->client->request('GET', '/api/v1/counteragents', [], ['search' => $email]);
    foreach ($search['data'] ?? [] as $ca) {
        if ($ca['email'] === $email) {
            return $ca['id'];
        }
    }

    // Create
    $isLegal = !empty($inn);
    $payload = $isLegal ? [
        'type'    => 'legal_entity',
        'name'    => $props->getItemByOrderPropertyCode('COMPANY')->getValue(),
        'inn'     => $inn,
        'kpp'     => $props->getItemByOrderPropertyCode('KPP')?->getValue() ?? '',
        'email'   => $email,
        'phone'   => $phone,
    ] : [
        'type'     => 'individual',
        'fullname' => $name,
        'email'    => $email,
        'phone'    => $phone,
    ];

    $result = $this->client->request('POST', '/api/v1/counteragents', $payload);
    return $result['id'];
}

Sales Document (Invoice / Waybill)

public function createSaleDocument(\Bitrix\Sale\Order $order, int $contragentId): int
{
    $items = [];
    foreach ($order->getBasket() as $basketItem) {
        // VAT from product properties
        $vatRate  = $this->resolveVatRate($basketItem->getProductId());
        $vatValue = round($basketItem->getPrice() * $basketItem->getQuantity()
            * ($vatRate / (100 + $vatRate)), 2);

        $items[] = [
            'name'      => $basketItem->getField('NAME'),
            'quantity'  => $basketItem->getQuantity(),
            'unit'      => 'pcs',
            'price'     => $basketItem->getPrice(),
            'total'     => round($basketItem->getPrice() * $basketItem->getQuantity(), 2),
            'vat_rate'  => $vatRate,  // 0, 10, 20
            'vat_value' => $vatValue,
        ];
    }

    // Discount at order level
    $discount = $order->getField('PRICE_DELIVERY') > 0 ? [
        'name'   => 'Delivery',
        'amount' => $order->getField('PRICE_DELIVERY'),
    ] : null;

    $doc = $this->client->request('POST', '/api/v1/documents/sale', [
        'date'           => date('Y-m-d'),
        'number'         => $order->getField('ACCOUNT_NUMBER'),
        'counteragent_id' => $contragentId,
        'items'          => $items,
        'shipping'       => $discount,
        'comment'        => 'Order from site #' . $order->getField('ACCOUNT_NUMBER'),
    ]);

    return $doc['id'];
}

Payment Invoice

For B2B orders, after creating the sales document, we generate an invoice:

public function createInvoice(int $documentId, \Bitrix\Sale\Order $order): string
{
    $invoice = $this->client->request('POST', '/api/v1/invoices', [
        'document_id' => $documentId,
        'due_date'    => date('Y-m-d', strtotime('+5 days')),
    ]);

    // Get invoice PDF and attach to order in Bitrix
    $pdfUrl = $invoice['pdf_url'] ?? '';
    if ($pdfUrl) {
        $this->attachInvoicePdfToOrder($order->getId(), $pdfUrl);
    }

    return $invoice['number'] ?? '';
}

Incoming Payments

AddEventHandler('sale', 'OnSalePaymentPaid', function(\Bitrix\Sale\Payment $payment) {
    $order      = $payment->getOrder();
    $docId      = MoeDeloSyncTable::getDocumentId($order->getId());
    if (!$docId) return;

    (new MoeDeloSyncService())->registerPayment($docId, $payment);
});

public function registerPayment(int $docId, \Bitrix\Sale\Payment $payment): void
{
    $this->client->request('POST', '/api/v1/payments/income', [
        'date'        => date('Y-m-d'),
        'amount'      => $payment->getSum(),
        'document_id' => $docId,
        'type'        => $payment->getPaySystem()->getField('CODE') === 'cash'
            ? 'cash' : 'bank',
        'comment'     => 'Payment for order #' . $payment->getOrder()->getField('ACCOUNT_NUMBER'),
    ]);
}

Automation via Events

Why Automation Beats Manual Entry?

Automation outperforms manual entry: each order is processed in 5 seconds instead of 10–15 minutes — 180 times faster. Manual entry errors reach 5%, while automation yields less than 0.1% — a 50 times lower error rate. Duplicate counterparties are eliminated, documents always comply with tax authority requirements. The integration pays for itself in 2–3 months by reducing manual labor — real savings.

What's Included

We deliver a complete package:

• PHP client for MoeDelo API
• Search and creation of counterparties (individuals and legal entities)
• Creation of sales documents and invoices
• Registration of payments and returns
• Synchronization table, error handling, and retry logic
• Integration documentation and staff training
• 3 months of warranty support

What Is Synchronized Automatically?

Beyond orders, we synchronize counterparties (with duplicate detection), product items (optional), reconciliation acts (on request), returns, and adjustments. All data undergoes validation before being sent to MoeDelo — eliminating format errors.

Work Process

1. Audit — analyze current Bitrix configuration, order schema, document requirements.
2. Design — agree on field mapping and error scenarios.
3. Implementation — write code, configure events, test on staging.
4. Testing — run 100+ orders, check all scenarios (payment, cancellation, return).
5. Deploy — roll out to production, monitor for 2 weeks, train staff.

Typical Mistakes in Self-Integration

Incorrect date format (API accepts only YYYY-MM-DD), lack of retry logic on timeouts (orders lost), ignoring API rate limits (30 requests per minute — a queue is needed). We account for all these details, ensuring stable integration. To handle API rate limits, we implement a queue system with exponential backoff. Failed requests are retried up to 5 times with increasing delays, ensuring no order is lost.

Timeline: basic integration from 3 weeks, extended up to 8 weeks. We assess your project for free based on your technical specifications. Contact us to discuss details. Get a consultation — we'll help you choose the optimal scope of work.

Our automatic order export to MoeDelo ensures counterparty synchronization and invoice automation. We provide 1C-Bitrix MoeDelo integration for online stores, enabling seamless document export to MoeDelo.

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.