Reliable Stock Sync from 1C to Bitrix with Warehouse Support

Stock quantities are part of the standard CommerceML exchange. They are transmitted in the offers.xml file as the <Quantity> element for each trade offer. However, in most projects, the standard exchange is insufficient: more frequent synchronization, breakdown by warehouse, or partial updates without a full catalog export are required. With over 10 years of experience and 200+ successful integrations, we ensure reliable synchronization. We configured the exchange for a store with 50,000+ items, where stock updated every 5 minutes via REST API — without failures or delays. A typical full CommerceML exchange for 30,000 SKUs takes 15–20 minutes, which is unacceptable with high sales dynamics.

What problems do we solve?

Delays during full export. Each full catalog exchange via CommerceML takes minutes, and with large volumes — hours. If stock requires updating every 15 minutes, this is unacceptable. We reduced synchronization time for a client from 20 minutes to 30 seconds using a separate XML file.

Lack of warehouse accounting. Standard exchange transmits only the total quantity, but for a chain of 20 stores, stock per warehouse is required. In Bitrix, the 'Warehouses' module is enabled and the breakdown is configured in 1C.

Synchronization errors. Often stock resets to zero after exchange or is not updated at all — this is related to incorrect export settings in 1C or component logic. According to our data, 70% of problems are solved by enabling the stock export flag in 1C.

Our typical project saves clients up to 40% on synchronization time, resulting in monthly savings of up to 5,000 rubles for a mid-size store.

How do we do it?

We offer three synchronization options — from simple to complex. The choice depends on volumes and update frequency requirements.

Method Comparison

Synchronization Time Comparison for 50,000 Products

// Find PRODUCT_ID by XML_ID
$element = CIBlockElement::GetList(
    [],
    ['XML_ID' => $xmlId, 'IBLOCK_ID' => OFFERS_IBLOCK_ID],
    false,
    ['nTopCount' => 1],
    ['ID']
)->Fetch();

if ($element) {
    CCatalogProduct::Update($element['ID'], ['QUANTITY' => $newQuantity]);
}

Separate XML File

1C generates a lightweight XML without descriptions and images, sends it to a separate Bitrix endpoint. On the Bitrix side, a custom handler reads the XML and updates b_catalog_product.QUANTITY. This achieves stock update without catalog exchange. Suitable if direct connection from 1C is difficult.

REST API

1C sends a POST request with JSON: sku → quantity. The handler on the Bitrix side receives, validates, and updates stock. Using 1C REST API, this is faster than XML parsing, easier to debug. We implemented this for an auto parts online store — stock updates every 5 minutes without errors. This approach supports Bitrix stock by warehouse as needed.

Via Bitrix Agent

1C writes stock to an intermediate table or file on the server. A Bitrix agent reads the intermediate data every N minutes and updates the catalog. This Bitrix agent stock update method is chosen if a direct HTTP request from 1C is impossible (e.g., due to corporate security policies).

Warehouse Accounting

If the store has multiple warehouses, we enable warehouse accounting: Catalog → Warehouses. The b_catalog_store_product table stores stock per warehouse for each product. Update:

\Bitrix\Catalog\StoreProductTable::update(
    ['PRODUCT_ID' => $productId, 'STORE_ID' => $storeId],
    ['AMOUNT' => $newAmount]
);

When warehouse accounting is enabled, b_catalog_product.QUANTITY becomes aggregated (sum across all warehouses) and updates automatically. This is key for Bitrix warehouse accounting.

Stock Update Frequency

The choice of method determines frequency: CommerceML — once per hour, separate XML — up to 5 minutes, REST API — up to 1 minute. For a clothing store with 10,000 SKUs, we configured an agent with updates every 3 minutes — sufficient to avoid overselling. The phrase "1C stock export every 5 minutes" is achievable with REST or separate XML.

Displaying Stock on the Site

Check which property the catalog component uses (QUANTITY or custom). If warehouse accounting is enabled, evaluate the stock at the corresponding warehouse. A common mistake is the component hiding a product at zero stock even if warehouse accounting is not configured. In this case, change to QUANTITY or add a check.

Stock Export Configuration from 1C

Details for each method are described above. Development and setup costs start from 15,000 rubles and depend on the complexity of integration, number of warehouses, and update frequency. For example, for a store with 20 warehouses and 30,000 SKUs, the time savings on synchronization is about 40%. Our average project cost is 25,000 rubles. The 1C-Bitrix exchange setup cost is included in the project.

Work Process

1. Analytics — examine current exchange, error logs, catalog volume, number of warehouses.
2. Design — choose synchronization method, handler architecture. Ensure Bitrix 1C integration stock requirements are met.
3. Implementation — write custom handler or modify existing one.
4. Testing — test on a test server with a copy of the catalog. Run load tests.
5. Deployment — move to production, set up monitoring.

Deliverables and What Is Included

• Development or modification of the stock export handler.
• Configuration of warehouse accounting (if required).
• Documentation on 1C and Bitrix interaction.
• Testing for 3–5 days after launch.
• Incident support (response within 1 business day).

Common Errors

• Stock goes to zero with every full exchange — 1C does not transmit stock in offers.xml. Enable stock export in 1C exchange settings.
• Stock updates, but the product shows as 'out of stock' on the site — check component logic: it may be using a custom property 'In stock' instead of QUANTITY.
• Negative stock — 1C allows negative quantities. In the Bitrix handler, limit to max(0, $quantity).
• 1C stock export errors like zero quantities are resolved by our specialists. We provide full 1C-Bitrix exchange setup to ensure seamless integration.

Contact us for a consultation — we will select the optimal method for your project. Order exchange setup and get stable synchronization with a work guarantee.

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.