Integration of 1C-Bitrix with Kufar (Belarus)

1C-Bitrix Integration with Kufar (Belarus)

Kufar is a Belarusian classifieds platform, similar to Avito, with a dedicated section for online stores. For shops selling in categories such as "Electronics", "Automotive", "Clothing", and "Home Goods", Kufar drives real traffic through listings. Integration with 1C-Bitrix enables automatic publication of product listings and keeps them up to date without manual effort.

Kufar API for Business Accounts

Kufar provides an XML feed for bulk listing uploads through the partner dashboard. Unlike Avito, Kufar does not offer a direct REST API for real-time listing publication — all operations go through a feed that the platform polls periodically (typically every few hours).

The Kufar feed format is a proprietary XML dialect. Core listing fields:

<ad>
  <id>12345</id>
  <title>Samsung Galaxy A54 Smartphone 8/256GB</title>
  <description>Product description, no 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: Kufar uses its own category IDs (category_id). The current category list is available in the partner documentation. An incorrect category_id means a listing ends up in the wrong section.

Feed Generation in 1C-Bitrix

We create an agent that builds the XML feed from the catalog infoblock. The standard 1C-Bitrix export module (catalog.export) is not suitable for Kufar — the format is too platform-specific. We write a custom generator.

Product filtering for the feed:

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

One caveat: Kufar limits the number of active listings per business account (depending on the subscription plan). If the catalog exceeds the limit, prioritisation is required: we export top products by margin or turnover. The selection criteria are agreed with the client.

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

Descriptions Without HTML

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

Listing Parameters: Property Mapping

Each Kufar category has a list of required and recommended parameters. For smartphones, for example: storage capacity, screen diagonal, SIM type. These parameters are sourced from infoblock properties and mapped to the <param> fields in the feed.

Property mapping: a table of infoblock_property_ID → Kufar_parameter_name. Stored in the integration module settings or in a separate reference infoblock. Without populated parameters, a listing ends up in the "basic" listing without filtering — resulting in lower conversion.

Feed Updates and Listing Rotation

Kufar pushes older listings down in search results. To maintain visibility, some listings need to be periodically "bumped" (refreshed). In a feed-based integration, bumping is emulated by changing the <price> or <description> field — when the feed changes, the listing is treated as updated. This is not an abuse: prices genuinely change, and keeping them current is legitimate.

Estimated Timelines

Pricing is calculated individually after analysing the catalog and the Kufar account's tier limits.