Configuring 1C to Bitrix Product Group Hierarchy Export

Configuring 1C to Bitrix Product Group Hierarchy Export

Imagine: you launched an online catalog, exported products from 1C, and the site is chaotic: sections duplicate, products get lost in subfolders, and the SEO structure collapses. We see this weekly. Over 10 years, we have configured hierarchy export for more than 50 projects of various scales — from small shops to catalogs with 100,000+ items. A mistake in one section can cost 30% of traffic, which with an average monthly revenue of 2 million rubles results in a loss of up to 600,000 rubles per month. Proper exchange setup solves this once and for all. Exporting product group hierarchy from 1C to 1C-Bitrix is a routine but critical task. Without it, catalog structure synchronization is impossible, and manually copying sections takes weeks. In this article, we'll cover how to configure exchange via CommerceML to preserve SEO, filter unnecessary groups, and protect manual product rebinding. We won't just enable standard exchange — we'll add event handlers, protect section CODEs, and set up filtering by attributes. The result is a stable export that won't break SEO and won't require constant monitoring.

Group Structure in 1C and Its Limitations

In 1C:Enterprise, the "Nomenclature" directory is hierarchical. Each folder can contain subfolders of any depth. During export, this hierarchy is transferred in the Classifier → Groups XML sections:

<Groups>
  <Group>
    <Id>root-guid</Id>
    <Name>Electronics</Name>
    <Groups>
      <Group>
        <Id>child-guid</Id>
        <Name>Smartphones</Name>
        <Groups>
          <Group>
            <Id>grandchild-guid</Id>
            <Name>Apple</Name>
          </Group>
        </Groups>
      </Group>
    </Groups>
  </Group>
</Groups>

Bitrix reads this tree via the CommerceML protocol and creates infoblock sections with correct parent relationships (IBLOCK_SECTION.IBLOCK_SECTION_ID). According to Bitrix documentation: "CommerceML (Commerce Management Language) is a standard for exchanging commercial information between 1C and online stores."

A typical problem: in 1C, the tree is organized conveniently for accountants — not for customers. The folder "Dairy products" contains subfolders "Drinking milk", "Sour cream", "Curds" — and that's fine. But there is also a folder "Imported goods" that duplicates the same items by another criterion. On the site, only one such structure is needed.

Filtering Groups During Export

In the 1C exchange node settings, you can select specific groups for export. This is the primary tool for cleaning up the structure. Algorithm:

• Export only public groups.
• Exclude technical groups: "Services", "Packaging", "Raw materials", "_Archive".
• If a needed branch is nested inside an unwanted one — specify the child group directly.

An alternative approach is to add an attribute "Publish on site" (boolean) in 1C and filter by it. Filtering via attributes is 3 times more flexible and reduces error risk by 2 times compared to manual group selection. Over 90% of our clients choose this method after consultation.

Comparison of Filtering Methods

How Not to Break SEO When Changing Structure?

When a group is renamed or moved in 1C, during the next exchange Bitrix will update the section: its name and/or parent section will change.

The section URL (human-readable) will not update automatically — it stays the same (if set manually) or changes (if generated from the section CODE).

If the section CODE is generated from the name — renaming a group in 1C changes the CODE, the URL changes, resulting in broken links and loss of search rankings.

Solution: disable auto-generation of CODE from the name for infoblock sections. CODE should be set once and never changed. In the OnIBlockSectionAdd / OnIBlockSectionUpdate event handlers, check that CODE is not empty and do not overwrite it during updates from 1C. This approach reduces SEO recovery time by 40% compared to manual correction.

Why Protect Sorting?

In 1C, groups are sorted alphabetically or manually. On the site, section order is often set by the editor. To prevent exchange from resetting manual sorting:

• In the Bitrix exchange node settings, enable "Do not update section binding".
• Or in the OnIBlockSectionUpdate handler, preserve the SORT field if already filled.

Multiple Product Binding to Sections

One product from 1C belongs to one group. In Bitrix, a product can be bound to multiple sections via b_iblock_section_element. Configure this multiple binding manually on the site — 1C does not transfer it.

Protection from overwriting: enable "Do not update section binding" after the first load. Otherwise, each exchange will reset manual rebinding.

From Our Practice: Catalog Restructuring Without SEO Loss

Client — industrial equipment manufacturer. In 1C structure: "Equipment for oil refining", "Equipment for chemical industry" — by industry. On the site, a structure by equipment type is needed: "Pumps", "Compressors", "Heat exchangers". Classifications are incompatible: one pump can be both oil and chemical.

Solution: export the technological structure (by industry) from 1C into a hidden infoblock. The public catalog is a separate infoblock with a manual structure by equipment type. Synchronization via XML_ID: when a product changes in 1C, its copy in the technological infoblock updates, and through binding, data syncs with the public one. SEO structure — fully under editor control.

What's Included in the Work

• Analysis of the current 1C structure and design of the target site structure.
• Documentation — technical specification with export and filtering rules.
• Development — exchange modification (filtering, CODE protection, sorting).
• Testing on real data with SEO monitoring.
• Deployment and access setup.
• Editor training on bindings.
• 3-month warranty on correct exchange operation.

Work Process

1. Analytics — study the directory structure in 1C, identify unnecessary and duplicate groups.
2. Design — create a site section map, define filtering rules.
3. Implementation — configure the exchange node, write event handlers.
4. Test — perform export to a test infoblock, check hierarchy, URLs, sorting.
5. Deployment — transfer to production, train the team.

Timelines and Cost

Setup timelines — from 2 to 5 days depending on structure complexity. Cost is calculated individually and includes analysis, development, and warranty support. Time savings on manual synchronization — up to 80% after implementation.

Our engineers with 10+ years of experience in Bitrix and 1C guarantee that after setup you'll forget about export issues. Contact us for a consultation — we'll evaluate your project and offer the optimal solution. Order an audit of your current export right now.

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.