Setting Up Credit Limits for B2B Clients in 1C-Bitrix

Imagine: your B2B portal on 1C-Bitrix processes hundreds of orders daily, but there is no control over accounts receivable. Clients overdue by 30+ days place new shipments, increasing the cash gap. Without credit limit configuration, the system accepts orders from clients with growing debt. We solve this problem with automation: create a Highload-block b2b_credit_status, configure integration with 1C, and automatically block orders when the limit is exceeded. Everything turnkey in 2–3 weeks. We will evaluate your project for free — contact us.

Problems We Solve

• Lack of automatic control. Managers manually check debt before each order — this slows processing and causes errors. Our solution automatically checks the limit when an order is placed in the OnBeforeSaleOrderAdd event.
• Outdated data. Limits are manually updated once a month. We set up synchronization with 1C every 2–4 hours via agent, and additionally a event trigger when an order status changes to "Paid".
• Insufficient transparency. Clients cannot see their current limit and debt. We add a widget to the personal account with a progress bar and a warning when approaching the limit.

How Does the Limit Check Work?

The OnBeforeSaleOrderAdd event handler performs three steps:

1. Identifies the current user's company via the b2b_company_users table.
2. Reads the record from the Highload-block b2b_credit_status by UF_COMPANY_ID.
3. Compares the sum of used limit plus new order with the established limit.

If the blocking condition triggers, the order is not created, and the client sees a message: "Credit limit exceeded. Available: X rub. Debt: Y rub." For VIP clients with unlimited credit, the UF_CREDIT_LIMIT field is set to 0, and the check is skipped.

Why Is Synchronization with 1C Critical?

Limit data lives in the accounting system. Without automatic synchronization, it becomes outdated within a couple of days. We use CommerceML or 1C REST API to export JSON/XML. An agent on the Bitrix side reads the file or requests the service and updates records in the Highload-block. Additionally, forced update upon receiving a webhook about order payment.

"To ensure data relevance in Highload-blocks, it is recommended to use agents with an interval of no more than 4 hours" — official 1C-Bitrix guide.

What Data Is Stored in the Highload-Block?

Step-by-Step Guide to Setting Up Credit Limits

1. Create a Highload-block with the fields from the table above.
2. Set up a synchronization agent with 1C (interval 2–4 hours).
3. Register an OnBeforeSaleOrderAdd event handler.
4. Develop a personal account widget with a progress bar.
5. Test all scenarios (exceed, unlimited, overdue).

What Is Included in the Setup?

• Analysis of current debt accounting scheme — we break down integration with 1C and business processes.
• Creation of Highload-block b2b_credit_status with necessary fields.
• Development of limit check logic — event handler, conditions for VIP clients.
• Widget in personal account — display limit, progress bar, blocking warning.
• Synchronization with 1C — agent, webhooks, error handling.
• Documentation — description of structure and logic for your team.
• Training — 2-hour webinar for managers and admins.
• Post-release support — 2 weeks of monitoring correct operation.

How Long Does Implementation Take?

Why Choose Us

We have been working with 1C-Bitrix for over 10 years and have completed 50+ projects on credit setup and 1C integration. Our solutions use tagged caching for widgets and agents for synchronization — this delivers high performance even on catalogs with millions of products. Code warranty — 1 year. 1C-Bitrix certificate (available upon request).

Typical mistake in self-setup — checking the limit on the 1C side (only during synchronization). An order can be placed between updates for an amount exceeding the remaining limit. We do real-time checking on the site side — this is 60% faster than weekly synchronization and eliminates limit breaches.

Manual order checking takes up to 30% of managers' time — automation frees up resources. If you want to implement automatic credit limit control, contact us for a preliminary assessment. Get a consultation on your project — we will evaluate the scope and exact timeline within 1 day.

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.