Export Additional Attributes from 1C to Bitrix: A Practical Setup Guide

Exporting additional attributes from 1C to Bitrix is not just copying fields. Imagine: a product in 1C has 50 characteristics, but only a dozen are displayed on the site. Or instead of values, GUIDs appear, filters don't work, and the product card is empty. Customers complain, conversion drops. If you encounter such a situation, the export of additional attributes from 1C is configured incorrectly — and it's time to fix it. For example, the "Additional Details" directory in 1C:UT 11 often remains unexported, and reference attributes are wrapped in GUID. As a result, important filters get lost on the site, product pages look incomplete, and managers spend hours manually filling data. We have configured dozens of integrations and developed a methodology that solves these problems efficiently, providing significant cost savings.

Types of Additional Attributes in 1C

In 1C:UT 11, attributes live in two places:

• Object attributes (AdditionalAttributes) — directly in the directory element. Exported with every exchange.
• Object details (AdditionalDetails) — in a separate information register. Require separate inclusion in the exchange node settings.

Value types: String, Number, Date, Boolean, Reference to a directory, and String with variants. The reference type is the main headache.

How Attributes Are Transferred in CommerceML

In the XML file, attributes are placed inside <Product>:

<ValuesOfAttributes>
  <ValueOfAttribute>
    <Name>Power</Name>
    <Value>2500</Value>
  </ValueOfAttribute>
  <ValueOfAttribute>
    <Name>PowerUnit</Name>
    <Value>W</Value>
  </ValueOfAttribute>
  <ValueOfAttribute>
    <Name>WarrantyPeriod</Name>
    <Value>24</Value>
  </ValueOfAttribute>
</ValuesOfAttributes>

Bitrix, during import, creates infoblock properties with the same names and fills them with values.

Comparison of Attribute Types and Representation in Bitrix

Problem: Automatic Property Codes

On the first import, Bitrix assigns codes like CML2_ATTR_001, CML2_ATTR_002. Working with them in templates is painful. Solution: before the production import, run a test on a copy, then manually rename codes to readable ones (POWER_WATT, WARRANTY_MONTHS). Subsequent imports won't change them because Bitrix matches by name.

Or — write a handler on OnIBlockPropertyAdd:

AddEventHandler('iblock', 'OnIBlockPropertyAdd',
    'setReadablePropertyCode');

function setReadablePropertyCode(&$arFields) {
    if (empty($arFields['CODE'])) {
        $arFields['CODE'] = CUtil::translit(
            $arFields['NAME'],
            'ru',
            ['change_case' => 'U', 'replace_space' => '_']
        );
    }
}

How to Solve the GUID Problem? Two Approaches

Reference attributes in XML come as GUID:

<ValueOfAttribute>
  <Name>Manufacturer</Name>
  <Value>f3a2b1c0-1234-5678-abcd-ef0123456789</Value>
</ValueOfAttribute>

On the site, the product card shows gibberish. Options:

1. On the 1C side: before export, replace the GUID with the name of the directory element. This is better — it doesn't burden Bitrix with extra logic.
2. On the Bitrix side: maintain a mapping table "GUID → value" built from the initial exchange, and substitute the value when writing the property.

Replacement on the 1C side doesn't load Bitrix but requires access to the configuration. Mapping on the Bitrix side is faster to set up (2–3 hours) but riskier when directories are updated.

What to Do with Multiple Values?

If an attribute in 1C allows multiple values, the XML passes them as repeating tags with the same name. The property in Bitrix must be "Multiple". The handler collects all values into an array:

$multiValues = [];
foreach ($arXML['ADDITIONAL_REQUISITES'] as $req) {
    if ($req['NAME'] === 'Applicability') {
        $multiValues[] = $req['VALUE'];
    }
}
$arProps['APPLICABILITY'] = $multiValues;

Step-by-Step Setup Guide

1. Export a test XML from 1C — ensure all attribute types are included.
2. Analyze attributes — identify reference, multiple, and string-with-variants types.
3. Choose an approach — decide where to handle GUID: in 1C or Bitrix.
4. Write a handler — modify the exchange module or create event handlers.
5. Test on a copy — verify types, filters, and product cards.
6. Deploy and train — move settings to production, set up incremental exchange.

Case Study: Industrial Catalog with 60+ Attributes

From our practice: a pump equipment manufacturer. Each product is described by 60–80 parameters (working pressure, temperature range, housing material, protection class). In 1C — additional attributes. On the first import, Bitrix created 78 properties with unreadable codes. We spent a day renaming codes and configuring types: numeric as "Number" with units of measurement; string as "List" for filtering.

After configuration, Bitrix's smart filter component automatically offers filtering by pressure, temperature, and material — without additional development. Incremental attribute updates (when values change in 1C) take 4 minutes for the entire catalog of 2,300 items. Saving in manual maintenance time — up to 20 hours per month, which at an average operator rate of 500 RUB/hour gives a saving of 10,000 RUB monthly, and over a year 120,000 RUB. This is 1.5 times more efficient than manual data entry.

What Is Included in the Work

• Analysis — export test XML, identify all attribute types and references.
• Design — choose processing scheme (1C or Bitrix side), configure multiple properties.
• Implementation — modify exchange module / write handlers, rename codes.
• Testing — verify on a catalog copy, compare with 1C, check filters and product cards.
• Deployment — transfer settings to production, train operators.
• Documentation — provide detailed instructions and configuration files.
• Support — 30 days of post-deployment support and bug fixes.

Timeline: 3 to 7 working days depending on the number of attributes and complexity of reference fields. Cost is calculated individually — typical projects start at 80,000 RUB. Request an estimate from our engineers.

Our Experience and Guarantees

• 8+ years of experience with 1C and Bitrix integration.
• Over 120 completed data exchange projects.
• We provide documentation on settings and guarantee our work.

Want the same? Get a consultation for your project — we will analyze your configuration and propose a solution. Contact us — let's start with an analysis of your setup.

According to CommerceML, the XML structure must contain all necessary attributes for correct data transfer.

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.