Bitrix to Satu.kz Integration: Feed, Orders, API

Recently, an appliance store from Almaty approached us. They had a catalog on 1C-Bitrix with prices in rubles, but they needed to list on Satu.kz in tenge. Manual price list export took half a day daily, and orders were lost. We set up automatic integration in 2 weeks. Now the feed updates hourly, orders flow directly into CRM, and conversion increased by 25%. In this article, we'll break down the integration components and how to avoid common pitfalls.

Satu.kz Feed Format

Satu.kz accepts feeds in YML (Yandex Market Language) format. The basic structure is identical to standard YML, but prices must be strictly in Kazakhstani tenge (KZT). This is critical: even if your catalog stores prices in RUB, the output feed needs conversion.

Required offer fields:

• <url> — product page URL on your site
• <price> — price in KZT
• <currencyId>KZT</currencyId>
• <categoryId> — category ID from your tree (specified in the <categories> block)
• <name> — product name
• <available> — availability

Additional <param> parameters for specific categories increase offer clickability in filter results. They should be filled for products with sizes, colors, or other characteristics.

Setting Up Currency Conversion for Satu.kz Feed

If the store maintains prices in rubles or dollars, the feed needs conversion to KZT. The National Bank of Kazakhstan (NBK) rate is published via an open RSS: https://nationalbank.kz/rss/rates_all.xml. A Bitrix agent requests the rate once a day, saves it in b_catalog_currency, and uses it when generating the feed.

In b_catalog_currency, add the KZT currency and configure exchange rate updates. When generating the feed, take the price from b_catalog_price and convert using \Bitrix\Currency\CurrencyManager::convertCurrency(). For a catalog of 10,000 products, generation takes no more than 2 minutes.

Satu.kz API for Orders

The EVO platform provides a REST API for order management. Base URL: https://satu.kz/api/v1/. Authentication: store token in the header token: {your_token}.

Main methods:

• GET /orders/ — list orders (filter by status, date)
• GET /orders/{id}/ — order details
• POST /orders/{id}/update-shipping/ — update shipping status

Orders placed via Satu.kz are created in b_sale_order in Bitrix. Customer data from the Satu order is mapped to b_sale_order_props fields. The Satu order ID is saved in a custom order field for feedback when updating statuses.

A typical mistake is not handling payment confirmation. If an order is paid on Satu.kz, the API sends a paid status. On the Bitrix side, you need to set the payment flag in b_sale_order and, if needed, launch a business process. Automation saves up to 40 hours per month on order processing.

Why Category Mapping Is Critical

Satu.kz's category tree differs from your site's catalog structure. Without a mapping table (your Bitrix category → Satu.kz category), products end up in inappropriate sections and get lost in filters. This directly impacts visibility and sales. Mapping is implemented via an HL-block or a separate database table.

Compare two approaches:

Automatic mapping delivers 15% more product card visits, based on our measurements.

Feed Generation in Bitrix

An agent runs every hour and generates the XML file:

// Get products with stock
$res = \Bitrix\Iblock\ElementTable::getList([
    'filter' => ['IBLOCK_ID' => CATALOG_IBLOCK_ID, 'ACTIVE' => 'Y'],
    'select' => ['ID', 'NAME', 'CODE', 'DETAIL_PAGE_URL'],
]);

// For each product, get price and stock
// b_catalog_price JOIN b_catalog_product
// Convert price to KZT
// Build XML offer

The file is saved to /upload/satu_feed.yml. The feed URL is registered in the Satu.kz personal account. You can validate correctness using the platform's built-in validator.

Special Note: Product Reviews and Ratings

Satu.kz aggregates customer reviews. The store rating affects listing position. Integration does not manage reviews directly, but timely order processing (accurate stock, correct statuses) reduces negative feedback. Experience shows that stores with fast order processing average a 15% higher rating.

What's Included in the Integration Work?

As part of the project, we provide:

• YML feed setup with KZT conversion and category mapping.
• REST API integration for order retrieval and updates.
• Testing on real data: at least 100 orders to verify.
• Documentation on agents and the exchange rate update procedure.
• Support for 30 days after launch.

The integration budget ranges from 100,000 to 300,000 tenge depending on catalog size and logic complexity. We'll calculate the exact cost after auditing your project.

Timeline Estimates

Cost is calculated individually after analyzing the catalog structure and SKU volume. Get a consultation: contact us to assess your project.

We guarantee correct feed and order processing. Contact us to discuss details.

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.