Bitrix-1C XML Exchange: Fixing Timeouts and Duplicates

We've faced this situation dozens of times: a client starts an exchange with 1C, and the result is timeouts, duplicate products, or prices that don't update. The standard Trade Catalog module (catalog) supports the CommerceML 2.x protocol, but in practice it breaks in three scenarios: non-UTF-8 encoding, non-standard <Классификатор> structure, and exceeding time limits with files over 50 MB. We configure import turnkey in 1-2 days with guaranteed stable operation.

Why timeouts occur when importing large XML files

The main cause is the max_execution_time limit in PHP. When uploading a 180 MB file containing 200,000 products, the 1c_exchange.php script cannot process the data within the standard 30 seconds. Even set_time_limit(0) doesn't help if PHP-FPM has request_terminate_timeout configured. The solution is to enable step-by-step import. In the 1C module settings, we set the "File size for step-by-step processing" (parameter CATALOG_IMPORT_STEP_SIZE). Bitrix uses a SAX parser to split the file into chunks of 10 MB and processes them sequentially. This not only prevents timeouts but also reduces database load: each step is committed, and if a failure occurs, the exchange resumes from the last successful chunk. On one project with an equipment catalog (150,000 SKUs), this approach reduced import time from 4 hours to 40 minutes.

How to avoid duplicate products during exchange?

Duplicates occur when the GUID of an item (<Ид>) changes in 1C. For example, after migrating to a new configuration version or transferring data. Bitrix cannot match the new GUID with the existing XML_ID in b_iblock_element and creates a new element. To fix duplicates, we use a direct SQL query or CIBlockElement::Update(). Prevention: configure in 1C to prohibit unloading elements with empty or non-unique GUID. In complex cases, we write an OnSuccessCatalogImport event handler that checks uniqueness and forcibly updates XML_ID.

What to do if prices are not updating?

A common reason is mismatched price type names. In 1C, the price type might be called "Основная", while in Bitrix it's "Розничная". Mapping is set in /bitrix/admin/cat_price_type.php. Ensure that <ТипЦены><Наименование> in XML matches NAME in b_catalog_price_type. If multiple price types need mapping, we write a custom OnSuccessCatalogImport handler. In it, we parse XML using SimpleXMLElement and update prices via CPrice::Update().

Setting up export from Bitrix to 1C

For the reverse flow (orders → 1C), the endpoint with parameter type=sale is used. Bitrix generates orders.xml with the <Документ> structure containing order items. It is critical to check that the exchange settings have the "Export deliveries" flag enabled and the required order status is set. Parameters of the bitrix:catalog.import.1c component:

• IBLOCK_ID — information block of the catalog
• PRICE_TYPE — default price type
• STORE_ID — default warehouse
• USE_CML2_DESCRIPTION — take description from XML

Configuration process

Total setup takes 1-2 working days.

Comparison of approaches: standard vs custom

What is included in the work

• Diagnostics of current exchange configuration (encoding, <Классификатор> structure, price types)
• Setting up step-by-step import for large files (optimal chunk size)
• Mapping price types and warehouses (direct mapping or custom handlers)
• Fixing duplicates and GUID errors (SQL or API)
• Test run with real export (timing, checking prices and stock)
• Exchange scheme documentation (data scheme, field descriptions)
• Consultation on further maintenance

We have 10+ years of Bitrix development experience, over 200 projects with 1C integration. Certified engineers guarantee correct synchronization of catalog, prices, and stock. For non-standard tasks (custom handlers, non-standard 1C structure), an additional day for development is added.

We will assess your project within 1 hour — contact us. Get an engineer consultation and a turnkey import setup proposal.

CommerceML — official specification of the exchange protocol.

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.