Configuring 1C:Comprehensive Automation and 1C-Bitrix Exchange
1C:Comprehensive Automation (KA) is a configuration often chosen by companies that have outgrown Trade Management but are not ready for the complexity of ERP. From an integration perspective it is more interesting than UT: it includes CRM, production, payroll — and data from all these subsystems is sometimes needed on the website. At the same time, the CommerceML export mechanism in KA is inherited from UT and carries the same limitations.
What KA Can and Cannot Do Out of the Box
KA has a built-in website exchange node — practically identical to the one in UT 11. It exports: items with characteristics, prices (multiple types), warehouse stock levels, customer orders. It does not export out of the box: CRM data (counterparties, deals), production orders, mutual settlement documents in a format convenient for the website.
KA-specific note: the configuration is regularly updated, and updates sometimes affect the exchange module. If you have customized the KA-side export (e.g., added tags to the XML), those customizations may be lost after a configuration update. Always make changes in a configuration extension, not in the configuration itself.
Configuring the Exchange Node in KA
Path: Administration → Data Exchange → Website Exchange on 1C-Bitrix.
Create a new node. Required parameters:
-
Site address —
https://example.com/bitrix/admin/1c_exchange.php - Login/password — a 1C-Bitrix user with exchange rights (Administrators group or a custom role)
- Organization — which organization to export (if there are multiple)
- Price type — one or more price groups
- Warehouses — select specific warehouses or "all"
A note on prices: in KA, multiple price types can be configured for simultaneous export. On the 1C-Bitrix side, each price type corresponds to a separate price type in the trade catalog. The mapping is configured under Settings → Trade Catalog → Price Types.
Item Characteristics: A Common Problem
In KA, item characteristics are stored in the PropertyValuesOfObjects information register. During export, they are placed in the Properties section of the XML. 1C-Bitrix reads them and creates infoblock properties.
The problem arises when a characteristic in KA is a reference type (e.g., "Manufacturer" → a Counterparties reference book). 1C-Bitrix receives the counterparty's GUID instead of its name. A handler is needed that substitutes the GUID with the string value during XML processing.
// Exchange event handler
AddEventHandler('catalog', 'OnIBlockCMLImport2ElementAdd',
'fixReferenceProperties');
function fixReferenceProperties(&$arFields, &$arProps, $arXML) {
// If the 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 the value in the mapping table
$propVal = getPropertyValueByGuid($propCode, $propVal);
}
}
}
Order Exchange: From 1C-Bitrix to KA
Orders from 1C-Bitrix are transmitted to KA in CommerceML format — the Documents section. In KA they are created as "Customer Order" records in the corresponding section.
A critical point: order statuses. In 1C-Bitrix, a status is a code (e.g., N, P, F). In KA, it is an enumeration (NewOrder, InProgress, Completed). The mapping must be configured manually in the exchange node on both sides. Without this, orders are created in KA without a status or with an incorrect one.
Additional order fields. If the website has custom fields (e.g., "Desired delivery date", "Order comment"), they are transmitted via AttributeValue in the order XML. On the KA side, the corresponding attributes must be added to the "Customer Order" object and registered in the exchange node settings.
Case Study: KA + Multi-Warehouse + Multiple Websites
A household appliance distributor: KA with 3 warehouses (Moscow, Kazan, Krasnodar), two 1C-Bitrix websites — retail and wholesale (different prices, different stock).
Solution: two exchange nodes in KA — one per website. Each node is configured for its own price type and its own set of warehouses. Incremental exchange (changes only) — every 20 minutes. Full exchange — overnight.
Complication: both websites on the same server; PHP exchange processes overlapped in time and locked the 1C-Bitrix lock file. Resolved by adding a delay in cron: the retail site runs at 00:00, the wholesale site at 00:15.
Configuration Timelines
Basic setup (items + prices + stock + orders) — 2–4 working days. If non-standard entities are needed (reference-type characteristics, multi-warehouse, multiple websites) — 5–10 days including testing.