Multi-Vendor Marketplace Architecture on 1C-Bitrix

Multi-Vendor Marketplace Architecture on 1C-Bitrix

A typical multi-vendor marketplace on Bitrix faces duplicate products (up to 15% duplicates), order confusion with three or more sellers, and manual commission calculations that waste up to 20 hours per week. Our solution isolates vendor data at the information block level and automates payouts, cutting administration time by three times. On one project, we handle 50,000 products from 200 vendors — the system processes 1,000 orders per day without lags. Order a preliminary assessment of your project — we will analyze the complexity and propose the optimal path.

How to Isolate Vendor Data?

The most practical approach is to add a vendor ID at the catalog information block level. The vendor registers as a Bitrix user in the “Vendors” group; their USER_ID serves as VENDOR_ID. The main catalog information block is extended with a UF field UF_VENDOR_ID (link to b_user.ID). All catalog components add a filter by UF_VENDOR_ID during selection. In the vendor’s personal account, only elements with their UF_VENDOR_ID appear.

An alternative for large marketplaces: a HighLoad information block as an intermediate layer that stores the PRODUCT_ID → VENDOR_ID mapping and is used for quick permission checks.

Vendor table (via HL information block or custom):

How to Split Orders Between Vendors?

A customer adds products from three vendors to the cart. In Bitrix, this is one order in b_sale_order. We use sub-orders as child records: an additional table mp_sub_orders is created with fields ORDER_ID, VENDOR_ID, STATUS, TOTAL, COMMISSION. Upon order creation, the OnAfterOrderAdd handler automatically creates sub-orders by grouping cart items by the products’ UF_VENDOR_ID. The vendor sees only their sub-orders.

Our sub-order solution handles 1,000 orders per day without delays, while the typical event-based approach starts lagging at 200 orders. An alternative is to store VENDOR_ID in b_sale_basket as a custom property and manage statuses at the item level. This approach is simpler but complicates payout aggregation. For most projects, sub-orders are optimal.

Vendor Personal Account

Minimum vendor account components:

• Product management: add/edit/deactivate with forced UF_VENDOR_ID = current user
• Sub-order management: list, status change, invoice printing
• Stock and price management: bulk update via CSV or AJAX
• Analytics: sales by period, top products, returns based on sub-orders
• Profile and payment details: documents, payment info, verification status
• Finance: accrued commissions, payout history, balance

Permissions: user in the “Vendors” group plus UF_VENDOR_ID check on every request.

Commission System

Commissions are calculated at sub-order creation or when it reaches a final status. Logic:

// Simplified pseudocode
$commissionRate = $vendor['UF_COMMISSION_RATE']
    ?? $categoryRate[$product['IBLOCK_SECTION_ID']]
    ?? $defaultRate;

$commission = $subOrder['TOTAL'] * $commissionRate / 100;

// Save to financial operations table
MpFinanceTable::add([
    'VENDOR_ID' => $vendor['ID'],
    'ORDER_ID'  => $orderId,
    'TYPE'      => 'commission',
    'AMOUNT'    => -$commission,
    'STATUS'    => 'pending',
]);

Commission can vary: flat rate, by product category, individual vendor rate, progressive (based on turnover). Clients save up to 500,000 rubles per year on manual payouts.

Product Moderation

Vendor products undergo moderation before publication. Technically, this is a status of the information block element: when a vendor adds a product, ACTIVE = N and a special status UF_MODERATION_STATUS = 'pending' are set. The moderator (user in the “Moderators” group) sees the moderation queue, reviews, sets ACTIVE = Y or rejects with a comment. Vendor notification via CEvent::Send() or built-in Bitrix notifications.

What’s Included in Development: Delivery and Documentation

Each project includes:

• Project documentation: ER diagram, commission logic description, access rights scheme.
• Access to code repository (Git).
• Operation manual for admin and vendors.
• Team training (up to 2 hours via webinar).
• 2 weeks of free support after launch.
• 6-month code warranty.

How We Develop a Multi-Vendor Marketplace: Step by Step

1. Analysis and architecture – design ER diagram, access rights scheme.
2. Vendor registration – configure profiles, payment details, tax ID verification.
3. Product and order isolation – implement UF_VENDOR_ID and sub-orders.
4. Vendor personal account – develop module for product, order, and analytics management.
5. Financial module – automatic commission calculation, payouts via bank API.
6. Moderation and analytics – moderation queue, admin reports.
7. Testing and launch – load testing, team training, 2 weeks of support.

Development Timeline

Timelines are for development from scratch. Using a ready multi-vendor module as a base reduces customization to 10-16 weeks.

Benefits of Working with Us

Our experience in Bitrix development spans over 5 years; we have completed 30+ projects. Certified 1C-Bitrix specialists ensure a 6-month code warranty. Contact us for a consultation — we will evaluate your project in one day and provide a solution.

What Problems Does the Multi-Vendor Architecture Solve?

We eliminate typical pain points: product duplicates, order confusion, manual commission calculation, slow moderation. Our clients save up to 30% of time on marketplace administration. Get an engineer consultation — discuss your case.

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.