Setting up the export of product descriptions from 1C to 1C-Bitrix

Configuring Product Description Export from 1C to 1C-Bitrix

Product descriptions in CommerceML are transmitted in the <Description> tag of the product item. By default, 1C exports the "Full Name" field there — which is useless for an online store. SEO copywriters write texts on the website, while technical specifications are managed in 1C — the configuration task comes down to ensuring neither system overwrites the other's data.

What 1C Exports by Default

In the standard website exchange handler in UT 10/11, the <Description> tag is populated with the "Name" or "Full Name" field of the product item. Detailed descriptions are not provided for in standard 1C configurations — they are added via additional attributes or custom product attributes.

Adding a "Description" Attribute in 1C

In the 1C configurator or via the interface Administration → General Settings → Additional Attributes and Information:

• Add the attribute "Website Description" with type "String" (unlimited length)
• Attribute code: WebsiteDescription

In the XML export handler (the standard "ExportProductsCommerceML" processing module or the built-in UT 11 handler) — modify the population of the <Description> tag so that it takes the value from the new attribute instead of the standard name field.

Mapping on the 1C-Bitrix Side

By default, <Description> from the XML is mapped to the DETAIL_TEXT field of the info block element. To split the short (PREVIEW_TEXT) and full description:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'iblock',
    'OnIBlockElementBeforeAdd',
    function(\Bitrix\Main\Event $event) {
        $fields = $event->getParameter('fields');
        if (!empty($fields['DETAIL_TEXT'])) {
            $plain = strip_tags($fields['DETAIL_TEXT']);
            $fields['PREVIEW_TEXT'] = mb_substr($plain, 0, 300);
        }
        return new \Bitrix\Main\EventResult(
            \Bitrix\Main\EventResult::SUCCESS,
            ['fields' => $fields]
        );
    }
);

Protecting Descriptions from Overwriting

The main risk: an SEO specialist wrote a unique text for a product card, and the next 1C exchange overwrote it with a technical description from the database. Two protection methods:

Via module settings: in Settings → Online Store → Fields to Update on Exchange, uncheck the DETAIL_TEXT field.

Via a handler with a lock flag: add a SEO_DESCRIPTION_LOCK element property (type: list, values: Y/N). The OnIBlockElementBeforeUpdate handler checks the flag:

if ($existingElement['PROPERTY_SEO_DESCRIPTION_LOCK_VALUE'] === 'Y') {
    unset($fields['DETAIL_TEXT'], $fields['PREVIEW_TEXT']);
}

The flag is set by the content editor when saving unique text. Managers can see in the admin product card whether the text is protected from overwriting.

Technical Specifications vs. Marketing Descriptions

Best practice: export technical specifications from 1C (weight, dimensions, material composition) to dedicated info block properties. Write marketing descriptions on the website and protect them from overwriting. This provides a clear separation of responsibilities: 1C is responsible for data accuracy, the website is responsible for text quality.

Setup Timeline

Configuring description export with 1C customisation and overwrite protection — 4–8 hours. With development of a lock flag management interface — 1 day.