1C:AutoService to Bitrix Integration Guide

Complete Guide to 1C:AutoService and Bitrix Exchange

Imagine an auto parts online store with 45,000 items, each having an OEM number, cross-analogs, and vehicle applicability. All this data lives in 1C:AutoService—and on the website you need not only to display it but also provide fast search and filtering. In a typical implementation, CommerceML only transfers the name and SKU—but for an auto service, OEM number, cross-analogs, and vehicle applicability are critical. If not configured correctly, the buyer won’t find the needed part, and the exchange will bog down the site for hours.

We have encountered such cases dozens of times, and each time the same problems arose: standard CommerceML does not transmit the complex applicability structure, the exchange "hangs" the server, and cross-numbers get lost during import. We'll walk through how to set up integration to make it stable and fast, with specific configuration examples and optimizations.

Reach out to us for an audit of your 1C and Bitrix configuration—we will propose the optimal integration scheme.

How to Set Up Exchange Between 1C:AutoService and 1C-Bitrix?

Items in 1C:AutoService

The configuration stores spare parts with extended attributes:

• Manufacturer article (OEM number)
• Cross-numbers (analogs from other manufacturers)
• Applicability (make, model, year, engine)
• Brand/manufacturer
• New/used flag
• Warranty period

Standard CommerceML transfers only name and SKU. OEM numbers, cross-numbers, and applicability are transmitted via AdditionalProperties. In Bitrix, each of these properties must become an infoblock property with the correct type (string, multiple value for cross-numbers, reference to a dictionary for applicability). According to official CommerceML documentation, these properties can be transferred without quantity limits, but it is important to properly configure the import handler.

Applicability: The Most Complex Part

Part applicability is a many-to-many relationship: one part fits multiple vehicles, one vehicle uses many parts. In 1C:AutoService, applicability is stored in a register of information. CommerceML has no standard way to transfer this structure. We consider two approaches.

Option 1: JSON in a property. In 1C, we form a JSON string with applicability and put it in an AdditionalProperty:

[
  {"make":"Toyota","model":"Camry","year_from":2006,"year_to":2011,"engine":"2AZ-FE"},
  {"make":"Toyota","model":"RAV4","year_from":2005,"year_to":2012,"engine":"2AZ-FE"}
]

In Bitrix—a property of type "Text" storing JSON. Filtering by applicability is done via full-text search or a separate table.

Option 2: Separate applicability infoblock. We create a separate infoblock "Applicability" (make/model/year/engine) in Bitrix and an "Items" infoblock with a binding property of type "Link to elements". This is the correct architecture for full-blown car selection, but synchronizing it from 1C is more complex—a custom import handler is needed.

The choice depends on scale. For a catalog up to 100,000 items with infrequent car selection, JSON is sufficient; for large stores with active filtering, use a separate infoblock.

Why the Exchange May Slow Down Your Site and How to Fix It

With a full catalog exchange of 45,000 items, standard CommerceML generates a huge XML file (up to 100 MB) which the server processes for tens of minutes. During import, the database is locked, and the site "freezes". Solutions: export only items in stock, transfer images via FTP separately from XML, use incremental (delta) exchange—transfer only records changed since the last synchronization.

Incremental exchange works up to 6 times faster than full exchange for comparable data volume, and server load is reduced by 80%.

How to Set Up Search by Cross-Numbers?

Cross-numbers are codes of the same part under different brands. A buyer searches by cross-number on the site—the part must be found even if an analog from another manufacturer is sold. In Bitrix, cross-numbers are stored as a multiple property of the infoblock. Search by them is done through the bitrix:catalog.smart.filter component or a custom search using CIBlockElement::GetList with a property filter.

When importing from 1C:AutoService, cross-numbers are transmitted via AdditionalProperties with multiple values:

<ЗначениеРеквизита>
  <Наименование>КроссНомер</Наименование>
  <Значение>BP-35</Значение>
</ЗначениеРеквизита>
<ЗначениеРеквизита>
  <Наименование>КроссНомер</Наименование>
  <Значение>ATE-603310</Значение>
</ЗначениеРеквизита>

The import handler in Bitrix must collect multiple values of one property into an array.

Work Orders: Auto Service Specifics

In 1C:AutoService, besides selling parts, "Repair Orders" are maintained—documents for performing services. On the website, this can be a service booking form or online diagnostics. Transferring orders from the site to 1C:AutoService is typically done not via CommerceML but via a REST request to the 1C HTTP service. The order is created as an "Appeal" or "Repair Order" in the "New" status.

Case Study: Used Parts Store (From Our Practice)

A car disassembly company: 45,000 items of used parts, each with photo, condition rating (1-5), applicability. Full exchange with 1C:AutoService took 40 minutes and "hung" the server.

Optimizations:

• Export filter: only "In stock" (quantity > 0)
• Images via FTP separately from XML (XML without base64 is half the size)
• Applicability stored as JSON in one field (not a separate infoblock)
• Incremental exchange every 30 minutes: only items with changed stock

Result: full exchange—12 minutes (at night), incremental—2 minutes. The site stopped slowing down, search became fast.

What's Included in the Work

When you order the exchange setup, you get:

1. Audit of your current 1C:AutoService configuration and data structure in Bitrix
2. Design of the import scheme (fields, property types, vehicle linking)
3. Development of the import handler (CommerceML + custom properties)
4. Setup of REST service for orders (if needed)
5. Performance optimization (incremental exchange, filters)
6. Testing on live data and error monitoring
7. Documentation on maintenance and exchange schedule

Our Experience and Guarantees

We have been integrating 1C and Bitrix for over 10 years, having completed more than 50 projects for auto services and parts stores. Clients include large car dismantlers and service station chains. All work adheres to official 1C-Bitrix and 1C:Enterprise recommendations. Every integration comes with a 6-month guarantee.

Get a consultation—we will assess your project and propose the optimal solution. Order the exchange setup today to ensure your online store runs without failures.

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.