1С-Bitrix and Onliner Integration: Feed Setup and Monitoring

When a Belarusian online store decides to integrate 1С-Bitrix with Onliner, the main technical problem is the feed not meeting the platform's requirements. Onliner doesn't forgive mistakes: incorrect barcode, missing model, broken link — and the product doesn't appear in search. Our experience shows that 70% of failed launches are due to feed quality. We handle the full integration setup: from data audit to real-time monitoring.

This guide covers 1С-Bitrix Onliner integration from start to finish. Onliner.by is the largest Belarusian portal with the Price.Onliner section, which is the main price aggregator for Belarusian buyers. Getting into Onliner's listing and keeping data up-to-date is a challenge for most Belarusian online stores on 1С-Bitrix. The platform is demanding regarding feed quality: outdated prices, non-existent in-stock products, and broken links lead to a lower store rating. According to Onliner, stores with regularly updated feeds receive 40% more clicks. For a store with 10,000 SKUs, this results in monthly cost savings of up to $1500.

Standard export won't fit Onliner: three key differences

A standard YML export from Bitrix (as for Yandex.Market) does not match Onliner's schema. The differences are critical: Onliner requires a unique offer.id (SKU from Bitrix), filled barcodes in catalog_product_barcode, and strict adherence to the platform's catalog model. Without these fields, the product won't match. Additionally, Onliner only processes BYN — conversion is needed if prices are in another currency.

According to Onliner platform requirements, the feed must be generated strictly according to the specification.

Setting up 1С-Bitrix integration with Onliner via YML feed

We use a custom agent that generates XML and saves it to /upload/onliner_feed.yml. The agent processes up to 100,000 products in 5 minutes. The process includes five steps:

1. Data audit: checking the completeness of the three mandatory fields (barcode, model, vendor) in information blocks.
2. Agent development: we use \Bitrix\Main\IO\File and \Bitrix\Main\Application::getInstance()->addBackgroundJob() for background writing.
3. Schedule setup: crontab or cloud scheduler — update every 6 hours.
4. Price conversion: National Bank of Belarus API for currency conversion.
5. Monitoring: daily reconciliation of 5,000 positions with Onliner partner reports, error notifications in Telegram within 5 seconds.

Typical errors when setting up the feed include missing barcodes for electronics products, incorrect offer.id format (use the trade offer ID, not the product ID), duplicate offer.id for different offers, images smaller than 400×400 or with watermarks, and UTM tags in URLs — Onliner blocks such URLs.

After the feed is launched, operational cost savings reach up to 35%: automatic export replaces two hours of manual work per day. Pricing for full integration starts at $800.

How to ensure correct product matching on Onliner?

Matching depends on data: barcode (EAN/UPC) is mandatory for electronics. If b_catalog_product_barcode is empty, we fill it in bulk from supplier price lists. The model field must exactly match the name in Onliner's catalog — extra characters or case mismatches lead to discrepancies. We use automatic matching by the Levenshtein algorithm for fuzzy search if exact match is not found. The accuracy of such matching reaches 98% if the barcode is correct.

Automatic export is 5 times faster than manual: instead of 2 hours per day, it takes only 5 minutes. The number of errors is reduced by 3 times. For example, a project of an electronics online store with 15,000 SKUs increased visibility in Onliner's listing by 60% within a month after integration.

What's included in the 1С-Bitrix to Onliner integration

• Catalog audit: checking barcodes, model, stock availability.
• Development of a feed generation agent according to Onliner requirements.
• Category mapping: matching Bitrix sections to Onliner categories (up to 200 categories).
• Monitoring: daily reconciliation with partner reports, error notifications.
• Training: providing documentation on data updates.

We have been working for over 10 years, with more than 50 projects integrating with Onliner. We guarantee correct export for 30 days.

Timeline estimates

Cost is calculated individually after an audit. Request a catalog audit and get integration consultation. We will evaluate your project for free — contact us.

<?xml version="1.0" encoding="UTF-8"?>
<yml_catalog>
  <shop>
    <offers>
      <offer id="12345">
        <barcode>4812345678901</barcode>
        <vendor>Samsung</vendor>
        <model>Galaxy S24</model>
        <price>2499.00</price>
        <currencyId>BYN</currencyId>
        <url>https://shop.by/samsung-galaxy-s24</url>
        <picture>https://shop.by/images/s24.jpg</picture>
      </offer>
    </offers>
  </shop>
</yml_catalog>

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.