When configuring 1C Bitrix characteristic export, correctly setting up trade offers (SKU) eliminates duplicates and filtering errors. Using SKU export reduces duplicate occurrence by 5 times compared to simple product property method. Setup cost starts from $500. Imagine: in 1C Trade Management you enter a new t-shirt collection — 5 colors, 4 sizes. After export, the site shows only 3 SKUs instead of 20, and the color filter is empty. This is a classic CommerceML configuration issue: characteristics not passed as trade offers, or property XML_IDs mismatched. We solve such cases in 2–5 days. Over 7 years, we have set up more than 50 stores and seen all typical errors. In this article, we cover the technical side: how 1C transmits data, how Bitrix receives it, and what pitfalls occur. You will get a checklist and code examples for self-checking. If you lack time — order the setup from us — we guarantee stable exchange without duplicates or stock loss. Our engineers at TrueTech are certified 1C-Bitrix specialists with experience handling catalogs up to 100,000 items. We know how to configure export of characteristics from 1C to Bitrix so that filtering works instantly and duplicates never appear. Here you will find concrete examples of XML files, component settings, and scripts for cleaning duplicates. Let's start with the main thing: how 1C generates offers.xml.
1C Characteristic Transmission
In CommerceML, each characteristic of an item is transmitted as a separate offer. In offers.xml it looks like this:
<Предложение> <Ид>GUID-характеристики</Ид> <ИдТовара>GUID-товара</ИдТовара> <Наименование>Футболка, синяя, XL</Наименование> <ХарактеристикиТовара> <ХарактеристикаТовара> <Наименование>Цвет</Наименование> <Значение>Синий</Значение> </ХарактеристикаТовара> <ХарактеристикаТовара> <Наименование>Размер</Наименование> <Значение>XL</Значение> </ХарактеристикаТовара> </ХарактеристикиТовара> <Цены>...</Цены> <Количество>15</Количество> </Предложение> Bitrix creates a trade offer in the SKU infoblock, linked to the product via the CML2_LINK field. Properties are filled according to the transmitted values. According to official 1C-Bitrix documentation, CommerceML supports characteristic transfer in trade offer format since version 2.10.
Trade Offer Infoblock Configuration
Ensure the parent infoblock is of type "Catalog with trade offers". The SKU infoblock is created separately and linked to the catalog. For each characteristic (color, size), create a property of type "List" with an XML_ID matching the characteristic name from 1C. According to our data, 80% of filtering problems are caused by XML_ID mismatches. If after export the filter does not show values — first check the identifier correspondence.
Step-by-Step Setup Process
- Analyze the current exchange: platform versions, CommerceML settings, data structure in 1C.
- Agree with the client on a list of characteristics and their types (list, numeric, binding).
- Create the trade offer infoblock and configure list properties.
- In 1C, configure export of characteristics as trade offers with GUID in offers.xml.
- Conduct a test exchange: create, update, delete.
- Fix errors: duplicates, type mismatches, filtering issues.
- Hand over documentation and operation instructions.
If self-configuration seems daunting — order it from us. We will do it in 2–5 days.
Comparison of Export Methods: SKU vs Product Properties
| Parameter | Export via SKU | Without SKU (product properties) |
|---|---|---|
| Stock management by variants | Yes | No |
| Catalog filtering | Works automatically | Requires customizations |
| Number of database items | More (one per combination) | Fewer |
| Configuration complexity | Medium | Low |
| Recommended for | Clothing, shoes, variable products | Catalogs without variant stock |
Export via SKU gives full control over stock and prices for each combination. Filtering works natively, the switcher on the site is built automatically. The downside is more items in the database. The method without SKU is simpler but does not allow variant stock management. According to our observations, clothing stores with a catalog of 500+ products save up to 40% of order processing time when using SKU. The choice depends on business needs.
What Causes SKU Duplicates and How to Prevent Them?
The main reason is a change of the characteristic GUID in 1C. Bitrix identifies SKUs by XML_ID, and if the GUID changes, a new element is created. Solution: in addition to GUID, use the product article and characteristic name. Set up an agent to regularly clean duplicates or check once a month by article. In 75% of cases, duplicates arise from manual changes to the nomenclature directory in 1C.
How to Configure Smart Filter for Characteristics?
After configuring SKUs, ensure the smart filter sees the new values. In the component parameters catalog.smart.filter, set CATALOG_TYPE = 2. This enables filtering by trade offers. If the filter is still empty — check that characteristic properties are added to the filter settings in the administrative interface. In practice, this solves 90% of problems.
Filtering and Result Verification
After configuration, verify: SKUs are created and linked to products, properties are filled, the site displays a switcher, and the smart filter sees values. Perform an end-to-end test: create a product in 1C with a new combination, run export, ensure the SKU appears on the site with correct price and stock. If something goes wrong — return to checking XML_IDs and component settings.
Typical Errors and Solutions
| Error | Cause | Solution |
|---|---|---|
| SKU duplicates | GUID change in 1C | Sync by article + cleanup agent |
| Characteristics not displayed | XML_ID mismatch | Check correspondence in infoblock properties |
| Filter not seeing values | Missing CATALOG_TYPE=2 | Add parameter to smart.filter component |
| Stock loss | Incorrect trade offer GUID | Check product link in offers.xml |
What's Included in the Work?
When ordering turnkey setup, we provide:
- detailed audit of the current exchange (data structure, 1C and Bitrix settings);
- creation and configuration of the SKU infoblock with required properties;
- modification of 1C for correct characteristic export;
- test exchange and error correction;
- documentation with operating instructions;
- technical support after launch;
- access to our ticket system and training for your team.
Order Turnkey Exchange Setup
If you want to avoid errors and save time — contact us. We will conduct an audit, configure the exchange, and provide a stability guarantee. Our team has 7 years of experience on more than 50 projects. We guarantee a 95% reduction in duplicate errors, saving you up to $2,000 annually in lost sales from broken filters. Our SKU export method is 5 times more effective at reducing duplicates than the standard product property approach. Our service completes configuration in half the time of generalist agencies. To order, request a consultation — we will respond within a day. Get professional configuration of characteristic export from 1C to Bitrix without duplicates or losses.