Integration of 1C-Bitrix with WMS: Stock and Order Synchronization

Why Stock Desynchronization Occurs When Integrating with WMS

Stock desynchronization between 1C-Bitrix and WMS means direct financial losses. An order is placed on the site, a reserve is set, but WMS doesn't know. By the time of picking, the product isn't on the shelf — the customer gets a rejection. Without proper integration, you lose up to 3% of revenue due to oversell and shipping delays. Losses can reach 500,000 rubles per year. We integrate 1C-Bitrix with any WMS, guaranteeing atomic transfer and no "hanging" orders. The work is carried out by certified specialists using proven patterns. Contact us for an assessment of your project.

What Exactly Needs to Be Synchronized

Stock and Reserves

WMS is the source of truth for physical availability. Bitrix receives stock and updates b_catalog_product (fields QUANTITY, QUANTITY_RESERVED). Synchronization frequency is critical: with 200+ orders per day, a 15-minute delay already creates oversell. Losses can reach 200,000 rubles per month.

Orders

New order from Bitrix → WMS for reservation and picking. Picking statuses from WMS → Bitrix to update the order status for the customer. Atomicity is important here: the order is either accepted by WMS or not — "hanging" transfers are unacceptable.

Product Catalog

Nomenclature, barcodes, units of measurement, packages. Usually master data is maintained in ERP/1C, and WMS and Bitrix synchronize from it.

Which Integration Architecture to Choose

There is no direct API connection "Bitrix ↔ WMS" — each WMS has its own API or supports EDI/XML formats. The choice of architecture depends on reliability and latency requirements. Webhook with event queue is 3–5 times faster than polling and provides latency in seconds vs minutes. Let's compare the main approaches:

Polling is implemented via a handler in \Bitrix\Main\EventManager or a custom agent. Webhook/event queue: WMS sends an event on every stock change. Bitrix receives via REST endpoint and queue (RabbitMQ, Redis Streams). Via 1C broker: if 1C:Enterprise is in the chain, exchange goes through it: Bitrix ↔ 1C (standard CommerceML / REST) ↔ 1C ↔ WMS.

How to Technically Implement the Integration on the Bitrix Side

Stock is updated via \Bitrix\Catalog\ProductTable::update() or low-level CCatalogProduct::Update(). When updating, it's important to invalidate the cache: \Bitrix\Catalog\Catalog::clearProductCache($productId). Without this, the site shows old stock for another 30–60 minutes. Reservation when creating an order: the \Bitrix\Sale\Order object automatically sets a reserve via \Bitrix\Sale\Basket::setField('RESERVE_QUANTITY'). If the integration updates stock directly in the DB bypassing the API — reserves break. Always work through the public API of the sale module. To transmit orders to WMS, we hook into the OnSaleOrderSaved or OnSaleStatusOrderChange event — depending on the trigger. The event is processed synchronously, so long API calls are moved to a queue.

How to Avoid Order Duplication

Duplication occurs when the network is unstable and Bitrix repeats the request on timeout. Solution: idempotent requests with ORDER_ID from Bitrix as an external key in WMS — retransmission updates the existing record, does not create a new one. We always implement this mechanism to exclude financial losses from duplicates.

Why Atomicity of Transfer Is Important

Imagine: an order is transmitted to WMS, but WMS hasn't had time to accept it, and Bitrix has already marked it as "sent". The product is physically reserved, but remains hanging in the system. Atomicity ensures that the order is either fully transmitted and accepted, or not. Achieved through transactional queues and confirmations from WMS. This is our standard.

What Typical Errors Occur

Direct database updates bypassing the sale module API — reserves break. Ignoring cache invalidation after stock updates. No handling of timeouts for bulk requests. Discrepancies in units of measurement (pieces vs pallets) — without a conversion table, stock is incorrect. Solved by a conversion directory on the integration layer. When bulk updating stock, WMS sends 10,000 items in one request; Bitrix processes in batches with set_time_limit() and \Bitrix\Main\Application::getInstance()->getDbConnection()->startTransaction().

How Long Does the Integration Take

Cost is calculated individually — depends on the specific WMS API, volume of nomenclature, and real-time requirements. We start with an audit of current processes and WMS technical documentation. Contact us to get accurate timelines and a commercial proposal.

What Is Included in the Integration

• Audit of current warehouse processes and WMS API.
• Design of integration architecture (polling/webhook/1C broker).
• Development of exchange modules on the Bitrix side.
• Implementation of idempotency and atomicity.
• Queue setup (RabbitMQ/Redis if needed).
• Cache invalidation and tagged caching.
• Testing under production loads (oversell, timeouts).
• Documentation, team training, post-launch support.

Order a turnkey integration — we will prepare a detailed plan and timeline. Warranty on work — 12 months.

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.