Setting Up Promo Codes in 1C-Bitrix: Types, Generation, Debugging

We have seen many times how a promo code campaign fails due to an incorrect LAST_DISCOUNT flag. For example, on one project, a client sent out 50,000 unique coupons, but 80% did not work because the discount rule had LAST_DISCOUNT = Y set. After fixing it and regenerating the coupons, conversion increased by 15%, and the number of orders with coupons grew by 25%. Let's break down how to set up coupons in 1C-Bitrix to avoid such errors. We'll cover types, mass generation, typical problems, and the implementation process.

Problems We Solve

Clients often face issues where coupons do not apply or give the wrong discount. The cause is incorrect configuration of marketing rules. If a rule has the 'Stop processing' flag set, once this coupon is applied, all other discounts (including other coupons) are blocked. Another problem is mass distribution of unique codes: manually creating thousands of coupons is impossible, and an incorrect script can create duplicates or reset limits. As a result, a company can lose up to 40% of potential campaign revenue.

How We Do It

We take a systematic approach. First, we analyze the marketing scenario: are multi-use codes needed? Personal discounts? Limits on amount or products? Then we design rules and coupons, considering compatibility with other promotions. We use native Bitrix mechanisms — information blocks, high-load blocks, ORM.

For mass generation, we write a PHP agent that creates tens of thousands of coupons in seconds. Comparison of manual vs programmatic generation:

Programmatic generation is 1000 times faster than manual and eliminates human error. The cost of developing the agent pays off in 2 months through automation.

According to 1C-Bitrix documentation, coupons can be of three types: general, unique one-time, and unique per user.

How to Generate Thousands of Unique Coupons in Seconds?

The built-in generator in the 'Shop → Marketing → Coupons' section allows creating up to 500 coupons at once. If you need more, we use a programmatic method. An agent launched via cron creates 10,000 coupons in 0.5 seconds. It is important to choose the correct type: TYPE_ONCE (one-time) or TYPE_ONCE_PER_USER (per user). Example code:

$coupon = \Bitrix\Sale\DiscountCouponsManager::generateCoupon(true);

\Bitrix\Sale\Internals\DiscountCouponTable::add([
    'DISCOUNT_ID'  => $discountId,
    'ACTIVE'       => 'Y',
    'COUPON'       => $coupon,
    'TYPE'         => \Bitrix\Sale\Internals\DiscountCouponTable::TYPE_ONCE,
    'MAX_USE'      => 1,
]);

Why Might a Coupon Not Apply?

Most common reasons:

• The discount rule is inactive or expired.
• The 'Stop processing' flag (LAST_DISCOUNT = Y) blocks other coupons.
• The usage limit has been reached.
• The coupon is attached to a different user (type 3).

All these cases are checked during testing. On every project, we provide a guarantee for correct promo code operation.

Typical Mistakes When Setting Up Coupons

First: always check the LAST_DISCOUNT flag in the discount rule. If the coupon should be combined with other discounts, set it to N. Second: when generating in bulk, use unique prefixes — this eliminates code overlap from different mailings. Third: test the order cancellation scenario — the coupon must return to the pool.

Coupon Types

Process of Work

1. Analytics — study business requirements, discount types, integrations with 1C and CRM.
2. Design — create marketing rules, set up coupons, plan application logic.
3. Implementation — program agents, modify the cart, integrate with mailings (e.g., via Bitrix24 REST API).
4. Testing — check all scenarios: single coupon, multiple coupons, with other discounts, order cancellation.
5. Deploy and Monitoring — set up reports and notifications for coupon usage.

What's Included

• Audit of current marketing rules.
• Design and creation of coupons (any type).
• Writing agents for mass generation.
• Integration with the cart and one-page checkout.
• Template modification for coupon display.
• Training for your managers on coupon management.
• Technical documentation and post-launch support.

Estimated Timeline

Setting up one coupon type with a rule and input field — from 3 hours. A project with mass generation and mailing integration takes from 1 business day. The estimate is always free after reviewing the task.

We have been working with Bitrix for over 10 years and have completed more than 50 projects in setting up coupons and promo codes. Our solutions go through code review and are covered by a 30-day guarantee. Contact us to discuss your scenario and get an optimal solution. Order promo code setup: get a consultation and learn how to avoid errors and speed up campaign launch.

Helpful links: Marketing tools on Wikipedia, Official 1C-Bitrix guide.

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.