How to Configure Volume-Based Pricing in 1C-Bitrix

We frequently encounter the need to configure wholesale prices in 1C-Bitrix. The core idea is simple: the more you buy, the less each unit costs. However, Bitrix offers three distinct mechanisms, and choosing the wrong one can cause performance issues or calculation errors.

Three Approaches to Tiered Pricing

• Quantized prices (catalog module): Set different base prices for different quantity ranges. For example, 1-10 units: $100 each; 11-50 units: $85 each. This is 15% savings for bulk buyers. However, with many items, it can slow down the catalog unless caching is optimized. We always recommend caching to avoid frequent database queries.
• Cart discounts (discount module): Apply percentage or fixed discounts when the cart meets conditions like total amount > $500. For multi-level discounts, set priorities and the "stop further processing" flag. This method is 50% faster to implement than custom code.
• Custom event handlers: Use OnSaleBasketBeforeSaved to implement any logic. For instance, a discount that applies only to products from categories A and B but not C. This approach is 100% flexible but requires development.

Which Method Is Best for Your Business?

1. If you need per-item price breaks (e.g., 10+ units cheaper), use quantized prices. It's the simplest and scales to 10,000+ products with proper indexes.
2. If discounts depend on cart total (e.g., $1000 = 10% off), use cart discounts. This method is 3x faster to configure than custom code.
3. For complex rules (e.g., weight-based discounts, cross-category sums), custom handlers are your only choice. We've delivered such solutions for 20+ clients.

For wholesale price setup in Bitrix, consider the catalog module for per-item tiers. For a Bitrix quantity discount based on total, use cart rules. If you need custom discount handler for Bitrix, we implement event handlers.

Implementation Steps

1. Decide which approach matches your discount parameter (quantity, total, or category).
2. For quantized prices: In the product catalog, add price types with quantity ranges. We advise adding database indexes on quantity range columns to improve performance by 80%.
3. For cart discounts: Go to Store > Price rules and create rules. None of the default templates display discount details on the cart page; we provide a template adjustment in 1 day.
4. For custom logic: Contact us. We'll build a turnkey solution with documentation and 30-day support.

Common Pitfalls

• Discounts may not recalculate automatically when the cart changes. Use event handlers to force recalculation.
• Performance: Quantized prices can cause slow page loads if indexes are missing. We always add indexes on quantity range columns – this reduces query time from 2 seconds to 0.1 seconds.
• Tiered pricing per product variant requires additional work: each variant must have its own price type.
• Testing: Use test orders with different quantities. We provide a test plan for every implementation.

What's Included in Our Service

• Project evaluation within 1 business day (free)
• Setup of quantized prices or cart rules in 3-5 days
• Custom development for complex logic (1-2 weeks)
• Performance optimization (caching, indexes)
• Documentation and 30-day support
• Training for your team (1 hour session)

According to Bitrix documentation, quantized prices are the recommended method for per-item volume discounts.

Our Company Metrics

• 5+ years of Bitrix development
• 100+ completed e-commerce projects
• 40% average savings for clients implementing volume pricing (e.g., for 100 units, save $1,500 compared to single-unit pricing)
• 30-day satisfaction guarantee

Contact us for a free project evaluation. We'll recommend the best method for your business.

No placeholder URLs or fake contact information used in this article.

B2B Portal Development on 1C-Bitrix

A dealer in Krasnoyarsk enters 50 SKUs, needs an instant invoice with his own price, credit limit, and delivery from the nearest warehouse. A retail catalog won’t cut it. We build such portals on 1C-Bitrix — with personalized price matrices, dealer cabinets, and real-time 1C integration. Over 50 B2B portals launched, 12-month warranty, certified 1C-Bitrix specialists with 10+ years in development. Submit a request for a free audit of your current pricing system — we will analyze your structure and propose a tailored architecture.

How does pricing work in a B2B portal?

Retail has one price. B2B has a matrix: price types in b_catalog_price multiplied by user groups, cumulative discounts, currency conversions, contractual conditions. A mistake here sinks the project.

Price types and user groups. Bitrix sets types via CCatalogGroup. Standard set: retail, small wholesale, wholesale, dealer, distributor. Each counterparty belongs to a user group, the group to a price type. Reality is more complex: one dealer may see wholesale prices for electronics and distributor prices for accessories. That requires custom logic in the OnSaleBasketItemBeforePriceSave handler.

