Setting Up Price Rounding in 1C-Bitrix: Accuracy and Marketing

We often encounter this situation: a client updates 1C, and the site shows a price of 324.57 rubles for an item that costs 349 rubles with a 7% discount. Managers complain about "ugly" prices, the accounting department about discrepancies with 1C. Price rounding in Bitrix is the point where a mathematically correct result turns into an artifact if the rules are not set correctly. Our experience shows: properly configured rounding rules save hours of approvals and increase customer trust. In one project with a catalog of 50,000 items and three price types, manual correction took up to 3 hours a day — after automating rounding, the problem was solved in 4 hours. Our approach reduces the time to set up rules by 3 times compared to typical solutions.

With 10+ years of experience, we have completed over 200 Bitrix projects and are certified as "1C-Bitrix: Developer". Every solution is tested on a copy of the site before deployment.

More about the psychology of pricing — on Wikipedia

Where Is Rounding Configured?

Settings → Product Settings → Catalog → Price rounding. In earlier versions, it was in the component settings of bitrix:catalog.element and bitrix:catalog.section with parameters PRICE_VAT_INCLUDE and separate roundings.

Global rounding rules — CCatalogProduct::getRoundRules() reads from b_catalog_rounding_rule. The table is simple: price type ID, range, type, and precision. But in projects with dozens of price types and complex discount logic, manual configuration via the admin becomes a nightmare. We write migration scripts using \Bitrix\Catalog\RoundingTable.

What Rounding Rule Types Does Bitrix Support?

Mathematical rounding — the basic choice for accounting, but it doesn't give "beautiful" prices for the storefront. Rounding down is often used in marketing: price 324 instead of 324.57 looks more attractive. Rounding up is rare, when you need to avoid losing on kopecks.

How We Configure Rounding: A Real Case

In one project with a catalog of 50,000 items and three price types (retail, wholesale, small wholesale), the task was: for retail, round down to integers; for wholesale, round up to tens; for small wholesale, mathematically to 0.1. Plus for prices over 10,000 rubles — a separate rule. We wrote a script in PHP 8.1 using \Bitrix\Catalog\RoundingTable::add() and a migration via Yurii\BitrixModels\Migration. The whole process took 4 hours, including testing on a copy. After deployment, discrepancies with 1C disappeared, managers stopped manually correcting prices.

// Adding a rounding rule
\Bitrix\Catalog\RoundingTable::add([
    'CATALOG_GROUP_ID' => $priceTypeId, // 0 = all price types
    'PRICE_FROM'       => 0,
    'PRICE_TO'         => 999.99,
    'ROUND_TYPE'       => \Bitrix\Catalog\RoundingTable::ROUND_MATH,
    'ROUND_PRECISION'  => 0, // to integers
]);

// For prices from 1000 — another rule
\Bitrix\Catalog\RoundingTable::add([
    'CATALOG_GROUP_ID' => $priceTypeId,
    'PRICE_FROM'       => 1000,
    'PRICE_TO'         => null,
    'ROUND_TYPE'       => \Bitrix\Catalog\RoundingTable::ROUND_MATH,
    'ROUND_PRECISION'  => -1, // to tens
]);

ROUND_PRECISION — number of decimal places (negative values round to tens, hundreds). Important: if you have price types with VAT, rounding is applied before adding tax. This is standard behavior but often raises questions.

Why Does Rounding in the Cart Differ from the Storefront?

Rounding rules are applied when calculating the final price via CCatalogProduct::GetOptimalPrice(). In the cart component, it's when recalculating the line total. But discounts, coupons, and VAT can distort the result. For example: on the storefront, price with VAT is 1200 rubles, without VAT — 1000 rubles. In the cart, when applying a 10% discount, the base price rounds to 1080 (with VAT) or 900 (without). If VAT is added after rounding, the total may differ by kopecks. This is normal and regulated by the complex component settings.

Psychological Pricing

For prices like ".99", rounding rules are not suitable — this is a marketing task solved by a postfix handler. For example, an event handler for OnSaleOrderBeforeSaved or a custom price recalculation method. We implement such scenarios turnkey: configure the logic "price always ends in 9", "rounding to 49 or 99 kopecks", etc.

What Is Included in the Work

• Audit of current rounding rules: analysis of the b_catalog_rounding_rule table, identifying duplication and conflicts.
• Development of custom rules: writing migration scripts, custom handlers for psychological prices.
• Testing on a copy of the site: checking all price types, discounts, cart, export to 1C.
• Documentation: description of created rules, instructions for managers.
• Training: how to add new rules via the API, not the admin.

Deadlines and Guarantees

Basic setup of rounding rules for all price types — from 1 to 3 hours. Non-standard logic (psychological prices, different rules for categories, integration with 1C) — from 4 to 8 hours. We guarantee that after setup, prices on the storefront and in the cart will display correctly, and discrepancies with 1C will be eliminated. We will evaluate your project for free — get a consultation by contacting us via chat or email. Our team's experience: 10+ years of Bitrix development, over 200 completed projects, certification "1C-Bitrix: Developer".

Comparison of Rounding Approaches

Let's compare approaches. Mathematical rounding (ROUND_MATH) gives accounting accuracy but looks ugly on the storefront. Rounding down (ROUND_DOWN) is attractive to customers but slightly reduces margin. Rounding up (ROUND_UP) protects against loss, but customers may notice overpricing. A psychological handler provides a marketing effect but requires development. For most projects, we recommend a combination: for retail — rounding down to integers, for wholesale — mathematical to tens, and for promotional prices — a custom handler.

Contact us to discuss your project. We will analyze your current rules for free and suggest the optimal solution.

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.