Bitrix24 Marketplace Integration: Orders, Statuses, Analytics

A manager spends up to two hours daily manually transferring orders from Ozon, Wildberries, and Yandex Market dashboards into CRM. Manual entry introduces up to 10% errors—lost orders, duplicates, incorrect totals. Our certified Bitrix24 developers have over six years of 1C-Bitrix development experience and have completed over 30 integrations that completely eliminate this gap. Our Bitrix24 marketplace integration service ensures efficient order synchronization. Orders automatically flow into Bitrix24 as deals, statuses sync bidirectionally, and analytics consolidate into unified reports. Processing an order through integration takes 3 minutes versus 1.5 hours—a 30x time saving. The custom solution pays for itself in 3–6 months. Integration pricing starts from $3,000 for a single marketplace, with an average payback within 4 months.

What data is synchronized between Bitrix24 and the marketplace?

Bitrix24 is a CRM and teamwork tool, not an e-commerce platform. The integration solves three tasks:

• Orders in CRM. Each order is created as a deal (crm.deal.add) or lead. The manager views it, processes it, calls the customer—all within CRM. Statuses sync bidirectionally via API (see Bitrix24 REST API documentation).
• Notifications. On new order or status change—notification via im.notify.system.add or a task/activity.
• Analytics. Sales data from marketplaces populates CRM reports. Channels can be compared and funnels built.

For customer communication (e.g., messaging with Ozon), we integrate messages into the deal activity stream.

Architecture: why a middleware service is critical?

Bitrix24 REST API and marketplace APIs have no direct connection. We design middleware—a separate application (PHP/Node.js/Python) with queue and retry logic for hundreds of orders per day. Workflow:

1. Webhook from marketplace (new order, status change).
2. Data transformation into Bitrix24 REST API format.
3. Create/update entities in CRM.
4. Reverse sync: on deal stage change—call marketplace API.

For simple scenarios, no-code connectors (n8n/Make) work, but they lack the flexibility of custom development.

Data mapping: deal vs order

Marketplace order fields do not match Bitrix24 deal fields. We configure full correspondence:

A separate task is status mapping. Marketplace statuses and pipeline stages are matched in a configuration file.

Contact deduplication handling

A buyer may order from different marketplaces and the website. When creating a contact in Bitrix24, we check for duplicates via crm.duplicate.find.by.comm (email/phone). If found, we attach the deal to that contact. When data is hidden (Wildberries does not provide email, Ozon—on request), we use an external buyer ID in a custom contact field.

Reverse status synchronization

When a manager changes a deal stage in CRM, it must reflect in the marketplace dashboard. We subscribe to the ONCRMDEALUPDATE event, check the source (UF_MARKETPLACE_SOURCE) upon STAGE_ID change, and call the marketplace API: for Wildberries—/api/v3/orders/{orderId}/status, for Ozon—/v3/posting/fbs/status/set. Not all statuses are externally modifiable—this is accounted for in the logic.

Product catalog synchronization

If products are maintained in crm.product or on a 1C-Bitrix website, automatic export to the marketplace is possible. This requires attribute mapping (SKU, sizes, prices) and is part of the extended scope of work.

Development timelines

What’s included

• Audit of current processes and requirements.
• Middleware architecture design.
• Data mapping and synchronization logic development.
• Webhook and Bitrix24 event configuration.
• Catalog integration (optional).
• Architecture and setup documentation.
• Testing and post-launch support.

Ready-made solutions vs custom development

The Bitrix24 Marketplace offers connector apps for Ozon and Wildberries. They cover basic scenarios at a low cost. Limitations: fixed logic, no mapping customization, dependency on vendor updates. Custom integration is justified when non-standard logic, 1C or warehouse integration is needed, or reliability requirements exceed average. Our solution handles over 100 orders per day with 99.9% uptime, processing one order via integration takes 30 times less time than manual entry. A custom connector reacts to status changes 3 times faster than standard modules. Payback: 3 to 6 months. Get a preliminary consultation—we'll help you choose the best solution. Contact us for a project assessment.

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.