1С:УТ to Website Integration: Products, Prices, Orders

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:

1. Order received on website.
2. Reservation request sent to 1С.
3. Stock check.
4. Confirmation or rejection.

Why 1С:УТ is Better than Standard 1С:Accounting?

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

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.

1C:Enterprise Integration: Product, Order, and Stock Exchange

Monday morning. The manager opens the site and sees that the item sold out on Friday is still listed as "in stock". Three customers have already paid for a product that doesn't exist. We encounter this pain regularly: the lack of synchronization between 1C and the online store hurts revenue and reputation. We solve the problem end-to-end — setting up the exchange so that the accounting system and the storefront update synchronously, without data loss, and with consistency guarantees.

1C is the accounting system of most Russian companies. The site is the storefront. They must speak the same language and do so regularly, reliably, and without data loss. Our experience: over 50 successful integrations for clients with catalogs from 500 to 200,000 SKUs.

Why isn't standard CommerceML always sufficient?

CommerceML is a standard exchange protocol supported by 1C:Trade Management, 1C:Integrated Automation, and several other configurations. WooCommerce, Shopify, and other CMS have plugins for CommerceML (e.g., "1C-Bitrix" for their products, separate plugins for WordPress). Flow: 1C initiates exchange → sends a ZIP archive with XML to the site endpoint → site parses and updates the catalog.

CommerceML format is XML with its own schema: КоммерческаяИнформация, Классификатор, Каталог, ПакетПредложений. Categories, products, characteristics, images, prices, stock. The main difficulty: the hierarchy of characteristics in 1C and product attributes on the site do not always match one-to-one. Mapping is needed. For a deep understanding of the protocol, we recommend documentation on Wikipedia — Wikipedia: CommerceML.

How we overcome CommerceML limitations

For non-standard 1C configurations or when CommerceML is not suitable — we write an HTTP service in 1C (built-in since version 8.3) and interact via REST JSON. This gives full control over the data structure and synchronization frequency, but requires development from a 1C programmer.

For enterprise tasks with multiple accounting systems — Message Broker (RabbitMQ, Apache Kafka) as an intermediary. 1C publishes events to a queue, the site subscribes and processes them. Guaranteed delivery, buffering when one side is unavailable.

What we synchronize and how

Catalog (products, categories, attributes). The most voluminous part. Full export on first run, delta updates thereafter. When importing CommerceML: parse XML via PHP SimpleXML or XMLReader (for large files — only XMLReader, otherwise memory limit). Match products by GUID from 1C, which we store in a separate database field. If a product is deleted in 1C, we hide it on the site, not delete (order history may reference it).

Stock and prices. This is a separate ПакетПредложений in CommerceML, updated more often than the catalog. It's critical to do it atomically: not update stock one by one, but in a transaction. Otherwise, during the update, the user may see an inconsistent state. Frequency: once an hour for calm mode, once every 5–15 minutes for active trading.

Orders. Two-way exchange. Site → 1C: new order is sent with items, quantities, prices, customer contact info. 1C → site: order status (paid, assembled, shipped, delivered). For order transfer — either the same CommerceML (Документы block) or a direct REST call when an order is created on the site.

What typical problems do we solve?

Duplicate products. A 1C operator created an item with a typo in the SKU, then fixed it. On the site — two items. Solution: matching by GUID from 1C (not by SKU), GUID is immutable.

Cyrillic in XML and encodings. 1C historically works with Windows-1251. A CommerceML file may come in CP1251, PHP expects UTF-8. mb_convert_encoding() or iconv() in the first lines of the parser — mandatory.

Timeouts during large exports. A catalog of 100,000 items is 50–200MB XML. PHP default execution time of 30s is insufficient. Solution: CLI command (Laravel Artisan or Symfony Console) run via cron, without HTTP timeout. Or chunked processing via XMLReader with partial commits to the database.

Images. 1C can transmit images as Base64 inside XML (bloats file by 1.3x) or as file links. The second option is preferable. Download asynchronously, convert to WebP, place in media library.

Case: auto parts online store, 85,000 SKUs. Synchronization via CommerceML every 30 minutes. Problem: full export took 18 minutes, resulting in a new export starting while the old one was still running. Solution: lock via Redis (SET nx ex), delta export (only changed items in the last 2 hours via filter in 1C), processing via queue with 20 parallel workers. Sync time: 18 minutes → 2.5 minutes, no conflicts.

Comparison of integration methods

CommerceML in typical scenarios is 2-3 times faster than REST for catalog synchronization due to binary packing of XML and compact format. However, if custom exchange logic is required, REST provides full flexibility.

Process and timeline

Audit of 1C configuration (version, configuration type, export capabilities) → data mapping design → development of receiver on site and sender in 1C → testing on real data → schedule setup → monitoring of first exchanges.

Participation of a 1C programmer on the client side is mandatory, or we involve a trusted specialist.

| Scenario | Timeline | | CommerceML, catalog + stock, WooCommerce | 2–4 weeks | | Two-way order exchange | +2–3 weeks | | Custom 1C configuration, REST API | 4–8 weeks | | Enterprise: multiple 1C databases, data bus | 2–4 months |

What's included in the result (deliverables)

• Documentation: mapping scheme, data formats, error handling logic.
• Configured synchronization schedule with execution logs.
• Access to monitoring (Grafana/ELK — by agreement).
• Training for managers: how to run manual exchange, how to read logs.
• Post-launch warranty support — 2 weeks (issue fixing).

Get a consultation

We will evaluate your project within one business day — email us or use the chat. The integration cost is calculated individually based on project complexity. With over 7 years of experience in 1C integrations, we guarantee stable synchronization without surprises.