Integration of 1C-Bitrix with 1C:WMS Logistics
1C:WMS Logistics is a configuration on the 1C:Enterprise 8 platform that implements full warehouse management: address-based storage, picking tasks, zone and transport unit management. Integration with 1C-Bitrix in this case has a fundamental difference from exchange with SaaS WMS: both products come from the same vendor (1C), and in theory they should "understand each other". In practice, there is no ready-made direct exchange, and the integration must still be built from scratch.
Why the standard 1C-Bitrix exchange does not work here
The standard 1C-Bitrix exchange module (\Bitrix\Catalog\CatalogImport) works with classic 1C configurations: Trade Management, Retail, Integrated Automation. The CommerceML 2.09 format was designed for those.
1C:WMS Logistics is not a trade configuration. It does not manage customer orders directly, does not contain price lists, and is unaware of retail prices. It is a system for the operational management of a warehouse, which receives tasks from a "senior" system (ERP, TMS, or an online store) and manages the physical movement of goods.
This means the exchange must be built differently: not via CommerceML, but through the direct 1C:WMS API — either REST services published on the 1C platform, or HTTP services written in the configurator.
Architecture: 1C:WMS as the warehouse operations executor
The data exchange scheme for e-commerce:
1C-Bitrix (orders, stock) ↔ 1C:WMS Logistics (picking tasks, actual shipments)
Bitrix is the master for orders. 1C:WMS is the master for physical stock and picking statuses.
From Bitrix to 1C:WMS: a new order confirmed for picking. In 1C:WMS terms, this is a "Shipment Request" — the document ЗаявкаНаОтгрузку. We transmit: SKUs (matched by barcode or article number), quantities, priority, expected shipment date.
From 1C:WMS to Bitrix: the request execution status, actually shipped quantities (which may differ from the ordered amount in the case of mispicks), and a list of serial numbers or labelling codes for labelled goods.
Publishing HTTP services in 1C:WMS
For REST integration, create an HTTP service in the 1C configurator (the "HTTP Services" branch in the configuration tree). The POST /orders/create method accepts a JSON payload with order parameters, creates a ЗаявкаНаОтгрузку document, and returns the internal document ID for subsequent status polling.
On the Bitrix side, implement a client for this service — a class with methods createOrder(), getOrderStatus(), getStockBalance(). Authentication: Basic Auth on the 1C HTTP service publication (configured in the web server publication properties).
Stock synchronisation
1C:WMS tracks stock via the accumulation register ОстаткиТоваровНаСкладе. To retrieve available stock, an HTTP service or Web service (SOAP) is needed to query this register filtered by warehouse.
An important nuance: in 1C:WMS, stock is stored in warehouse accounting units of measure, which may differ from the website's units. A package of 12 units in the warehouse = 12 units in the Bitrix catalogue. A unit conversion table must be part of the integration layer.
Working with labelling
If the warehouse handles labelled goods, on shipment 1C:WMS must transmit the list of DataMatrix codes used in the order. These codes are required to create an outgoing UPD (Universal Transfer Document) in the EDI system and to confirm goods withdrawal in the GIS MT ("Honest Sign") tracking system.
The integration is then extended: Bitrix receives not just a "shipped" status from 1C:WMS, but an array of labelling codes. These codes are forwarded to the EDI module (Diadoc, SBIS) or directly to the Honest Sign API via POST /api/v3/true-api/outgoing-marks.
Estimated timelines
| Scenario | Timeline |
|---|---|
| Basic exchange: shipment requests + stock | 6–10 weeks |
| With partial shipment and error handling | 3–4 months |
| With Honest Sign labelling loop | 4–6 months |
Pricing is calculated individually. For estimation, the following are required: a description of the 1C:WMS configuration (version, customisations), the warehouse operations scheme, and labelling requirements.