Tailored Export Solutions for 1C-Bitrix: Tackling Large Catalog Feeds

When a client with a catalog of 15,000 items complains that Yandex.Market doesn't accept the feed and price aggregators see only half the products, the issue is almost always the standard YML export from 1C-Bitrix. Setting up 1C-Bitrix YML setup for large catalogs requires a special approach. YML (Yandex Market Language) is an XML format for transferring product data. According to the documentation, YML is the standard format for data exchange with Yandex.Market. We encounter this regularly: the built-in profile of the catalog module generates XML suitable only for the storefront, not for external platforms.

The challenge is not simply to enable export. You need to: configure stock filtering YML, correctly form trade offer names, export multiple images YML, add tags for discounts and delivery, and ensure the file updates automatically and stays valid. Our team of certified 1C-Bitrix developers has over 7 years of experience and has completed 150+ Bitrix projects. This turnkey solution is delivered in 1-2 days. Typical cost for a custom profile: $500-$1500, depending on catalog complexity. Savings from fixing errors can exceed $2000 per month.

Custom YML Export Setup for 1C-Bitrix

A custom export profile generates the feed 2-3 times faster than the standard one for catalogs of 30,000 items, while solving critical issues.

Why the standard YML export doesn't suit large catalogs?

The standard export profile (Shop → Settings → Catalog Export) generates a basic YML, but it has several critical limitations:

• Trade offers. If a product has SKUs (trade offer information block), an is created for each variation, and the is taken from the offer name, not the main product. As a result, instead of "Nike Air Max sneakers" you get "Nike Air Max sneakers — White, size 42". This may be acceptable for Yandex.Market but not for many aggregators.
• Multiple images. The standard export only takes DETAIL_PICTURE. Additional images from the MORE_PHOTO property must be explicitly connected in the profile settings. Each photo is a separate tag, and if not done, the feed will contain only one image per product.
• Stock filtering. There is no way to export only products with positive stock. All active items are exported. Deactivating out-of-stock items is a bad idea (harms SEO). The only solution is to modify the profile.
• Special characters. Symbols &, <, > in descriptions break XML. The standard profile escapes them, but if the information block properties contain raw HTML, the feed may become invalid. Validation via xmllint or an online YML validator is mandatory. We also use XSLT transforms to customize the feed and validate against the YML XSD schema.

How we configure YML export: a custom profile

We do not edit /bitrix/modules/catalog/load/yandex_run.php directly — changes will be lost on update. Instead, we copy the file to /bitrix/php_interface/include/catalog_export/, give it a new name, and register it as a custom profile.

Typical customizations:

• Custom format. Form the name as "Brand + Model + Key Property" instead of the standard NAME.
• for discounts. The standard profile does not export the strikethrough price. We fill it from another price type (e.g., "Retail before discount").
• . Tag with delivery conditions for Yandex.Market. Generated based on the Shipping module settings.
• <sales_notes>. A note for the buyer (up to 50 characters), e.g., a note specifying minimum order amount.

The custom profile solves all the listed problems and ensures feed validity. Based on our measurements, generation speed for a catalog of 30,000 items increases 2-3 times due to query optimization. Savings from fixing incorrect export errors can be substantial — one client saved $2000/month after fixing broken feeds. The cost of creating a custom profile is determined after analysis, typically starting at $500.

How to speed up YML generation for 50,000 items?

For catalogs over 50,000 items, standard generation can take 3-5 minutes and often times out. The solution is stepwise generation, splitting into parts of N items per iteration. We use Bitrix agents that run every 30-60 seconds and process 1000 items per step. This keeps within max_execution_time and does not overload the server.

Cron task for background generation:

*/30 * * * * /usr/bin/php /var/www/bitrix/modules/catalog/load/yandex_run.php PROFILE_ID

Alternatively, through an agent in the profile settings — the "Periodic export" option. Interval — 30-60 minutes for most stores. This ensures automatic YML generation for marketplaces.

Process

1. Analysis — examine the current catalog, information block structure, price types, presence of trade offers.
2. Design — agree on the list of tags and export format with platform requirements.
3. Implementation — create custom profile, add filters, tags, configure tagged caching.
4. Testing — validate via xmllint, test on sandbox platforms.
5. Deployment — set up cron/agent, connect monitoring (check file update date).

Timeframes

Cost is calculated individually — depends on catalog complexity (number of information blocks, properties, price types). On average, clients invest $800-$1500.

What's included

• Fully configured YML feed with necessary tags (guaranteed valid according to Yandex.Market 2.0 specification).
• Custom export profile with filtering and formatting.
• Automatic generation setup (cron/agent).
• Monitoring of validity and update date.
• Documentation on the profile and instructions for your administrator.
• 2 weeks of post-launch support (error fixes, tag adjustments).
• Certificate of completion and code audit.

Get a consultation on YML export setup — we'll evaluate your project in one day. Order turnkey setup — timelines from 1 day. Avoid standard export problems with our proven solution.

Savings from eliminating errors can be significant, and a correct feed architecture avoids substantial monthly losses due to data inconsistency. We guarantee a 99.9% uptime of your feed.

This guide covers custom export profile creation, stock filtering YML, multiple images YML, trade offers YML, automatic YML generation, and addresses standard export problems for large catalog YML optimization.

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.