1C:UT 10 to Bitrix Data Synchronization: Setup and Automation

We specialize in configuring automated data exchange between 1C:UT 10 and Bitrix sites. UT 10, though still widely used, presents specific challenges: profile settings are buried deeper, support for item characteristics is limited, and scheduled jobs are absent. A typical situation: a product catalog of 50 thousand items, each with 6 colors — characteristics fail to export because UT 10 has no built-in mechanism for variants. We have learned to work around these limitations.

Clients often face problems: orders from the site are not created in 1C, prices are not updated, or exchange runs only when the database is open. Our goal is to make synchronization automatic and error-free. To achieve this, we use external processing, Windows Task Scheduler, and, if necessary, modify the UT 10 configuration.

Automating exchange without manual startup

For automatic exchange from UT 10, an external processing file RunExchange.epf is required, launched via Windows Task Scheduler. Here is an example batch file:

REM File run_exchange.bat
"C:\Program Files\1cv8\common\1cestart.exe" ENTERPRISE /S "SERVER\DATABASE" /N "admin" /P "password" /Execute "C:\scripts\RunExchange.epf"

The processing performs exchange using the CommerceML protocol and closes the session. The scheduler runs the batch file on a schedule — for example, every hour. This approach is 3–5 times more reliable than manual startup and eliminates human error. Automated exchange is also 5 times more accurate than manual data entry.

What does exchange automation provide?

Automated synchronization saves employee time and eliminates manual entry errors. Where previously a manager had to log into 1C daily, start the export, and wait, now everything happens on a schedule without human involvement. Additionally, it improves data timeliness on the site — prices and stock levels are updated every hour instead of once a day. Based on our estimates, automation reduces exchange errors by 80%.

Location of exchange settings in UT 10

Services → Data exchange → Exchange with site (Bitrix)

If the menu item is missing — the configuration has been modified or the feature is disabled. To enable:

Services → Accounting parameters setup → Additional → Use exchange with site

Differences from UT 11 in exchange setup

Item characteristics. In UT 10, characteristics are poorly implemented. To transfer product variants (color/size), configuration modification or using series instead of characteristics may be necessary. In one project, we encountered a catalog of 50,000 items, each with 6 colors — we had to rework the series mechanism to export all variants.

Orders. In UT 10, orders from the site are created as documents "Customer order" (reference from the sales management subsystem). Order statuses — "New", "In Progress", "Completed", "Canceled". Mapping with Bitrix is straightforward.

Exchange schedule. UT 10 works only in file mode (thick client). Scheduled jobs only run when 1C is open. For automatic exchange without human involvement, a separate 1C session must be set up on the server.

Stages of UT 10 exchange setup

What's included in the exchange setup service

• Creating an exchange profile: site address, handler URL, authorization
• Modifying UT 10 configuration (if needed for characteristics, series, additional documents)
• Implementing automatic startup via Windows Task Scheduler
• Testing catalog and order synchronization
• Documentation on settings and access to the configured environment
• One hour of remote support after delivery and training session for your team

Cost and savings

Basic catalog and order exchange via UT 10 typically costs $500–$1000, depending on complexity. Automatic startup via scheduler adds $200–$400. If modifications are required, the price is calculated individually. Automation saves up to 20 hours of manual work per month, paying for itself within a few months.

Why consider upgrading to UT 11?

If you are still on UT 10 — whenever possible, we recommend upgrading to UT 11 or higher. Benefits for site exchange: scheduled jobs without manual startup, better support for characteristics and trade offers, HTTP services for REST API. Migrating exchange settings during the upgrade is a separate task — the data structure changes, requiring reconfiguration of mappings.

Timelines and cost

Basic catalog and order exchange via UT 10 takes 1–2 days. With automatic startup via the scheduler — plus 4–8 hours. If modifications are required (characteristics, series, non-standard documents), timelines are calculated individually. The final cost depends on the scope of work and is discussed after auditing your system.

Common issues during setup

• Characteristics not exported: UT 10 lacks built-in trade offers — we use series or modify the configuration.
• Exchange times out: on large catalogs, increase script execution limits.
• Orders created without status: check status mapping and Bitrix user permissions.

Our engineers have 10 years of experience in 1C and Bitrix integrations. We guarantee correct synchronization and post-setup support.

If you need to configure UT 10 exchange with Bitrix, contact us. Get a consultation and project estimate. Get in touch — we will find the optimal solution.

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.