Wildberries Seller Guide: Russian Marketplace + Odoo Integration

If you are looking to sell into Russia and the Commonwealth of Independent States (CIS), there is one marketplace you cannot ignore. Wildberries is the largest ecommerce platform in Russia and the CIS region, processing over 2.5 billion orders in 2025 alone. With a fulfilment network spanning 11 countries, 3,500+ delivery points, and a seller base exceeding 500,000 merchants, Wildberries dwarfs every competitor in its home market. For international sellers and Russian-based businesses running Odoo ERP, integrating with Wildberries is the gateway to a $50 billion+ ecommerce market.

Key Takeaways

• Wildberries processes 2.5 billion+ orders annually, making it Europe's largest marketplace by order volume
• The platform serves 11 CIS countries with 3,500+ delivery and pickup points
• Wildberries operates a seller-to-warehouse model — sellers ship to WB fulfilment centres
• API integration is essential because Wildberries' seller portal is entirely in Russian
• ECOSIRE's connector handles the unique challenges: Cyrillic product data, ruble-based accounting, Russian tax compliance
• Proper integration reduces fulfilment penalties by 85% and enables cross-border selling across the CIS

---

Understanding the Wildberries Opportunity

Wildberries started in 2004 as an online fashion retailer and evolved into a general merchandise marketplace that now carries everything from electronics to groceries. The platform's growth has been extraordinary — from $6 billion GMV in 2020 to over $25 billion in 2025, making it not just the largest Russian marketplace but one of the largest globally by transaction volume.

Wildberries Statistics (2025-2026)

Why Wildberries Is Uniquely Challenging

Several characteristics make Wildberries integration more complex than Western marketplace connectors:

1. Russian language requirement: All product listings, descriptions, and seller communications are in Russian. The seller portal interface is entirely Russian-language
2. Cyrillic data handling: Product data, customer addresses, and shipping labels all use Cyrillic script, requiring proper encoding throughout the integration pipeline
3. Fulfilment-centre model: Unlike Amazon FBA where you choose between self-fulfilment and marketplace fulfilment, Wildberries operates primarily on a warehouse model where sellers ship inventory to WB fulfilment centres
4. Russian tax system: VAT at 20%, specialised documentation requirements, and electronic document interchange (EDI) for B2B transactions
5. Currency considerations: All transactions in Russian rubles (RUB), with volatile exchange rates for international sellers
6. Regulatory environment: Evolving ecommerce regulations, mandatory product certification for certain categories, and country-of-origin labelling requirements

---

Wildberries API for Sellers

Wildberries provides a comprehensive API (the "WB API") for seller integrations. The API has evolved significantly and now covers all core seller operations.

API Modules

Content API

• Create and update product cards (descriptions, images, characteristics)
• Manage product variants and colour/size matrices
• Handle category-specific attributes and required fields
• Upload media (images, videos)

Marketplace API

• Manage pricing and discounts
• Set warehouse stock levels
• Configure delivery parameters
• Handle promotional campaigns

Statistics API

• Access sales data and order history
• Retrieve financial reports and settlements
• View return and defect statistics
• Monitor seller ratings and performance metrics

Supplies API

• Create supply requests to WB warehouses
• Generate supply barcodes and documentation
• Track supply acceptance and processing
• Manage supply scheduling

Orders API (for FBS — Fulfilment by Seller)

• Retrieve new orders for self-fulfilment
• Update order status and tracking
• Handle assembly and shipping workflows

Authentication

WB API uses token-based authentication with API keys generated in the seller's personal cabinet. Different API modules may require separate tokens with specific permission scopes. Token management is critical — expired or revoked tokens cause immediate sync failures.

FBO vs FBS Models

Wildberries offers two fulfilment models:

• FBO (Fulfilment by Operator/Wildberries): Seller ships inventory to WB warehouses; WB handles storage, picking, packing, and delivery. This is the dominant model used by 80%+ of sellers
• FBS (Fulfilment by Seller): Seller stores inventory and ships directly to the buyer or to a WB sorting centre. Less common, but necessary for oversized goods or sellers with their own logistics

Your integration must support whichever model you operate, and ideally both for maximum flexibility.

---

Integration Architecture

Data Flow for FBO (Primary Model)

Odoo (Product Master)
  ├── Products → WB Content API (listings)
  ├── Pricing → WB Marketplace API (price updates)
  ├── Stock → WB Supplies API (warehouse replenishment)
  │         → WB Marketplace API (availability)
  ├── WB Statistics API → Orders (sale records)
  ├── WB Statistics API → Returns (return processing)
  └── WB Statistics API → Settlements (financial reconciliation)

In the FBO model, the order fulfilment flow differs from typical marketplace integrations because Wildberries handles everything from the warehouse onwards. Sellers do not receive individual pick-and-pack orders — instead, they monitor sales data and ensure WB warehouses are adequately stocked.

Component 1: Product Content Sync

