If you sell on Wildberries and Ozon, your day is spent reconciling two marketplace dashboards against Odoo by hand — re-keying orders, guessing which warehouse a unit shipped from, and discovering stock-outs or oversells only after the marketplace has already penalized your card ranking. Commission tiers and logistics fees live in the seller portals, so your Odoo sale.order margins are fiction until someone exports a spreadsheet weeks later. Odoo core has no concept of Wildberries nmID/chrtID cards or Ozon posting_number FBO/FBS postings, and the FBS versus FBO split — where you ship yourself versus where the marketplace fulfils from its warehouse — has no native mapping to Odoo delivery operations at all.

ECOSIRE builds a dedicated Odoo connector that speaks both marketplaces' APIs natively. On the Wildberries side we integrate the Content, Marketplace, Prices & Discounts, and Statistics APIs; on Ozon we integrate the Seller API (/v2, /v3, /v4 product, posting, stocks and prices endpoints). We model it the Odoo way: new models.Model records for marketplace accounts, card mappings, warehouses and postings, linked to your existing product.template/product.product, stock.warehouse and sale.order. Computed fields (@api.depends) surface commission, logistics and storage fees against each order line so gross-versus-net margin is visible in real Odoo reporting. Inbound sync runs on ir.cron scheduled actions with cursor/offset pagination and idempotent upserts (marketplace IDs are the natural keys, so re-runs never duplicate), while outbound stock and price pushes are triggered by automated actions or ORM writes. Access is locked down with ir.model.access.csv plus record rules for multi-company/multi-store setups, and every sync writes to a log model you can audit from a standard Odoo tree/form view. Order documents and supply/shipment slips render through QWeb reports.

Functionally you get: product cards created and updated on both platforms from Odoo; orders imported for both FBO (marketplace-fulfilled) and FBS (seller-fulfilled) models, each mapped to the correct Odoo delivery flow; per-warehouse stock and price synchronization so a Kazan warehouse and a Moscow warehouse never share a phantom quantity; supply/shipment document generation for FBS deliveries; and commission plus logistics-fee visibility folded into the numbers you already trust in Odoo. Everything is exposed over Odoo's own XML-RPC/JSON-RPC API too, so downstream systems keep working. The module targets Odoo 17.0, 18.0 and 19.0, works on Community and Enterprise, and is built without dependence on Enterprise-only apps unless your instance already has them (we'll confirm during scoping).

Because this is build-to-order, nothing ships blind. We start with a short scoping call to pin down your exact platforms (one or both marketplaces), warehouse topology, FBO/FBS mix, Odoo version and edition, and any custom fields already in play. We then build the module against your requirements, run UAT on a staging copy of your database, and only cut over to production once you sign off — with a documented rollback. Typical delivery is one working week from confirmed scope, and you receive the full installable source plus a Git repository handover, so you are never locked to us.