Yandex.Market Product Feed Setup in 1C-Bitrix

We often encounter this scenario: a client launches product ads on Yandex.Market, and the system reports that 30% of items are not participating. Missing required attributes. On one project, out of 12,000 SKUs, only 7,000 were included in ads. The reason — absence of <param> tags with characteristics: color, memory, size. Without them, Yandex cannot properly match a product to a query, and campaign effectiveness drops by 2–3 times. A well-configured feed solves this problem and saves up to 30% of the advertising budget through better targeting. It reduces cost-per-click by 15–20% due to precise query matching.

What problems does a proper YML feed solve?

A correctly formed feed is not just a catalog export. It is the ability to control how Yandex sees your products. Without <param> tags, products do not appear in refined queries ("buy smartphone 128 GB black"). With them, conversion increases by 15–25%. Additionally, the absence of a product advertising profile means Yandex cannot correctly display ads by model, brand, or category.

Why standard export is not enough

The built-in profile (Catalog → Export → Add profile → Yandex.Market (YML)) generates a basic feed but does not output information block properties as <param>. For product ads, this is critical: without parameters, Yandex cannot show ads for refined queries. Also, the standard export does not allow flexible management of trade offer structure, and for large catalogs (over 50,000 items), generation time reaches 2 hours.

Let's compare the approaches:

A custom generator processes a catalog of 50,000 items 8 times faster – 15 minutes instead of 2 hours. This is especially important for daily feed updates.

How to speed up feed generation?

For large catalogs, use streaming XMLWriter without buffering the entire DOM. For example:

// /local/cron/yandex_market_feed.php
$categories = getIblockSections($IBLOCK_ID);
$tmpFile = tempnam(sys_get_temp_dir(), 'yml_');
$xml = new XMLWriter();
$xml->openUri($tmpFile);
$xml->startDocument('1.0', 'UTF-8');
// ... генерация структуры yml_catalog

Official documentation: YML format Yandex.Market emphasizes: the feed must contain all characteristics that influence buyer choice. We guarantee this.

How to add missing parameters to the feed?

The solution is to hook the OnGetYmlOfferXml event and add <param> elements:

// /local/php_interface/init.php
\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'catalog',
    'OnGetYmlOfferXml',
    function (\Bitrix\Main\Event $event) {
        $offer = $event->getParameter('OFFER');
        $xml   = $event->getParameter('XML');

        $paramProps = ['COLOR' => 'Color', 'MEMORY' => 'Memory', 'SCREEN_SIZE' => 'Screen size'];
        foreach ($paramProps as $propCode => $paramName) {
            if (!empty($offer['PROPERTIES'][$propCode]['VALUE'])) {
                $xml .= sprintf(
                    '<param name="%s">%s</param>',
                    htmlspecialchars($paramName),
                    htmlspecialchars($offer['PROPERTIES'][$propCode]['VALUE'])
                );
            }
        }

        return new \Bitrix\Main\EventResult(
            \Bitrix\Main\EventResult::SUCCESS,
            ['XML' => $xml]
        );
    }
);

Steps:

1. Identify the information block properties to be exported as parameters (color, memory, size).
2. Write a handler for OnGetYmlOfferXml that adds <param> for each property.
3. Validate the feed in your Yandex.Market account.

Typical errors and how to fix them

A common issue is an incorrect date format in yml_catalog. The date must be in YYYY-MM-DD HH:MM format, otherwise the feed is rejected. Duplicate offer IDs occur when products and trade offers have the same ID. Solution: generate unique IDs, e.g., 'Product123-Offer1'. Invalid XML characters (like ampersand) must be replaced with &. And finally, all products must have a price (price tag) — if missing, the item is not exported.

What is included in feed setup

Our engineers (5+ years of Bitrix experience, over 50 configured feeds) perform the full cycle:

• Analysis of catalog structure and information block properties. We identify which characteristics matter for Yandex.Market and check their completeness.
• Feed scheme design: we map standard fields and add custom parameters via events or a custom generator.
• Implementation: we write handlers or a separate generation script, using XMLWriter for performance.
• Testing: we upload the feed to Yandex.Market account, check for errors and validity.
• Performance optimization: for catalogs over 10,000 items, we configure caching and streaming writing.
• Integration with cron scheduler for daily feed updates.

Timeline estimates for setup

Standard YML profile with property mapping and <param> addition via hooks – 4–8 hours. Custom generator for complex catalog with trade offers and parameters – 1–2 business days. For an accurate estimate, a consultation on your project is required.

Get a free audit of your current feed — contact us. We will check the structure, performance, and advise on how to improve the export. Order feed setup and increase advertising efficiency.

Parser Development for 1C-Bitrix: Where to Start?

XMLReader, not SimpleXML — the choice of tool determines the project's fate. SimpleXML loads the entire XML into memory, and with an 800 MB supplier file, PHP will crash with a fatal error on a 512 MB limit. XMLReader processes streamingly, node by node, consuming 20–30 MB — 30 times more efficient. This detail starts any parser development for Bitrix. With over 10 years of Bitrix development and 50+ parser projects delivered, we know the pitfalls. Contact us to start your parser development today.

