Setting Up Marketplace Seller Payouts on 1C-Bitrix

Payout problems for marketplace sellers are familiar to aggregator owners: manual transfers take hours, calculation errors lead to conflicts, and tax authorities require documentation. Our team of certified 1C-Bitrix specialists with over 5 years of experience configures marketplace seller payouts on 1C-Bitrix — including balance accounting, manual requests, and automatic transfers via API. Over this time, we have implemented systems for 30+ marketplaces: from electronics online stores to service aggregators. Average client savings: up to 2 million RUB per year through automation.

Manual payouts are 5 times slower than automatic ones, but they are essential at the start. Automation via Tinkoff or YooMoney saves up to 70% of manager time. Our engineers ensure correct integration and compliance with 152-FZ requirements. Contact us for a consultation — we'll discuss your project details.

How seller balance accounting works — configuring seller payouts

Balance is compiled from financial transactions recorded at each event:

• • upon confirming sub-order payment: amount = subtotal - commission
• — upon confirmed payout: amount = payout_amount
• — upon buyer refund: amount = -refund_amount + refund_commission

Table mp_finance_log:

Current balance = SUM(AMOUNT) WHERE VENDOR_ID = X AND STATUS = 'confirmed'.

Source: 1C-Bitrix documentation — financial accounting

Why manual payouts are inefficient

Manual payouts take up to 10 minutes per operation: check request, verify balance, execute transfer via bank client. With 50 payouts per day, that's almost a full workday. Errors in entering details are a common cause of delays and reputational risks. For a large marketplace with 5000+ monthly transactions, automation savings exceed 1 million RUB — confirmed by our experience.

Comparison of approaches:

Automatic payouts are 10 times faster and virtually eliminate errors.

Manual payouts: step-by-step process

The seller clicks "Request payout" in the personal account, specifying an amount (not exceeding available balance). A record is created in mp_payout_requests with status pending. The manager sees the request in the admin panel and, after actually transferring funds, confirms it — the status changes to completed, and the balance decreases.

Minimum payout threshold and frequency (e.g., no more than once a week) are configured in b_option via the admin panel.

How to set up automatic payouts via API

Step-by-step automation plan

1. Select a payment gateway. Suitable options: Tinkoff, YooMoney, CloudPayments, QIWI B2B. Each has its own security and speed requirements.
2. Encrypt payment details. Store seller payment data in a separate table with AES-256 (152-FZ requirement).
3. Develop a payout agent. Write a Bitrix agent that runs on a schedule (e.g., every Friday at 10:00). The agent collects requests with status pending, sends a request to the gateway API, and upon success changes status to completed and debits the balance.
4. Logging and notifications. Record each payout in the financial log, send notifications to the seller and manager.
5. Generate documents. Upon payout completion, generate a PDF service acceptance certificate (via tcpdf) and attach it to the operation.

Typical automation mistakes

• Ignoring payment gateway limits (e.g., maximum transfer amount or daily limit).
• Lack of API error handling: on failure, the payout may hang in status pending and the balance won't decrease. Implement callback notifications.
• Complexity with refunds: on order cancellation, correctly restore the seller's balance and cancel the payout if not yet executed.

Why tax documents matter

During payouts, the platform must generate service acceptance certificates (for commission) and sales reports. PDF generation via tcpdf or template is standard. Documents are attached to the payout and available for download by the seller and admin. This is an FTS and 54-FZ requirement.

What's included in the work

• Designing the financial transaction scheme (infoblocks, HL-blocks)
• Developing the balance accounting and request module
• Integrating with a payment gateway (Tinkoff, YooMoney, CloudPayments, QIWI B2B)
• Generating PDF documents
• Testing and documentation
• Training managers and sellers

Timeline

• Balance accounting and manual payouts: 1–2 weeks
• Automatic payouts via API: +1–2 weeks
• Financial document generation: 3–5 days

Final timeline depends on integration complexity and catalog volume. We'll assess your project in one day — contact us for a consultation.

Get a ready-made module with documentation and support. Order payout configuration — and your sellers will receive money on time.

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.