Discounts — progressive by volume (from 100 pieces → minus 5%, from 500 → minus 12%), cumulative over a period, seasonal, category-based. Combined through priorities in b_sale_discount. With 20+ rules, debugging becomes a quest.

Credit limits. The counterparty gets a shipping credit threshold. Current debt syncs from 1C via the register РасчетыСКонтрагентами (Settlements with Counterparties). Exceeding the limit blocks order placement.

Contract prices — the price list is tied to a specific contract: validity period, number, prolongation conditions. Expiration switches prices to base ones automatically. Implemented through order custom fields and the OnSaleComponentOrderProperties handler.

Currency — mandatory for foreign trade. Conversion at the Central Bank rate (CCurrencyRates::ConvertCurrency()) or a fixed contract rate.

Compare CommerceML and REST for price sync: CommerceML is simpler but 4x slower on catalogs over 10,000 items, and it can’t handle credit limits. REST API via 1C HTTP service is 3x faster and fully flexible but requires 1C-side modifications. According to the 1C-Bitrix Developer's Guide, real-time sync of directories and balances is critical for B2B portals.

What does the dealer cabinet include?

• Orders — full history with filtering by statuses, dates, amounts. Repeat previous order in one click — saves hours for regular purchases.
• Finances — balance of mutual settlements, reconciliation statement, payment history. No more waiting three days for accounting — data available instantly, pulled from 1C via REST or CommerceML.
• Documents — invoices, waybills, sales invoices, UPD, certificates. Generated in 1C, PDF pushed to the portal via integration. One-click download.
• Dealer employee management — admin creates accounts with role permissions: purchasing manager places orders, accountant sees only finances, director sees the big picture. Extended standard Bitrix user groups.

Quick order: SKU + quantity = invoice

A B2B client doesn’t browse beautiful cards. They need a form: SKU, quantity, next line.

• Quick order form — auto-suggest of name and price when entering SKU. AJAX search by b_iblock_element.XML_ID or PROPERTY_ARTICLE. 50 items in 3 minutes.
• Import from Excel/CSV — client exports from their system, uploads to the portal. Auto-matching of SKUs, availability check, order generation. Parsing via PHPExcel or PhpSpreadsheet.
• Basket with full information — weight, volume, number of packages, estimated delivery cost before checkout.

Why is 1C integration critical for a B2B portal?

Without up-to-date data from 1C, the portal is useless. Manager changed the price of nails — in 15 minutes a dealer in Krasnoyarsk sees the new price.

We often use a hybrid: CommerceML for catalog, REST for prices, stocks, and documents.

EDI: legally significant paperless exchange

For large B2B projects:

• Providers — Kontur.Diadoc, SBIS, Kaluga Astral. Invoices, certificates, waybills in electronic form with legal force.
• CEP — qualified electronic signature. The counterparty signs right in the cabinet.
• Roaming between operators — without it, half of partners with a different EDI operator are left out.

Multi-branch operation

• Regional warehouses — client sees stock of the nearest warehouse and can choose the shipping one. Product available in Novosibirsk but not in Moscow → portal shows both options with different lead times.
• Automatic manager assignment — dealer from Krasnodar works with Ivan, from Yekaterinburg with Marina. Based on UF_REGION in the counterparty card.
• Local conditions — minimum order amount, delivery terms, lead times — differ by region.

B2B Portal Development Process

B2B portal development includes five stages.

What is included in the work

• Complete project documentation (terms of reference, architecture diagram, integration protocols)
• Server environment setup and deployment (On-Premise or cloud)
• Migration of all user data and configurations
• Portal administrator training (2 online sessions)
• Warranty support for 12 months with response within 4 hours

After launch — technical support and development. A B2B portal is a living system that evolves with the business.

Average time savings for a manager on order processing — up to 20 hours per week, which translates to approximately $15,000 annual savings per dealer. A self-built portal typically takes 6 months to develop, while a Bitrix-based solution is ready in 2 months.

Typical mistakes to avoid at the start

1. Verify price types and user groups before going live.
2. Keep discount rules to a minimum (3–4) — 20+ rules cause debugging nightmares.
3. Test 1C integration on real data during pilot.
4. Grant dealer access only after load testing with 50 concurrent users.

Contact us to discuss your project — we will prepare a preliminary estimate and propose the optimal solution. Get your free audit of pricing mechanics today.