Effortless Real-Time Data Sync for 1C and Bitrix Stores

Effortless Real-Time Data Sync for Your 1C-Bitrix Store

Imagine your online store runs on 1C-Bitrix while inventory and accounting are in 1C. During a promotion, you update prices, but CommerceML transfers them every 30 minutes. Customers see outdated prices and incorrect stock levels—orders ship with negative inventory. Sound familiar? We specialize in integrating 1C and Bitrix via a REST-based interface. With over 10 years in production, we've deployed seamless exchange for 100+ projects. Our solution synchronizes data in real time, eliminating delays and errors.

CommerceML is a synchronous batch file exchange. REST API is event-driven, triggering updates the moment data changes. The difference is critical: REST updates data in seconds and supports entities CommerceML cannot handle—custom directories, documents, tasks. That's why this approach is becoming the de facto standard for modern commerce.

Why REST API Is Faster Than CommerceML

When to Choose REST API Over CommerceML

REST integration is justified when: data must update faster than every 15 minutes (promotional prices, critical stock); exchanging non-standard data; integrating with a custom 1C configuration that lacks the standard exchange handler; connecting multiple sites or services to the same 1C database. Moving to this method reduces manual sync overhead and lowers error probability.

How We Configure Inventory Sync via REST

Bitrix provides REST API through the rest module. For external systems, create an inbound webhook: Settings → Product Settings → REST API → Inbound Webhooks → Add. Assign only required permissions: catalog for catalog, sale for orders. Never grant administrator rights.

From 1C (via HTTP connection in the configurator), send a request to the Bitrix API:

POST https://myshop.ru/rest/1/WEBHOOK_KEY/catalog.storeproduct.update
Content-Type: application/json

{
    "productId": 12345,
    "storeId": 3,
    "amount": 47
}

This is a point update—only the specific product at the specific warehouse is changed. Unlike batch processing that handles all 50,000 items, a REST call takes milliseconds.

Case study: For one client with a catalog of 20,000 items, we replaced a CommerceML sync that took 8 seconds per operation with REST API calls averaging 1.2 seconds. Manual error corrections dropped by 90%.

How We Deliver Orders to 1C Without Delays

Instead of file exchange, 1C polls the REST API on a schedule:

GET https://myshop.ru/rest/1/WEBHOOK_KEY/sale.order.list
    ?filter[STATUS_ID]=N
    &filter[>=DATE_INSERT]=DATE_LAST_SYNC
    &select[]=ID
    &select[]=ACCOUNT_NUMBER
    &select[]=PRICE
    &select[]=CURRENCY

The response is a JSON list of new orders. 1C processes each, creates documents, then updates the status via sale.order.update.

For immediate event delivery (new order, status change), set up Bitrix outbound webhooks that send data to an HTTP service in 1C: Settings → REST API → Outbound Webhooks → Add. Enter the HTTP service URL and event type ONSALEORDERNEW. When a new order appears, Bitrix immediately POSTs to 1C—no waiting for the next exchange session.

How to Avoid Common Integration Errors

Frequent issues: incorrect webhook URL (no response), order duplication (improper status handling), authentication error (wrong key). Solutions: check HTTP service accessibility, use idempotent keys, verify permissions in REST API settings. Details in the official documentation.

What's Included in Our Turnkey Configuration

• Audit of your current integration to identify bottlenecks.
• Design of exchange schema: selecting REST methods, setting up webhooks.
• Implementation of HTTP service in 1C to receive requests.
• Writing exchange scripts for inventory, prices, and orders.
• Testing synchronization accuracy on test data.
• Operation documentation and training for your staff.
• One month of warranty support after deployment.

Our Process

1. Analysis: We study your 1C configuration and site setup.
2. Design: We develop integration architecture.
3. Implementation: We configure REST API and write the HTTP service.
4. Testing: We verify sync across all scenarios.
5. Deployment: We go live in production.

Timeline and Pricing

Basic inventory and order sync: 1–2 days. With bidirectional webhooks: 3–5 days. Full replacement of CommerceML for a large catalog: 1–3 weeks. Price is determined after audit. Our basic integration starts at €500 and typically pays for itself within 2-3 months through reduced manual labor. Contact us for a free consultation—we'll evaluate your project and propose the best solution. The investment typically pays for itself in 2–3 months.

We guarantee quality: all work is done by engineers with 10+ years of experience in Bitrix and 1C. We provide certificates and references. Order your integration today—get a free consultation.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.