Marketplace Commission Setup for 1C-Bitrix

We've repeatedly seen this scenario: the Bitrix marketplace is live, but commissions are calculated manually in Excel. Sellers get confused, accounting spends days on reconciliations, and calculation errors lead to losses. One client — a marketplace with 200 sellers — was losing up to 1.5 million rubles per month due to incorrect rate application. Automation solved the problem: commissions started to accrue correctly, and reconciliation time dropped from 3 days to 2 hours. Turnkey marketplace commission setup in 1C-Bitrix allows implementing any calculation model in 1–3 weeks. According to the official documentation, HL-blocks are the standard way to store custom entities, providing flexibility for commission rules. You can reduce manual calculation costs and improve financial transparency.

What commission models exist?

Commission is a percentage or fixed amount that the platform deducts from a sale. Rules can be:

• Global — a single rate for all sellers.
• By category — different percentages for different product groups.
• By seller — individual conditions for key partners.
• Combined — for example, 5% for items up to 1000 rubles, 3% above.
• Progressive — the percentage decreases as the seller's turnover increases (implemented via sales history).

We implement any variant using HL-blocks with versioning and validity periods. This is more reliable than storing rules in b_option. Our engineers are certified as "1C-Bitrix: Developer" and have 10+ years of experience, guaranteeing stable algorithm performance even under loads of 10,000+ orders per day.

Why HL-blocks are optimal for storing commission rules

HL-blocks allow storing rules in a structured format with support for data types, indexes, and filtering. Unlike b_option, complex queries can be implemented — e.g., finding a rule by seller-category combination. Validity periods (ACTIVE_FROM, ACTIVE_TO) are implemented by adding two date fields, and versioning via a change history. This provides flexibility to manage promotions and temporary tariffs without overwriting data.

How to set up complex commission rules

The rule table structure is universal:

The rule selection algorithm is implemented in the OnAfterOrderAdd handler:

function calculateCommission(int $vendorId, int $categoryId, float $amount): float
{
    // Priority: vendor+category > vendor > category > global
    $rule = findRule($vendorId, $categoryId)
        ?? findRule($vendorId, null)
        ?? findRule(null, $categoryId)
        ?? findRule(null, null);

    if (!$rule) return 0.0;

    $commission = $rule['RATE_TYPE'] === 'percent'
        ? $amount * $rule['RATE_VALUE'] / 100
        : $rule['RATE_VALUE'];

    if ($rule['MIN_AMOUNT']) $commission = max($commission, $rule['MIN_AMOUNT']);
    if ($rule['MAX_AMOUNT']) $commission = min($commission, $rule['MAX_AMOUNT']);

    return round($commission, 2);
}

The commission is written to the financial operations table with type commission and linked to the order. This ensures complete transparency for accounting and allows building reports by seller and period. Marketplace commission setup in 1C-Bitrix also includes integration with payment systems for correct fiscal data calculation.

How to set up a progressive commission scale

A progressive scale involves changing the rate based on the seller's accumulated turnover over a period (e.g., month or quarter). This requires an additional table to store sales history for each seller. The algorithm, at the time of commission calculation, sums the turnover for the required period and selects the corresponding rule from the HL-block. We implement this logic with caching of the turnover sum to avoid recalculating each time. Typical accounting time savings with a progressive scale — up to 60%.

Comparison of basic and complex models

What's included in the work?

• Analysis of current business logic and commission requirements.
• Design of rule structure and database.
• Implementation of the calculation algorithm with priority handling.
• Development of an admin interface for rule management (CRUD, filters, date pickers).
• Creation of a commission report with Excel export.
• Testing on a database copy (min. 100 orders of various types).
• Deployment to production and operator training.
• 30-day warranty for identifying hidden errors.

Process

1. Analysis — call with you, study the requirements, capture all commission nuances.
2. Prototype — database schema and algorithm within 1–2 days.
3. Development — writing code, creating the admin interface.
4. Testing — verification on test data with multiple scenarios (50+ test orders).
5. Deployment and training — launch on the live server, instructions for managers.

Timelines and cost

