1C:Retail and 1C-Bitrix Exchange Setup
Integrating an online store on Bitrix with retail outlets running 1C:Retail is a common challenge for retailers expanding their sales. The standard exchange via CommerceML can synchronize product catalogs, stock, and orders, but it has limitations: stock is tied to cash registers, statuses aren't transferred, and orders don't arrive in real time. Typical errors include incorrect warehouse mapping, missing order status filters, and ignoring item GUID after database migration. We've configured exchange for 50+ stores over 5 years and guarantee reliable synchronization from the start. Our team holds 1C-Bitrix certifications and has experience integrating with any 1C configuration. We'll assess your project and propose a turnkey solution.
Why Exchange with 1C:Retail Is Harder Than with 1C:Trade Management
1C:Retail is designed for physical points of sale—it's not built for full-fledged online accounting. Unlike 1C:Trade Management, it lacks bidirectional counterparty and document exchange. It supports exporting nomenclature (products, variants, prices) and stock per cash register. Importing orders from Bitrix is possible, but statuses are not sent back. Product variants are supported, but their structure is simpler. If you need instant order transmission, you'll require a custom REST service.
Case Study: Setup for a 10-Store Chain
A client—a clothing retail chain—used 1C:Retail in each store and a site on Bitrix. The main pain points: cash register stock didn't aggregate on the site, orders didn't enter 1C, and product duplicates occurred. We audited the system: 1C had different price types for each store, while Bitrix had one warehouse. We mapped cash registers to warehouses and created a handler to sum balances. Orders started flowing into 1C within 30 minutes of placement. Result: error-free synchronization, the client saved up to 30% of time on inventory management.
How We Configure Exchange: Steps
- Analyze current architecture. Check 1C version, CommerceML settings, Bitrix information blocks. Determine which data is critical for synchronization.
- Map directories. Configure mapping of cash registers → warehouses, price types, counterparties. If 1C has multiple prices, decide which type to export to the site.
-
Configure exchange. In 1C:Retail, set the site URL, authorization data, warehouse, and price type. In Bitrix, configure the
catalogmodule and the1c_exchange.phphandler. - Load orders. Enable order export from Bitrix, set up a status filter. Ensure orders appear in the "Customer orders" section in 1C.
- Test and go live. Run a full exchange cycle: products → stock → order → posting in 1C. Eliminate duplicates and discrepancies.
- Document and support. Deliver the exchange schema, settings, contacts. Provide one month of warranty support.
Comparison of 1C:Retail and 1C:Trade Management for Exchange
| Feature | 1C:Retail | 1C:Trade Management |
|---|---|---|
| Export nomenclature | Yes | Yes |
| Export stock | By cash register/warehouse | By warehouse |
| Import orders | Yes | Yes |
| Send statuses | No | Can be customized |
| Counterparty exchange | Simplified | Full |
| Document exchange | No | Yes |
| Real-time operation | No | Via REST |
Our solution for 1C:Retail is set up 3 times faster than typical thanks to preliminary data analysis and ready-made templates.
Typical Problems and Solutions
| Problem | Cause | Solution |
|---|---|---|
| Stock not linked to warehouses | Warehouses in Bitrix not configured | Enable and map cash registers to warehouses |
| Zero prices | Price type not set in 1C settings | Select the correct price type in exchange configuration |
| Orders not sent to 1C | Status filter disabled | Enable order export and configure the filter |
| Duplicate products | GUID changed after database migration | Reset GUID in nomenclature or restore unique identifiers |
Additional tips for troubleshooting
- If orders aren't sent, check the status filter settings in Bitrix.
- Ensure "Upload orders" parameter is active.
- To send statuses back, we recommend a custom REST service—it's faster than modifying CommerceML.
How to Speed Up Order Exchange?
If you need instant order transmission to the cash register, use an HTTP request from Bitrix to the 1C REST service. This updates accounting in real time, not by schedule.
What If Order Statuses Are Not Transferred?
Standard CommerceML does not transfer statuses. To synchronize statuses (e.g., "shipped"), we implement reverse exchange via a 1C HTTP service or a custom REST service. We set up such a module in 2-3 days.
Setup Timelines
Estimated timelines: from 3 to 7 business days, depending on configuration complexity and number of stores. Cost is calculated individually after analysis.
Our team holds 1C-Bitrix certifications and has multi-year experience integrating with 1C:Retail and 1C:Trade Management.
Contact us—we'll conduct a free analysis of your configuration and propose a solution with stability guarantee. Order a turnkey exchange setup: get synchronization, documentation, and launch support.