1C-Bitrix Integration with Avito: XML Feed, API & Automation

1C-Bitrix Integration with Avito

We regularly encounter situations where an online store on 1C-Bitrix is already running, but entering Avito is delayed due to format incompatibility and moderation complexities. Avito is not a classic marketplace but a classifieds board with marketplace elements. This determines the integration specifics: products are uploaded as listings via XML feed (Avito Autoload), management is done through the personal account or REST API. The main challenge is that each Avito category has its own set of fields and moderation rules, different from any other marketplace.

Our experience shows that a properly configured integration pays off within the first months by automating routine operations. We guarantee correct handling of category fields and compliance with all Avito requirements.

Two Integration Channels

1. Avito Autoload (XML Feed). The primary method for mass upload. The seller places an XML file on their server and specifies the URL in Avito settings: Professional tools → Autoload. Avito parses the feed on a schedule (every few hours).

2. Avito API (https://api.avito.ru/). REST API for managing listings, statistics, messages. Authorization via OAuth 2.0 (client_id + client_secret → access_token).

For integration with 1C-Bitrix, we typically use a combination: feed for catalog upload + API for status monitoring and automation.

Avito Autoload Feed Format

The Avito XML feed has its own schema, incompatible with YML:

<Ads formatVersion="3" target="Avito.ru">
  <Ad>
    <Id>unique_id</Id>
    <Category>Consumer Electronics</Category>
    <AdType>Product purchased for resale</AdType>
    <Title>Samsung Galaxy S24 smartphone</Title>
    <Description>Description text</Description>
    <Price>79990</Price>
    <Images>
      <Image url="https://site.ru/photo1.jpg"/>
      <Image url="https://site.ru/photo2.jpg"/>
    </Images>
    <Address>Moscow, Primernaya St., 1</Address>
    <ContactMethod>By phone and messages</ContactMethod>
    <!-- Category-specific fields -->
    <GoodsType>Phones</GoodsType>
    <Brand>Samsung</Brand>
    <Model>Galaxy S24</Model>
  </Ad>
</Ads>

Category fields are the main challenge. For the "Consumer Electronics" category, you need GoodsType, Brand, Model. For "Clothing" — Size, Gender, ClothingType. For "Auto Parts" — OEMPartNumber, Brand, PartType. The full list of categories and fields is available in the Avito Autoload documentation.

Generating the Feed from Bitrix Information Block

There is no standard export profile for Avito in Bitrix. Implementation:

Custom PHP script — file /local/avito_feed.php, run by cron or accessible via URL. Logic:

1. Get information block elements via CIBlockElement::GetList() with active and stock filters.
2. For each element, determine the Avito category. Mapping is stored in a separate element property (PROPERTY_AVITO_CATEGORY) or in a mapping table of information block section → Avito category.
3. Depending on the category, generate a set of specific tags.
4. Assemble XML and write to file.

Field mapping:

Problem with <Id>. Avito identifies a listing by <Id>. If the ID changes (e.g., during catalog reindexing in Bitrix), Avito will create a new listing and delete the old one. Views, statistics, and reviews are lost. Use article or external code (XML_ID), not the numeric element ID.

Problem with <Address>. Avito links a listing to an address. The address in the feed must exactly match one of the addresses specified in the seller's profile. Mismatch leads to listing rejection.

How to Set Up an XML Feed for Avito Without Errors?

When setting up the feed, it is important to provide category and field mapping for each product group. If your catalog contains 2000 products and moderation takes 2 hours on average, manual processing becomes impossible. We automate this process through custom mapping tables.

Avito API: Management and Automation

The API is used for tasks the feed does not cover:

• Get listing statistics. GET /core/v1/items/{item_id}/stats — views, calls, messages. Data can be saved to an information block user property for performance analysis.
• Manage listings. PUT /core/v1/items/{item_id} — update fields without reloading the feed.
• Get messages. GET /messenger/v3/accounts/{user_id}/chats — automate replies or forward to Bitrix24 CRM.
• Activate/deactivate. When a product runs out, deactivate the listing via API faster than waiting for feed update.

Handling SKUs

Avito does not support product variations within one listing. Each SKU (size, color) is a separate listing. For an online store with a size grid, this means:

• T-shirt S, M, L, XL — 4 listings in the feed.
• Each with a unique <Id> (e.g., ARTICLE_SIZE).
• Each with size indicated in title or description.

When generating the feed, we iterate over the SKU information block and create a separate <Ad> for each offer with non-zero stock. This significantly increases feed size — for a catalog of 1000 products with 4 sizes, that's 4000 listings.

Limits and Moderation

Avito limits the number of listings: free limit depends on category (usually 1–5), then paid listing packages. For online stores, the "For Business" tariff provides increased limits.

Moderation of each listing takes 1–24 hours. Common rejection reasons: duplicates (identical photos or descriptions), prohibited items, category mismatch, spammy description.

What's Included in the Integration Work?

• Audit of the current catalog and SKU structure in 1C-Bitrix.
• Development of an XML feed generation module with category and field mapping.
• Configuration of image export and error handling.
• Connection of Avito API for monitoring and automation (optional).
• Testing the feed on a test Avito account, fixing issues.
• Documentation of the process and staff training.
• Support after launch for 1 month.

Integration Timeline

If you need turnkey 1C-Bitrix integration with Avito, contact us — we will evaluate your project and prepare a commercial proposal. In our work, we use certified solutions and guarantee compliance with all Avito requirements.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.