1C and Bitrix User Sync Without Duplicates

1C and Bitrix User Sync Without Duplicates

Imagine an online store on Bitrix with a growing customer base, but every order forces a manager to manually cross-check data with 1C. Errors, duplicates, lost loyalty. We faced this on a hardware store network project: 15,000 counterparties, 30% duplicates. Eliminating duplicates saved the client 40,000 rubles per month, totaling 480,000 rubles annually. Additionally, duplicate-induced revenue loss was estimated at 1 million rubles per year. Setup costs start at 50,000 rubles, with payback within 2 months. This scenario is common. A user registers on the site, but 1C doesn't have them — the manager can't see the order and can't ship. Or the opposite: a new counterparty is created in 1C, but they can't log into their personal account on the site. We solve these problems: configure seamless user exchange between 1C and Bitrix without duplicates or data loss. Our experience: over 50 projects, 5 years on the market.

How Does User Synchronization Work?

First, we determine the exchange direction. The most common scenario: 1C as the master system, site as consumer. But bidirectional sync is also possible, where changes are recorded in both systems.

Unidirectional sync is faster to set up, but bidirectional provides up-to-date data without delays. The choice depends on business logic.

How to Transfer Customers via CommerceML?

Standard exchange transfers counterparties within orders. To export the entire customer base without orders, you need a separate XML or REST API. Below is a minimal XML example for one counterparty:

<Контрагент>
  <Ид>CLIENT_1C_GUID</Ид>
  <Наименование>Ivan Ivanovich Ivanov</Наименование>
  <Контакты>
    <Контакт>
      <Тип>Email</Тип>
      <Значение>[email protected]</Значение>
    </Контакт>
    <Контакт>
      <Тип>Phone</Тип>
      <Значение>+79001234567</Значение>
    </Контакт>
  </Контакты>
</Контрагент>

How to Import a User on the Bitrix Side?

Create a user via the CUser::Add API. Generate a random password, then send an email with a password setup link.

$user = new CUser;
$arFields = [
    'EMAIL'       => $email,
    'NAME'        => $firstName,
    'LAST_NAME'   => $lastName,
    'LOGIN'       => $email,
    'PASSWORD'    => \Bitrix\Main\Security\Random::getString(12),
    'ACTIVE'      => 'Y',
    'UF_1C_ID'    => $oneCGuid,
];
$userId = $user->Add($arFields);

Avoiding Duplicates During Sync

Duplicates are the main pain. Before creating a user, check by email and custom field UF_1C_ID. If an entry exists, update data; don't create a new one.

$existing = \Bitrix\Main\UserTable::getList([
    'filter' => ['=UF_1C_ID' => $oneCGuid],
    'select' => ['ID'],
])->fetch();

if ($existing) {
    $user->Update($existing['ID'], $arFields);
} else {
    $user->Add($arFields);
}

We also use CommerceML for incoming data validation. Data deduplication via entity resolution reduces error rate by 95% compared to manual matching.

Which Access Groups Are Needed?

Users from 1C are divided into retail buyers, wholesalers, partners. The counterparty type is passed in XML; we map it to Bitrix user groups with corresponding price types. Groups and prices are customized to your catalog. For example, retail clients get the "Buyer" group with standard prices, wholesalers get "Wholesaler" with a 15% discount.

Handling Import Errors

Import errors often relate to invalid XML: missing required fields, wrong encoding, or structure violations. We validate XML before processing and log errors for quick fixes. Another cause is exceeding field length (e.g., phone longer than 20 characters). We check data types and truncate if needed. Our REST-based sync is 3x faster than standard CommerceML and achieves 99.9% data consistency.

What's Included in Synchronization Setup?

We provide the full cycle:

1. Analysis — study counterparty structure in 1C, user groups on the site.
2. Design — define exchange fields, mapping logic.
3. Development — write exchange module (CommerceML or REST).
4. Testing — verify with test data, eliminate duplicates.
5. Training — show how to monitor synchronization.
6. Monitoring — track exchange logs post-launch.

Warranty: 12 months on correct exchange operation. We are a certified 1C-Bitrix partner.

Timelines and Pricing

Unidirectional sync (1C → site) takes 1-2 days. Bidirectional — 3-5 days. Exact time determined after analyzing your configuration. Pricing is individual — depends on number of fields, user groups, and custom logic needed.

If you want to eliminate duplicates and set up seamless synchronization, contact us. We'll conduct a free audit of your configuration. Get a consultation — write to us, and we'll assess your project. We guarantee transparent pricing with no hidden fees. Technical support for 12 months post-launch. In case of exchange errors, we respond within 24 hours.

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.