1С-Битрикс with МойСклад Integration: API, Products and Orders Sync

We often encounter a situation where an online store on 1С-Битрикс uses МойСклад for trade management, but there is no standard integration module. Off-the-shelf solutions from the marketplace cover 60–70% of scenarios. The rest — non-standard property mapping, warehouse stock synchronization, and attribute handling — requires custom development. Our experience shows that a properly configured integration pays for itself by eliminating manual entry and errors. Let's dive into the architecture, МойСклад API, and typical problems. In this article, we'll describe in detail the setup process for synchronizing products, stocks, and orders using МойСклад JSON API 1.2. You'll learn how to avoid common mistakes and which tools to use for reliable operation.

What We Synchronize

The Битрикс ↔ МойСклад integration usually involves four data streams:

The direction "МойСклад as master" for products is typical. A content manager works in МойСклад, and the site receives up-to-date data. Reverse synchronization (Битрикс → МойСклад) is rarely needed and creates conflict risk.

How the МойСклад API Remap 1.2 Works

МойСклад provides a REST API (JSON API 1.2) at Remap API 1.2. Authorization is via Basic Auth or Bearer Token.

Key endpoints:

• GET /entity/product — list of products. Supports filtering (filter=updated>${lastSyncTime}), pagination (limit, offset), and expanding nested entities (expand=group,productFolder).
• GET /entity/assortment — combined list of products, modifications, kits, and services. More convenient than product if you need everything at once.
• GET /report/stock/all — stock balances for all products. Can be filtered by warehouse (stockstore).
• POST /entity/customerorder — create a customer order.
• GET /entity/customerorder/{id} — get an order with statuses.

API limitations:

Why Proper Field Mapping Matters

Product synchronization is the heart of the integration. Algorithm for incremental sync:

1. Request GET /entity/assortment?filter=updated>${lastSyncTime}&limit=1000.
2. For each product, find the corresponding element in the Битрикс information block by external code (XML_ID = product UUID in МойСклад).
3. If found — CIBlockElement::Update() with updated fields.
4. If not found — CIBlockElement::Add().
5. Save lastSyncTime = now() in b_option.

Field mapping — the core of integration. Correspondence table:

Characteristics (modifications) in МойСклад are variant inside a product. In Битрикс, they correspond to trade offers (SKU) in a separate information block. Each variant → SKU information block element linked to the parent product via CHL_LINK (property CML2_LINK).

Stock Synchronization

Stock is the most sensitive stream. Selling a product with zero stock is a direct loss. We call GET /report/stock/all with a filter for warehouses that participate in online sales. The result contains assortmentId and quantity. We update the CATALOG_QUANTITY field in b_catalog_product or via \Bitrix\Catalog\ProductTable::update().

To display per-warehouse stock on the site (e.g., "in stock at Lenin store"), use Битрикс warehouse accounting: catalog module, table b_catalog_store_product. Each МойСклад warehouse maps to a Битрикс warehouse (b_catalog_store). Frequency: every 5 minutes via a cron script. Битрикс agents are not suitable for this task — they are tied to hits and do not guarantee the interval.

Order Transfer

When an order is placed in Битрикс (event OnSaleOrderSaved or OnSaleComponentOrderComplete), we create an order in МойСклад via POST /entity/customerorder. Request body structure:

{
  "organization": {"meta": {"href": "...entity/organization/{id}"}},
  "agent": {"meta": {"href": "...entity/counterparty/{id}"}},
  "positions": [
    {
      "assortment": {"meta": {"href": "...entity/product/{id}"}},
      "quantity": 2,
      "price": 150000
    }
  ]
}

The counterparty (agent) is the buyer. For the first order, create via POST /entity/counterparty; for repeat orders, search by email/phone. The counterparty UUID is stored in the Битрикс order user property or in the user UF_ field.

Error Handling and Queue

The network is unreliable; МойСклад API sometimes responds with 500. For orders, use a queue: on send error, save the order to the parser_queue table (or b_sale_order with a flag "not sent to МойСклад"), and an agent retries every 5 minutes. Maximum 5 attempts, after which notify the manager. For products and stock, a queue is unnecessary — the next sync cycle will pick up changes.

What’s Included in the Work

• Analysis of the catalog structure and creation of a mapping map
• Development of synchronization scripts for products, prices, and stock
• Setup of order and counterparty transfer
• Creation of integration documentation
• Training of staff on system operation
• Technical support after launch

Our team has over 10 years of experience and 50+ successful integrations. For an accurate timeline and cost estimate, contact us.

Timeline

Order a consultation on integration, and we will evaluate your project.

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.