Product listings on Wildberries require:

• Russian-language content: Titles, descriptions, and attributes must be in Russian. The integration must either sync Russian-language content from Odoo or invoke translation services
• Category compliance: Each product category has mandatory attributes. Electronics require certification numbers; clothing requires material composition; food requires expiration dates
• Image requirements: Multiple product images with specific dimension and format requirements
• Barcode assignment: WB uses its own barcode system alongside standard EAN/UPC codes

The connector manages the Odoo-to-WB content mapping, handling Cyrillic text encoding, mandatory attribute validation, and image format conversion.

Component 2: Supply Chain Management (FBO)

Instead of processing individual orders, FBO sellers manage supply shipments to WB warehouses:

1. Demand forecasting: Analyse sales velocity to determine replenishment needs
2. Supply creation: Create supply requests in WB system with SKU quantities
3. Barcode labelling: Generate and print WB-specific barcodes for each unit
4. Shipment tracking: Monitor supply acceptance at WB warehouses
5. Inventory reconciliation: Verify WB's reported stock levels match expected quantities

The Odoo integration automates this cycle — forecasting demand based on sales data, creating supply requests when stock at WB warehouses drops below thresholds, and tracking the entire supply pipeline.

Component 3: Sales and Order Tracking

In FBO mode, sellers do not receive traditional orders. Instead, the integration imports sales data from WB's Statistics API:

• Daily and weekly sales by SKU
• Order details including buyer region and delivery method
• Revenue and commission breakdowns
• Return information and reason codes

This data feeds into Odoo's sales module for reporting, forecasting, and profitability analysis.

Component 4: Pricing and Promotion Management

Wildberries has a dynamic pricing environment with:

• SPP (Seller Price Premium): WB may offer customers discounts funded by the seller's margin
• Promotional campaigns: Scheduled sale events where sellers commit to discounted pricing
• Competitor pricing pressure: WB's algorithm considers pricing relative to competitors
• Commission variation: Commission rates adjust based on category, brand, and performance

The connector manages pricing from Odoo with awareness of WB's pricing mechanisms, ensuring target margins are maintained after commissions and any WB-applied discounts.

Component 5: Financial Reconciliation

WB settlements are weekly and include:

• Gross sales revenue
• Commission deductions (5-15%)
• Logistics fees (delivery, storage, return processing)
• Penalty deductions (late supplies, defective products, packing violations)
• Promotional contribution deductions

The connector imports settlement data and creates detailed journal entries in Odoo, matching each line item to the appropriate revenue or expense account.

---

Setup Guide

Step 1: Wildberries Seller Account Preparation

1. Register as a Wildberries seller (requires Russian legal entity or foreign entity registration)
2. Complete seller verification (tax documents, bank details)
3. Generate API tokens from the seller's personal cabinet
4. Identify target WB warehouses for supply shipments

Step 2: Odoo Configuration

1. Russian localisation: Install Odoo's Russian localisation module for VAT, chart of accounts, and document formats
2. Currency: Configure RUB currency with exchange rate sources
3. Sales channel: Create "Wildberries" sales team
4. Warehouse: Set up a virtual warehouse representing WB's fulfilment centres
5. Product attributes: Add Russian-language fields to product templates
6. Tax: Configure 20% Russian VAT rules

Step 3: Install the ECOSIRE Connector

Deploy the ECOSIRE Wildberries connector module:

1. Install through Odoo Apps
2. Navigate to Settings > Wildberries Integration
3. Enter API tokens for each required module (Content, Marketplace, Statistics, Supplies)
4. Configure WB warehouse mappings
5. Set sync intervals (sales data: hourly, inventory: every 30 minutes, pricing: on-demand)

Step 4: Product Setup

1. Create Russian content for all products (or configure translation integration)
2. Map categories to WB's taxonomy (mandatory attributes per category)
3. Generate barcodes using WB's barcode system
4. Upload compliant images (minimum resolution, white background, specific dimensions)
5. Set pricing accounting for WB commissions and target margins

Step 5: Supply Chain Configuration

1. Set replenishment rules per SKU per WB warehouse
2. Configure supply scheduling (which days, lead times to WB warehouses)
3. Set up barcode printing for supply shipment labelling
4. Define safety stock levels at WB warehouses

Step 6: Test and Go Live

1. List 5-10 test products and verify content accuracy on WB
2. Create a test supply shipment and track acceptance
3. Monitor first sales and verify data import accuracy
4. Review first weekly settlement for reconciliation completeness
5. Gradually expand product catalogue and supply frequency

---

Wildberries-Specific Challenges

Challenge 1: Cyrillic Data Handling

Russian text encoding issues can corrupt product listings, customer data, and financial records if not handled correctly throughout the integration pipeline.

Solution: The connector ensures UTF-8 encoding at every data touchpoint, with specific handling for Cyrillic characters in API calls, database storage, and report generation. Odoo's underlying PostgreSQL database handles Unicode natively, but API communication layers must be explicitly configured.

