1C-Bitrix Price Types: Retail, Wholesale, Dealer Setup

1C-Bitrix Price Types: Retail, Wholesale, Dealer Setup

Imagine: you launch an online store on 1C-Bitrix. You have retail customers, wholesalers, and dealers. Each needs their own price for the same product. Without proper price type configuration, you risk showing everyone the same price or getting logical errors when calculating the cart. We have encountered projects where, due to incorrect user group binding, prices broke with every exchange with 1C. Let's break down how to configure price types competently to avoid such issues.

What problems does price type configuration solve?

Priority confusion. In Bitrix, one user can belong to multiple groups. Which price should be shown? By default, the type with the lowest SORT field value is applied. If SORT is not set, the order is undefined. We recommend explicitly setting SORT for each type: BASE = 10, wholesale = 20, dealer = 30. Otherwise, VIP customers might see the wholesale price instead of a special offer.

Import from 1C. Standard exchange via CommerceML passes prices in the PriceType property. Many developers mistakenly try to set prices through CIBlockElement::SetPropertyValues — this does not work. The only correct way is through CCatalogProduct::SetPrice or D7 API. Official documentation. Also useful to study the CommerceML format on Wikipedia.

Price type caching. If tagged caching is enabled, after changing prices or group bindings, the information block cache must be cleared. Otherwise, users will see old prices. We configure automatic cache clearing via agents when prices are updated from 1C.

How we do it: a case from our practice

Recently, a client came to us — a wholesale supplier of building materials. Catalog of 15,000 products, three price types (retail, small wholesale, large wholesale) linked to groups. The main pain: after hourly exchange with 1C, prices would break — some products would go to zero, others would duplicate. It turned out that 1C had 4 price types, while Bitrix had 3, and the mapping was incomplete. We:

1. Created a fourth type "Special Offer" linked to the "VIP" group.
2. Configured the OnBeforePriceUpdate event to check for duplicates and prevent zero prices.
3. Added an agent to clear tagged cache every 59 minutes (slightly less often than the exchange). Result: prices stable, users see their types, exchange works without failures. The client saved up to 40% of the budget by avoiding downtime and manual price corrections.

Process of working on your project

We don't just create price types in the admin panel. Stages:

1. Analytics — study your group structure, types from 1C, currencies. Collect all scenarios.
2. Design — determine SORT, bindings, base type. Decide if multi-currency is needed.
3. Implementation — create types, write code for import (if non-standard), integrate with 1C via CommerceML or API.
4. Testing — check each user group, each type, scenarios with zero prices.
5. Deployment — roll out to production, clear cache, monitor for a couple of days.

What is included in the result

After completion, you receive:

• Configured price types with correct user group bindings.
• Integration with 1C (if required) — type mapping, duplicate handlers.
• Documentation on the price scheme and recommendations for changes.
• Training for your administrator on working with price types.
• One month of free support in case of questions.

Comparison: professional setup vs DIY

Professional setup is 3 times faster than DIY and avoids typical errors that can lead to losses.

How to avoid errors when importing prices from 1C?

Typical errors and their solutions:

• Deleting the BASE type or creating multiple BASE types — leads to unpredictable catalog behavior. Never delete the base type.
• Setting prices via CIBlockElement::SetPropertyValues — prices won't save. Use only CCatalogProduct or D7.
• Ignoring caching — users will see old prices. Configure automatic cache clearing.
• Binding a type to only one group — if a user belongs to multiple groups, you won't get the expected price. Bind types to all relevant groups.

Timing and how to order

Basic setup of 2-3 price types with group bindings takes 2 to 4 hours. If complex import or multi-currency is needed, it takes 4 to 16 hours. Cost is calculated individually after analyzing your project. Contact us — we'll evaluate your case for free and propose a solution. Order price type setup today and get a month of support as a gift.

We guarantee correct price operation for all user groups — even with hourly exchange with 1C. Experience with Bitrix: over 7 years, dozens of projects with various price types. We have certificates and a development license.

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.