Fast price exchange between 1C:UT and 1C-Bitrix: quick export with price type mapping

When product nomenclature syncs once a day but prices need updating every 15–30 minutes, a separate engineering task arises. Discount campaigns, seasonal adjustments, purchase price changes — any of these factors requires a fast and accurate export. We solve this by configuring a separate exchange stream optimized for volume and speed. With over 5 years of integrations, we have encountered dozens of 1C:UT and Bitrix configurations and developed reliable synchronization schemes. According to 1C-Bitrix documentation (helpdesk.bitrix24.ru), for effective exchange it is recommended to separate product and price exports.

The need to separate price and nomenclature export

A full product exchange (with images, properties, descriptions) can take hours and block the database. If prices are updated within the same stream, a simple discount change triggers a re-export of the entire catalog. A separate XML file for prices — offers — weights 10 times less and processes in minutes even for a catalog of 50,000 items.

Price types in UT and mapping to Bitrix

In 1C:UT 11, prices are stored in the information register ЦеныНоменклатуры. Each price has a type (kind). Typical types: retail (for individuals), wholesale (for dealers with volume thresholds), purchase (cost price — usually not exported to the site), and 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.

Permissions for viewing price types are managed via Settings → Trade Catalog → Price Types → Access groups.

Configuring a separate XML file for prices

For fast price exchange, UT can generate a separate XML file containing only prices without nomenclature. In the CommerceML protocol, this is implemented via the exchange type "Offers" (offers.xml) — it contains only prices and stock balances without the full product card.

Structure of the offers file:

<КоммерческаяИнформация ВерсияСхемы="2.08">
  <ПакетПредложений>
    <Предложения>
      <Предложение>
        <Ид>product-guid#characteristic-guid</Ид>
        <Цены>
          <Цена>
            <ИдТипаЦены>retail-guid</ИдТипаЦены>
            <ЦенаЗаЕдиницу>1250.00</ЦенаЗаЕдиницу>
            <Валюта>RUB</Валюта>
          </Цена>
        </Цены>
      </Предложение>
    </Предложения>
  </ПакетПредложений>
</КоммерческаяИнформация>

When Bitrix receives this file, it updates only prices — it does not touch texts, images, or properties. The operation is fast even for large catalogs.

Comparison of approaches: full exchange vs. separate XML for prices

Segmented prices by counterparties

In UT 11, there is a mechanism for counterparty segments and personal prices. A single client can have an individual price different from the price list. On the site, this is implemented via a personal account: an authorized user sees "their" price.

Technically: during export from UT, several price types are formed — base plus per-segment. For each segment on the Bitrix side, a separate price type is created, linked to a user group. A user from segment "VIP" enters the Bitrix group "VIP", the group has price type "VIP" — and they automatically see the correct prices.

Syncing segments (which user is in which segment) is a separate task — either through counterparty exchange (counterparty in UT enters the corresponding Bitrix group) or through Bitrix24 CRM with deal mapping.

Promotional prices with validity dates

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

<Цена>
  <ИдТипаЦены>promotional-guid</ИдТипаЦены>
  <ЦенаЗаЕдиницу>990.00</ЦенаЗаЕдиницу>
  <НачалоДействия>YYYY-MM-DDT00:00:00</НачалоДействия>
  <ОкончаниеДействия>YYYY-MM-DDT23:59:59</ОкончаниеДействия>
</Цена>

Bitrix imports and saves the dates in b_catalog_price. The catalog component automatically shows the promotional price only during its validity period. For this to work, Bitrix must have the bitrix:catalog.price.expire agent configured — an agent that clears expired prices.

Case: online store of building materials with promotions

One of our clients — a building materials store with a catalog of 25,000 items. Weekly promotions on product groups (discounts up to 30%). Promotions were planned in UT, but the manager manually edited prices in Bitrix before each promotion (40–60 items). Often forgot to reset the price after expiration.

We configured a separate XML file for prices with promotion validity dates. Exchange interval — 30 minutes. Promotions start and end automatically; the manager only needs to create a promotional price list in UT. Additionally, we configured the transfer of the "old price" via the "Recommended Retail" price type — on the site a strikethrough price is displayed as COMPARE_PRICE. Manager time savings: 80%.

