Setting up price list export from 1C:UT to 1C-Bitrix

Configuring Price List Export from 1C:UT to 1C-Bitrix

Price lists are a separate task within the 1C:UT and Bitrix exchange. The item catalog may synchronize once a day, while prices must update every 15–30 minutes: promotional discounts, purchase price changes, seasonal adjustments. This requires a dedicated exchange stream optimized for volume.

Price Types in UT and Their Mapping to Bitrix

In 1C:UT 11, prices are stored in the information register ItemPrices. Each price has a type. Typical price types:

• Retail — for individual buyers
• Wholesale — for dealers, with volume thresholds
• Purchase — cost price, usually not exported to the website
• Special / Promotional — temporary prices

In Bitrix, each UT price type corresponds to a price type in the trade catalog (b_catalog_price). The mapping is configured in Settings → Trade Catalog → Price Types.

Access rights to price types are managed via Settings → Trade Catalog → Price Types → Access Groups.

Separate XML File for Prices

For fast price exchange, UT can generate a separate XML file containing only prices without the item catalog. In the CommerceML protocol, this is implemented through the "Offers" exchange type (offers.xml) — containing only prices and stock levels without full product cards.

Structure of the offers file:

<CommercialInformation SchemaVersion="2.08">
  <OfferPackage>
    <Offers>
      <Offer>
        <Id>product-guid#characteristic-guid</Id>
        <Prices>
          <Price>
            <PriceTypeId>retail-guid</PriceTypeId>
            <PricePerUnit>1250.00</PricePerUnit>
            <Currency>RUB</Currency>
          </Price>
        </Prices>
      </Offer>
    </Offers>
  </OfferPackage>
</CommercialInformation>

When Bitrix receives this file, it updates only prices — leaving texts, images, and properties untouched. The operation is fast even for large catalogs.

Segmented Prices (by Counterparty and Segment)

UT 11 has a counterparty segment mechanism with individual pricing. A single client may have a personal price different from the standard price list. On the website, this is implemented through the personal account: an authenticated user sees "their" price.

Technically: when exporting from UT, multiple price types are generated — a base price plus per-segment prices. On the Bitrix side, each segment has a dedicated price type linked to a user group. A user in the "VIP" segment belongs to the "VIP" group in Bitrix, the group is assigned the "VIP" price type — and they automatically see the correct prices.

Synchronizing segments (which user belongs to which segment) is a separate task. Either through counterparty exchange (a counterparty in UT is mapped to the corresponding Bitrix group), or through Bitrix24 CRM with deal mapping.

Promotional Prices and Validity Dates

In UT, promotional prices have start and end dates. CommerceML 2.08 supports transmission of price validity dates:

<Price>
  <PriceTypeId>promotional-guid</PriceTypeId>
  <PricePerUnit>990.00</PricePerUnit>
  <StartDate>2024-03-01T00:00:00</StartDate>
  <EndDate>2024-03-31T23:59:59</EndDate>
</Price>

Bitrix saves the dates in b_catalog_price during import. The catalog component automatically displays the promotional price only during its validity period. Important: for this mechanism to work in Bitrix, the bitrix:catalog.price.expire service must be configured (an agent that resets expired promotional prices).

Case Study: Building Materials Store with Promotions

A building materials store: 25,000 items, weekly promotions on selected product groups (discounts up to 30%). Promotions are planned in UT in advance — with start and end dates.

Before configuration: a manager manually edited prices in Bitrix before each promotion (40–60 items). Frequently forgot to reset prices after the promotion ended.

After: promotional prices with dates are configured in UT and exported to Bitrix. Price exchange — every 30 minutes. Promotions start and end automatically. The manager only creates the promotional price list in UT.

Additionally: configured the transmission of the "old price" (strike-through price on the website) via a separate price type "RecommendedRetail." Bitrix displays it as COMPARE_PRICE in the trade catalog.