Setting Up 1C:Comprehensive Automation and 1C-Bitrix Data Exchange

Imagine: you have 1C:Comprehensive Automation with three warehouses, two Bitrix sites, hundreds of products with properties, and the CommerceML exchange works intermittently — orders get lost, prices on the retail site don't match wholesale. Familiar? Companies choose the CA configuration when they outgrow Trade Management (UT) but aren't ready for ERP. It includes CRM, production, payroll — and data from all subsystems may be needed on the site. However, the CommerceML export mechanism in CA is inherited from UT and has the same limitations. For over 10 years, we have been setting up 1C:Comprehensive Automation exchange with 1C-Bitrix, and more than 200 projects confirm: stable synchronization is possible even in complex configurations.

What CA can do out of the box and where it falls short

CA has a built-in exchange node with the site — virtually identical to the node in UT 11. It exports: items with properties, prices (multiple types), stock balances by warehouse, and customer orders. It does NOT export out of the box: CRM data (counterparties, deals), production orders, settlement documents in a format convenient for the site.

CA peculiarity: the configuration is regularly updated, and updates sometimes affect the exchange module. If you customized the export on the CA side (added tags to XML), those customizations may break after configuration updates. Always implement changes in a configuration extension, not in the configuration itself. According to 1C documentation, extensions are designed to customize standard configurations without modifying the configuration itself.

Why configuration extension is the only safe way to customize

Using an extension is 100 times more reliable than direct editing — no customization is lost during updates. The solution is to use configuration extensions (BSP 3.1+, 1C 8.3). All changes to exchange rules, directories, and registers are implemented in a separate 'Extension' object. When the standard configuration is updated, the extension remains untouched. This approach has been repeatedly justified — our case with a distributor with three warehouses showed: 4 CA updates in a year, no customization suffered. Setting up 1C:Comprehensive Automation and 1C-Bitrix exchange requires understanding both systems, but with an extension, you are protected from surprises.

How to avoid losing customizations during 1C updates

Create a configuration extension in 1C. This guarantees that all changes to exchange rules remain operational after standard configuration updates. We always use extensions, and over years of work, there has not been a single case where a customization broke during an update.

Step-by-step exchange setup guide

1. Create a configuration extension in 1C.
2. Configure the exchange node: site URL, login/password, organization, price type, warehouses.
3. Configure the price type mapping on the Bitrix side.
4. If there are reference properties, add the OnIBlockCMLImport2ElementAdd handler.
5. Map order statuses in both systems.
6. Run a test exchange and check all entities.

Configuring the exchange node in CA

Path: Administration → Data Exchange → Exchange with site on 1C-Bitrix.

Create a new node. Required parameters:

• Site URL — /bitrix/admin/1c_exchange.php
• Login/password — a Bitrix user with exchange rights (group 'Administrators' or custom role)
• Organization — which organization to export (if multiple)
• Price type — one or more price groups
• Warehouses — select specific warehouses or 'all'

Price nuance: in CA, you can configure export of multiple price types simultaneously. On the Bitrix side, each price type is a separate price type in the trade catalog. The mapping is configured in Settings → Trade Catalog → Price Types.

Item properties: a typical problem

In 90% of cases, property problems are solved by adding a handler. In CA, item properties are stored in the information register ЗначенияСвойствОбъектов. During export, they appear in the Свойства section of XML. Bitrix reads them and creates infoblock properties.

The problem arises when a property in CA is a reference type (e.g., 'Manufacturer' → counterparty directory). Bitrix receives the GUID of the counterparty instead of its name. A handler is needed that, during XML processing, replaces the GUID with a string value.

// Exchange event handler
AddEventHandler('catalog', 'OnIBlockCMLImport2ElementAdd',
    'fixReferenceProperties');

function fixReferenceProperties(&$arFields, &$arProps, $arXML) {
    // If property value is a GUID (format 8-4-4-4-12)
    foreach ($arProps as $propCode => &$propVal) {
        if (preg_match(
            '/^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i',
            $propVal
        )) {
            // Look up value in mapping table
            $propVal = getPropertyValueByGuid($propCode, $propVal);
        }
    }
}

How to exchange orders between Bitrix and 1C?

Orders from Bitrix to CA are transmitted in CommerceML format — the Документы section. In CA, they are created as 'Customer order' in the corresponding section.

Critical point: order statuses. In Bitrix, the status is a code (e.g., N, P, F). In CA, it's an enumeration (NewOrder, InProgress, Completed). The mapping must be configured manually in the exchange node on both sides. Without this, orders are created in CA without a status or with an incorrect one.

Additional order fields. If the site has custom fields (e.g., 'Desired delivery date', 'Comment to order'), they are transmitted via ЗначениеРеквизита in the order XML. On the CA side, corresponding attributes must be added to the 'Customer order' object and specified in the exchange node settings.

Case from our practice: CA + multi-warehouse + multiple sites

A home appliance distributor: CA with 3 warehouses (Moscow, Kazan, Krasnodar), two Bitrix sites — retail and wholesale (different prices, different stock). Our engineer configured two exchange nodes in CA — one for each site. Each node is configured with its own price type and set of warehouses. Incremental exchange (only changes) — every 20 minutes. Full exchange — at night.

Complexity: both sites on the same server, PHP exchange processes overlapped in time and blocked Bitrix's lock file. Solved by adding a delay in cron: retail runs at 00:00, wholesale at 00:15.

What's included in the exchange setup work

• Audit of the current exchange node and bottleneck identification
• Creation of a 1C configuration extension (customizations survive updates)
• Field and price type setup according to your catalog
• Implementation of handlers for non-standard data (reference properties, custom order fields)
• Multi-warehouse and multi-site integration (if required)
• Full-cycle exchange testing: export, import, status synchronization
• Documentation and administrator training
• 30-day guarantee on exchange functionality

Timeline expectations

Basic setup (items + prices + stock + orders) — 2–4 business days. If non-standard entities (reference properties, multi-warehouse, multiple sites) are needed — 5–10 days including testing. Setting up 1C:Comprehensive Automation and 1C-Bitrix exchange is an investment that pays off 80% faster than custom development from scratch. Get a consultation on exchange setup — just write to us. Contact us for cost and timeline estimation.

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.