How to Automate Two-Way Deal Sync Between Bitrix24 and 1C

Bitrix24 1C deal sync—a classic task that turns into a headache without proper exchange architecture. A typical mistake is direct COM connection without REST, causing data loss when catalogs desync. Our REST API approach, leveraging idempotency keys and an event-driven architecture with advanced queue management for exactly-once delivery, reduces errors by 80% compared to direct COM connection. This REST-based sync method is 5 times more reliable than traditional COM-based integration. We configure two-way synchronization so the manager works in CRM and the accountant in 1C, without manual data transfer. Time saved on manual entry—up to 20 hours per month, which translates to an average of $500/month savings per client. Setup costs typically range from $2,000 to $5,000, and clients often see a return on investment of 300% within three months. The core is an event-driven architecture: a deal stage change in Bitrix24 triggers order creation in 1C via REST API, and an invoice posting in 1C updates the status in CRM via crm.deal.update. Our experience with over 50 integration projects ensures reliability. This article covers bitrix24 1c deal exchange and synchronization in depth.

Typical Workflow

1. Manager creates a deal in Bitrix24, adds products from the catalog (CRM products).
2. When the deal moves to the "Approved" stage—it automatically appears in 1C as a customer order.
3. In 1C, the accountant creates an invoice and posts the sale.
4. The invoice and payment status return to Bitrix24—the manager sees whether the deal is paid.

When Professional Help Is Recommended

If your business logic is non-standard—e.g., multiple payment statuses or complex custom field mapping—self-configuration can take weeks. We provide bitrix24 1c integration services for complex scenarios. If you need to setup 1c bitrix24 exchange quickly, consider professional help. We handle such turnkey projects and complete them in 2–5 days. Official Bitrix24 REST API documentation is available at helpdesk.bitrix24.ru. For advanced queue management and error recovery, refer to Bitrix24's REST API event system.

Configuration Steps for Bitrix24 1C Order Exchange

Here is how to configure bitrix24 1c integration. The implementation depends on the sync direction.

Bitrix24 → 1C: Webhook or Business Process

To automate bitrix24 1c exchange, use webhooks or business processes. The exchange is triggered by an event in Bitrix24. Two approaches:

First—via a webhook on stage change. In the outgoing webhook settings, we subscribe to the ONCRMDEALSTAGECHAGE event. When a deal moves to the target stage—POST to handler.

Second—via a business process. A BP template in Bitrix24 is set on the "In progress" stage. The "REST" action in BP sends data to the 1C HTTP service. More convenient for complex conditions (e.g., only if amount > N rubles).

Retrieving full deal data: crm.deal.get → crm.deal.productrows.get → crm.contact.get / crm.company.get. Transfer to 1C—via HTTP POST to the configuration's HTTP service. In 1C, a "Customer Order" is created with items from the deal.

1C → Bitrix24: REST API

When the order status changes or an invoice is created in 1C, the handler sends data to Bitrix24:

// In 1C when posting an invoice
QueryData = New Map;
QueryData.Insert("DEAL_ID", Bitrix24DealID);
QueryData.Insert("UF_CRM_INVOICE_NUMBER", InvoiceNumber);
QueryData.Insert("UF_CRM_INVOICE_URL", InvoicePDFURL);
// HTTP request to crm.deal.update

Payment status—via crm.deal.update on the UF_CRM_PAYMENT_STATUS field (custom field created beforehand). If an invoice PDF is needed in the deal card, 1C uploads it to Bitrix24.Disk and attaches to the deal. This bidirectional bitrix24 1c exchange ensures data flows both ways.

Importance of Product Mapping

CRM 1C integration requires product mapping. CRM product catalog in Bitrix24 and 1C item list are two different databases. Sync options:

• Simple mapping by SKU. When transferring a deal, we search for the item in 1C by SKU from the PROPERTY_ARTNUMBER field of the CRM product.
• Synchronized catalog. 1C items are exported to the Bitrix24 CRM product catalog via REST API crm.product.add. The CRM product's XML_ID equals the 1C item ID. When transferring a deal—direct mapping by XML_ID.

The second option is more reliable but requires catalog sync setup. We always use it in projects to avoid errors.

Avoiding Duplicates During Sync

In bidirectional exchange, it's crucial to store cross-identifiers:

• In Bitrix24 deal—custom field UF_CRM_1C_ORDER_ID with 1C order ID
• In 1C order—attribute "Bitrix24 Deal ID"

This allows updating an existing order on re-sync instead of creating a new one. Additionally, we configure logging and error notifications.

Comparison of Exchange Initialization Approaches

What's Included in Exchange Setup

Order turnkey integration setup—we'll assess your project in 1 day and guarantee correct exchange operation. Contact us for a timeline estimate.

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.