Installing and Configuring 1C-Bitrix Marketplace Modules

You bought a module from the 1C-Bitrix marketplace, clicked "Install", but instead of a working integration, you got an error 500 or a blank screen. This is a standard scenario we encounter daily. Free modules often contain outdated dependencies or undocumented bugs. Paid ones require configuration of API keys, webhooks, and field mapping according to the vendor's documentation. Installing Bitrix modules from the marketplace without development experience leads to 2 to 8 hours of wasted time just to find the causes of malfunction. And if the module touches the core, the consequences of an error may require restoration from a backup.

We have configured over 50 commercial modules—from simple SEO widgets to complex CRM connectors with two-way synchronization. Self-configuration takes twice as much time as our work and results in 60% more errors. In this article, we'll break down typical pitfalls and show how we set up modules from scratch to production.

Why Modules Fail After Installation?

According to our data, 60% of post-installation problems are related to PHP version incompatibility. The module is written for PHP 8.1, but your hosting uses 7.4—this gives a syntax error. Check via phpinfo() or /bitrix/admin/sysinfo.php. Another common cause is event handler conflicts. Two modules register on the same event in the b_module_to_module table, and the wrong handler is called. Or the module cannot create its tables due to missing MySQL permissions for CREATE and ALTER. Sometimes the module fails because of an incorrect composer.json—dependencies are not installed, classes are not autoloaded. Solution: run composer install in the module's folder. There can also be a problem with tagged caching: the module does not invalidate the cache, so users see old data. Bitrix API configuration requires correct webhook addresses, otherwise the module cannot exchange data with external services.

How to Set Up a Payment Module: Example with YooKassa

Let's consider setting up a payment module through YooKassa. After installation via the admin panel (Marketplace → Installed Solutions), we:

1. Register a webhook in the YooKassa account to the module's URL (usually /bitrix/tools/sale_ps_result.php).
2. Enter shopId and secretKey in the module settings: COption::SetOptionString('yukassa', 'shop_id', ...).
3. Switch to test mode to verify sandbox transactions.
4. Create a test order, make a payment, check the callback status success/fail/cancel.
5. In production mode, change the secret key and disable the test flag.

Complex shipping modules (CDEK, Russian Post) require additional configuration: pickup point mapping tables, tariffs, dimension settings. We always check the cost calculation for different cities and weights. Configuring a module through vendor support takes on average twice as long as our work—due to queues and lack of understanding of your site's architecture. We perform up to 80% of the work remotely, without downtime of your site.

// Example of registering an event handler
RegisterModuleDependences("sale", "OnSalePayOrder", "vendor.module", "\Vendor\Module\Event", "onPayOrder");

Why Trust Professionals with Setup?

Our team has extensive experience with Bitrix and Bitrix24. We have installed and configured over 50 modules with external integrations. We work with CommerceML and REST API. We guarantee that after setup, the module will not break existing functionality—we use tagged caching and write unit tests. Time savings on debugging—up to 8 hours per module. According to Bitrix documentation, the module must be registered in the b_module table. We monitor this and check record integrity.

What's Included in the Work

• Checking compatibility with your Bitrix and PHP versions.
• Installation via admin panel or manually (if no access).
• Configuration of all parameters: API keys, webhooks, mapping.
• Testing all scenarios (success/error/cancel) in sandbox.
• Resolving potential conflicts with other modules.
• Brief documentation on settings for your team.
• Support after launch—2 weeks guarantee for correct integration operation.

How to Avoid Typical Integration Mistakes?

Prepare in advance the credentials for external services (API keys, OAuth tokens). Ensure access to the Bitrix admin panel with administrator rights. Check the current PHP and Bitrix versions via /bitrix/admin/sysinfo.php. If the module uses events or agents, verify that they do not conflict with already installed solutions. Our testing includes checking all possible statuses and callback requests to avoid production failures.

Comparison of Self-Setup vs Professional Setup

Module Complexity Comparison

Contact us for a consultation on your module. Order setup—and we'll launch on the day of request. We'll respond within an hour and propose a solution.

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.