B2B Portal Development on 1C-Bitrix Turnkey

B2B Portal Development on 1C-Bitrix Turnkey

A standard Bitrix online store doesn't suit wholesale sales: one price for everyone, a public catalog, no credit limits, and no order approval workflow. When a manager spends 40 minutes manually processing each order via CRM, and a dealer calls to check stock, it's a sign of a missing B2B portal. We design the architecture, configure pricing, integrate with 1C, and implement approval business processes. Contact us to evaluate your project.

How a B2B Portal Fundamentally Differs from a Public Store

Architecturally — different authorization logic, pricing model, and ordering scenario. A B2B portal on Bitrix is implemented 3-5 times faster than a custom solution with comparable functionality.

Authorization and user groups. In bitrix:sale, a user is tied to one group. For B2B, a hierarchy is needed: company → contact person → role (buyer, accountant, director). Standard groups are flat and unsuitable. This is implemented via a custom module with a company_user link table and D7 ORM (Bitrix\Main\ORM\Data\DataManager). Action rights are set via a bitmask in a Highload role block.

Price types. The catalog module supports multiple price types: CATALOG_GROUP_ID in the b_catalog_price table. For B2B, this is mandatory — each user group gets its own price type. Individual contract prices are implemented via the OnSaleOrderBeforeSaved event handler or a custom price provider.

Real-time stock catalog. B2B buyers order in large quantities and check availability before ordering. Stock data from b_catalog_store_product is updated during synchronization with 1C via CommerceML. If synchronization runs once per hour, the client sees outdated data. Solution: 1C REST API + incremental update via CCatalogStoreProduct::Update(). Saves managers up to 40 hours per month.

How to Organize Authorization on a B2B Portal?

For B2B, a custom authorization module is needed, implementing a "Company — Contact Person — Role" hierarchy with permission separation. This allows, for example, giving the accountant access to financial documents but not orders. The 1C-Bitrix commercial platform provides D7 ORM for building such relationships.

Key Modules and Components

• sale module — the basis for cart and orders. In B2B it is extended: we add statuses (Pending, Approved, Rejected), configure business processes via bizproc module.
• catalog module — pricing, SKUs, warehouse management. CatalogGroup and DiscountCoupon are mandatory.
• crm module (if using Bitrix24) — synchronization of portal orders with CRM deals via REST API crm.deal.add / crm.deal.update.
• Personal account — order history with repeat, current orders, debt, documents (invoices, PDF), contact person management.

Integration with 1C

Standard exchange via CommerceML covers products, prices, warehouses, orders. But it does not cover:

• Credit limits and debt — exported via separate XML or 1C REST service. On Bitrix side — a custom Highload block b2b_credit_limits.
• Documents — invoices and waybills stored in 1C. The portal requests the list via REST, caches in /upload/b2b/docs/ with TTL 24 hours.
• Specifications — individual contract items, stored in a Highload block linked to the company.

Important: do not break the standard CommerceML exchange. Custom fields and logic — via events OnBeforeCatalogImport1C, OnSuccessCatalogImport1C, separate tables.

Performance Under Load

A B2B portal with 500+ active companies and peak load requires:

• Tagged catalog cache: CIBlock::clearIblockTagCache($iblockId) when stock updates.
• Alternative for personal prices: cache by key user_group_price_{groupId}_{productId}.
• Redis sessions for load balancing.
• Elasticsearch for catalog search instead of the search module.

Development Stages

Total: 12-22 weeks depending on 1C integration complexity.

Typical Errors and Their Solutions

Step-by-Step Guide: How 1C Integration Is Done

1. Configure CommerceML on the 1C side: set the schedule for exporting products, prices, stocks.
2. Create a REST service in 1C to transfer credit limits and documents.
3. Implement Bitrix event handlers (OnBeforeCatalogImport1C, OnSuccessCatalogImport1C).
4. Test exchange on a test environment.
5. Deploy to production and monitor.

What's Included

• Full technical documentation (architecture, DB schema, API contracts).
• Source code of custom modules with a license to use.
• Access to dev and prod environments, repository.
• Administrator training (up to 8 hours) and user manuals.
• 6-month warranty support with 4-hour response time.

Ready to discuss your project? Contact us for a consultation. Order a turnkey B2B portal development and get a cost and timeline estimate.

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.