What Problems Does Parsing Solve?

• Primary catalog filling — 15,000 cards with descriptions, characteristics, photos. Manually, that's three months of content manager work; a parser takes a week with debugging.
• Competitor price monitoring — collecting data from Ozon, Wildberries, competitor sites. A competitor drops the price on a hot item — you find out in two hours, not two weeks.
• Supplier aggregation — five price lists in different formats (CSV with CP1251, XML in CommerceML, Excel with merged cells) become a single catalog with a unified property system.
• Card enrichment — pulling characteristics, instructions, 3D models from manufacturer sites. Without this, a product card is an SEO empty shell.
• Assortment update — products missing from the supplier feed are deactivated via CIBlockElement::Update($ID, ['ACTIVE' => 'N']). New ones are created. The catalog stays synchronized.

What Tools Do We Use in Parser Development?

Static websites — PHP (Goutte, Symfony DomCrawler) or Python (Scrapy, lxml). Speed: 50–100 pages/sec. Sufficient for catalogs without JS rendering.

SPA and dynamic websites — Puppeteer or Playwright. Infinite scroll, AJAX filters, lazy-load images — headless browser handles it all. Speed drops to 1–10 pages/sec, but there is no alternative: data exists only after JavaScript execution.

Supplier files:

• Excel (XLS, XLSX) — PhpSpreadsheet. Beware of merged cells and formulas — they break automatic mapping.
• CSV — fgetcsv() with correct encoding. Suppliers love CP1251, BOM in UTF-8, and semicolons instead of commas. All need detection and handling.
• XML/YML — XMLReader for large files, SimpleXML for feeds up to 50 MB.
• CommerceML — standard exchange format with 1C. We parse import.xml and offers.xml, map to information block structure.

API — Supplier REST endpoints, marketplace APIs (Ozon Seller API, Wildberries API). We work within rate limits, handle pagination.

How Is the Auto-Population Pipeline Structured?

Four stages. Each can break in its own way.

1. Collection. Parser crawls sources via cron schedule. Raw data goes to an intermediate table — not directly into b_iblock_element. Log everything: pages visited, elements parsed, where we got 403 or timeout. Without logs, debugging a parser is like fortune-telling.

2. Normalization. Main work here:

   • Clean HTML tags, extra spaces, Unicode garbage
   • Units: "mm" → "mm", "millimeters" → "mm", "миллиметр" → "mm"
   • Map supplier categories to Bitrix information block sections. One supplier has "Notebooks", another "Notebooks and tablets", third "Laptops" — all into one section
   • Deduplication by SKU, EAN/GTIN. One product from three suppliers should not appear three times

3. Load into Bitrix. Via CIBlockElement::Add() for new elements, CIBlockElement::Update() for existing. Images: download, resize via CFile::ResizeImageGet(), convert to WebP. Properties via CIBlockElement::SetPropertyValuesEx(). SEO meta via \Bitrix\Iblock\InheritedProperty\ElementValues. SEF URLs generated from name transliteration.

4. Update. Key point — not overwrite manual edits by content manager. Update only price, stock, activity. Description and photos manually edited are flagged with UF_MANUAL_EDIT property and skipped during import. Products missing from feed are deactivated, not deleted.

Why Is Competitor Price Monitoring Necessary?

A separate subsystem with its own specifics:

Result — dashboard: your product vs competitors, price history, trends. The manager sees where to raise price without losing position, and where to react.

CSV/XML Import Module: Customization for Your Format

For supplier files — custom module with admin panel:

• Configurable mapping: "column B in file → BRAND property of information block"
• Auto-detect encoding (CP1251, UTF-8, UTF-16) via mb_detect_encoding() with validation
• Download images from URL with queue — to avoid channel saturation
• Incremental update by row hash: row changed — update, no — skip
• Cron schedule, report: created 145, updated 892, errors 3 (with details)

Large files: CSV processed in batches of 1000 rows via fgetcsv() (10 times faster than row-by-row), XML streamed via XMLReader, background execution via Bitrix agent queue — no PHP timeouts.

Legal Aspects to Consider

• robots.txt — respect it. Crawl-delay — comply.
• Request frequency — 1–2 per second, no more. Don't DDoS someone else's site.
• Manufacturer content — use it. Unique author texts — don't copy.
• Personal data — don't collect.

What Is Included in a Turnkey Parser Development?

How We Work and Deadlines

1. Prototype — parser for 1–2 sources in 2–3 days. Assess data quality, pitfalls (Cloudflare protection, captcha, dynamic loading).
2. Development — full pipeline: parser → normalization → import into Bitrix → admin panel for management.
3. Testing — run on full catalog volume, check edge cases (empty fields, malformed HTML, broken images).
4. Launch — configure cron, error monitoring via Telegram bot.
5. Support — competitor changed layout? Update CSS selectors in parser.

Get in touch for a free consultation — we will analyze your data sources and propose the optimal parser architecture. Request a project assessment today and get a fixed deadline. We guarantee stable parser operation and full support throughout the usage period.