Configuring Seller Analytics on a 1C-Bitrix Marketplace

A seller on a 1C-Bitrix marketplace only sees aggregate numbers—total revenue and order count across the entire store. They need clear insight: which products bring profit or loss, at what prices they sell, earnings after platform commissions, and the return rate. Standard trade reports in /bitrix/admin/sale_reports.php do not differentiate sellers and lack per-product detail. We developed a dedicated analytics module right in the seller's personal cabinet, using the built-in tables mp_sub_orders and mp_finance_log. The module is built on D7 ORM and tagged caching, ensuring dashboard response times as low as 200 ms. We hold a 1C-Bitrix certificate and have years of integration experience—over 50 projects on this platform. Our analytics gives full control over revenue, commissions, and returns, enabling a net profit increase of 15–25%. Every day the system processes thousands of sub-orders, calculating key metrics in real time. Thanks to Bitrix agents, heavy aggregations are cached, while operational data is computed on the fly. The proposed marketplace reporting includes granular detail per seller and per product.

How to Gather Data for Seller Analytics

Analytics is built on data from several tables. Below are the sources and their purposes:

These datasets are joined by VENDOR_ID and period. To speed up queries, we use a documented indexing approach—a composite index (VENDOR_ID, CREATED_AT, STATUS). For integration with accounting systems, we use the CommerceML format, which automatically syncs products and orders without manual data entry.

Which Metrics Are Calculated

Revenue for the period — SUM(PRICE * QUANTITY) over the seller's sub-orders, grouped by day for a dynamics chart. Top products — GROUP BY PRODUCT_ID, ORDER BY SUM(QUANTITY) DESC, showing top 10 with revenue and sales count. Return rate — ratio of sub-orders with status refunded to total (typically 2-5%). Net profit — revenue minus commissions (from mp_finance_log) minus return costs. Conversion by status — percentage of successfully completed sub-orders, averaging 10-15%. A conversion funnel shows how many orders pass each stage from cart to payment. All metrics respect access rights: sellers see only their own data. Bitrix agents cache heavy aggregations once per hour.

A second table shows formulas and update frequency:

Why Query Performance Matters

Aggregating queries on tables with millions of records is a bottleneck. For date-range analytics, a composite index is essential:

CREATE INDEX idx_sub_orders_vendor_date
ON mp_sub_orders (VENDOR_ID, CREATED_AT, STATUS);

Heavy aggregations (yearly totals, all-products ranking) are moved to cache, refreshed via CAgent::AddAgent(). Operational data for the current day is computed on each request. Our approach is 2x faster than standard solutions due to tagged caching, reducing dashboard response time to 200 ms.

How to Build the Dashboard Step by Step

1. Create a component custom:analytics.dashboard based on Component 2.0, including JS (Chart.js) and CSS.
2. Set up an agent to cache aggregated data: CAgent::AddAgent('CAnalyticsAgent::AggregateSales();', 'analytics', 'N', 3600).
3. Design the dashboard: four cards (revenue, orders, average order value, returns), a revenue dynamics chart, and a top-10 products table.
4. Add AJAX loading for real-time data and an export button to XLSX via PhpSpreadsheet.

Dashboard Interface

The dashboard displays: revenue for the last 7 days, number of orders, average order value, rating—4–6 key figures prominently displayed. A line chart (Chart.js) for revenue dynamics and a top-10 products table. All data loads via AJAX. A period filter (yesterday/7d/30d/quarter/custom) and an export button are mandatory. Export is implemented via PhpSpreadsheet (XLSX) or CSV. Savings from implementation can reach up to 20% of turnover by discontinuing unprofitable products and optimizing prices.

What's Included in the Work

• Analytics module with seller personal cabinet
• Dashboard with 6 key figures, chart, and top-products table
• Period filter and export to Excel/CSV
• User manual and employee training
• 12-month warranty on the module

Timeline and Cost

Basic analytics (revenue, top products, order metrics) with charts — 1–2 weeks. Extended analytics with funnels, cohort analysis, and forecasts — 3–5 weeks. Cost is calculated individually, depending on integration complexity. Request implementation—we will assess your project within one day. Get a consultation for your scenario. For an accurate estimate, access to the store's data structure is needed.

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.