Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $499.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Wildberries & Ozon Connector for Odoo (CIS/Russia)
A build-to-order Odoo module that connects Wildberries and Ozon to your Odoo instance — syncing product cards, FBO/FBS orders, per-warehouse stock and prices, and shipment documents. ECOSIRE scopes, builds, installs and supports it; it is not an instant apps.odoo.com download.
$499.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
Wildberries Content API integration: create/update cards by nmID and chrtID, characteristics, sizes and barcodes, with mapping to Odoo product.template/product.product variants
Ozon Seller API integration (v2/v3/v4): product create/update, attribute mapping and card status tracking against Odoo products
FBO order import: marketplace-fulfilled postings pulled in and reconciled to sale.order without generating outbound stock moves you don't own
FBS order import: seller-fulfilled postings mapped to Odoo delivery orders (stock.picking) with correct source warehouse
Per-warehouse stock synchronization to each marketplace warehouse, sourced from Odoo stock.quant so Kazan and Moscow never share a phantom quantity
Price and discount push using the Wildberries Prices & Discounts API and Ozon prices endpoints, driven by Odoo pricelists or list_price
Supply/shipment (поставка) document generation for FBS, rendered as QWeb PDF reports with marketplace barcodes/stickers where the API provides them
Commission and logistics-fee capture via computed fields (@api.depends) so net margin appears on sale.order lines alongside your normal reporting
Idempotent upserts keyed on marketplace IDs (nmID, posting_number, offer_id) — scheduled re-runs never duplicate orders or cards
ir.cron scheduled sync with cursor/offset pagination, per-account rate-limit handling and exponential backoff on 429s
Dedicated sync-log model with success/error rows viewable in a standard Odoo tree/form, plus Sentry-friendly logging for failures
Multi-account / multi-store support: several Wildberries and Ozon seller accounts in one Odoo database, isolated by record rules
Security via ir.model.access.csv and record rules scoped to company and marketplace account, with API keys stored in ir.config_parameter (not hard-coded)
Exposed over Odoo XML-RPC/JSON-RPC so external systems and the standard Odoo API keep working; built for Odoo 17.0, 18.0 and 19.0 on Community and Enterprise
इस उत्पाद के बारे में
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.
Wildberries & Ozon Connector for Odoo (CIS/Russia) क्यों चुनें
Wildberries Content API integration: create/update cards by nmID and chrtID, characteristics, sizes and barcodes, with mapping to Odoo product.template/product.product variants
Ozon Seller API integration (v2/v3/v4): product create/update, attribute mapping and card status tracking against Odoo products
FBO order import: marketplace-fulfilled postings pulled in and reconciled to sale.order without generating outbound stock moves you don't own
FBS order import: seller-fulfilled postings mapped to Odoo delivery orders (stock.picking) with correct source warehouse
Per-warehouse stock synchronization to each marketplace warehouse, sourced from Odoo stock.quant so Kazan and Moscow never share a phantom quantity
Price and discount push using the Wildberries Prices & Discounts API and Ozon prices endpoints, driven by Odoo pricelists or list_price
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 2–4 weeks from confirmed scope, and you receive the full installable source plus a Git repository handover, so you are never locked to us.
What you get
- Installable Odoo module source code for your exact version (17.0, 18.0 or 19.0) and edition, with a clean __manifest__.py and pinned dependencies
- Installation and configuration on your environment (or a documented handover pack if your team deploys), including API-key setup for each marketplace account
- Technical documentation: data model, sync flows, cron schedule, ir.model.access.csv/record-rule matrix and troubleshooting notes
- End-user guide plus a live training session for your operations team on cards, orders and stock/price sync
- UAT on a staging copy of your database with a signed-off test plan and a documented rollback procedure before production cutover
- Post-go-live support window for defect fixes and configuration adjustments after launch
- Git repository handover with full commit history so you own and can extend the code independently
- Marketplace field-mapping sheet (Odoo fields ↔ Wildberries/Ozon attributes) so future catalog changes are self-serviceable
Who this is for
CIS marketplace seller on Wildberries & Ozon
Runs day-to-day sales on both platforms and needs orders, stock and prices to live in Odoo instead of two separate seller dashboards, with FBO and FBS handled correctly.
Operations / fulfilment manager
Owns warehouse accuracy and shipping SLAs; needs per-warehouse stock sync, FBS supply documents and no oversells that hurt card ranking or trigger marketplace penalties.
Finance / margin owner
Wants commission, logistics and storage fees visible against each order in Odoo so reported net margin is real, not a spreadsheet reconciled weeks later.
Odoo partner or in-house Odoo admin
Needs a clean, documented module on 17/18/19 with proper access rules, a Git handover and no Enterprise lock-in, so it can be maintained and extended in-house.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Wildberries & Ozon Connector for Odoo (CIS/Russia) module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Wildberries & Ozon Connector for Odoo (CIS/Russia), and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Wildberries & Ozon Connector for Odoo (CIS/Russia) Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Wildberries + Ozon coverage | Both marketplaces' current APIs, scoped to your needs | Whatever your dev has time to build and maintain | Often one platform or partial endpoint coverage | |
| FBO vs FBS handling | Both models mapped to correct Odoo delivery flows | Depends on in-house understanding of both models | Frequently FBS-only or FBO-only | |
| Per-warehouse stock sync | Sourced from stock.quant per marketplace warehouse | Buildable but error-prone to get right | Often single-warehouse assumption | |
| Commission & logistics-fee visibility | Computed fields on order lines for real net margin | Extra scope, rarely finished | Usually not included | |
| Fit to your Odoo version/edition | Built for your 17/18/19, Community or Enterprise | Fits, but you own all the work | Version support varies; may lag releases | |
| Ownership & lock-in | Full source + Git handover, no lock-in | You own it fully | Vendor-controlled, license-gated updates | |
| Delivery model | Build-to-order, 2–4 weeks, UAT + rollback | Weeks-to-months of internal effort | Instant download, then you self-integrate | |
| Support after launch | Post-go-live window + documented handover | Your team only | Generic ticket queue, API-change lag |
Frequently Asked Questions about Wildberries & Ozon Connector for Odoo (CIS/Russia)
+How long does delivery take?
This is a build-to-order module, so it is built for your specific setup rather than downloaded instantly. Typical delivery is 2–4 weeks from confirmed scope — after we've agreed platforms (one or both marketplaces), warehouse topology, FBO/FBS mix, and your Odoo version and edition on the scoping call. Tighter timelines are sometimes possible for a single marketplace with a simple warehouse setup; we'll be honest about it during scoping.
+How do support and updates work after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive full source and a Git repository handover, your team can also extend the module independently. When a marketplace changes its API (Wildberries and Ozon both version their endpoints), we can quote an update, or your own developers can apply it using the technical documentation we provide. We do not hold your code hostage.
+Does it support both FBO and FBS?
Yes. FBO (fulfilled by the marketplace) orders are imported and reconciled to sale.order without generating outbound stock moves for inventory you no longer hold, while FBS (fulfilled by you) orders map to Odoo delivery orders (stock.picking) from the correct source warehouse and can generate supply/shipment documents. The exact behaviour is confirmed against your fulfilment model during scoping.
+Which Odoo versions and editions are supported?
Odoo 17.0, 18.0 and 19.0, on both Community and Enterprise. The module is built to avoid Enterprise-only dependencies unless your instance already runs Enterprise apps you want it to use — we confirm this on the scoping call and target your exact version so there are no surprises after cutover.
+Will it duplicate orders or overwrite my product data if a sync runs twice?
No. Inbound sync uses idempotent upserts keyed on the marketplace's own identifiers (Wildberries nmID/chrtID, Ozon posting_number and offer_id), so scheduled re-runs update existing records instead of creating duplicates. Outbound card and price pushes are mapped field-by-field, and we run everything through UAT on a staging copy of your database before touching production.
+How are our marketplace API keys stored?
API keys are stored in Odoo's ir.config_parameter (or an equivalent secured settings record), never hard-coded in source, and access to the connector's models is restricted through ir.model.access.csv plus record rules scoped to the relevant company and marketplace account. Multi-account setups are isolated so one store's staff cannot see another's data.
+Can it integrate with other systems we run?
Yes. The connector is standard Odoo, so all of its data is reachable over Odoo's XML-RPC/JSON-RPC API just like any other model. If you already push data from a WMS, BI tool or another ERP, those integrations keep working, and we can map custom fields you already use during scoping.
कोटेशन का अनुरोध करें
Wildberries & Ozon Connector for Odoo (CIS/Russia)
A build-to-order Odoo module that connects Wildberries and Ozon to your Odoo instance — syncing product cards, FBO/FBS orders, per-warehouse stock and prices, and shipment documents. ECOSIRE scopes, builds, installs and supports it; it is not an instant apps.odoo.com download.
- Wildberries Content API integration: create/update cards by nmID and chrtID, characteristics, sizes and barcodes, with mapping to Odoo product.template/product.product variants
- Ozon Seller API integration (v2/v3/v4): product create/update, attribute mapping and card status tracking against Odoo products
- FBO order import: marketplace-fulfilled postings pulled in and reconciled to sale.order without generating outbound stock moves you don't own
- FBS order import: seller-fulfilled postings mapped to Odoo delivery orders (stock.picking) with correct source warehouse