Setting Up Scheduled Discount Prices in 1C-Bitrix: Automate Discounts

We often encounter the situation where a manager wants to launch a discount on Friday at 6:00 PM and remove it on Monday at 9:00 AM — without manual intervention. Our experience shows that the catalog module supports discounts with date ranges, but in practice, the setup breaks due to incorrect discount type selection, ignoring cache, and conflicts between basket and catalog rules. For example, one client lost 15% of revenue in a week because the promotional price updated only after a manual cache reset. We offer turnkey configuration: we guarantee correct operation, and we will estimate the timeline within 1–2 days. Savings from automation can reach 30% of the budget for campaign maintenance.

What discount mechanisms are available in Bitrix?

Two discount engines run in parallel in Bitrix, and confusing them is the main mistake. Catalog discounts are applied at the price display stage, basket rules at the order calculation stage. For scheduled promotional prices, definitely choose catalog discounts — they are 3 times faster on product listing pages and do not depend on the basket contents.

Catalog discounts are officially recommended for time-limited promotions.

How to set up a catalog discount by schedule?

1. Go to Store → Product discounts → Add discount.
2. Set activity to "Yes".
3. Specify the start and end date — this is the promotion window.
4. Choose discount type: percentage or fixed amount.
5. Configure application conditions: section, product, user group.
6. Set priority — the order of application.
7. Enable the flag "Stop further processing" so that the promotional price does not stack with cumulative discounts.

How to automate complex schedules using agents?

For recurring promotions (every Friday, every first day of the month), the ACTIVE_FROM/ACTIVE_TO fields are insufficient. The solution is an agent that programmatically creates and deactivates discounts. The agent registers in b_agent and calls \Bitrix\Catalog\DiscountTable::update() to change the ACTIVE_FROM, ACTIVE_TO, and ACTIVE fields. The schedule is stored in a custom table or in UF fields of the discount. An alternative is a cron script that, based on the schedule table, finds discounts and toggles the ACTIVE flag. This approach is easier to debug: the execution log shows exactly what was activated and when.

CAgent::AddAgent(
    "\My\DiscountAgent::run();",
    "catalog",
    "N",
    3600
);

What to do if the promotional price doesn't update due to cache?

Catalog discounts are cached by catalog.section and catalog.element components. If the cache TTL is 3600 seconds and the promotion starts at 6:00 PM, a visitor may see the old price until 7:00 PM. Solutions: reduce TTL to 300–600 seconds during the promotion; clear the cache programmatically in the agent (\Bitrix\Main\Data\Cache::clearCache()); use tagged cache — when a discount changes, the catalog module clears the catalog tag, but only if the discount is changed via the API, not raw SQL.

The strikethrough old price appears automatically if the price type specifies an "old price" and the component template supports OLD_PRICE output. Check that the catalog template outputs both values — otherwise the visitor will not see the benefit.

Typical problems and solutions

What's included in turnkey promotional price setup?

• Audit of current discounts and price types.
• Schedule design and mechanism selection (catalog discounts / agents / cron).
• Implementation: creating discounts, writing agent or cron script.
• Cache configuration and cache clearing upon activation.
• Staging testing, price display verification (including OLD_PRICE).
• Schedule maintenance documentation.

Contact us for an evaluation of your project — we will set up your promotion schedule in 1–2 days. Request a consultation to discuss discount automation. Our team, with many years of Bitrix experience, has implemented over 50 projects with discount automation.

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.