Basic implementation (single rate + category-based rules) takes 1 week. Complex model (individual rates, progressive tariffs, temporary promotions) takes 2–3 weeks. Cost is calculated individually after requirements analysis. We'll evaluate your project for free — just contact us. Request a free audit of your current commission system — we'll identify bottlenecks and propose an optimal solution.

We've been working with Bitrix for over 10 years and are certified as "1C-Bitrix: Developer". On your project, you'll get a ready-made solution, documentation, and post-implementation support. Contact us for a consultation — we'll choose the best architecture for your marketplace model.

Marketplace Development on 1C-Bitrix: Overcoming Standard Architecture Limitations

The b_sale_order table and related b_sale_basket are not designed for multivendor out of the box. Bitrix has no built-in 'marketplace' module — each time it's custom development on top of the sale module. The standard sale module cannot split orders by different suppliers: if the cart contains items from three sellers, Bitrix creates a single order with one number, status, and total. It's impossible to send each sub-order to a separate dashboard, calculate commissions for each seller, or allow partial shipment. We have to redefine the entire logic: from cart to status model. Additionally, the standard search (Sphinx) and caching are not optimized for a multivendor catalog — with 100,000 items from 500 suppliers, filters by supplier lead to performance degradation (queries with WHERE on IBLOCK_ELEMENT_PROPERTY become 5–10 times slower). We write a separate module that extends the standard cart: adds item-to-supplier binding via order property, splits a single order into sub-orders by seller, and routes each separately.

Why Standard Solutions Are Not Suitable for Multivendor Platforms?

Marketplace Models

Classic marketplace — the operator does not hold inventory. All product logic lies with sellers, the platform handles traffic and payment gateway. Technically, this is a separate supplier infoblock linked via UF_VENDOR_ID in the highload catalog infoblock.

Hybrid model — the operator sells alongside external suppliers. The main pain: ranking in the catalog. If suppliers see that the platform's own listings always rank higher, they leave. We solve this with a separate sorting component where position is determined by rating, shipping speed, and price, without privileges for 'own' items.

Service marketplace — requests, tenders, escrow. Here, instead of b_sale_basket, a custom request entity works with a workflow via Bitrix business processes.

B2B marketplace — contracts, reconciliation statements, credit lines, EDI. Authorization by TIN, multi-price groups via b_catalog_group, shipping limits.

What Technical Problems Does Marketplace Development on 1C-Bitrix Solve?

Monetization Models

What Does the Seller Dashboard Include?

The dashboard is the heart of a marketplace. An inconvenient dashboard = empty platform. No standard solution exists; we build from scratch using Bitrix components.

• Catalog management — CRUD for products via custom component, bulk CSV/XML upload via CIBlockXMLFile. Nobody manually enters 10,000 SKUs, so import is the first thing we do.
• Order processing — sub-orders land in the dashboard via ajax-polling or websocket. Confirmation, invoice printing via CSalePdf, status update with back-sync to the main order.
• Financial analytics — dashboard on highload infoblock of aggregated data. Revenue, commissions, payouts — details by product and period. The seller sees what sells and what just occupies the showcase.
• Delivery settings — seller's own tariffs, binding to sale.delivery.handler.
• Communication — built-in chat without revealing contacts. Implemented via im module or custom message table.
• Promotions — discounts, promo codes via b_sale_discount with filter by vendor_id.

Moderation and Quality Control

One batch of counterfeit goods kills the platform's reputation. Therefore, moderation is mandatory.

• Product moderation — status ACTIVE='N' until verification. Auto-moderation filters obvious violations (banned words, missing photos), manual moderation handles disputes. Handler OnBeforeIBlockElementUpdate prevents bypass.
• Seller verification — TIN check via Federal Tax Service API, document scans upload. Statuses: new → verified → premium. Each level unlocks limits on product count and commissions.
• Rating system — not just stars. The algorithm considers shipping speed (AVG(ship_date - order_date)), return rate, and answer quality.
• Anti-fraud — detect rating manipulation by patterns (same IP, identical texts, abnormal frequency). Duplicate accounts caught by TIN and bank details.
• Typical mistake: storing supplier data in a regular infoblock — with 1000+ sellers, queries become slow. Use highload infoblocks.

How Is the Seller Payout System Structured?

The financial module is why sellers join the platform.

