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
| Scenario | Timeframe |
|---|---|
| Basic exchange: shipment requests + stock | 6–10 weeks |
| With handling of partial shipments and errors | 3–4 months |
| With mandatory labeling | 4–6 months |
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.