Setting Minimum Order Amount for B2B in 1C-Bitrix

Imagine: a client from the 'New Wholesale' group has a cart worth below the required minimum, but the minimum for their group is set higher. If you block checkout only at the final step, you risk losing the client. We solve this with cart warnings and flexible rules tied to user groups or companies. Our experience: 10+ years developing on Bitrix, over 50 projects with custom order restrictions. The result — transparent conditions for each client and a 30-40% reduction in cart abandonment.

Standard Approach: Single Threshold via Admin Panel

Bitrix has a built-in restriction: store settings → field "Minimum order amount". This is a single value for everyone. When attempting to place an order below the threshold, an error is displayed. This method works for simple B2C, but B2B requires flexibility.

How to Set Minimum Amount for Different User Groups?

Implemented via the OnBeforeSaleOrderAdd handler. Logic:

1. Determine the user's group or their dealer company.
2. Get the minimum amount from storage (module options or Highload block).
3. Compare with $order->getPrice().
4. If below, add an error via $event->addError().

Storage: Highload block b2b_order_limits with fields UF_GROUP_ID, UF_MIN_AMOUNT, UF_CURRENCY.

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale',
    'OnBeforeSaleOrderAdd',
    function (\Bitrix\Main\Event $event) {
        $order = $event->getParameter('ENTITY_OBJECT');
        $userId = $order->getUserId();
        $userGroup = \CUser::GetUserGroup($userId);
        $minAmount = \Bitrix\Main\Config\Option::get('module_name', 'MIN_AMOUNT_'.$userGroup[0]);
        if ($order->getPrice() < $minAmount) {
            $event->addError(new \Bitrix\Main\Error('Minimum order amount: '.$minAmount.' RUB.'));
        }
    }
);

Why Cart Warning Matters?

Blocking at order creation is too late. The user should see an indicator directly in the cart. In the component's result_modifier.php, we calculate the difference and add a flag IS_BELOW_MINIMUM. The template shows: "Add X RUB more to reach the minimum order amount."

Comparison Table

Why Single Threshold is Inefficient for B2B?

A single threshold ignores client categories. For example, beginners could have a lower threshold, while VIP dealers have no limit. This either loses small clients or misses profit from large ones. A custom solution via handler and Highload block is 5 times more flexible than the standard one.

Use Cases

Minimum by Category

Sometimes the rule applies not to the entire order but to specific categories. For example, the "Fragile goods" category ships only from a minimum order amount. In the OnBeforeSaleOrderAdd handler, we group cart items by IBLOCK_SECTION_ID, extract the limit for each category from the same Highload block, and if any category falls short, add an error.

What's Included in the Work

• Audit of current rules and calculation schemes.
• Structure design: groups, companies, categories.
• Development of handler and Highload blocks.
• Improvement of cart visual part (indicator, calculation).
• Testing of scenarios (including edge cases).
• Documentation and training for your managers.
• 6-month warranty.

Get a consultation on configuring flexible rules for your store — our specialists will help you choose the optimal solution.

Guarantees and Support

All completed work comes with a 6-month warranty. If your business logic changes, we quickly adapt the rules. A team of certified 1C-Bitrix specialists ensures stable operation even under high loads.

Estimated Timelines

Basic setup via interface — 1 day. Development of group minimums with cart warning — from 3 to 5 days. Timelines are refined after auditing your project. Cost is calculated individually.

Contact us for a consultation — we will help you choose the optimal solution for your B2B.

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.