1C Integration with Marketplaces

Marketplaces require fast and accurate data exchange: item master, stock, prices, orders, and returns must sync without manual spreadsheets. Each platform has its own seller API and its own model: Wildberries, Ozon, and Yandex Market describe product cards, order statuses, and FBO/FBS/DBS operating models differently. Product data often lives in one system, while warehouse-level prices and stock live in another, so before launch we define:

• single source of truth for products, prices, and stock: 1C, PIM, or multiple systems;
• the operating model on each marketplace (FBO, FBS, DBS) - stock and order exchanges depend on it;
• marketplace API limits and the required synchronization frequency for stock and prices;
• how marketplace sales and commission reports are reconciled with accounting in 1C;
• who is responsible for product cards, prices, and reservations when discrepancies arise.

We connect Wildberries, Ozon, Yandex Market, and other marketplaces through their seller APIs. For each flow, we define the data source, format, exchange frequency, and error handling.

• catalog and product cards: item master, attributes, and media from 1C or PIM;
• prices and stock by warehouse, including reservations;
• orders and statuses - from creation to shipment and delivery, with writeback to 1C;
• returns and non-redemptions with correct warehouse transactions;
• sales and commission reports for reconciliation with accounting;
• sales channel analytics.

Direct 1C-to-marketplace exchange works while there is only one channel. As the number of marketplaces grows, point-to-point integrations turn the architecture into a monolith: every marketplace API change requires changes to 1C. We move exchanges into a separate integration layer (ESB or message broker):

• one connector per entity - item master, prices, stock - instead of a separate exchange for each marketplace;
• marketplace format mappings live in the integration layer, not in 1C code;
• queues and buffering: 1C is not overloaded with requests, and data is not lost when the recipient is unavailable;
• monitoring and alerts for each flow: it is clear which marketplace did not receive stock;
• tools: WSO2, Kafka, RabbitMQ, n8n, Datareon, and others.

The team can connect new marketplaces faster, see up-to-date stock, and spend less time manually reconciling orders and reports. The approach has been proven across a network of 200+ 1C:Retail systems: one API per entity instead of hundreds of pairwise connectors.

• a new marketplace or sales channel is connected by copying a ready-made connector, without changing the 1C core;
• stock and prices on storefronts match 1C - fewer order cancellations due to outdated stock;
• reconciliation of sales and commission reports takes less time;
• exchange failures are visible in monitoring before customers notice them.