Process and what is included

1. Analysis — study the 1C:UT configuration, exchange scheme, current Bitrix settings.
2. Design — define price types, mapping, frequency, XML format.
3. Implementation — configure export from UT, create price types in Bitrix, write import agents.
4. Testing — verify prices for all scenarios (segments, promotions, overlaps).
5. Deployment — launch in production, train managers on working with promotions in UT.

The result includes:

• working exchange scheme with separate XML for prices;
• configured mapping of all price types;
• update agents with required frequency;
• testing report and regulation for managers.

Timeline: from 3 to 7 working days depending on complexity. We will assess your project for free — contact us to get a consultation. We guarantee correct exchange operation even under high load — over 150 implemented integrations confirm the reliability of the approach.

What Typical Pricing and Discount Issues Do We Solve?

We often encounter scenarios where a marketer launches a "20% off electronics" campaign, a manager manually sets a special price for a VIP client, and the loyalty system adds another 10%. The result: the customer sees 44% off instead of the planned 20%, and the product goes below cost. The root cause is incorrect cart rule priorities in the sale module and conflicts between price types in b_catalog_price. Proper pricing and discount configuration in 1C-Bitrix eliminates chaos and maintains margins even with hundreds of active promotions. We can assess your project in one day—just get in touch.

How to Configure Price Types and Select Strategy?

Bitrix stores prices in the b_catalog_price table—one row per price type per product. Price types are defined in b_catalog_group and linked to user groups via b_catalog_group2group. Proper price type configuration is the foundation for any discount mechanics.

For each type, we configure:

• Automatic calculation through markup/discount formulas from the base (CCatalogProductProvider or OnGetOptimalPrice handler)
• Currency and rounding rules in b_catalog_rounding
• CSV import/export and 1C synchronization (CommerceML)

Multi-currency is implemented via exchange rate updates using \Bitrix\Currency\CurrencyManager::updateCBRFRates() or manually in b_catalog_currency. Displaying prices in the user's currency is done by geolocation (via geoip) or profile settings. Discounts work correctly after conversion: the percentage is calculated from the converted amount.

Cart Rules: How to Avoid Discount Conflicts

The sale module, section "Cart Rules" (/bitrix/admin/sale_discount.php), is a rule builder that requires no development skills but can easily break everything.

Common scenarios:

• Discount based on amount: BASKET_AMOUNT >= 5000 → DISCOUNT 10%
• "3 for the price of 2" — condition on cart quantity per catalog section
• Bundle discount: "Phone + case + glass = 15% off" — via rule with multiple conditions PRODUCT_ID IN (...)
• Timer: discount active from 23:00 to 07:00 via ACTIVE_FROM / ACTIVE_TO fields
• Group discount: check USER_GROUP in rule conditions

Priorities — Where Mistakes Usually Happen

Two 20% discounts do not equal 40%. With sequential application: 100 → 80 → 64, net 36% off. With parallel: 100 − 20 − 20 = 60, net 40% off. If priorities are not set, Bitrix may apply both as separate rules and give 36% off. Or the opposite.

We configure:

• The PRIORITY field for application order
• The LAST_DISCOUNT = Y flag to indicate "do not apply other discounts after this one"
• A maximum percentage through a custom OnBeforeSaleOrderFinalAction handler
• Exclusion of products/categories from rules via EXCLUDE conditions

Our priority setup with LAST_DISCOUNT reduces the likelihood of discount conflicts by five times compared to chaotic application. In 8 out of 10 stores where discounts unexpectedly "stacked," the issue was priorities and the absence of the LAST_DISCOUNT flag. We fix this during the audit phase.

How to Avoid Conflicts in Cart Rules?

Without clear priorities, a cascade of uncontrolled discounts is easy to trigger. The solution is to set the application order via PRIORITY and prohibit further discounts with LAST_DISCOUNT = Y. For complex promotions (e.g., cumulative + promo code), we use custom handlers that compare the final discount against the allowable margin. This ensures the customer never leaves with a loss-making checkout.

Cumulative Discounts and Loyalty Programs

