Publishing an Application in the Bitrix24 Marketplace

You have developed an application for Bitrix24, but the process of publishing in the marketplace turned out to be more complex than the code. Partner registration, card design, technical moderation—each stage can take weeks. Our experience shows that without preparation, the first attempt rarely passes on the first try. We have helped dozens of projects get through moderation—from simple integrations to complex subscription services. For example, a task management app integrating Bitrix24 and Trello passed moderation only on the third attempt due to incorrect OAuth token handling. We fixed the logic and got approval within two weeks.

Publishing in the Bitrix24 marketplace is a separate project because moderation requirements are constantly changing. Recently, OAuth scope checks have been tightened: extra permissions mean automatic rejection. Handling 429 Too Many Requests is a typical reason for rejection. We have systematized common errors and use a 50+ point checklist. As a result, the average time to pass moderation is reduced by 3 weeks, and budget savings from avoiding rework reach up to 100,000 rubles. A typical integration project costs between 100,000 and 200,000 rubles, so these savings are significant.

Our Approach and Key Solutions

We address compliance with moderation requirements, design a card that sells, and set up billing and subscriptions. Specifically:

• Compliance: We check security, correct API operation, and UX. We remove unnecessary scopes, configure error handling, and ensure Russian language support.
• Card design: We prepare screenshots (1280×800 PNG), an icon (128×128 with transparency), a short description up to 160 characters, and a full description with formatting. We avoid typical mistakes like test data on screenshots or using the Bitrix24 logo without permission.
• Billing: For paid applications, we connect the 1C-Bitrix system. For subscriptions, we implement onAppPaymentAdd and onAppPaymentDelete event handling.

We use PHP 8.2+, Bitrix24 REST API, and custom components. Example: a logistics app integrating CDEK. The main challenge was correctly handling subscription cancellation via the onAppPaymentDelete event. We implemented automatic feature deactivation without deleting user data, and the app passed moderation on the first try. Another example: a customer support chatbot rejected due to missing CSRF protection. After adding tokens and verifying the request source, moderation was successful.

Preparation and Process

Before submission, ensure your app meets basic requirements. Use the official REST API Bitrix24 documentation. Verify that all API requests handle errors 401 (re-auth) and 429 (backoff with exponential delay). Make sure there are no placeholder screenshots and the icon does not violate trademarks. We include two moderation iterations in our service, covering 90% of cases.

Our work process:

1. Analysis – study your app's API and check scopes.
2. Card preparation – write descriptions and prepare media.
3. Technical preparation – configure HTTPS, error handling, and sandbox.
4. Submission for moderation – go through all stages.
5. Rework based on feedback – up to two iterations if needed.
6. Publication and monitoring.

Estimated timelines: 2 to 6 weeks depending on complexity and number of iterations. On average, our clients get approved 3 weeks faster than typical due to our preliminary audit.

What's Included in Our Service

• Compliance checklist (over 50 items)
• Card design: title, description, screenshots, icon
• OAuth/scope configuration and event handlers
• Testing on a sandbox portal
• Moderation submission and up to two rounds of rework
• Monetization consultation (model selection, billing setup)
• One month post-publication support

Moderation and Handling Rejection

The moderator tests the app in a test environment, checking security (no access_token in GET, CSRF protection, XSS prevention), correct API operation (handling 401 and 429), and UX (meaningful loading states, errors shown on screen, mobile functionality). Apps that do not handle 429 are rejected in 80% of cases, while those with correct backoff get approved on the first try. Rework costs can reach 30,000–50,000 rubles per iteration.

If rejected, analyze the reason: scopes, description mismatch, or technical errors. Usually, fixing the issues and resubmitting suffices. Our service includes two moderation iterations.

Monetization Models

Common Mistakes in Moderation

Why Choose Us

We have over 5 years of Bitrix24 experience and more than 30 integrations and applications. Our solutions get approved without rejection, with an average publication time of 3 weeks. We rely on the OAuth standard and the official Bitrix24 REST API guide. If you want to speed up the process and avoid typical mistakes, contact us for an audit and preparation. Get a consultation right now to assess your solution's readiness.

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.