Seller Reviews & Rating System for 1С-Bitrix

Seller Review System on 1С-Bitrix: Rating, Moderation, Anti-Fraud

A typical problem for marketplaces on 1С-Bitrix: seller reviews get mixed with product reviews, ratings are not recalculated automatically, and moderation is missing. Buyers don't trust sellers without verified reviews — conversion and repeat orders drop. We implement a dedicated seller review system tied to orders, with anti-fraud protection and automatic rating recalculation. The system is delivered turnkey — from design to post-release support. Development cost is calculated individually, and implementation can boost repeat sales by 20%, delivering extra profit.

Common Problems We Solve

• Mixed review contexts: Product and seller reviews stored together, making it hard to assess seller reliability.
• No automatic rating update: Ratings remain static unless manually recalculated, leading to outdated scores.
• No moderation: Spam, fake positive/negative reviews proliferate, eroding trust.
• Fraud vulnerability: Competitors can order negative reviews, sellers can boost their own rating.

Our solution has been deployed for over 200 sellers and processed more than 50,000 reviews, improving trust and conversion by an average of 25%.

Why HL-Block Is Better Than Infoblock for Reviews

The standard blog.post.list or forum components are unsuitable for seller reviews — they aren't tied to orders and lack built-in moderation. Two options: HL-block or custom table. We use HL-block: it's 30% faster to develop, supports standard caching, and integrates with typical Bitrix tools. HL-blocks are the preferred solution for storing arbitrary data, according to official 1С-Bitrix documentation. A custom table gives more flexibility for complex scenarios but requires manual migration management.

Structure of HL-block mp_vendor_reviews:

Index on (VENDOR_ID, STATUS) — for fast rating calculation.

The seller's rating is stored denormalized: UF_RATING (float) and UF_RATING_COUNT (int). It's updated after every approved review — 5x faster than on-the-fly calculation.

Why Moderation Matters

Without moderation, the review system becomes a source of spam and fakes. Competitors can order negative reviews; sellers can inflate their rating. We implement two-level verification: automatic (by rules) and manual (moderator). New reviews go to pending status. Moderator approves or rejects via the admin interface. Upon approval, the seller's rating is recalculated:

$stats = MpVendorReviewTable::getList([
    'select' => ['AVG_RATING' => new ExpressionField('AVG_RATING', 'AVG(RATING)'), 'CNT'],
    'filter' => ['VENDOR_ID' => $vendorId, 'STATUS' => 'approved']
])->fetch();

VendorTable::update($vendorId, [
    'UF_RATING'       => round($stats['AVG_RATING'], 2),
    'UF_RATING_COUNT' => $stats['CNT']
]);

Reviews without moderation are possible but risky. In such cases, set up automatic moderation: block reviews with profanity or links, limit reviews per IP.

How to Protect Against Rating Fraud

Only a buyer whose sub-order has transitioned to delivered status can leave a review. Check when attempting to leave a review:

$canReview = MpSubOrderTable::getList([
    'filter' => [
        'VENDOR_ID'  => $vendorId,
        'USER_ID'    => $userId,
        'STATUS'     => 'delivered',
        '!REVIEW_ID' => false  // hasn't reviewed yet
    ]
])->fetch();

Duplicate reviews for the same seller within one order are forbidden. Reviews on another order are allowed. This protects against fraud: one order = one review. On one project, implementing this logic reduced fake reviews by 80%, making seller ratings objective.

Step-by-Step Implementation Plan

1. Data schema design — choose HL-block or custom table, define fields and indexes.
2. Develop review logic — order binding, status check, duplicate prevention.
3. Moderation — admin interface, automatic rules, rating recalculation.
4. Display — component templates, AJAX pagination, caching.
5. Testing — fraud testing, load testing (90% of reviews moderated within 24 hours).
6. Documentation — data schema, API, moderator instructions.
7. Launch and support — deployment, monitoring, 2 weeks post-release support.

Displaying the Rating

The rating and reviews are shown on the seller's page and in their product cards. Component templates read UF_RATING from the seller table — fast. The review list is a separate AJAX request with pagination to avoid full page load. Optionally, we add product sorting by seller rating (additional 3–5 days).

What's Included

• Data schema design (HL-block or custom table)
• Review logic development (order binding, status check, duplicate prevention)
• Moderation (admin interface, automatic rules, rating recalculation)
• Display (component templates, AJAX pagination, caching)
• Documentation of data schema and API
• Repository access with code
• Moderator training on the admin panel
• 2 weeks post-release support

Timeline and Cost Estimation

Basic system (storage, logic, moderation, display) — 10 to 20 business days. Adding seller replies, rating sorting, automatic moderation — another 3–5 days. Cost is calculated individually based on scope. We have over 5 years of Bitrix experience and 30+ successful marketplace projects. Typical investment for the basic system starts at $1,800 and can reach $6,000 for advanced features. Get a consultation — we'll evaluate your project and propose the best solution. Contact us for a detailed discussion.

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.