• Commission calculation — handler on order status change. Commission depends on category, seller status, current conditions. Stored in a separate table vendor_transactions.
• Periodic payouts — cron task generates a register: weekly, bi-monthly, or monthly. Minimum payout amount, holding until confirmation.
• Acts and reports — PDF generation via PhpOffice\PhpSpreadsheet, automatic numbering, one-click download.
• Holding — funds held until product received. Reduces disputes and returns.
• Payouts via banking API — YooKassa, CloudPayments, direct banking APIs. Seller receives money without calls or reminders.
• Important: splitting orders at the OnSaleOrderSaved handler leads to status mismatch. Split at the cart stage.
• Manual fiscalization of each sub-order violates 54-FZ. Use a single receipt with 'agent' attribute. On one project, fiscalization automation saved significant monthly costs. On another, search optimization via Elasticsearch reduced catalog loading time by 80% (from 3 seconds to 0.6 seconds).

How We Build Marketplace Architecture

1. Define business model — choose marketplace type and monetization scheme.
2. Database design — highload infoblocks for catalogs over 50,000 SKU, separate tables for sub-orders (orders_split) and transactions.
3. Core development — create module marketplace.vendor, implement product-to-supplier binding, order splitting mechanism, agents for commission calculation.
4. Payment gateway and 54-FZ integration — configure fiscalization via ATOL Online or CloudPayments.
5. Load testing — use k6 or ab to verify 5000 orders per day.

Typical Mistakes in Bitrix Marketplace Development

• Storing suppliers in a regular infoblock — causes slowdowns with >1000 records. Use highload infoblocks.
• Splitting orders after saving — breaks the status model. Split at the cart stage.
• Manual fiscalization of each sub-order — violates 54-FZ. Fiscalize with a single receipt with agent attribute.
• Ignoring tagged caching for the catalog — with multivendor, cache is invalidated entirely. Configure tags by vendor_id.

Technology Stack

• 1C-Bitrix 'Business' or 'Enterprise' — sale + catalog modules as foundation. Multivendor wrapper — custom modules.
• Highload infoblocks — catalogs over 100,000 SKU. Regular infoblocks at such volumes fail on filtering: CIBlockElement::GetList with a dozen properties generates JOINs on dozens of b_iblock_element_prop_sNN tables. Highload solves this with a flat structure.
• Elasticsearch — full-text search. Elasticsearch processes queries 10 times faster than the built-in search module (Sphinx). User types 'nike sneakers' — finds 'Nike sneakers'.
• Queues — catalog import, payout calculation, report generation. Bitrix agents (CAgent) for light tasks, separate queue via RabbitMQ or supervisor + custom CLI for heavy tasks.

We guarantee that the developed module will handle a load of up to 5000 orders per day on a standard VPS. Certified 1C-Bitrix specialists (over 10 years of experience, 50+ completed projects) perform architecture audit before development starts. At a scale of 2000 sellers, average moderation time is 15 minutes, and 95% of orders are processed automatically.

Industry Marketplaces

Each niche has its own pitfalls:

• Building materials — oversized delivery calculation. Pallets, tonnage, floor lift. Standard delivery calculator cannot handle it; we write custom sale.delivery.handler.
• Food products — expiration dates in infoblock properties, temperature regime, same-day delivery slots. A logistics error means write-off.
• Auto parts — VIN selection via Laximo API, cross-references, originals and analogs. A separate headache is different delivery times from different sellers for the same part.
• Clothing — size charts (EU/US/RU), high return rate. Return processing logic with commission redistribution is a whole layer.
• Industrial equipment — B2B with tenders, quotation requests. Product card with 50+ parameters in table form.

Timelines and Stages

Trying to launch everything at once is a sure way to launch nothing.

MVP in 3-4 months. Full-featured platform — 6-12 months of iterative development.

What Is Included

• Documentation: architecture diagram, API description, seller instructions.
• Access: code repository, test environment, admin panel.
• Training: two sessions for administrators and managers.
• Support: 1 month free support after launch, then according to SLA.
• Warranty on developed modules — 12 months.

Contact us for an assessment of your project — we will calculate timelines and cost individually. Request a consultation, and we will show on a real case how we solve the multivendor problem in 30 minutes. Get a detailed development plan for your marketplace today.