Challenge 2: WB's Pricing Algorithm

Wildberries may apply additional discounts to seller products through the SPP mechanism, effectively reducing the seller's received price below the listed price.

Solution: The connector tracks actual received prices (after SPP and commissions) alongside listed prices, providing true margin visibility. Pricing alerts warn when WB-applied discounts push margins below configurable thresholds.

Challenge 3: Supply Acceptance Delays

WB warehouses may delay acceptance of supply shipments during peak periods, causing inventory shortages on the platform while physical stock sits in transit.

Solution: The integration accounts for in-transit inventory in its demand forecasting, triggers earlier replenishment during historically busy periods, and diversifies across multiple WB warehouse locations to reduce single-point congestion.

Challenge 4: Penalty Avoidance

WB imposes penalties for late supplies, packing violations, incorrect barcodes, and product defects. Penalties are deducted from settlements and can significantly impact margins.

Solution: The connector implements pre-supply validation checks (barcode accuracy, packaging compliance, documentation completeness) and maintains a penalty tracking dashboard. Patterns in penalties (e.g., recurring barcode issues from a specific warehouse) trigger targeted alerts.

Challenge 5: Cross-CIS Expansion

Expanding from Russia to Kazakhstan, Belarus, or other CIS countries involves different tax rules, product certification requirements, and logistics routing.

Solution: The connector supports multi-country configuration within the CIS, handling country-specific tax calculations, product compliance requirements, and warehouse allocation for cross-border fulfilment.

---

Manual vs ECOSIRE Connector

---

Strategic Considerations for the Russian Market

Regulatory Compliance

Selling in Russia requires attention to:

• Mandatory certification: Many product categories require EAC (Eurasian Conformity) or GOST certification
• Country of origin labelling: Required for all imported products
• Data localisation: Russian personal data must be stored on servers located in Russia (affects CRM data)
• Electronic document interchange (EDI): Required for B2B transactions and increasingly for B2C

Logistics and Fulfilment

Russia's geography creates unique logistics challenges:

• 11 time zones spanning 6,600 miles east to west
• Delivery to Vladivostok from Moscow takes 7-14 days by ground
• WB's fulfilment network is concentrated in western Russia, with growing coverage eastward
• Seasonal factors (extreme winter weather) affect supply chain timing

For broader strategies on managing multiple marketplaces alongside Wildberries, see our multi-marketplace management guide.

---

ECOSIRE Support for Russian Marketplace Integration

ECOSIRE's Odoo integration services include specialised support for Russian and CIS marketplace operations:

• Wildberries connector deployment and configuration
• Russian localisation setup (accounting, tax, documents)
• Supply chain workflow design for FBO operations
• Cross-CIS expansion planning and configuration
• Training in Russian or English for your operations team

Browse the complete ECOSIRE connector module catalogue for Wildberries and 30+ other marketplace integrations.

---

Frequently Asked Questions

How does the connector handle WB's weekly settlement reconciliation?

Settlement data is imported weekly and parsed into individual line items: sales revenue, commissions, logistics fees, storage fees, penalties, and adjustments. Each line creates a journal entry in Odoo mapped to the correct account, with automatic matching against recorded sales and variance flagging for discrepancies.

What about WB's penalty system?

The connector tracks all penalty types (late supply, packing violations, barcode errors, quality defects) in a dedicated Odoo dashboard. Pattern analysis identifies recurring issues for proactive correction, and penalty trends are charted over time to measure operational improvement.

How does supply replenishment work with the FBO model?

The connector analyses sales velocity per SKU per WB warehouse and calculates optimal replenishment timing and quantities. When warehouse stock drops below configurable thresholds, it creates supply requests automatically in Odoo for warehouse staff to prepare. Supply documentation (barcodes, packing lists) is generated through the Odoo interface.

Which Odoo versions are supported?

The ECOSIRE Wildberries connector supports Odoo 17, 18, and 19 (Community and Enterprise). Russian localisation features (accounting, VAT, document formats) are included with the module.

---

Conclusion

Wildberries represents a massive, rapidly growing marketplace opportunity that most international sellers overlook due to language barriers, regulatory complexity, and the unfamiliarity of the Russian and CIS ecommerce landscape. Those barriers are precisely what create the opportunity — sellers who overcome them face less competition than on Amazon, eBay, or other Western platforms.

The key to success on Wildberries is operational integration. The platform's FBO model, supply-based fulfilment, penalty system, and Russian-language requirements all demand a level of process automation that manual workflows cannot sustain. Connecting Wildberries to Odoo through a purpose-built connector transforms these challenges from barriers to competitive advantages.

Whether you are a Russian domestic seller scaling operations or an international brand entering the CIS market, ECOSIRE's Wildberries connector provides the integration foundation you need to operate efficiently and grow profitably on the platform.