1C UNF-Bitrix Integration: CommerceML, REST, Cases

We've repeatedly encountered situations where a client uses 1C UNF and wants to synchronize the catalog and orders with a Bitrix site. UNF is the choice of small businesses that run CRM, warehouse, and sales in one place without the excessive complexity of ERP. Integration with Bitrix here works differently than with UT or KA: UNF lacks a full-fledged CommerceML exchange mechanism in the old style, but it does have REST API and Bitrix Drive — the official connector from 1C. Setting up the exchange requires understanding protocols and common errors: for example, item variants don't always map correctly to SKUs, and standard CommerceML does not transmit serial numbers. We'll cover two paths and show how to avoid duplicates and freezes.

How to Choose the Exchange Method?

Path 1: CommerceML (classic). UNF supports the standard exchange protocol via /bitrix/admin/1c_exchange.php. Nomenclature, prices, stock balances are exported, and orders are imported. It works, but with limitations: no full characteristics, no serial numbers, and CRM documents are not transmitted. Read more about the protocol at CommerceML.

Path 2: REST API + Webhooks. UNF from version 1.6 has a built-in HTTP service. Bitrix can poll it or receive push notifications about changes. This path is more flexible but requires development on both sides.

For most tasks (catalog + orders), CommerceML is sufficient. REST is needed when transferring non-standard objects: CRM deals, tasks, documents.

How to Set Up CommerceML in UNF Step by Step

1. Go to Company → Integration → Exchange with site.
2. Specify the site URL (e.g., https://example.com) and credentials (login/password for 1C exchange).
3. Select item groups for export — tick only those that should appear on the site.
4. Set the price type (retail or wholesale) and choose warehouses for stock export.
5. Configure order status mapping: in UNF, statuses are "New", "In Progress", "Completed", "Cancelled" — map them to your site's status chain.
6. Run a test exchange manually via the "Run Exchange" button.

Orders from Bitrix to UNF

Orders are created in UNF as "Customer Order". The counterparty is created automatically from order data. Order processing takes an average of 2 seconds during synchronization. "Previously, status updated once every 15 minutes; now clients see changes instantly. That increased loyalty." — client, a service center.

Critical point: statuses. In UNF, an order goes through statuses: New → In Progress → Completed / Cancelled. In Bitrix, there is its own status chain. The mapping is configured in the exchange node. If not configured, orders in UNF will hang in "New" status.

Reverse status synchronization — when a manager changes the order status in UNF, this change must reach Bitrix. Standard exchange supports this: at the next exchange session, the order status is updated in Bitrix. But there is a delay equal to the exchange interval (usually 5–15 minutes).

Why REST API Is Faster Than CommerceML?

With CommerceML, synchronization delay is 5–15 minutes. For service companies where the client waits for repair status updates, this is critical. REST API with webhooks gives instant feedback — delay drops to 1–2 seconds. Over 90% of our clients with a service model choose REST.

Case Study: Service Center (from our practice)

Our client — a service center for equipment repair. They use UNF for CRM (client requests, repair history), and the site has a request form and customer personal account.

Task: website request must go to UNF as "Inquiry", and the client must see the repair status in the personal account on the site.

Solution: used UNF REST API. When the form is submitted on the site:

1. Bitrix creates an order in its system.
2. A script makes a POST request to the UNF HTTP service: creates an inquiry.
3. UNF returns the inquiry ID; Bitrix saves it in a custom order field.

For reverse status synchronization — webhook from UNF: when the inquiry status changes, a POST request is sent to a Bitrix endpoint, which updates the order status.

Status synchronization delay: 0 (instant via hook) instead of 5 minutes with polling.

{
  "event": "crm.invoice.status.update",
  "url": "https://site.bitrix24.ru/rest/1/токен/hook.php"
}

Process Overview

A typical project takes 5 to 7 days. Cost is calculated individually, but average time savings on synchronization is up to 90%.

What's Included in the Work

• Data structure and exchange schema analysis — 1–2 days
• CommerceML or REST API setup — 2–3 days
• Scenario testing (orders, nomenclature, statuses) — 1–2 days
• Documentation for operators and administrators — 0.5 day
• Employee training (1–2 hours) — included
• Post-launch support for 2 weeks

UNF Integration Limitations

UNF is well-suited for integration if the catalog is small (up to 20,000 items) and lacks complex characteristics. If the business grows — plan for migration to KA or UT without rebuilding the site (preserve XML_ID of nomenclature).

Typical Errors and Checklist

• Status mapping not configured — orders hang.
• XML_ID of nomenclature mismatch during exchange — duplicates.
• All item groups uploaded, including service ones — clutter on site.
• Serial numbers used but CommerceML does not transmit them — need REST.

Conclusion

Our engineers hold 1C and Bitrix certifications, have over 5 years of experience, and have completed more than 50 integration projects. We guarantee seamless exchange without data loss. Order a turnkey setup — timeline from 5 days. Contact us for analysis of your project – get an engineer's consultation.

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.