An operator spends 2–3 hours daily manually transferring orders from Ozon Belarus to 1C-Bitrix. Prices become obsolete, Ozon blocks product cards. Stocks diverge, and customers complain about cancellations. Sound familiar? We automate the exchange of products, orders, and stocks between your 1C-Bitrix store and Ozon Belarus. This automation can save you up to 20 hours per month, reducing operational costs by $500–$1,200 monthly. With over 8 years of experience and 50+ completed integration projects, we know the platform inside out. Ozon is actively expanding in Belarus: a dedicated seller section, warehouses in Minsk, and FBS/FBO schemes. Technically, the integration uses the Ozon Seller API—the same as in Russia but with Belarusian specifics for document flow and logistics. Typical investment for full integration ranges from $2,000 to $5,000, depending on catalog size and complexity. We analyze your catalog and propose a solution within 1–2 days. Get a consultation—contact us.
How Does the Ozon Seller API Work?
Ozon provides a REST API at https://api-seller.ozon.ru/. Authentication uses the headers Client-Id: {id} and Api-Key: {key}, both obtained from the seller's dashboard. Key methods:
-
POST /v2/product/import— product upload (asynchronous, via queue) -
POST /v1/product/import/prices— price update -
POST /v2/products/stocks— stock update (FBS) -
POST /v3/posting/fbs/list— list FBS orders -
POST /v4/posting/fbs/ship— confirm shipment
Product upload is asynchronous: send an array of products, receive a task_id, then poll GET /v1/product/import/info?task_id={id} until completion. Typical processing time is 5–15 minutes. We ensure correct error handling and retries on failures.
The Ozon Seller API allows full automation of assortment and order management — Ozon documentation.
Why Is Attribute Mapping Critical?
Ozon has its own category tree and mandatory attributes for each. Retrieve attributes via POST /v3/category/attribute. For the "Smartphones" category, there are 30+ attributes: brand, color, storage capacity, OS—some mandatory. Values come from Ozon reference books: you cannot write "red"—you need a value ID. Get IDs via POST /v2/category/attribute/values. Mapping: a Bitrix infoblock property (e.g., PROP_COLOR = "Red") → Ozon attribute ID (attribute_id: 10096) → value ID (value_id: 61587). We maintain this table as a separate entity in Bitrix—it changes when new categories are added. Without correct mapping, the product may be blocked.
FBS: Managing Stocks and Orders
Under FBS (fulfillment by seller), the key cycle is:
- Update stocks in Ozon from Bitrix—every 15–30 minutes.
- Retrieve new orders from Ozon—poll
POST /v3/posting/fbs/listwith filterstatus: awaiting_packaging. - Create an order in Bitrix, reserve product.
- Pick and pack, generate a label (method
POST /v2/posting/fbs/package-label). - Transfer the shipment acknowledgment to Ozon.
Ozon labels are PDFs with 2D barcodes. We print them on a label printer (Zebra, TSC) or a regular A4 printer. We automate this process so you don't waste time on manual printing.
How to Avoid Oversell and Stock Discrepancies?
If the integration updates stocks less frequently than orders arrive, oversell can occur—selling an item that is out of stock. For high-turnover products, we reduce the displayed stock on Ozon by 10–20% as a buffer or increase sync frequency to 5–10 minutes. We also configure automatic reservation in Bitrix when an order is received from Ozon. This reduces discrepancy risk to under 1%.
Specifics for Belarusian Sellers
Belarusian sellers ship to Ozon warehouses in Belarus (Minsk) or directly to pickup points. Logistics is simpler and faster than shipping to Moscow. Document flow: Ozon requires an electronic transfer acceptance certificate upon shipment. For Belarusian legal entities, this is the TN-2 waybill. We generate this document in Bitrix or an integrated accounting system.
Returns are handled automatically: Ozon creates returns (refund or cancelled postings). The integration tracks events via POST /v3/returns/company/fbs, creates a return document in Bitrix, and restores stock. We guarantee that no return is lost.
What's Included in the Integration Work?
| Stage | Scope | Documentation |
|---|---|---|
| Analysis | Audit of catalog, 1C-Bitrix, workflows | Technical specification |
| Design | Attribute mapping, category matching, Ozon API configuration | Data exchange schema |
| Implementation | Module development, synchronization, product card upload | Operation manual |
| Testing | Verification of all scenarios (stocks, orders, returns) | Test report |
| Launch | Go-live, operator training | — |
We additionally provide:
- Access to configured systems.
- Training for your staff on using the integration.
- 30-day warranty support after launch.
- Possibility of expansion (adding new categories, schemes).
Typical Problems and Solutions
Product blocked by Ozon. Common cause: attribute mismatch with category requirements. Check status via POST /v2/product/info (field status.state_failed), read status.validation_errors, and correct attributes. We include automatic blockage notifications.
Stock discrepancies. Solved by buffer (10–20%) or increasing sync frequency. For accuracy, we use tagged caching in Bitrix—order data updates faster.
Timeline Estimates
| Scenario | Time |
|---|---|
| FBS: stocks + orders (without product card upload) | 3–5 weeks |
| + product card upload, attribute mapping (1–3 categories) | 2–4 weeks extra |
| Full integration with returns and documents | 2–4 months |
Cost is calculated individually after auditing your catalog and workflow (FBS/FBO). Typical investment starts from $2,000. Get a consultation—contact us for an assessment of your project.