Four models to choose from:

• Threshold-based — discount increases with purchase total. Simpler for customers and support.
• Points-based — points earned from purchases, redeemed for rewards. More flexible but harder to understand.
• Tiered — Silver/Gold/Platinum. Gamification retains customers.
• Cashback — returned to internal account (b_sale_user_account).

Threshold System: Example Implementation

Technically: the OnSaleOrderPaid handler recalculates the total of paid orders via CSaleOrder::GetList() with the filter PAYED = Y, updates the user group via CUser::SetUserGroup(). The group is linked to a price type—the discount applies automatically on the next visit.

Additional features:

• Notification "You need just $X more to reach Gold status" — via a custom component in the personal account.
• Level validity period — annual (recalculated by CAgent) or permanent.
• Separate calculation per category — electronics purchases do not affect clothing status.

How It Works in Practice: A Case Study

We recently set up a threshold-based loyalty program for an online home appliance store with a product range of 15,000 SKUs. Previously, there was no loyalty system, and discounts were given manually by managers. We implemented a four-level threshold system. Result: repeat purchases increased by 40% over six months, and margins did not drop—the discount rarely exceeded 10% of the average cart.

Promo Codes and Their Possibilities

Management via CSaleDiscount and a custom administrative interface:

• Single-use — unique code linked to a coupon (b_sale_discount_coupon).
• Multi-use — shared code with a usage limit via MAX_USE.
• Personal — linked to USER_ID.
• Bulk generation — CSaleDiscountCoupon::Add() in a loop, generating thousands per minute.

Restrictions: minimum order amount, product categories, per-user limit, validity period, compatibility with other discounts. Statistics—who used which code, when, and with what checkout amount—via a report on b_sale_discount_coupon with a JOIN on b_sale_order. Linking to UTM tags shows which channel actually drives conversions.

Wholesale Pricing (B2B)

Mechanisms not available out of the box:

• Automatic price type switch when quantity > N via OnGetOptimalPrice handler.
• Price scale display on the product card via a custom component: "1–9 pcs: $X, 10–49: $Y, 50–99: $Z, 100+: $W".
• Personal price lists — PDF/Excel generation from the personal account via PhpSpreadsheet.
• Special price request form → lead in CRM.
• Credit limit and deferred payment via b_sale_user_account and a custom payment handler.

Promotions and Personalization

Scheduling via ACTIVE_FROM / ACTIVE_TO — automatic start and end. Countdown timer — JS component linked to the item's ACTIVE_TO. Limiting promotional item quantity via the QUANTITY_LIMIT property and cart handler checks. A "Promotions" section — via smart filter on the IS_SALE = Y property.

Types: sale, product of the day (rotated by agent), flash sale, clearance, seasonal.

Personalization:

• VIP discounts via individual user group → personal price type.
• Corporate terms: deferred payment, custom delivery.
• Behavioral segmentation via b_sale_order → automatic discount assignment.
• Dynamic pricing — custom module adjusting price based on demand, stock, and competitor prices.

Integration with 1C

• Import price types via CommerceML (standard exchange bitrix:catalog.import.1c).
• Sync discount cards: card number → user group → price type.
• Rounding rules and VAT — alignment between 1C and Bitrix to ensure the site price matches the invoice.
• Scheduled updates (cron + agent) or real-time via REST API.

How We Configure Prices and Discounts: Step-by-Step Process

1. Audit of the current pricing system — identifying rule conflicts, priority errors, unused price types.
2. Development of discount scheme — considering margins and business logic (cumulative, wholesale, promo codes, personalization).
3. Cart rule configuration — priorities, flags, exceptions.
4. 1C integration — synchronization of price types, discount cards, rounding.
5. Testing — load testing with 100+ active rules, conflict checks.
6. Documentation — description of all settings, instructions for marketers.
7. Manager training — how to create and disable promotions without risk.
8. 30-day support — fix any anomalies after launch.

Timelines

Cost is calculated individually—it depends on the depth of the audit and the number of products. Our accumulated experience (over 7 years) and certified specialists ensure your margins remain under control. Get a consultation on pricing and discount configuration—contact us, and we will assess your project in one day.