Setting up 1C:Accounting and 1C-Bitrix exchange

1C:Accounting (BP) is not a trade system, but in practice it often ends up being the only accounting program in small businesses. An online store runs on Bitrix, item nomenclature and prices are maintained in BP, and the request arises: 'make products on the site update from 1C'. The standard exchange module in BP exists but is significantly simpler than in Trade Management (UT) or Comprehensive Automation (KA). We professionally set up exchange between 1C:Accounting and 1C-Bitrix turnkey. Our experience: over 50 successful integrations for stores with catalogs ranging from 500 to 50,000 items. We will evaluate your project and offer an optimal solution—contact us for a consultation. Time savings on manual upload—up to 40 hours per month, and configuration cost pays off on average in 3-4 months. Integration cost starts from 50,000 rubles, with average savings of 30,000 rubles per month.

Comparison of exchange capabilities in 1C:Accounting and 1C:Trade Management

What the exchange in BP can do out of the box

In 1C:Accounting Enterprise (edition 3.0), the exchange module with the site is located in Administration → Data exchange. Functionality is limited:

• Upload of nomenclature (name, article, unit of measurement)
• Upload of prices (one type—'Main selling price')
• Upload of balances (total balance, without warehouse detail)
• Download of customer orders (creates document 'Customer invoice')

What's missing: variants (options), multiple price types, warehouse-level detail, images, categories (group hierarchy is transmitted as a flat list with no nesting deeper than one level). For a small store (up to 5000 items, one price, one warehouse) this is sufficient. For everything else—customization or switching to CommerceML (see Wikipedia) is needed.

Why the standard exchange is not suitable for stores with variants?

If a product has options (color, size, material), BP has no mechanism to transfer them. Each modification becomes a separate nomenclature item, and their relationship is lost. 80% of exchange errors are related to incorrect category hierarchy settings. Variants require custom development or upgrading to Trade Management.

Configuring price upload and order download

BP supports only one price type—'Main selling price'. On the Bitrix side, it maps to the base price type. If retail and wholesale prices are needed but not maintained in BP—a typical solution is to upload the base price from BP and calculate surcharges using Bitrix formulas:

BASE_PRICE * 0.85

Orders from Bitrix arrive as 'Customer invoice'. Configure automatic posting of the invoice via the AutomaticPosting = Yes flag in the exchange node settings. Duplicate counterparties are a common issue: we recommend transferring the buyer's unique XML_ID from Bitrix so BP searches by it.

Case study: jewelry online store (from our practice)

A jewelry store, 3000 items, all prices in BP. Prices changed multiple times a day (gold, silver—exchange rates), but the site updated once a day. We configured incremental exchange—only price changes—every 30 minutes. In BP, we wrote a scheduled task: when the metal rate changes, recalculate prices. Bitrix fetches changes at the next exchange. The XML volume during incremental exchange averages 200–400 items instead of 3000. Processing time: 8 seconds instead of 90. Incremental exchange is 3 times faster than full exchange.

How to configure incremental exchange: step-by-step guide

1. In 1C:Accounting, enable upload of only changed objects (flag 'Upload only changed').
2. Set up the scheduled task 'Exchange with site' with an interval of 30 minutes.
3. In Bitrix, enable import by XML_ID (in the exchange module settings).
4. Configure cleanup of temporary folders to prevent file duplication.
5. Test on a test product: change the price in 1C and verify the update on the site.

Typical errors and their solutions

What's included in the exchange configuration work

• Audit of current exchange
• Design of synchronization scheme
• Customization of exchange module on 1C and Bitrix sides
• Setup of scheduled tasks
• Testing on live data
• Employee training (accountant, content manager)
• Technical documentation
• Post-release support for 2 weeks

Limitations and when to upgrade to Trade Management

BP is suitable for integration with Bitrix if: up to 10,000 items, one price type (or simple formula-based surcharges), one or two warehouses, no variants. If any condition is not met—consider upgrading to 1C:Trade Management or Comprehensive Automation. Migration of data from BP to Trade Management using standard tools takes 1–2 days.

Reliable 1C and Bitrix integration from certified specialists

Our company has 7+ years of experience in 1C-Bitrix integration and over 50 successful projects. Certified specialists guarantee stable exchange operation from the first launch. Contact us for a free evaluation of your project—we will offer an optimal solution. Reduce maintenance costs by up to 60%.

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.