Yandex product feed integration — generate and maintain a YML feed for Yandex Products, Market, and related services so prices, stock, images, and attributes stay in sync via URL without manual exports. VivaCoding in Cyprus (Paphos) connects feeds from €290 in typically 3–7 days: WooCommerce, OpenCart, Bitrix, Laravel, and custom catalogues.
A Yandex product feed is a YML file (Yandex Market Language, XML) describing the store and offers: id, name, price, currency, URL, images, description, categories. Yandex fetches the feed from a direct link and updates the catalogue. Without a valid, fresh feed, cards in Yandex Products and on Market either never appear or fail diagnostics.
Below: why YML matters, which 2026 requirements break uploads, VivaCoding packages, how a feed differs from manual cabinet entry and Google Merchant, and when API/1C beats a file-only setup.
Key takeaways
- YML over HTTPS with auto-refresh is the main path; manual file upload is for testing only.
- VivaCoding ranges: Start from €290, Business from €490, Custom from €890+; basic export usually takes 3–7 days.
- Critical: UTF-8, fresh
date(feed not older than ~10 days), unique ids, correct price/url/picture, parity with the site. - Market fees and ads are separate; we handle technical export and error diagnostics.
What Yandex feed integration means
Integration means generating YML from your CMS/ERP and publishing a stable URL that Yandex periodically downloads. Scope usually covers: catalogue fields → YML elements, filters (what to export), rebuild schedule, validator/cabinet diagnostics, and fixes (broken images, duplicate ids, stale date).
Where the feed connects
- Yandex Products / product search — product surfaces after site ownership in Webmaster.
- Yandex Market — assortment for placement models (including DBS and delivery fields in YML).
- Ads and retargeting — product campaigns that pull creatives and prices from the feed.
- Price comparison / aggregators — third parties that accept YML.
YML requirements that break exports
From Yandex docs and 2026 practice, common blockers:
- Root
yml_catalogwith adateattribute; stale feeds are rejected. - UTF-8 encoding (or Windows-1251); URL-hosted feeds allow larger catalogues than manual cabinet upload.
- Unique offer
ids; required fields: name, price, currencyId (Market often RUB/RUR), url, picture. - Prices and availability must match the site — or moderation and buyer complaints follow.
- Images reachable over HTTPS, adequate size, no single placeholder for every SKU.
Platforms we support
| Platform | Typical path | When custom |
|---|---|---|
| WooCommerce | YML plugin/export + field tweaks | Complex variations, B2B prices |
| OpenCart / Bitrix | Export module + attribute mapping | Multi-warehouse, custom price types |
| Laravel / custom | YML generator + cron + cache | Large catalogues, multiple storefronts |
| 1C / ERP | Export → intermediate feed or API | Frequent stock, multiple legal entities |
Packages
Prices cover integration work. Market placement, ad spend, and platform fees are separate. Pricing sits in the same band as other Cyprus integrations (basic link in the low hundreds of euros; custom higher).
| Package | From | Timeline | Includes |
|---|---|---|---|
| Start | €290 | 3–5 days | CMS YML, public URL, basic mapping, diagnostics pass, cabinet setup guide |
| Business | €490 | 5–10 days | Start + filters/categories, variations, schedule, cabinet error fixes, generation failure alerts |
| Custom | €890+ | 2–4 weeks | Custom generator, 1C/API, multiple feeds (regions/storefronts), optional Google Merchant dual |
How we connect — 4 steps
- Catalogue audit — CMS, SKU count, variations, currency, images, target (Products / Market / ads).
- Mapping and generator — fields → YML, filters, staging URL.
- Diagnostics — cabinet/validator upload, fix errors, price parity check.
- Go-live and monitor — live URL, cron, training; 14–30 days of feed fix support.
Yandex vs Google Merchant
Both need a product feed, but schemas differ: Yandex uses YML; Google Merchant uses RSS XML with g: attributes. Fields and moderation are not 1:1. For both channels we build two exporters or a shared data layer (Custom package); for Google see Google product feed integration. For RU/CIS audiences Yandex is often primary; for EU/EN — Google.
When it fits — and when it does not
Fits: you have a store or catalogue with live prices; you want auto-updates in Yandex Products/Market; you can improve card content (titles, photos), not only “enable a plugin”.
Does not fit: a 10-SKU catalogue with no growth plans — manual upload may be enough; no HTTPS or stable hosting for the feed URL; you only need site SEO without product surfaces — see website promotion and Yandex SEO.
Related services
- WooCommerce customization
- online store development
- online store promotion
- Yandex SEO
- contacts — short brief
FAQ
What is a YML feed?
An XML file in Yandex Market Language describing the store and products. Yandex downloads it from a URL and updates offers in its services.
How much does Yandex product feed integration cost?
At VivaCoding: from €290 for a basic CMS export, from €490 with filters and monitoring, from €890 for custom/1C. Market fees and ads are separate.
How often does the feed refresh?
We schedule generation via cron (often hourly or more for stock). The platform fetches on its own cadence; the file at the URL must stay fresh with an up-to-date date.
Is a stock CMS plugin enough?
For a simple catalogue — often yes, with field mapping. Variations, multi-warehouse, and non-standard attributes usually need custom mapping or a generator.
Do we need Content API instead of a file?
For large, fast-changing assortments API helps with point updates. Most SMBs do well with a solid YML URL. We decide on the audit.
Can you also build a Google Merchant feed?
Yes — in Custom or as a separate job: one catalogue → two exporters (YML + Google). Formats differ; one “universal” file rarely passes both without adaptation.