Ozon Integration: Selling Into Russia With Russian Content
Ozon integration for cross-border sellers: the Russian-language content requirement, FBO and FBS models, rouble pricing with a floor, and order flow into your ERP.
Ozon integration connects your seller account on Ozon, one of Russia's largest marketplaces, to your existing systems for content, pricing, inventory and orders. For a seller outside Russia, the most visible difference is language: titles, descriptions and product attributes must be in Russian. Add rouble-based pricing, two fulfilment models and customs paperwork, and Ozon is a channel that rewards structure. Integration provides it: Russian content goes out from the central catalog, prices live in a rouble column, and orders reach the ERP with their export documents.
Why Ozon draws attention
Russia has long been a market for textiles, home goods, footwear and cosmetics from nearby producing countries, and transit times from Turkey or Central Asia are shorter than to Western Europe. Ozon is strong across several categories and accepts sellers from abroad. Put those together and Ozon comes up often for businesses starting cross-border sales.
At the same time, payment, logistics and regulatory conditions in this market change more often than elsewhere. Which product groups are accepted, how you get paid and which logistics partner you use are things to verify against Ozon's current seller agreement and your own forwarder. This article covers the integration side; for commercial terms the marketplace itself is the only current source.
The Russian content requirement
Product cards on Ozon are created in Russian: title, description, attribute fields, size charts and any text inside images. Content in Cyrillic with the right terminology is what earns search visibility and buyer trust. You may be able to start with an English card, but conversion suffers.
This pushes you toward central content management rather than per-channel editing. The Russian version sits in its own field next to the master record; product attributes are mapped from your catalog fields to Ozon's category dictionary. Content Studio helps generate the Russian description and produce a size chart image with Russian labels. Even so, a native speaker should proofread; small machine-translation errors in textile terms turn into return reasons.
The quality tab lists products with an empty Russian field, a missing category attribute or an image problem. The approach is described in marketplace product content and quality score.
Fulfilment models: FBO and FBS
Ozon offers two basic models. Under FBO you send goods to Ozon's warehouse in advance; Ozon packs and delivers each order. Under FBS stock stays with you; when an order arrives you prepare it and hand it to Ozon's designated drop point or logistics partner. For cross-border sellers the flow usually resembles FBS: you dispatch from your own warehouse through Ozon's contracted logistics line.
For the integration, the difference is the source of stock. FBS products are fed from the shared pool, so a unit sold on Amazon or Trendyol is removed from Ozon as well. FBO stock sits at Ozon; the panel reads it separately and keeps it out of the pool. The ownership flag marks which product is on which model, so the panel writes to the stock you manage and leaves Ozon's alone.
Rouble pricing and exchange rates
Ozon prices are in roubles. In the price matrix, the Ozon column carries list, selling and floor prices in that currency. The floor protects cost, fee, logistics and return risk; when rates move, the panel recalculates its home-currency equivalent. When Ozon's promotion mechanics push your price down, the floor is what holds.
Currency volatility can be higher in this market than in others. Setting a price at a fixed rate and forgetting it ends in selling at a loss months later. Multi-currency and exchange rate management explains how we handle that balance. On the profitability page, Ozon stands next to your other channels with its own fee model, so you can see which products actually earn in Russia.
Order flow and paperwork
A confirmed Ozon order reaches the panel and is written to the ERP with customer, line items, carrier and payment details. Invoicing and shipping continue in your own process. Because the order crosses a border, export paperwork, the declared value and customs data are prepared at order time; the step-by-step version is in micro-export and ETGB order flow.
For FBS orders Ozon generates the label and shipping document in its own system; the panel attaches it to the order. Tracking is written back to Ozon. Cancellations and returns follow Ozon's own process; the panel reads the status, records the return in the returns portal and checks in the settlement screen whether the fee was refunded.
Handling time is decisive on Ozon. An order that misses its window can be cancelled and the seller score drops. The panel notifies the warehouse the moment an order lands; delay usually comes from an order not being seen, not from it being hard to prepare.
Seven things to settle before Ozon
- Confirm in the current seller terms that your product groups are accepted and which certificates are required.
- Set up a working routine for Russian content: who produces it and who proofreads.
- Make sure every product and variation has a clear SKU and barcode in your catalog; matching depends on it.
- Decide FBS or FBO, or which products go on which model, before you start.
- Calculate a rouble floor price for every product including fee, logistics and return risk.
- Learn your forwarder's transit time to Russia and the customs procedure.
- Run at least a week in shadow mode so the first orders appear in the report before write permission is switched on.
The general setup path is in integration setup in four steps.
How it works with Bulutegra
In Bulutegra, Ozon has its own tab in the Integration Panel alongside more than 24 marketplaces. Russian content goes out from multilingual catalog fields; the quality tab lists missing Russian fields. The price matrix holds rouble list, selling and floor prices for Ozon and recalculates the home-currency equivalent as rates change. The ownership flag separates FBO from FBS products. Orders are written automatically to Nebim V3, Logo, Mikro or SAP, with export paperwork ready at order time. Channel monitoring raises an alert and sends a phone notification if the Ozon connection goes quiet.
To add Ozon to your setup, request a quote; every supported marketplace is listed under Channels.
Frequently asked questions
Do I need Russian-language listings to sell on Ozon?
Yes. Titles, descriptions and attribute fields must be in Russian; Ozon buyers do not expect content in other languages. You do not need to speak Russian yourself, but the content has to be produced and checked in Russian. Multilingual catalog fields and Content Studio help, and a native proofread is worth the cost.
What do FBO and FBS mean on Ozon?
With FBO your goods sit in Ozon's warehouse and Ozon ships them; with FBS stock stays with you and you dispatch each order. Cross-border sellers mostly ship from their own warehouse. Confirm which models are open to you in Ozon's current seller terms.
Do Ozon orders flow into my ERP automatically?
They do. A confirmed Ozon order is written to Nebim V3, Logo, Mikro or SAP with the customer, line items, carrier and payment details, and export paperwork with the declared currency value and customs data is prepared at order time.


