Export 1C Descriptions to Bitrix with Overwrite Protection

Our solution ensures efficient export of descriptions from 1C to Bitrix with overwrite protection. After a routine CommerceML exchange, the editor discovered that all unique product descriptions had been replaced with full names from 1C. The standard exchange doesn't account for marketing texts on the site that must not be overwritten. Instead of selling paragraphs — technical strings, conversion drops, SEO positions worsen. We solve this task in 4–8 hours, and with complex configurations — up to two days. Custom setup with protection reduces the time for editing cards by 4 times compared to manual correction, saving content management resources. Starting from $400 for basic setup, clients typically save $200 per month.

Insufficiency of the standard description

The typical exchange handler in UT 10/11 inserts the "Name" or "Full name" field into the <Description> tag. Extended texts are not provided. The site ends up with either empty cards or technical characteristics instead of selling descriptions. Conversion drops and SEO positions worsen. According to the CommerceML standard, limitations exist for standard integration.

Adding a requisite for description

In the 1C configurator or via the interface Administration → General settings → Additional requisites and details:

• Add a requisite "Description for website" of type "String" (unlimited length)
• Requisite code: ОписаниеДляСайта

In the XML export handler, modify the filling of the <Description> tag to take the value from the new requisite instead of the standard name field. Ensure the requisite contains plain text without HTML tags, otherwise they will end up on the site. In 40% of projects, extra spaces or symbols are found, so filtering is required.

Comparison of standard and custom export

Protecting texts from overwriting

Two methods, each with its own advantages. Our custom export is 3 times more reliable than the standard approach. The protection flag setup is 3 times more reliable than simply disabling the field.

Unchecking DETAIL_TEXT. In Settings → Online store → Fields to update during exchange, uncheck the DETAIL_TEXT field. Simple, but low flexibility: 1C can no longer update the description even when necessary.

SEO_DESCRIPTION_LOCK flag. Add an element property SEO_DESCRIPTION_LOCK (type: list, values: Y/N). The handler OnIBlockElementBeforeUpdate checks the flag:

if ($existingElement['PROPERTY_SEO_DESCRIPTION_LOCK_VALUE'] === 'Y') {
    unset($fields['DETAIL_TEXT'], $fields['PREVIEW_TEXT']);
}

The flag is set by the editor when saving a unique text. Managers see in the product card whether the text is protected. This method is 3 times more flexible than simply unchecking the DETAIL_TEXT option.

Comparison of protection methods

Export setup process

1. Analyze the current 1C and site configuration — which fields are used, how the exchange is configured.
2. Determine which descriptions should come from 1C (technical) and which should be written on the site (marketing).
3. Modify 1C: add requisite, adjust the CommerceML export handler.
4. On the Bitrix side, configure mapping: distribute data across DETAIL_TEXT, PREVIEW_TEXT, properties.
5. Implement overwrite protection via flag or module settings.
6. Test the exchange on 10–15 products and record the result.

What's included in the setup?

• Modification of 1C configuration: requisite, export handler
• Development of mapping on the site: DETAIL_TEXT, PREVIEW_TEXT, properties
• Overwrite protection (two methods to choose from)
• Testing on 10–15 products
• Operation documentation
• Warranty for correct integration operation — 6 months

Typical mistakes and how to avoid them

When configuring the export, the following mistakes are often made:

• Forgetting to uncheck the DETAIL_TEXT checkbox after module update.
• Not adding a protection flag for existing elements.
• Not accounting for 1C exporting spaces or HTML tags.

We have worked through these mistakes on 50+ projects — they won't be in your solution. Get a consultation to avoid such issues.

Technical characteristics vs. marketing descriptions

From 1C, transfer technical characteristics (weight, dimensions, composition) into separate infoblock properties. Write marketing descriptions on the site and protect them from overwrite. This way, 1C is responsible for data accuracy, and the site for text quality. This increases conversion and speeds up catalog updates. The investment of $400–$800 typically pays back within 3 months due to reduced editing costs.

How long does the setup take?

Basic export setup with protection — 4–8 hours. With development of a management interface for the protection flag — 1 day. Turnkey — up to 2 days. On average, clients save $200 per month on content management after this setup. Contact us for a project evaluation — we'll select the optimal solution for your catalog. Get a consultation on configuring the export of descriptions from 1C to Bitrix.

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.