1C-Bitrix Integration with KLADR: Import, Search, Mapping to FIAS

1C-Bitrix Integration with KLADR

When developing an online store on 1C-Bitrix, sooner or later you face the need for address autocomplete. Clients enter city and street manually — errors, duplicates, delivery failures. We regularly encounter situations where the accounting system 1C:Enterprise uses KLADR, while the site has FIAS connected via DaData. Addresses don't match, orders stall. In this article, we'll break down how to properly integrate KLADR into Bitrix and ensure seamless exchange with 1C.

Why KLADR is Still Relevant

KLADR — the address classifier of the Russian Federation, maintained by the Federal Tax Service. It was the primary standard. Today, most new systems have migrated to FIAS, but legacy infrastructure in 1C and reporting to the Federal Tax Service still require the KLADR code. If you have an online store on Bitrix integrated with 1C, ignoring KLADR is not an option.

When You Need KLADR Integration Instead of FIAS

• Client's accounting system is 1C:Enterprise version 8.3.14 or lower, which operates with KLADR codes.
• Exchange with the Federal Tax Service in formats requiring the KLADR code.
• Transport companies (CDEK, Russian Post) that haven't yet switched to FIAS.
• Import of an old address database where all records are in KLADR format.

If no such limitations exist, go ahead and use FIAS — it is officially supported and more precise. But for hybrid scenarios, mapping between KLADR and FIAS is essential.

KLADR Structure

The KLADR code is an 11-digit or 13-digit number (including the relevance indicator). Structure:

PP RRRRR GGG RRR ULITCH
2  5     3   3   4       = 17 characters (with extensions)

• PP — subject code (region).
• RRRRR — district code.
• GGG — city code.
• RRR — locality code.
• ULITCH — street code.

KLADR database files are downloaded from the Federal Tax Service website (fias.nalog.ru — same section, KLADR). Format — DBF files. Source: fias.nalog.ru

Importing KLADR into MySQL/PostgreSQL

# Convert DBF → SQL using dbf2sql utility or Python
python3 -c "
import dbf, csv
table = dbf.Table('KLADR.DBF')
table.open()
for record in table:
    print(','.join([str(f) for f in record]))
table.close()
" > kladr.csv

After importing into the kladr_objects table, create indexes on code and parent code for fast search.

KLADR Search in Bitrix

function searchKladrCities(string $regionCode, string $cityName): array {
    $connection = \Bitrix\Main\Application::getConnection();
    $name = $connection->getSqlHelper()->forSql(mb_strtolower($cityName));

    $sql = "
        SELECT CODE, NAME, SOCR
        FROM kladr_objects
        WHERE CODE LIKE '{$regionCode}%'
          AND LENGTH(CODE) = 13  -- city level
          AND LOWER(NAME) LIKE '%{$name}%'
          AND STATUS = '1'       -- active records
        LIMIT 20
    ";
    // ...
}

This method returns a list of cities whose code starts with the region code. It's used in the autocomplete component.

Mapping KLADR ↔ FIAS

Since modern systems use FIAS and legacy uses KLADR, a mapping table is often needed. The FIAS database has a CODE field — that's the KLADR code. The ADDROBJ table contains both identifiers: AOGUID (FIAS) and CODE (KLADR).

// Get KLADR code from FIAS GUID
$sql = "SELECT CODE FROM fias_ADDROBJ WHERE AOGUID = '" . $fiasGuid . "'";

The mapping table solves address mismatch during exchange with 1C.

Address Autocomplete via DaData with KLADR Code

DaData returns both kladr_id and fias_id in the suggestion response. If you specifically need KLADR:

$("#address").suggestions({
    token: dadataToken,
    type: "ADDRESS",
    onSelect: function(suggestion) {
        const d = suggestion.data;
        $("#kladr-id").val(d.kladr_id);
        $("#fias-id").val(d.fias_id);
        // Store both — for different downstream systems
    }
});

Storing both identifiers is best practice when migrating from KLADR to FIAS.

Passing to 1C:Enterprise

When syncing orders with 1C:Enterprise via CommerceML or direct REST exchange, the address is transmitted in a format that 1C recognizes. If 1C version is old (below 8.3.14), it accepts KLADR codes. Pass the kladr_id from the order field along with the string address.

How We Implement KLADR Integration in Bitrix

Our approach is structured and tested:

1. Analyze the current address schema: what fields are stored, which identifiers 1C uses.
2. Import the KLADR database (latest version from the Federal Tax Service) into a separate kladr_objects table.
3. Create REST endpoints for hierarchical search: regions → cities → streets.
4. Map existing addresses (if any) to KLADR codes via open FIAS data.
5. Integrate with DaData or another autocomplete service, preserving the KLADR code in the order.
6. Configure exchange with 1C: add a kladr_id field in CommerceML.
7. Test on live data — verify that all addresses from 1C map correctly.

On one project, we integrated for a retail chain with 50,000 addresses. The KLADR database took about 2 GB after indexing. City search by first characters executed in 0.02 seconds.

What Our Work Includes

• Import and configuration of the KLADR database on your server.
• REST API for address search with parent code filtering.
• Mapping table between KLADR and FIAS for seamless operation with modern services.
• Integration with 1C: setting up exchange of address requisites.
• Documentation on API usage and post-implementation support.

Timeline and Pricing

Effort depends on the volume of legacy data:

Cost is calculated individually after auditing your system. We'll assess your project within one day — contact us.

Contact us — write to us via Telegram or leave a request on our website. We'll respond within an hour.

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.