1C-Bitrix Marketplace Integration Services

1C-Bitrix Integration with Marketplaces

A typical scenario: a manager manually updates inventory on Ozon while Wildberries simultaneously sells a product that's already out of stock. The customer places an order — and gets a cancellation. The seller's rating drops, the platform cuts visibility. Sound familiar? There's only one fix — programmatic Bitrix integration with marketplaces via API, where inventory, prices, and orders sync automatically from a single admin panel.

Why Connect to Marketplaces

Marketplaces mean ready-made traffic. Millions of buyers with a card in hand.

• Sales channels — traffic that a standalone online store can't generate. More than half of online purchases go through platforms.
• Savings on acquisition — the platform handles traffic. All you need is the right assortment and pricing.
• Unified management — products, inventory, and orders from all channels in Bitrix. No manual entry.
• End-to-end analytics — margin per channel. Decisions based on data, not intuition.

Which Marketplaces We Connect

Ozon — Seller API v3. Product card creation (/v3/product/import), price updates (/v1/product/import/prices), inventory (/v2/products/stocks), FBO/FBS orders (/v3/posting/fbs/list), returns. We configure automatic barcode and label generation via label/task.

Wildberries — Supplier API. Nomenclature upload with category-based attributes (/content/v2/cards/upload), barcodes, inventory sync across WB warehouses (/api/v3/stocks), order and shipment processing, media content. A common problem: inventory drifts between the website and WB, and a customer orders a product that doesn't exist. We solve this with synchronization every 15 minutes via a Bitrix agent.

Yandex.Market — Partner API. Catalog via feed or push model, prices, inventory, DBS/FBS/FBY orders (/campaigns/{campaignId}/orders), Yandex.Delivery integration.

SberMegaMarket — Merchant API. Products, offers, orders, status synchronization.

Others — AliExpress Russia, Avito, industry-specific platforms (Lamoda, Leroy Merlin).

Integration Mechanisms

Direct API integration — the most reliable approach. We develop a custom Bitrix module that directly calls marketplace endpoints. Full control: if a marketplace breaks backward compatibility (and WB does this regularly) — we update the module ourselves instead of waiting on a third party. Every request is logged in b_event_log, retries on 429/500 — automatic.

Aggregators — RetailCRM, MoySklad, ApiShip. They unify exchange with multiple platforms. Quick start, but a black box: when something breaks, debugging through someone else's layer is questionable at best. Suitable for limited budgets.

Feeds (YML/XML) — catalog export in Yandex.Market format (YML), Google Merchant (XML). Generation is configured via the catalog.export module or a custom handler using CIBlockXMLFile. A classic approach that works for basic integration.

Product Export and Synchronization

Export isn't just "press a button." Serious prep work lies behind it.

• Category mapping — matching Bitrix infoblock sections to the marketplace's category tree. Ozon has its own taxonomy (/v1/description-category/tree), WB has its own. Required attributes differ.
• Property mapping — infoblock properties (PROPERTY_*) → marketplace attributes. Unit and format conversion — automated via a mapping table in a highload infoblock.
• Card enrichment — rich content for Ozon, video reviews for WB, 360-degree photos. Platforms rank by completeness: the sales difference between a bare card and a polished one is 2x.
• Images — automatic generation at required resolutions via CFile::ResizeImageGet().

Synchronization runs on a schedule via CAgent::AddAgent() agents:

Order Processing

Orders from marketplaces land in b_sale_order automatically and are processed in a unified flow.

• Creation — the order arrives with all details. The module parses the API response, creates an order via \Bitrix\Sale\Order::create(), and links it to the payer type and the marketplace payment system.
• Unified flow — managers handle orders from all channels in a single interface. The order source is visible in the ORDER_PROP property.
• Status synchronization — picked, shipped, delivered — the status updates on the marketplace via callback. Handled by OnSaleStatusOrder.
• Returns — a cancellation on the marketplace creates a return in Bitrix. Inventory is restored automatically.
• Transfer to 1C — orders go to 1C:Enterprise via the standard CommerceML exchange. A single source of truth.

Monitoring

Multi-channel selling without monitoring is chaos with growing entropy.

• Inventory control — alerts on discrepancies between Bitrix, the marketplace, and 1C. Products with zero stock are blocked automatically — you can't sell what you don't have. Checked via cron every 10 minutes.
• Logging and retries — every API request is logged in b_event_log with request and response bodies. Failure? Auto-retry with exponential backoff. Critical error? Notification to the admin's Telegram bot.
• Pricing — automatic calculation factoring in marketplace commission, logistics, and target margin. Formula in module settings: price = base_price / (1 - commission) + logistics.
• Analytics — dashboard: revenue, orders, average order value, returns, margin — broken down by marketplace.

Integration Approach

1. Audit — we review the Bitrix catalog, infoblock structure, existing 1C exchanges. We assess data readiness. Sometimes, 80% of the work is getting product cards in order: filling in required properties, standardizing units of measurement.
2. Strategy — priority platforms, fulfillment model (FBO/FBS/DBS), integration depth.
3. Module development — mapping, validation, error handling. We cover critical scenarios with unit tests: order splitting, inventory recalculation on partial cancellation.
4. Testing — test product uploads, order emulation via marketplace sandbox APIs, edge cases (zero stock, product without photos, price below minimum).
5. Launch — we roll out integrations sequentially, monitoring the first exchanges in real time.
6. Maintenance — marketplaces regularly update their APIs (WB — without warning). We adapt promptly.

Timeline

Specific timelines depend on catalog size, number of platforms, mapping complexity, and the state of the 1C exchange. We provide a detailed estimate after the audit.