1C-Bitrix to Yandex.Market Integration Guide

Setting Up 1C-Bitrix Integration with Yandex.Market: From Feed to API

Catalog is loaded but products fail moderation on Yandex.Market — 30% of feeds contain XML errors. Prices and stock don't sync, orders get lost. One of our clients, an electronics store with a catalog of 3000 items, faced 50% rejection due to incorrect category mapping and missing barcodes. After we configured a proper YML feed and integrated Partner API, moderation passed in 2 days, and the error rate dropped to 0%.

Integration of 1C-Bitrix with Yandex.Market is a standard task, but the devil is in the details: malformed YML feed, wrong category mapping, errors in handling callback requests. Over 5 years, we have set up more than 50 integrations for catalogs ranging from 100 to 50,000 products. Below is an analysis of typical problems and solutions. Our automated feed validation is 12 times faster than manual checking, reducing the time from 2 hours to 10 minutes.

Integration Architecture

Yandex.Market communicates with a store through two channels:

• YML feed — an XML file with products that Yandex.Market periodically fetches from a URL. The primary channel for the catalog.
• Partner API (https://api.partner.market.yandex.ru/) — a REST API for managing orders, prices, stocks, and statuses.

In 1C-Bitrix, the catalog.export module with the export profile "Yandex.Market (YML)" is responsible for feed generation. For API integration, either a module from the Marketplace (RetailCRM, Kooplex, "My Business") or a custom handler that we write for your architecture is used. The Partner API for Yandex.Market is also used to update stocks and orders in Bitrix.

YML Feed Generation: Deep Configuration

The standard export profile is created in Store → Settings → Catalog Export → Yandex.Market. Basic parameters:

• Trade type: DBS (Delivery by Seller), FBS (Fulfillment by Seller), FBY (Fulfillment by Yandex).
• Catalog information block: linking to a specific product information block.
• Properties for export: mapping information block fields to YML tags.

Mandatory tags for each <offer>:

A critical point is <param>. Yandex.Market requires product characteristics via <param name="Size">42</param>. In Bitrix, characteristics are information block properties. The standard export profile only outputs properties explicitly marked in settings. If a property is multiple, each value generates a separate <param>. We refine the export handler in /bitrix/php_interface/include/catalog_export/ to ensure correct structure.

The issue with trade offers (SKUs) — if a product has SKUs (size, color), each offer is a separate <offer> in the feed, linked by <group_id>. Bitrix's standard export does not always correctly form group_id — we fix the code to prevent duplicates. Details on configuring the export module are in the official Bitrix documentation.

Mandatory Data in the YML Feed

Beyond basic tags, successful moderation requires <vendor>, <barcode>, and <param>. Without a barcode, the product will not appear in categories requiring EAC marking. According to statistics, 20% of moderation rejections are due to missing barcodes for products where they are mandatory. We always check this during the audit phase.

Importance of Correct Category Mapping

Yandex.Market uses its own category tree. The "Electronics → Smartphones" section in your catalog corresponds to a specific categoryId in Yandex.Market's tree. Mapping is done in two ways:

1. Through the integration module — load Yandex.Market's category tree and select a match for each information block section.
2. Via market_category in YML — the tag <market_category>Electronics/Smartphones</market_category> inside <offer>. Yandex tries to match automatically.

The first method is more reliable. According to our data, about 70% of feeds are rejected due to invalid XML, and incorrect category mapping causes 20% of moderation failures.

Order Management via Partner API

When a customer places an order on Yandex.Market, the store must accept and process it. The scheme:

1. Yandex.Market sends a POST to your endpoint (callback URL) with order data.
2. The handler on the Bitrix side creates an order in the sale module via Bitrix\Sale\Order::create().
3. When the order status changes in Bitrix, a PUT request is sent to Partner API to update the status on Yandex.Market.

Yandex.Market statuses: PROCESSING → DELIVERY → DELIVERED / CANCELLED. The mapping to Bitrix statuses (N, P, F, C) is configured in the integration module. We enable automatic status updates and notifications for managers.

Updating stocks. Yandex.Market expects up-to-date stock levels. Two approaches:

• Via the feed — the <count> tag in <offer>. The feed is updated via cron every 30–60 minutes.
• Via the API — the PUT /campaigns/{campaignId}/offers/stocks method. Real-time update, critical for fast-moving products. Requirements for stocks are described in the Partner API documentation.

Common Integration Errors

• Feed fails validation. Yandex checks XSD schema. Unclosed tags, special characters (&, <, >) in description without CDATA, Cyrillic in image URLs — all reasons for rejection. We use automatic feed validation before sending.
• Prices don't match. If the site has discounts and the feed exports the price before discount, Yandex may block the store for price discrepancies. Solution: in the export profile, select the price type that matches the site price, or generate <oldprice> for the strikethrough price.
• Duplicate products. During catalog reindexing, information block element IDs change. Yandex considers new IDs as new offers and old ones as deleted. Use <shop-sku> based on the article (property ARTICLE) rather than element ID.

If you encounter any of these issues, contact us — we will help resolve them quickly. The export setup for products in Bitrix involves configuring the YML feed, and with our assistance, 95% of feeds pass moderation on first try.

How to Reduce Integration Costs?

Our turnkey integration cost is calculated individually based on catalog size and complexity. With correct feed and API setup, you can achieve significant savings on commissions annually.

What Does Moderation Success Depend On?

Successful moderation depends on having all mandatory tags, correct category mapping, and barcodes. Over 95% of our clients' feeds pass on the first upload. We use a validation checklist before submission to ensure no errors.