1C marketplace integration: Ozon, Wildberries, Yandex Market

Two-way exchange between your 1C and Ozon, Wildberries, Yandex Market, and Megamarket: orders, stock, prices, statuses, and returns flow through an integration layer, not a boxed solution built for one configuration.

Discuss the 1C ↔ marketplace data exchange setup

Our clients

Capital Group
FSK Group
SMLT
Tochno
Dogma
Sber City
FM Logistic
Danone
Relief Center
Pandora
1C Marketplace Integration — Orders, Inventory, Pricing
Saint-Gobain
Askona
FIX PRICE
Snezhnaia Koroleva
Muztorg
TVOE
Greenway
Polaris
Campari
Yandex
Lenta
International perfume and cosmetics brand
1C Marketplace Integration — Orders, Inventory, Pricing
RAEC
EKF
L'Etoile
Inventive Retail Group

1C marketplace integration is automated two-way data exchange between your 1C system (UT, ERP, UNF, 1C:Retail) and Ozon, Wildberries, Yandex Market, and Megamarket: orders arrive in 1C as a Customer Order with the To Fulfill status, stock and prices are sent to the marketplaces on schedule (for FBS, via a scheduled job, estimated by integrators at every 5-10 minutes), item master data is matched to product cards, and statuses and returns are synchronized without manual exports.

KT.Team builds this as an integration layer between 1C and all marketplaces, not as a boxed module for one configuration: 13 years of enterprise integration, an ESB bus with queuing and monitoring, a single product card for all channels - a new marketplace can be connected without reworking accounting.

8.59 trillion RUBWildberries, Ozon, and Yandex Market sales in 2025, up 32.2% year over year - Data Insight
≈ 80%of online orders in CIS go through marketplaces - Data Insight / sostav
10 days -> 1 daylaunching new collections on marketplaces - Relief-Center case
200+ 1C:Retaila single API instead of point-to-point integrations - retailer case

Exchange flow: 1C, integration layer, and marketplaces

How data moves between 1C and marketplaces

Accounting system

1C: Trade Management · ERP · SMB Accounting · Retailorders, stock, prices, item master
WMS / PIMorder assembly and product card

Integration layer (ESB)

Queue · mapping · monitoringdelivery guarantee, Dead Letter Queue, unified log

Marketplaces

Ozon · Wildberries · Yandex Market · MegamarketFBS · FBO · DBS workflows

Synchronization monitor: 1C and marketplaces

1C Marketplace Integration — Orders, Inventory, PricingProduct screen: platform statuses for Ozon, Wildberries, Yandex Market, and Megamarket at the top, with the last sync time and FBS, FBO, DBS workflows. In the center, 1C and marketplaces exchange data through an ESB integration layer: stock, prices, and product cards go to the marketplaces, while orders, statuses, and returns come back. Below are the message queue states processing, delivered, retry, and Dead Letter Queue, an item master mapping table, and an order status funnel. All values are illustrative placeholders.Synchronization monitor: 1C ↔ marketplacesExchange structure and statuses - values are illustrativeOzonWildberriesYandex MarketMegamarketFBS · FBO · DBSFBS · FBO · DBSFBS · FBO · DBSFBS · FBO · DBSonlineonlinedelayonlinesync: 00:00sync: 00:00sync: 00:00sync: 00:005-10 min schedule5-10 min schedule5-10 min schedule5-10 min schedule1CTrade Management · ERP · UNF1C:RetailIntegration layer(ESB)queue · mapping · monitoringMarketplacesOzon · WB · YM · MMstock · prices · product cards →→ to marketplaces← orders← statuses · returnsESB message queueprocessingdeliveredretryDead Letter Queue————manual reviewItem master mapping1C SKUmarketplace product cardbarcodeunit / packstatusSKU-0000—4600000000000pc / box x10matchedSKU-0000——pcnot foundOrder statusesnewto assemblyassembled (scanner scan)shippeddeliveredreturntracking number (DBS / realFBS) -> to the marketplaceAvailable stock = on hand - reserved - reserved by other channels
Exchange monitor diagram between 1C and marketplaces: platform statuses, data flows, message queue, and item master mapping. Values are illustrative.

What we synchronize between 1C and marketplaces

Orders

An order from the marketplace is created in 1C as a Customer Order: picking by handheld scanner scan (WMS on 1C) -> the "Packed" status is sent to the marketplace -> label printing -> tracking number for DBS/realFBS.

Stock

Available stock = on hand - reserved - reserved by other channels. For FBS, stock is pushed to marketplaces by a scheduled job; there is an option to zero it out on a schedule.

Prices and promotions

Base and promotional prices are sent to marketplaces from 1C - without manual edits in each personal account.

Item master and product cards

Product cards are generated from 1C by mapping SKUs, barcodes, units, and packaging to each marketplace's requirements.

Statuses

Order and processing statuses are synchronized both ways: 1C and the marketplace always see the same state.

Returns

Returns from marketplaces come into 1C; for FBO, the marketplace is responsible for storefront stock, while ERP handles supply planning and assembly.

