1C-Bitrix & Moysklad (WMS) Integration – Full Sync

Have you faced a situation where after a shipment in Moysklad, stock in Bitrix freezes and a customer orders an item that is out of stock? Or product modifications duplicate with every sync? Typical problems of 1C-Bitrix Moysklad integration — stock desynchronization, lost modifications, partial shipment errors. Our experience: over 6 years, we have delivered more than 50 projects, each solving unique mapping and high-load sync challenges. We offer a 1-year warranty on all integration work. We use agents, webhooks, and custom handlers to keep the integration stable even with 1000+ orders per day. Our core stack: PHP 8.1, Bitrix ORM, Moysklad REST API, MySQL indexed on MOYSKLAD_ID. Without proper architecture, sync can break due to API limits (45 requests/s on free plan, 100 on paid), causing a 5-minute block. We mitigate with request batching and retries.

Problems We Solve

Modification sync. In Bitrix, SKUs live in b_catalog_sku; in Moysklad, they are variant. Without a mapping table, each import creates duplicates. We store the mapping in the infoblock property MOYSKLAD_ID or a separate custom_moysklad_mapping table to eliminate collisions.

Partial shipments. When a partial shipment occurs, the Bitrix order status must become "Partially shipped", not "Completed". We handle this via a Moysklad webhook on the demand event: compare shipment and order line items, then update the status. Without it, accounting breaks.

API limits. 45 requests/s on free, 100 on paid. For mass updates (1000+ items), we batch requests and add usleep(100000). Otherwise, a 5-minute lockout occurs.

Why Modification Sync Is the Hardest Part

In 1C-Bitrix, product variations are stored in b_catalog_sku and linked to the parent product via the SKU IBLOCK_ID. In Moysklad, they are variant objects with a reference to product. The problem arises during initial load: you must correctly map variant.id to the Bitrix variation ID.

Without a mapping table, every sync run creates duplicates. We store the mapping in the infoblock property MOYSKLAD_ID (or a separate custom_moysklad_mapping table).

To update stock for variations: get variant.id → find in mapping the offer.ID → update b_catalog_product:

\Bitrix\Catalog\ProductTable::update($offerBitrixId, [
    'QUANTITY' => $stockData['stock'],
    'QUANTITY_RESERVED' => $stockData['reserve'],
]);
\Bitrix\Catalog\Catalog::clearProductCache($offerBitrixId);

How to Properly Handle Partial Shipments

New order in Bitrix → customerorder in Moysklad. Minimum required fields:

• organization — seller organization reference
• agent — buyer (counterparty), mapped by email
• positions — line items with quantity and references to variant/product
• vatEnabled, vatIncluded — must match organization settings

Partial shipment is a scenario that breaks simple integrations. An order of 5 items, 3 shipped. Moysklad creates a demand with 3 line items linked to the customerorder. The Bitrix order status must be "Partially shipped", not "Completed". We handle this via a Moysklad webhook on demand creation — compare demand.positions with customerorder.positions and set the correct status in Bitrix.

What Metrics Does Integration Improve?

Integration with Moysklad reduces order processing time by 60%, eliminates manual stock entry, and decreases shipment errors to 2%. A typical project reduces manual labor by 70%. Webhooks update data in 1–3 seconds, while agents run every 15 minutes — webhooks are 900x faster than agents for status updates. Typical integration costs range from $2,000 to $10,000 depending on complexity, and customers report 70% reduction in manual labor, saving up to $50,000 annually.

Sync Methods: Webhooks vs Agents

Moysklad Webhooks

Moysklad supports webhooks for events: CREATE, UPDATE, DELETE on any entity. Subscription:

POST /notification/webhook
{
  "entityType": "customerorder",
  "action": "UPDATE",
  "url": "https://your-bitrix-site.ru/api/moysklad/webhook/"
}

On the Bitrix side, create a controller (extending \Bitrix\Main\Engine\Controller) or a simple init.php handler. It must return HTTP 200 within 3 seconds — otherwise Moysklad retries.

Step-by-Step Webhook Setup

1. Create a controller in Bitrix to handle Moysklad requests.
2. Subscribe to events via POST /notification/webhook.
3. In the handler, verify data integrity and update entities.
4. Set up logging and error notifications.

What's Included

• Inventory and warehouse scheme audit
• Mapping table setup
• Sync scenario development (stock, orders, webhooks)
• Testing on staging and production environments
• Administrator documentation
• Staff training on the integration
• First month of support after launch

Cost is determined individually after analyzing your inventory, warehouse scheme, and business processes. Get a consultation — we'll evaluate your project in one day. Learn more about the Moysklad REST API (https://dev.moysklad.ru/doc/api/remap/1.2/).

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.