Integrating 1С-Битрикс with 1С:WMS Logistics

We have repeatedly encountered situations where an online store on 1С-Битрикс tries to sync stock with 1С:WMS Logistics, but the standard CommerceML yields no results — warehouse documents are not generated, and stock data becomes stale. Over 5 years of integrations, we have developed an architecture that solves this without excessive modifications. Below is a proven approach with real technical details.

1С:WMS Logistics is a configuration on the 1С:Enterprise 8 platform that implements full warehouse management: address storage, picking tasks, zone management, and transport units. Integration with 1С-Битрикс in this case has a fundamental difference from exchange with a SaaS-WMS: both products come from the same vendor (1С), and theoretically should “understand each other”. In practice, there is no direct ready-made exchange, so integration still needs to be built.

What problems does the 1С:WMS-Битрикс integration solve?

The first and main problem is the lack of standard exchange. The standard exchange module of 1С-Битрикс (\Bitrix\Catalog\CatalogImport) works with classic 1С configurations: Trade Management, Retail, Integrated Automation. The CommerceML 2.09 format is designed for them. 1С:WMS Logistics is not a trade configuration. It does not directly handle customer orders, has no price lists, and does not know about retail prices. It is a warehouse operational management system that receives tasks from a “senior” system (ERP, TMS, or online store) and manages the physical movement of goods.

The second problem is mandatory labeling. If the warehouse works with labeled goods, during shipment 1С:WMS must transmit the list of DataMatrix codes used in the order. These codes are needed for creating an outgoing electronic invoice in the EDI system and confirming disposal in the GIS MT. Without integration, this process is done manually, leading to errors and fines.

Why doesn't the standard 1С-Битрикс exchange work here?

It all comes down to architecture: 1С:WMS is an executor of warehouse operations. This means the exchange must be built not through CommerceML, but through the direct API of 1С:WMS — either REST services published on the 1С platform, or HTTP services written in the configurator. This approach processes orders 2–3 times faster compared to modifying CommerceML.

Architecture: 1С:WMS as the executor of warehouse operations

Exchange scheme for e-commerce:

1С-Битрикс (orders, stock) ↔ 1С:WMS Logistics (picking tasks, shipment fact)

Битрикс acts as master for orders. 1С:WMS acts as master for physical stock and picking statuses.

From Битрикс to 1С:WMS: a new order confirmed for picking. In 1С:WMS terminology, this is a “Shipment request” — document ShipmentRequest. We transmit: items (linked by barcode or SKU), quantity, priority, expected shipment date.

From 1С:WMS to Битрикс: status of the request execution, actual shipped quantity (may differ from ordered due to shortages or overages), list of serial numbers or labeling codes for labeled products.

Publishing HTTP services in 1С:WMS

For REST integration, we create an HTTP service in the 1С configurator (the “HTTP services” branch in the configuration tree). The method POST /orders/create accepts JSON with request parameters, creates a ShipmentRequest document, and returns the internal document ID for subsequent status polling.

On the Битрикс side, we implement a client for this service — a class with methods createOrder(), getOrderStatus(), getStockBalance(). Authentication: Basic Auth on the 1С HTTP service publication (configured in web server publication properties).

Stock synchronization

1С:WMS maintains stock in the accumulation register RemainingGoodsInWarehouse. To get available stock, an HTTP service or Web service (SOAP) is needed that queries this register with a warehouse filter.

An important nuance: in 1С:WMS, stock is stored in the warehouse unit of measure, which may differ from the site's unit. A pack of 12 pieces in the warehouse = 12 pieces in the Битрикс catalog. A unit conversion table must be part of the integration layer.

Working with mandatory labeling

If the warehouse handles labeled goods, during shipment 1С:WMS must transmit the list of DataMatrix codes used in the order. These codes are needed for creating an outgoing electronic invoice in the EDI system and confirming disposal in GIS MT (“Chestny Znak”).

In this case, the integration expands: Битрикс receives not just a “shipped” status from 1С:WMS, but an array of labeling codes. These codes are then passed to the EDI module (Diadoc, SBIS) or directly to the “Chestny Znak” API via the method POST /api/v3/true-api/outgoing-marks.

What is included in the work

We provide a full package:

• Audit of current 1С:WMS and Битрикс configurations.
• Design of exchange scheme (field mapping, units, statuses).
• Development of HTTP services on the 1С side and client on the Битрикс side.
• Setup of stock and order synchronization.
• Integration with EDI and GIS MT if required.
• Testing on staging and production environments.
• Documentation and employee training.
• 3 months warranty support after launch.

Timeline estimates

Cost is calculated individually. For an estimate, we need: description of your 1С:WMS configuration (version, customizations), warehouse operations scheme, labeling requirements. Contact us — we will prepare a preliminary assessment within 2 days.

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.