Map out your integration landscape

clients@kt.team Telegram @kt_team_it

How we configure the integration

  1. 01

    Scope audit

    We look at which 1C systems (UT/ERP/UNF/Retail), which marketplaces, which FBS/FBO/DBS schemes and volumes, and where boxed integration is no longer enough.

  2. 02

    Item master mapping

    We match SKUs, barcodes, reference data, and units of measure against marketplace requirements at the master-data level, not manually for each item.

  3. 03

    Pilot on one marketplace

    We launch the exchange on one marketplace or a group of SKUs, then verify orders, stock, and prices on live data.

  4. 04

    Connect the remaining flows

    We add marketplaces, prices, statuses, and returns through the same layer - without reworking accounting.

  5. 05

    Monitoring and support

    Logs, alerts, and adaptation to marketplace API changes: the exchange runs as a service, not a one-time setup.

Boxed module or integration layer

Cases

Case studies: high-volume 1C and marketplace exchange

All cases

FAQ

FAQ on integrating 1C with marketplaces

How do you set up 1C integration with marketplaces?

Scope audit (which 1C configurations - Trade Management, ERP, SMB Accounting, 1C:Retail, which marketplaces, FBS/FBO/DBS schemes, volumes) -> mapping of item master and reference data -> pilot on one marketplace -> connect the remaining flows -> monitoring and support. Exchange runs through marketplace APIs via an integration layer; for FBS, stock is sent by a scheduled job, according to integrators' estimates, every 5-10 minutes.

What are the implementation timelines for 1C marketplace integration?

It depends on the number of marketplaces and the state of data in 1C. We can launch a pilot on one marketplace or a group of SKUs quickly; for comparison, in the Relief-Center case, we launched a PIM-to-marketplace publishing service in 2.5 months. We set the exact timeline after the scope audit.

What exactly is synchronized between 1C and the marketplace?

Orders arrive in 1C as a Customer Order, stock is sent to marketplaces (real-time for FBS), prices and promotions go to marketplaces, item master and listings go through mapping, statuses are synchronized both ways, and returns come into 1C. Free stock is calculated as on hand minus reserved minus stock reserved by other channels.

Boxed module or custom integration - which should you choose?

Boxed solutions are one-sided: some work only with one marketplace, such as Ozon, while for Wildberries they often support only item mapping and stock export, without order automation (vendor estimate). According to integrators, marketplace APIs change every 3-4 months and break unsupported connectors. Multi-marketplace support, Wildberries orders, and resilience to API changes are provided by a supported integration layer, and a detailed breakdown of how to launch the exchange is in the blog. how to connect 1C with Wildberries, Ozon, and Yandex Market.

Do you support Ozon, Wildberries, Yandex Market, Megamarket, and any 1C system?

Yes. The layer is not tied to one 1C configuration or one marketplace: we build exchanges for Trade Management, ERP, SMB Accounting, and 1C:Retail with all major marketplaces and FBS, FBO, and DBS schemes through 1C integration via ESB. A new marketplace can be connected without reworking accounting.

How much does 1C integration with marketplaces cost?

We work on a fixed price for the agreed result, not by the hour: a guideline for a typical process is from 300,000 RUB over 1-2 weeks. We assess a multi-marketplace integration setup after an audit. More about the model - in the section pricing fundamentals.

Pricing and kickoff

How much does 1C integration with marketplaces cost

We work on a fixed price for the agreed result, not by the hour: a guideline for a typical process is from 300,000 RUB over 1-2 weeks. We assess a multi-marketplace integration setup after reviewing the environment. More about the model - pricing fundamentals.

  • Fixed price for results
  • Typical project - from 300,000 RUB
  • Timeline: 1-2 weeks
  • Kontur - after the audit
Discuss the 1C ↔ marketplace data exchange setup

Related KT.Team solutions

- 1C Marketplace Integration - solution overview: a node in the 1C hub when you need a high-level overview, not a transactional exchange launch. - Marketplace integration from the catalog and PIM side: listing publication and content, not 1C accounting data exchange. - PIM implementation: management of product listing content and master data. - 1C integration via ESB: OData and HTTP services: how 1C connects

to the integration layer. - 1C:Retail synchronization with marketplaces through the bus: an industry tool for retail. - PIM for marketplaces: a breakdown of listing content for marketplaces.

Discuss: 1C integration with marketplaces: Ozon, ...

Send via:

By clicking the button, you accept the offer and grant consent to the processing of personal data.

Related solutions

All solutions
1C Integration with Chestny Znak and TS PIoT1C and Diadoc integration — electronic document exchange1C integration with SBIS: EDI and regulated reporting1C integration with Takskom for reporting

Articles on the topic

All articles

Related videos

All videos
4:40 The Diadoc Module for 1C | Making Document Work Easier 4:46 Chestny Znak and 1C integration | Automatic product labeling 4:19 Cloud Native ESB / Flexibility and Speed for Your Business

News on the topic

All news