1C:Enterprise to Website Integration: Orders, Products, Stock

Manual data entry from 1C to a website and back is a constant source of errors and wasted time. Orders are lost, stock becomes outdated, customers leave. Over 10 years, we have integrated 1C:Enterprise with dozens of websites on various CMS: from 1C-Bitrix to custom solutions on Laravel. Each 1C configuration is unique—standard CommerceML export often does not cover business logic. We build a reliable exchange architecture that eliminates data loss and blocking. We guarantee stable synchronization with any data volume.

One of our projects—a chain of 50 stores—transmitted 10,000 orders daily via RabbitMQ. After implementation, order processing time dropped from 30 minutes to 30 seconds. Time savings—up to 80%. Average maintenance cost savings—up to 40%. We will assess your project for free.

Architectural Integration Options

Option 1: 1C as Master Data 1C holds authoritative data (stock, prices, catalog), the site periodically syncs. Suitable if 1C is the primary accounting system and the site is just a storefront.

Option 2: Two-Way Synchronization Orders are created on the site and sent to 1C. Data updates flow from 1C to the site. Requires careful conflict resolution logic.

Option 3: Site as Master for Orders The site manages orders, 1C receives them for accounting and fulfillment. Catalog data comes from 1C.

How to Choose the Integration Method?

If the load is low and simplicity outweighs fault tolerance, direct web services suffice. For high-load projects, a message broker is 3 times more reliable than direct HTTP. With rare catalog updates (once a day), CommerceML may be enough.

Methods of Connecting to 1C

1C Web Services (SOAP/REST) – 1C publishes an HTTP service via a web server (Apache/IIS). The site calls it directly. Requires publishing 1C externally or using VPN.

Message Broker (recommended) – A queue (RabbitMQ or Redis Queue) sits between the site and a 1C agent. The agent (Node.js, Go, Python) reads the queue and calls the 1C COM object or HTTP service.

Site → RabbitMQ (exchange: site_to_1c) → 1C agent → 1C
1C → RabbitMQ (exchange: 1c_to_site) → PHP Worker → Site

CommerceML (1C→site) – XML format for catalog export from 1C. More details in the CommerceML description.

1C: Connector for Websites – Ready module for 1C-Bitrix. For other CMS, no off-the-shelf solution; custom development is required.

What Data Do We Synchronize?

Synchronization of Nomenclature

From 1C we export: SKU, name, description, characteristics (color, size), unit of measure, VAT, images (URLs or base64), barcodes. Export format: JSON via 1C REST API or XML via CommerceML.

// Process received nomenclature
foreach ($nomenclature as $item) {
    Product::updateOrCreate(
        ['sku_1c' => $item['code']],
        [
            'name'        => $item['name'],
            'description' => $item['description'],
            'price'       => $item['price'],
            'stock'       => $item['stock']
        ]
    );
}

Synchronization of Stock and Prices

Stock and prices change more often than the catalog. They need more frequent sync (every 15–30 minutes). Incremental export—only changed items since last sync—is optimal.

-- In 1C: only export changed items since last sync
SELECT Items.Code, StockBalances.QuantityBalance
FROM AccumulationRegister.WarehouseStock.Balance AS StockBalances
WHERE StockBalances.Period > &LastSync

Transfer of Orders to 1C

Orders are sent to 1C after confirmation and payment. The format depends on the 1C configuration. For "Trade Management", it's a "Customer Order" object:

{
    "Number": "SITE-12345",
    "Date": "2025-01-01T10:30:00",
    "Contractor": {
        "TIN": "7712345678",
        "Name": "IE Ivanov"
    },
    "Items": [
        {
            "SKU": "ART-001",
            "Quantity": 2,
            "Price": 1500.00,
            "Amount": 3000.00,
            "VATRate": "20%"
        }
    ],
    "TotalAmount": 3000.00,
    "Comment": "Courier delivery"
}

Reference Data: Counterparties, Warehouses, Organizations

Before sending an order, we may need to create or find a counterparty in 1C by TIN or email. This is a separate request to the 1C service. If not found, a new one is created.

Typical Errors and Their Solutions

1C is a system with limited fault tolerance. Common errors:

• 1C locked by another user (exclusive mode)
• Referential integrity violation (item in order missing from 1C)
• Timeout with large data volumes

All operations are logged in sync_log with request and error details. Alerts for error bursts are sent to Telegram/email.

Step-by-Step Integration Plan

1. Audit of current 1C and website configuration
2. Design integration architecture
3. Develop REST API/broker/CommerceML
4. Configure sync of catalog, stock, and orders
5. Test and debug with production data
6. Documentation and training for your staff
7. Post-launch technical support

Why Is Security Important?

1C should not be directly accessible from the internet. We recommend:

• VPN or dedicated network between the website server and 1C
• Message broker as the single point of contact
• IP whitelist for the 1C REST service

What Is Included in the Work

• Audit of current 1C and website configuration
• Design integration architecture
• Develop REST API/broker/CommerceML
• Configure sync of catalog, stock, and orders
• Test and debug with production data
• Documentation and training for your staff
• Post-launch technical support

Time savings on order processing—up to 80%, and average maintenance cost savings—40% after implementation.

Development timeline: 6–10 weeks depending on 1C configuration, data volume, and chosen integration method.

Get a consultation for your project. Order an audit of your current integration. We have years of experience and dozens of successful 1C integration projects.

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.