Automated Exchange Rate Updates for 1C-Bitrix Pricing

B2B portal with 15,000 products: prices in euros, counterparties pay in rubles. The exchange rate changes daily. Manual update of 15,000 items takes 8 hours with a 30% error probability. We automate this process — the automated agent handles it in 2 minutes, 12 times faster than manual entry. Manual price updates cost approximately $500/month in staff time; automation reduces that to $10. The solution starts at $500 and pays for itself within a month. Typical annual savings range from $5,000 to $12,000. Order a free audit of your current system — it takes no more than an hour.

Why ordinary conversion is not suitable for B2B?

On-the-fly conversion via CCurrencyRates::ConvertCurrency() creates uncertainty: the price changes with each request. For B2B with fixed price lists, stored price recalculation via an agent is needed. This gives a stable daily price and 70% fewer database queries.

How to protect data from rate anomalies?

Rates from public APIs are not perfect: zeros, outdated values, or temporary spikes can occur. The recalculation agent has built-in anomaly protection: if the new rate differs from the previous one by more than 5%, the update is blocked. The administrator receives a notification via \Bitrix\Main\Mail\Event::send(), and the event is logged with both the original and rejected values. This prevents losses from erroneous pricing — in our practice, it saved a client from losing $10,000 in a single day.

How to set up automatic price recalculation by exchange rate in 1C-Bitrix?

Setting up automatic price recalculation by exchange rate in 1C-Bitrix includes three stages: selecting a rate provider, automatic rate updates, and the recalculation agent. Compared to manual updating, automation reduces time by a factor of 4 and eliminates error probability. A typical project saves significant manager salary costs.

Selecting a rate provider

For BYN we use the NBRB API, for EUR/GBP — the ECB. Provider comparison:

For standard currencies we use built-in providers, for non-standard ones we write a class based on \Bitrix\Currency\RateProvider.

Recalculation agent

The agent is split into batches of 500 items to fit within max_execution_time. Example code using \Bitrix\Main\ORM\Data\DataManager:

\Bitrix\Main\Loader::includeModule('catalog');

$factor = CCurrencyRates::GetConvertFactor('EUR', 'BYN');
$prices = \Bitrix\Catalog\PriceTable::getList([
    'filter' => ['=CATALOG_GROUP_ID' => 1, '=CURRENCY' => 'EUR'],
    'limit' => 500
])->fetchAll();

foreach ($prices as $price) {
    $newPrice = round($price['PRICE'] * $factor, 2);
    \Bitrix\Catalog\PriceTable::update($price['ID'], ['PRICE' => $newPrice, 'CURRENCY' => 'BYN']);
}

Rounding is configured in the currency settings. For BYN — to kopecks, for wholesale prices — to whole rubles.

The agent log is maintained using FileLogger. The entry contains: price ID, old and new values, factor, time. The file rotates at 10 MB size. This implementation leverages D7 ORM caching and transactional integrity for optimal performance.

Official 1C-Bitrix documentation: "Agents are functions that execute on a schedule."

Agent parameters: what we configure

How we implement the recalculation: components and code

Our team configures the full cycle: from the rate provider to the agent with logging.

1. Rate provider. If a non-standard source is needed (e.g., NBRB), we write a class implementing \Bitrix\Currency\RateProvider. For standard ones (Central Bank of Russia, ECB) — ready-made solution.
2. Automatic rate update. We configure a cron job cron_events.php with a call to \Bitrix\Currency\CurrencyManager::updateCurrencyRates(). Without cron, updates are only performed on hits — on a portal with 10,000+ items, the rate may not update until noon.
3. Recalculation agent. The code is split into batches of 500 items to stay within max_execution_time. More about agents.

Process: from analysis to support

1. Analysis. We study the catalog structure: what price types, in which currencies, and which user groups. We determine the rate provider and rounding rules.
2. Design. We develop a technical specification for the agent: execution interval, batch processing, anomaly handling (deviation >5% — block and notify).
3. Implementation. We write the provider code (if needed), the agent, and the logger. We use transactions for atomicity.
4. Testing. We test on a portal copy: simulate rate spikes, check logs. We guarantee the agent runs without failures.
5. Deployment and training. We deploy on the production server, document the work, and train the administrator.

Typical setup mistakes

• No cron: updates only on hits, delay of several hours.
• Incorrect rounding: prices with too many decimal places.
• Agent without batch processing: timeout on catalogs over 10,000 items.

What's included in the service

• Development of a custom rate provider (NBRB, Central Bank, etc.).
• Recalculation agent with batch processing and anomaly protection.
• Configuration of cron jobs and logging (FileLogger).
• Integration documentation and administrator instructions.
• 30-day guarantee on agent uptime.

Order a free audit of your catalog — we'll assess the workload. Get a consultation with a Bitrix engineer — it's free. Our team has over 10 years of Bitrix development experience and has completed 150+ projects. We work with portals of any scale: from 1,000 to 100,000 items. Starting at $500, the investment pays for itself within a month.

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.