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.
| Entity | Exported by default | Needs customization |
|---|---|---|
| Items | Yes | No |
| Properties | Yes, except reference types | Yes, if type is 'Reference' |
| Prices (multiple types) | Yes | No |
| Stock by warehouse | Yes | No |
| Customer orders | Yes | Status mapping |
| Counterparties from CRM | No | Yes |
| Production orders | No | Yes |
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.
More about property setup
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. A handler is needed that, during XML processing, replaces the GUID with a string value. An example handler is given below.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
- Create a configuration extension in 1C.
- Configure the exchange node: site URL, login/password, organization, price type, warehouses.
- Configure the price type mapping on the Bitrix side.
- If there are reference properties, add the
OnIBlockCMLImport2ElementAddhandler. - Map order statuses in both systems.
- 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
| Stage | Duration | Comment |
|---|---|---|
| Audit and design | 1 day | Analysis of current configuration and requirements |
| Exchange node setup | 1–2 days | Basic settings and extension |
| Handler development | 1–3 days | For non-standard data |
| Testing and debugging | 1–2 days | Full cycle verification |
| Documentation and training | 0.5 days | Knowledge transfer to administrator |
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.