B2B Personal Account Development on 1C-Bitrix

B2B Personal Account Development on 1C-Bitrix

We specialize in building B2B cabinets on 1C-Bitrix. Our experience spans dozens of projects with non-standard role logic, approvals, and integrations. Picture this: a corporate client logs into the cabinet but cannot find an order within two minutes, download an invoice, or check their credit limit. Instead, they call the manager. Such calls are a failure metric. We eliminate the root cause: we design the cabinet so that business processes run without employee distraction. We cut those calls by 50% — direct savings of your managers' time.

In 12–20 weeks, we deliver a turnkey cabinet where each employee sees only their tasks, orders are created from the legal entity, and documents from 1C are pulled automatically. Get your project assessed free — contact us.

How Role Management Works

The central entity is Company, linked to Bitrix users via a Highload-block b2b_company_users. Fields: UF_COMPANY_ID, UF_USER_ID, UF_ROLE, UF_ACTIVE, UF_CREATED_AT.

Roles are defined as constants in a module:

• ROLE_OWNER — full rights, manages employees and company details
• ROLE_BUYER — creates and views company orders
• ROLE_ACCOUNTANT — documents and finances only, no order creation
• ROLE_VIEWER — view history only

Inviting an employee: the owner enters an email → a token is generated → an email is sent via CEvent::Send with template B2B_COMPANY_INVITE → the link creates (or links) a Bitrix user → a record is added to b2b_company_users.

What is Needed Beyond Standard Orders

List of company orders, not user orders — CSaleOrder::GetList with filter by UF_COMPANY_ID (custom order field). Filter by status, date, manager. Search by order number and SKU via CSaleBasket::GetList with a subsequent JOIN.

Approval statuses: we add custom ones (APPROVAL_PENDING, APPROVED, REJECTED) to b_sale_status. Transitions are handled in OnSaleStatusOrderChange handlers with notifications via CEvent::Send. Order comments — via Highload-block order_comments with fields UF_ORDER_ID, UF_USER_ID, UF_TEXT, UF_CREATED_AT, UF_IS_INTERNAL (for internal notes).

Why 1C Integration is Critical

Documents from 1C are a key value. The scheme:

1. In 1C, set up an HTTP service or regular XML export via CommerceML.
2. A Bitrix agent (CAgent::AddAgent) polls the service every 2–4 hours.
3. Results are stored in the Highload-block b2b_documents: UF_COMPANY_ID, UF_DOC_TYPE (invoice, waybill, reconciliation), UF_NUMBER, UF_DATE, UF_AMOUNT, UF_FILE_ID (or UF_EXTERNAL_URL).
4. In the cabinet — a list with filters, PDF download.

If 1C provides PDFs directly — we cache them in /upload/b2b/docs/{company_id}/ named by document number. If only metadata — on click we make a request to 1C and stream the file via PHP without saving to disk (saves space).

Financial Summary

The "Finance" block on the dashboard: current credit limit and used amount (progress bar), overdue debt with date, monthly order total. Source — Highload-block b2b_credit_status, synced from 1C. If data is older than 6 hours — a warning "Data is being updated". If overdue exceeds a threshold — a banner in the header and the "Create order" button is blocked.

Notifications

Two channels:

• Email: mail events (CEventType, CEvent) B2B_ORDER_CREATED, B2B_ORDER_STATUS_CHANGED, B2B_ORDER_APPROVED, B2B_DOCUMENT_READY. Templates are editable in the control panel.
• Internal: unread counter in the cabinet via Highload-block b2b_notifications (UF_USER_ID, UF_TYPE, UF_TEXT, UF_LINK, UF_IS_READ, UF_CREATED_AT). AJAX every 30 seconds or WebSocket (pull module).

Comparison: Custom vs Standard Cabinet

A custom cabinet cuts order creation time threefold — that's dozens of hours saved per month for your clients.

What is Included in the Work

• Audit of current business processes and requirements.
• Architecture design for roles and entities (Company, Highload-blocks).
• Development of components for order and document management.
• Integration with 1C via CommerceML or REST.
• Setup of notifications (email + internal).
• Testing on real scenarios.
• Handover of documentation and administrator training.

We are certified 1C-Bitrix partners, guaranteeing deadlines and full transparency. Contact us for a project assessment — we will prepare a custom proposal.

Timelines

Total: 12–20 weeks. Less if a ready-made framework is used. More if non-standard approval logic or complex 1C exchange is needed.

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.