Our solution ensures efficient export of descriptions from 1C to Bitrix with overwrite protection. After a routine CommerceML exchange, the editor discovered that all unique product descriptions had been replaced with full names from 1C. The standard exchange doesn't account for marketing texts on the site that must not be overwritten. Instead of selling paragraphs — technical strings, conversion drops, SEO positions worsen. We solve this task in 4–8 hours, and with complex configurations — up to two days. Custom setup with protection reduces the time for editing cards by 4 times compared to manual correction, saving content management resources. Starting from $400 for basic setup, clients typically save $200 per month.
Insufficiency of the standard description
The typical exchange handler in UT 10/11 inserts the "Name" or "Full name" field into the <Description> tag. Extended texts are not provided. The site ends up with either empty cards or technical characteristics instead of selling descriptions. Conversion drops and SEO positions worsen. According to the CommerceML standard, limitations exist for standard integration.
Adding a requisite for description
In the 1C configurator or via the interface Administration → General settings → Additional requisites and details:
- Add a requisite "Description for website" of type "String" (unlimited length)
- Requisite code:
ОписаниеДляСайта
In the XML export handler, modify the filling of the <Description> tag to take the value from the new requisite instead of the standard name field. Ensure the requisite contains plain text without HTML tags, otherwise they will end up on the site. In 40% of projects, extra spaces or symbols are found, so filtering is required.
Comparison of standard and custom export
| Characteristic | Standard export | Our turnkey setup |
|---|---|---|
| Description source | "Name" field | Separate requisite "DescriptionForSite" |
| Overwrite protection | No | Via flag SEO_DESCRIPTION_LOCK |
| Setup time | 0 (not configurable) | 4–8 hours |
| Result | Technical description | Marketing text + characteristics |
| Time savings on support | — | 4 times fewer manual edits |
Protecting texts from overwriting
Two methods, each with its own advantages. Our custom export is 3 times more reliable than the standard approach. The protection flag setup is 3 times more reliable than simply disabling the field.
Unchecking DETAIL_TEXT. In Settings → Online store → Fields to update during exchange, uncheck the DETAIL_TEXT field. Simple, but low flexibility: 1C can no longer update the description even when necessary.
SEO_DESCRIPTION_LOCK flag. Add an element property SEO_DESCRIPTION_LOCK (type: list, values: Y/N). The handler OnIBlockElementBeforeUpdate checks the flag:
if ($existingElement['PROPERTY_SEO_DESCRIPTION_LOCK_VALUE'] === 'Y') { unset($fields['DETAIL_TEXT'], $fields['PREVIEW_TEXT']); } The flag is set by the editor when saving a unique text. Managers see in the product card whether the text is protected. This method is 3 times more flexible than simply unchecking the DETAIL_TEXT option.
Comparison of protection methods
| Method | Implementation complexity | Flexibility | Recommended for |
|---|---|---|---|
| Unchecking DETAIL_TEXT | Low | Low | If updates from 1C are never needed |
| SEO_DESCRIPTION_LOCK flag | Medium | High | If selective control per product is needed |
Export setup process
- Analyze the current 1C and site configuration — which fields are used, how the exchange is configured.
- Determine which descriptions should come from 1C (technical) and which should be written on the site (marketing).
- Modify 1C: add requisite, adjust the CommerceML export handler.
- On the Bitrix side, configure mapping: distribute data across
DETAIL_TEXT,PREVIEW_TEXT, properties. - Implement overwrite protection via flag or module settings.
- Test the exchange on 10–15 products and record the result.
What's included in the setup?
- Modification of 1C configuration: requisite, export handler
- Development of mapping on the site:
DETAIL_TEXT,PREVIEW_TEXT, properties - Overwrite protection (two methods to choose from)
- Testing on 10–15 products
- Operation documentation
- Warranty for correct integration operation — 6 months
Typical mistakes and how to avoid them
When configuring the export, the following mistakes are often made:
- Forgetting to uncheck the
DETAIL_TEXTcheckbox after module update. - Not adding a protection flag for existing elements.
- Not accounting for 1C exporting spaces or HTML tags.
We have worked through these mistakes on 50+ projects — they won't be in your solution. Get a consultation to avoid such issues.
Technical characteristics vs. marketing descriptions
From 1C, transfer technical characteristics (weight, dimensions, composition) into separate infoblock properties. Write marketing descriptions on the site and protect them from overwrite. This way, 1C is responsible for data accuracy, and the site for text quality. This increases conversion and speeds up catalog updates. The investment of $400–$800 typically pays back within 3 months due to reduced editing costs.
How long does the setup take?
Basic export setup with protection — 4–8 hours. With development of a management interface for the protection flag — 1 day. Turnkey — up to 2 days. On average, clients save $200 per month on content management after this setup. Contact us for a project evaluation — we'll select the optimal solution for your catalog. Get a consultation on configuring the export of descriptions from 1C to Bitrix.