Complete Guide: Exporting Serial Numbers and Batches from 1C to Bitrix

In an electronics online store, a buyer enters a serial ID and sees the warranty period, model, and sale date. Or a grocery customer selects milk and sees that the batch in stock has an expiry date of May 25. Without configuring the export of serials and batches from 1C to Bitrix, such scenarios are impossible. The standard 1C-Bitrix synchronization via CommerceML transfers prices and balances — but not serial numbers and batches. For electronics, medical equipment, groceries, and pharmaceuticals, this is critical: without a serial number, warranty service cannot be organized, and without batch tracking, sell-by dates cannot be monitored. The exchange must be modified so that the site receives this data. Our experience shows that even minimal transfer (e.g., only expiry date) gives the business a competitive edge and reduces returns by up to 30%.

Why the standard exchange fails for serials and batches

CommerceML (the data transfer standard between 1C and Bitrix) does not directly handle serials and batches. The XML structures lack tags for serial numbers in product balances. The format must be extended: add AdditionalRequisites to the document or create separate exchange files. An alternative is REST API, but 1C UT/KA do not provide ready-made REST services for batch accounting. The CommerceML standard does not support serial numbers (see official documentation).

Serials and batches in 1C

Serial — a unique identifier of a specific instance (serial number). One TV = one serial. Accounting in the GoodsInWarehouses register is maintained per serial.

Batch — a group of goods from one receipt with common characteristics (production date, expiry date, manufacturer batch number). One box of milk of a certain date = one batch. A warehouse may have 10 boxes from two different batches.

In 1C:UT 11, serial accounting is enabled in the item settings: Use serials. Batch accounting is a separate setting. Both mechanisms increase granularity and complicate data exchange.

Required data on the website

It is not always necessary to transfer all serials and batches. Typical scenarios:

Prices for integration vary from $2,500 for basic serial verification to over $6,000 for full batch selection. Clients typically see ROI within 6 months.

How to implement expiration date as an attribute?

The most demanded case is transferring the nearest expiration date from 1C to the site. Steps:

1. In 1C (on the UT/KA side), create a scheduled job.
2. For each item with batch accounting, determine the nearest expiry date from existing balances.
3. Write this date into the AdditionalRequisite of the item "ExpirationDate".
4. On the next exchange, this requisite will appear in the XML and update the property in Bitrix.

Alternative: a direct HTTP request from Bitrix to a 1C service when loading the product card. However, this creates a dependency of page speed on 1C speed; response time may increase by 300ms.

How to transfer serial numbers during an order?

If a buyer orders a product with serial accounting — when shipping from 1C, a specific serial number is attached to the order. It is useful to transfer this number back to Bitrix: in the personal account, the buyer sees the serials of purchased products — convenient for warranty service.

Reverse transfer of serials: in CommerceML, an order when updating its status can contain extended data. Add saving logic for serial numbers from the document's AdditionalRequisites to the status update handler in Bitrix.

// Order update handler from 1C
function onOrderStatusUpdate($arOrder, $arXML) {
    foreach ($arXML['ITEMS'] as $item) {
        if (!empty($item['SERIAL_NUMBERS'])) {
            saveSerialNumbers(
                $arOrder['ID'],
                $item['PRODUCT_ID'],
                $item['SERIAL_NUMBERS']
            );
        }
    }
}

Batch reservation in 1C

When an order is placed on the site and sent to 1C, a specific batch must be reserved (especially with a short expiry date). The standard reservation mechanism in 1C automatically reserves a batch using the FEFO algorithm (First Expired First Out).

On the site, the buyer does not choose a batch — 1C does. The site only transfers the quantity. 1C reserves the appropriate batch and can return information about it (the expiry date of the reserved batch) in the order response.

Case from our practice: a food manufacturer

Our client is a dairy producer. Direct B2B sales from the site to retailers. Each order is for specific SKUs considering batches (production date, expiry date). The retailer wants to see on the site not just 'milk 1L', but 'milk 1L, produced 10.03, expiry 20.03'.

We implemented via HighloadBlock 'Batches': during each exchange (every 2 hours), a list of available batches for each item is transferred from 1C. In the product card, there is a dropdown 'Select production date'. When added to the cart, the batch ID is saved. When the order is sent to 1C, the batch GUID is specified in the order item requisites.

1C reserves the specific batch — no expiry date errors. Client savings: a 20% reduction in spoilage due to expiry dates, equating to $50,000 annually.

Deliverables and project scope

• Audit of current 1C-Bitrix exchange (2 days)
• Design document with serial/lot transfer scheme (1 day)
• Modification of 1C: scheduled jobs, additional requisites (3-5 days)
• Modification of Bitrix: properties, HL blocks, order handlers (3-5 days)
• Testing and launch (2 days)
• Documentation and training (1 day)
• Post-implementation support (1 month)

We have been working with 1C for over 7 years and have completed more than 30 integrations with Bitrix. We will assess your project in 1 day. Order turnkey export setup for serials and batches from $5,000. Get a consultation right now.

In this guide, we have covered how to configure the 1C Bitrix exchange for serial numbers and batches. For batch accounting integration in ecommerce, proper setup ensures accurate stock and expiry information.

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.