1C-Bitrix Integration with Ozon Belarus

1C-Bitrix Integration with Ozon Belarus

Ozon actively works with Belarusian sellers: there is a dedicated section for Belarusian sole traders and legal entities at seller.ozon.ru, with support for both FBS (fulfilment by seller) and FBO (fulfilment by Ozon) schemes. For a store built on 1C-Bitrix, integration with Ozon is technically identical to the Russian setup, but differs operationally in terms of logistics points and document flow.

Ozon Seller API: Structure

Ozon provides a REST API at https://api-seller.ozon.ru/. Authentication uses the headers Client-Id: {id} and Api-Key: {key}. Both values are obtained from the seller dashboard.

Core endpoints for integration:

• POST /v2/product/import — upload products (asynchronous, via queue)
• POST /v1/product/import/prices — update prices
• POST /v2/products/stocks — update stock levels (FBS)
• POST /v3/posting/fbs/list — FBS order list
• POST /v4/posting/fbs/ship — confirm shipment

Product uploads to Ozon are asynchronous: we submit a request with an array of products, receive a task_id, then poll GET /v1/product/import/info?task_id={id} until completion. Typical processing time: 5–15 minutes.

Product Attributes: Mapping to Ozon Categories

Ozon has its own category tree and mandatory attributes for each category. We retrieve the attribute list via POST /v3/category/attribute. For the "Smartphones" category this amounts to 30+ attributes, some mandatory (brand, colour, storage capacity, operating system), some recommended.

Ozon attribute values come from reference dictionaries: you cannot write "red" for a colour — you need the value ID from the Ozon dictionary. IDs are retrieved via POST /v2/category/attribute/values.

Mapping: 1C-Bitrix infoblock property (e.g. PROP_COLOR = "Red") → Ozon attribute ID (e.g. attribute_id: 10096) → Ozon dictionary value ID (e.g. value_id: 61587). This mapping table is maintained as a separate entity in 1C-Bitrix — it changes as new categories are added.

FBS: Stock and Order Management

Under the FBS (fulfilment by seller) scheme, the key cycle is:

1. Update stock in Ozon from 1C-Bitrix — every 15–30 minutes
2. Retrieve new orders from Ozon — poll POST /v3/posting/fbs/list with filter status: awaiting_packaging
3. Create an order in 1C-Bitrix, reserve the product
4. Pick and pack, generate a label (method POST /v2/posting/fbs/package-label)
5. Submit the shipment act to Ozon

Ozon labels are PDFs with a 2D barcode. Retrieved via /v2/posting/fbs/package-label and printed on a label printer (Zebra, TSC) or a standard A4 printer.

Belarus-Specific Considerations

Belarusian sellers ship to Ozon warehouses in Belarus (Minsk) or directly to pickup points. Logistics are simpler and faster than shipping to Moscow as required for WB.

Document flow: upon shipment, Ozon requires an electronic transfer act. For Belarusian legal entities, this is a TN-2 consignment note. The data for generating it is taken from the Ozon order; the document is generated in 1C-Bitrix or the integrated accounting system.

Returns. Ozon automatically creates returns (refund or cancelled postings). The integration must track these events, create a return document in 1C-Bitrix, and restore the product to stock. The endpoint for retrieving returns: POST /v3/returns/company/fbs.

Common Issues

Product blocked by Ozon. The most frequent cause is attribute non-compliance with category requirements. Check status via POST /v2/product/info (field status.state_failed). Read status.validation_errors and correct the attributes.

Stock discrepancies. If the integration updates stock less frequently than orders arrive, overselling is possible. For high-velocity products: reduce the stock quantity exposed on Ozon by 10–20% as a buffer, or increase synchronisation frequency.

Estimated Timelines

Pricing is calculated individually after auditing the catalog and operational scheme (FBS/FBO).