1C-Bitrix Integration with Kufar (Belarus)

1C-Bitrix Integration with Kufar (Belarus) We've encountered situations: a shop spends hours manually adding listings on Kufar, while competitors have already automated the export. As a result, products appear late, some are never published due to description errors. **We take on full turnkey int

Our competencies:

Frequently Asked Questions

1C-Bitrix Integration with Kufar (Belarus)

We've encountered situations: a shop spends hours manually adding listings on Kufar, while competitors have already automated the export. As a result, products appear late, some are never published due to description errors. We take on full turnkey integration — from XML feed to category mapping and auto-updating.

Kufar is a Belarusian classifieds site with a section for online stores. Categories like 'Electronics', 'Auto', 'Clothing', and 'Home Goods' drive real traffic. Our integration with 1C-Bitrix allows you to publish and update listings automatically, without manual work.

Why Doesn't Kufar Use a REST API for Publishing?

Unlike Avito, Kufar does not provide a direct REST API for instant publishing. All bulk uploads go through an XML feed — the partner cabinet periodically polls your feed (usually every few hours). This imposes constraints: listings don't appear immediately, but it provides stability for large volumes.

The feed format is a custom XML dialect. Example entry:

<ad> <id>12345</id> <title>Samsung Galaxy A54 8/256GB Smartphone</title> <description>Product description without HTML</description> <price>1299</price> <currency>BYR</currency> <category_id>1113</category_id> <condition>new</condition> <images> <image>https://yourshop.by/img/samsung-a54-1.jpg</image> </images> <params> <param name="Brand">Samsung</param> </params> </ad> 

Important detail: Kufar uses its own category IDs (category_id). The current category list is available in the partner documentation. An incorrect category_id means the listing ends up in the wrong category.

Generating the Feed in 1C-Bitrix

We create an agent that builds the XML feed from the catalog infoblock. The standard Bitrix export module (catalog.export) doesn't work for Kufar — the format is too specific. We write our own generator.

Product filtering for the feed:

  • ACTIVE = Y — only active products
  • QUANTITY > 0 in b_catalog_product — only in stock
  • Explicit exclusion of product categories that Kufar does not accept or that are irrelevant

A nuance: Kufar limits the number of active listings per business account (depends on the tariff). If the catalog exceeds the limit, prioritization is needed: we export top products by margin or turnover. The selection criteria are agreed with the client.

Images. Kufar requires direct URLs to images. If Bitrix uses image resizing via CFile::ResizeImageGet() with temporary parameters in the URL, those links are unstable. It's better to specify original URLs from /upload/.

Descriptions Without HTML

Kufar does not accept HTML markup in listing descriptions. The <description> field must be plain text. In Bitrix, product descriptions are often stored in b_iblock_element in DETAIL_TEXT or PREVIEW_TEXT fields with *_TYPE = html. Processing is needed: strip_tags() plus decoding HTML entities (html_entity_decode()).

Listing Parameters: Property Mapping

Each Kufar category has a set of required and recommended parameters. For example, for smartphones: storage capacity, screen diagonal, SIM type. We take these parameters from the infoblock properties and map them to the <param> fields in the feed.

Property mapping: a table infoblock_property_ID → Kufar_parameter_name. Stored in the integration module settings or in a separate reference infoblock. Without filling parameters, the listing goes into a 'basic' listing without filters — lower conversion.

Feed Update and Listing Rotation

Kufar pushes older listings down in the listing. To maintain visibility, some listings need to be 'bumped' periodically (updated). Within the feed integration, bumping is simulated by changing the <price> or <description> field — when the feed changes, the listing is considered updated. This is not abuse: prices actually change, and updates are legitimate.

What's Included in the Work

Stage Result
Catalog analysis Determine volume, Kufar limits, priority categories
Feed generator development Bitrix agent, filters, image and description processing
Category and parameter mapping Matching Kufar IDs to infoblock properties
Testing Publish test listings, adjust
Documentation and training Manager instructions, update procedure
Support 1 month of support after launch

How to Avoid Typical Integration Mistakes?

  • Incorrect category_id — consult the Kufar reference.
  • Images with temporary URLs — use original file paths.
  • HTML in descriptions — always strip markup.
  • Exceeding listing limit — configure prioritization.
More about Kufar limits The active listing limit depends on the business account tariff. Check in your personal account or with the platform manager. If the limit is exceeded, new listings are not published, and old ones are not updated.

Timeframes

Task Timeframe
Setting up XML feed for Kufar 3–7 days
+ parameter mapping for 3–5 categories 1–2 weeks
Full setup with prioritization and auto-update 2–3 weeks

The cost is calculated individually after analyzing the catalog and Kufar account tariff limits. We'll evaluate your project for free — just contact us, and we'll prepare a solution for your tasks. Certified 1C-Bitrix specialists, 10+ years of experience, over 100 successful integrations with classifieds sites. We guarantee stable feed operation and timely support.