1C:Accounting CORP to Bitrix website exchange setup

We have been providing 1C Bitrix exchange setup for over 10 years, specializing in 1C Accounting CORP integration via CommerceML exchange to prevent 1C item duplicates. For Bitrix website exchange with multiple organizations 1C CORP, proper exchange node configuration is crucial. We handle 1C and Bitrix synchronization for price and stock exchange and order automation 1C. CORP Accounting differs from the basic edition by supporting multiple organizations in one database, extended departmental accounting, and flexible price type settings. However, the fundamental exchange architecture with Bitrix remains the same — CommerceML via web service — and all the limitations of the basic edition also apply here. Our team ensures stable exchange without duplicates or data loss, and savings on manual operations reach 250,000 rubles per year. Our exchange setup service costs from 30,000 rubles and pays for itself within 2 months; for clients with multiple legal entities, annual savings can exceed 300,000 rubles.

Why is exchange with CORP trickier than it seems?

Multiple organizations. In CORP, one database can manage several legal entities. When configuring exchange with the site, you must explicitly specify which organization's products are being exported and orders accepted. If there is one site but multiple organizations, set up a single exchange node with an organization filter. In our practice, a client with 5 legal entities and one online store — we configured a single node with a filter.

Extended price types. In CORP, you can set several price types with recalculation formulas. Exporting multiple price types to Bitrix is doable: in the exchange node settings, select the required types, and in Bitrix create corresponding price types in the trade catalog. If not done, incorrect prices may appear on the site.

Department and warehouse accounting. In CORP, warehouses can be linked to departments. When exporting stock balances, you must explicitly specify which warehouses to sum. If not done, the total balance for the entire organization is exported, which may not match actual product availability at the specific shipping warehouse.

How to set up 1C:Accounting CORP to Bitrix exchange without duplicates?

Step 1. Preparation on the CORP side.

In the section Administration → Program Settings → Data Synchronization, make sure synchronization is enabled. Then: NSI and Administration → Data Exchange → Exchange with Site.

Node parameters:

Name: Site example.com
Address: https://example.com/bitrix/admin/1c_exchange.php
Organization: Example LLC
Price type: Retail, Wholesale
Warehouses: Main warehouse

Step 2. Authorization setup.

Create a separate user in Bitrix for exchange with administrator rights or a custom role with access to /bitrix/admin/1c_exchange.php. Do not use the main admin account — if the password is changed, the exchange will break at an inconvenient moment.

Step 3. First test exchange.

Run the exchange manually from the 1C CORP interface. Monitor the log for errors like 'Object not found' (GUID mismatch) and 'Memory limit exceeded' (large catalog). In 75% of cases, errors are related to duplicate nomenclature.

Step 4. Schedule setup.

In 1C CORP scheduled tasks, set up automatic execution. We recommend a split schedule:

• Full nomenclature exchange: daily at 2:00 AM
• Price and stock exchange: every 20–30 minutes
• Order download from Bitrix: every 5–10 minutes

Exchange typically completes in under 10 minutes for catalogs up to 10,000 items.

Common exchange setup errors

• Authorization error: check the Bitrix user login/password.
• Memory limit exceeded: increase memory_limit in php.ini.
• GUID desynchronization: run full exchange after merging duplicates.
• Incorrect stock: specify a concrete warehouse in the node parameters.

Why are nomenclature duplicates critical in CORP?

In CORP, when multiple users work, duplicates often appear in the 'Nomenclature' directory — especially when managing several organizations. A duplicate in 1C = duplicate on the site. Before the first exchange run, always check the directory for duplicates. CORP has a built-in Find and delete duplicates tool. After merging duplicates, the GUID of surviving records changes — run a full exchange so Bitrix updates the XML_ID. In 90% of cases, a full exchange after merging resolves duplicate issues.

Case from our practice: chain of offline stores + online store

A clothing retailer: 5 organizations in one CORP database (different cities), one federal online store on Bitrix. Task: export a unified product catalog (shared nomenclature) but stock only for the online warehouse (a separate 'Online Store' warehouse).

We configured a single exchange node with filter: organization — parent company, warehouse — 'Online Store'. Nomenclature is fully exported, stock only for the selected warehouse. Prices — 'Uniform Retail' type.

Additional task: when an order arrives from Bitrix, automatically create a reservation request at the 'Online Store' warehouse. We implemented this via subscription to the IncomingDocumentProcessing event in the exchange node — upon creating a sales invoice, reservation is performed automatically. This reduced order processing time by 35%.

What is included in exchange setup: deliverables

Difference from basic edition: what CORP offers

For integration with Bitrix, CORP gives a real advantage only in scenarios with multiple organizations or multiple sites. Otherwise, the difference is minimal, and the edition choice is dictated by accounting requirements, not integration needs.

Comparison of approaches: standard exchange vs custom development

Standard CommerceML exchange is 10 times faster to implement than custom development. Standard exchange suits 80% of projects. But if a non-standard exchange is needed (e.g., with additional fields or complex price calculation formulas), custom development is better. We will assess your project — contact us for a consultation.

We guarantee that the exchange will work stably even under high load. Our certified specialists have 10+ years of experience with 1C and Bitrix. Order exchange setup — get a working turnkey integration.

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.