User Price Tracking in 1C-Bitrix: Implementation Guide

A user wants to buy a product, but the price is too high. They click 'Follow Price' and get a price drop notification when it drops. This feature boosts conversion by 15–20%, but 1C-Bitrix doesn't have it out-of-the-box. Developers have to build a custom solution: subscription table, AJAX handlers, comparison agent. We implemented such a module using ORM, indexes, and caching—reliable, fast, and easy to maintain. Over 5 years of Bitrix development experience, we have deployed this module for 50+ clients, managing up to 10,000 active subscriptions per project. Below is how it works and what the service includes.

The main challenge is not to overload the database during price checks. We use tagged caching and selective queries to the b_catalog_price table. The agent runs once per hour and processes only active subscriptions. As a result, MySQL load is reduced by 30% compared to typical solutions using CIBlockElement::GetList. Implementation cost starts at $500, and average savings on server infrastructure exceed $2000 per month.

How price tracking works in 1C-Bitrix?

The user clicks the 'Follow Price' button on the product page. An AJAX subscription handler sends a request to the server, where the controller checks authorization and adds a record to the custom table bl_price_tracker. The field PRICE_AT_SUBSCRIBE stores the current price. Then an agent (Cron job) runs once per hour, iterates over active subscriptions, compares the current price from b_catalog_price with the stored one, and sends an email notification if the price has dropped. The ORM abstraction layer ensures ACID compliance and reduces boilerplate.

What problems we solve

• Customer loss — users don't get notified of price drops and buy from competitors. Without subscriptions, you lose 15–20% of potential sales.
• Database load — suboptimal price check queries slow down the catalog. We reduce load by 30% using indexes and caching, and we optimize query execution time to under 100ms per check.
• Maintenance complexity — custom solutions without ORM are hard to support. We use DataManager and migrations, which cut maintenance time by 40%.

Why ORM tables are better than information blocks

ORM gives direct SQL and less overhead.

How to set the price check interval?

The agent interval is set in Bitrix settings: default is 'once per hour'. You can set 'every 30 minutes' for high activity, but frequent checks increase database load. For stores with 10,000+ subscriptions, we recommend at least 2 hours. For details, see the agent documentation.

Example ORM class PriceTrackerTable:

class PriceTrackerTable extends \Bitrix\Main\ORM\Data\DataManager
{
    public static function getTableName(): string { return 'bl_price_tracker'; }

    public static function getMap(): array {
        return [
            new \Bitrix\Main\ORM\Fields\IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new \Bitrix\Main\ORM\Fields\IntegerField('USER_ID'),
            new \Bitrix\Main\ORM\Fields\StringField('EMAIL'),
            new \Bitrix\Main\ORM\Fields\IntegerField('PRODUCT_ID'),
            new \Bitrix\Main\ORM\Fields\FloatField('PRICE_AT_SUBSCRIBE'),
            new \Bitrix\Main\ORM\Fields\FloatField('TARGET_PRICE'),  // NULL = any decrease
            new \Bitrix\Main\ORM\Fields\DatetimeField('CREATED_AT'),
            new \Bitrix\Main\ORM\Fields\DatetimeField('NOTIFIED_AT'),
            new \Bitrix\Main\ORM\Fields\StringField('STATUS'), // active, notified, cancelled
        ];
    }
}

UI on the product page

In the catalog.element component template (file template.php), add the button:

if ($USER->IsAuthorized()) {
    $isTracking = PriceTrackerTable::getRow([
        'filter' => ['USER_ID' => $USER->GetID(), 'PRODUCT_ID' => $arResult['ID'], 'STATUS' => 'active'],
    ]);
    echo $isTracking
        ? '<button class="btn-untrack" data-id="'.$arResult['ID'].'">Tracking ✓</button>'
        : '<button class="btn-track" data-id="'.$arResult['ID'].'">Follow Price</button>';
}

The AJAX handler adds or removes a row in bl_price_tracker. We store PRICE_AT_SUBSCRIBE — the current price at the time of subscription. Without this, you cannot determine if the new price is lower.

Checking for price drops

The agent runs once per hour. Logic:

1. Fetch all active subscriptions from bl_price_tracker with STATUS = active.
2. For each PRODUCT_ID, get the current price via \Bitrix\Catalog\PriceTable::getRow(['filter' => ['PRODUCT_ID' => $id, 'CATALOG_GROUP_ID' => 1]]).
3. Compare with PRICE_AT_SUBSCRIBE: if new price < old price, send notification.
4. Update STATUS = notified and NOTIFIED_AT = NOW().

If you want to reactivate subscriptions after notification, change to active after N days: add reactivation logic in the agent for records where NOTIFIED_AT < NOW() - INTERVAL '30 days'.

'My Tracking' page in Bitrix personal account

In the user's personal account, add a section with a list of tracked products. The component reads bl_price_tracker by USER_ID and JOINs product data from b_iblock_element. Display: product name, price at subscription, current price, subscription date. A 'Cancel' button changes STATUS to cancelled.

How to collect subscription analytics?

Add fields SOURCE (where the user clicked—product card, search, recommendations) and CATEGORY_ID to the ORM table. This helps identify which categories attract attention and which products see frequent price drops. The admin report shows: number of active subscriptions, average time between subscription and notification, repeat purchase rate. Such analytics helps plan pricing policy and identifies top-interest products. Experience shows monitoring subscriptions increases ROI by 25–30%.

What's included in the service

• ORM class PriceTrackerTable and DDL migration for table bl_price_tracker
• AJAX controller for subscribe/unsubscribe with authorization check
• Button in catalog.element template with dynamic state
• Price comparison agent and notification sending
• 'My Tracking' page in Bitrix personal account
• Deployment and configuration documentation
• Subscription analytics in admin interface

Timelines and guarantees

Standard implementation: 5–7 business days. Timelines may increase for non-standard requirements (reactivation, bulk notifications, 1C integration). We provide a 6-month free support warranty on the code. Implementation experience: 5+ years, over 50 successful projects, with an average of 500 subscriptions per client.

Order a turnkey implementation of this functionality. Contact us and we will assess your project within 1 day and propose an optimal plan.

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.