Note: when an e-commerce store starts working with 1С:Trade Management, manual synchronization becomes a bottleneck: prices go stale, stock diverges, orders get lost. For an assortment of 5000+ items, daily manual updates are a source of errors. We solve this with turnkey automatic integration — setting up two-way exchange so you forget about manual export/import.
How to Automate 1С:УТ to Website Synchronization?
Manual synchronization kills time. When you have 5000+ products and 10% of inventory changes daily, exporting updates by hand is a mistake. Often, promotional prices are forgotten or discontinued items remain on sale. Automatic exchange solves these tasks without manager intervention.
Stock conflicts. When multiple managers work in parallel or you integrate with marketplaces, overselling occurs. Official 1С documentation recommends setting up reservation to prevent selling out-of-stock items. As a result, a company was losing up to 150,000 rubles monthly. We configure the chain: order received → stock check → reservation → confirmation.
How to Avoid Stock Conflicts?
Reservation upon order is the key mechanism. After an order is placed on the website, 1С:УТ sends a reservation request. If stock is insufficient, 1С returns an error and the order is set to "requires clarification". This guarantees you won't sell what you don't have. The process includes four steps:
- Order received on website.
- Reservation request sent to 1С.
- Stock check.
- Confirmation or rejection.
Why 1С:УТ is Better than Standard 1С:Accounting?
| Criterion | 1С:УТ (Trade Management) | 1С:Accounting |
|---|---|---|
| Customer orders | Has 'Customer order' object | No (only invoices) |
| Pricing | Price types, discounts, price groups | Limited |
| Warehouse management | Multiple warehouses, reservation | Single warehouse |
| Website integration | OData, CommerceML, SOAP | Only manual exchange |
1С:УТ outperforms 1С:Accounting by 3–4 times in order processing speed and stock accuracy.
Technical Aspects: Stack and Case Study
Protocols Used — 1С:УТ Integration
We use proven protocols: CommerceML for standard synchronization, OData (if edition 11.x) or SOAP for more complex scenarios. In one of our projects — an auto parts e-store with 20,000 SKUs — we implemented a hybrid scheme: product catalog via CommerceML, and prices/stock via direct HTTP service calls to 1С. This reduced synchronization time by 80% and eliminated overselling losses averaging 250,000 rubles monthly.
// Price request for a specific customer segment $priceRequest = [ 'Номенклатура' => $sku, 'Характеристика' => $variantCode, 'Количество' => $quantity, 'КонтрагентID' => $customer1cId, // for individual prices 'ДатаЦены' => date('d.m.Y') ]; // 1С returns price considering discounts and customer price group Multi-Warehouse Stock
If the store has multiple warehouses (retail + e-commerce), you need to determine which warehouse is available for which order type. Often, online orders are shipped from one warehouse only, while others serve retail. We configure rules: for example, show total stock with "in stock" label, but when ordering, reserve from the specific warehouse.
// Stock response from 1С [ ['Склад' => 'Main Warehouse', 'Остаток' => 15], ['Склад' => 'Retail Store', 'Остаток' => 3], ] // On the site, display total stock or breakdown for pickup Work Process: Stages and Timeline
| Stage | Duration | Description |
|---|---|---|
| Configuration analysis | 3–5 days | Examine 1С version, data structure, load. |
| Exchange design | 3–5 days | Choose protocol, define field mapping. |
| Development | 2–4 weeks | Write exchange module on 1С side and web service on website. |
| Testing | 1–2 weeks | Run on real data, check edge cases. |
| Deployment & documentation | 3–5 days | Deploy to production server, hand over schemas and contacts. |
Estimated timeline: 6 to 10 weeks. Cost is determined individually after analyzing your configuration. Contact us for a detailed analysis — we'll evaluate the project within one business day. Guaranteed quality: over 7 years of experience, 50+ implemented integrations, certified 1С specialists.
What's Included in the Integration?
- Setup of two-way exchange (products, prices, stock, orders)
- Development of 1С processing modules (export/import)
- Adaptation for editions 10.3 and 11.x
- Testing and bug fixes during warranty period
- Support and server access documentation
- Training staff on integration operations
Typical Mistakes in Self-Setup
- Missing fields. Often, units of measurement or additional attributes are forgotten.
- Duplicate products. Without a unique identifier, each exchange creates new product cards.
- Price conflicts. Multiple price groups can overwrite each other — clear priority rules are needed.
Get a consultation — we'll help avoid these mistakes and set up an integration that lasts for years.
Technical details for developers
When working with 1С:УТ 10.3, use COM connection via V83.COMConnector. For 11.x, prefer OData service: /odata/standard.odata/Catalog_Номенклатура. Common errors: GUID mismatch in mapping, timeout overrun on large data volumes (batch requests in groups of 100 records).