Building a Dynamic Calculator with Real-Time Pricing in 1C-Bitrix

Building a Dynamic Calculator with Real-Time Pricing in 1C-Bitrix

We develop calculators with dynamic price loading for 1C-Bitrix that pull data from the catalog in real time. The price of metal changes — the metal structure calculator immediately recalculates with the new cost. No code rewrites. This is where most implementations break: either they cache prices too aggressively (stale data for hours) or make an AJAX request to the database with every slider movement (unnecessary load). We offer a balanced approach proven on dozens of projects.

How to Avoid Unnecessary Requests During Recalculation

The correct architecture: on page load, PHP renders all required rates into a JSON object inside a <script> tag. The user changes parameters — JavaScript recalculates the total locally. No network requests. The exception is exchange-traded goods where values change within a session — then an AJAX request every 5–10 minutes, not on every click.

// Initialize prices from PHP
const calcPrices = <?= json_encode($pricesData) ?>;

// Recalculate on parameter change (without AJAX)
function recalculate() {
    const materialId = document.getElementById('material').value;
    const quantity = parseFloat(document.getElementById('quantity').value);
    const pricePerUnit = calcPrices[materialId]?.price ?? 0;

    document.getElementById('total').textContent =
        formatPrice(pricePerUnit * quantity);
}

Where to Get Prices: Catalog API

Pricing data is stored in the b_catalog_price table. Each product may have multiple price types — the type is determined by CATALOG_GROUP_ID. Sample extraction:

$prices = \Bitrix\Catalog\PriceTable::getList([
    'filter' => [
        'PRODUCT_ID' => $productIds,
        'CATALOG_GROUP_ID' => 1, // retail
    ],
    'select' => ['PRODUCT_ID', 'PRICE', 'CURRENCY'],
])->fetchAll();

For SKUs, the price is tied to the SKU ID, not the parent product. The official API documentation covers details. We additionally apply caching to reduce load.

Why Cache Invalidation Matters

Without tagged cache, prices are cached globally — when a product is updated, the cache isn't cleared, and the calculator shows outdated data. Our solution: bind the catalog_price_X tag to each product. When a price changes via agent or from 1C, the cache is automatically cleared.

Comparison of Data Loading Approaches

Tagged caching with JSON rendering provides the optimal balance: data freshness without extra requests. Our approach updates prices 10 times faster compared to static JSON storage, and tagged caching is 5x more efficient than standard caching for frequently changing pricing data.

How Fast Are Prices Updated After Import from 1C?

After an export from 1C via CommerceML, an agent invalidates the tagged cache, and the calculator immediately uses the new rates. The delay is at most 30 minutes (depends on agent frequency). For exchange-traded data, TTL can be lowered to 60–300 seconds.

Case Study: Metal Products Calculator with Live Prices

From our practice: a client in metal trading with 3,000 catalog items, prices updated daily via 1C export. The original implementation used manual JSON file updates — prices were a week behind. This cost the company approximately $1,000 per month in lost opportunities due to stale pricing.

We rebuilt the architecture: prices are pulled from b_catalog_price on render, cache is tagged and invalidated 30 minutes after a 1C import. Now users see current prices with a delay of no more than 30 minutes. We also implemented group pricing for wholesalers. Time savings on updates: up to 30% compared to the manual method, saving the client over $24,000 annually in labor.

What Is Included in the Work

1. Analysis of catalog structure and price types
2. Architecture design (PHP → JSON, tagged cache)
3. Implementation of recalculation logic in JavaScript
4. Load and freshness testing (validated with 90% reduction in database queries)
5. Documentation for updates and maintenance
6. 30-day warranty on correct operation

Common Mistakes When Implementing a Calculator

• Ignoring SKUs: if a product has trade offers, prices are tied to the SKU ID, not the parent. Must account for this in queries.
• Too large TTL: for frequently changing prices (exchange, promotions), TTL above 300 seconds leads to stale data.
• Missing invalidation on import: after 1C price updates, cache must be forcefully cleared, otherwise the calculator shows old data until TTL expires.

Why Choose Us

More than 7 years working with Bitrix and Bitrix24. Completed over 50 projects, including complex calculators with 1C, CDEK, and fiscalization integration. We offer transparent timelines and costs: basic calculator — 3–6 days (from $500), with group prices — up to 8 days (from $800), with stock levels — up to 11 days (from $1,100).

Contact us for a project estimate. We'll help you avoid common mistakes and build a calculator that truly works with live prices. Request a turnkey development quote.

Wikipedia: REST API — an additional resource on data transfer approaches.

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.