Configuring 1C:Retail and 1C-Bitrix Exchange
1C:Retail is designed for physical retail points, but with an online store on Bitrix, exchange between them allows synchronizing merchandise accounting: stock balances, prices, and orders. The 1C:Retail configuration supports CommerceML exchange, but with limitations compared to 1C:UT.
What 1C:Retail can and cannot do in terms of exchange
Supported:
- Nomenclature export (products, characteristics, prices)
- Export stock balances by registers and warehouses
- Import orders from Bitrix to 1C:Retail
Limitations:
- No full two-way exchange of counterparties — the customer base in 1C:Retail is simplified
- No document exchange (invoices, delivery notes)
- Characteristics (product variants) are supported but have a simpler structure than in 1C:UT
- Warehouse accounting is tied to a register/retail point
Configuration on 1C:Retail side
In the configuration: Service → Exchange with website. Parameters:
- Website URL and Bitrix authorization credentials
- Warehouse/register for stock export
- Price type for export
- Export mode: full or changes only
- Auto-exchange schedule
Important point with prices: in 1C:Retail, price can be tied to a register (price lists by location). The price type specified in the exchange settings is exported — make sure it is the retail price for the online store.
Configuration on Bitrix side
Standard CommerceML mechanism: catalog module with 1c_exchange.php handler. Additional configuration relative to 1C:UT exchange is minimal — standard infoblock mapping settings are sufficient.
1C:Retail specifics: the configuration may transmit stock balances broken down by registers (retail points). If Bitrix doesn't need warehouse accounting — sum balances across all points in the handler. If needed — enable warehouses in Bitrix and map 1C registers → Bitrix warehouses.
Importing orders from Bitrix to 1C:Retail
Orders are exported from Bitrix to orders.xml and transmitted to 1C:Retail during the next exchange session. In 1C:Retail, the order appears in the Customer Orders section and can be processed as a sale.
Limitation: 1C:Retail does not work with orders in real-time mode. Order exchange is periodic (on schedule), not in real-time. If instant order transmission is needed — only through custom integration (HTTP request from Bitrix to 1C REST service or via intermediate bus).
Order statuses
Standard exchange does not transmit order statuses back from 1C:Retail to Bitrix. If status synchronization is needed (e.g., "shipped from store") — implement additionally: either through reverse CommerceML exchange or via HTTP service from 1C.
Typical issues
| Issue | Cause |
|---|---|
| Balances are exported but not tied to warehouses in Bitrix | Warehouses not configured or not mapped |
| Prices are zero | Price type not specified in 1C:Retail exchange settings |
| Orders don't go to 1C | "Export orders" parameter disabled or status filter not configured |
| Product duplicates during exchange | Nomenclature GUID changed in 1C after database migration |