Uzbekistan Uzum Market
Uzum Market connector for Odoo: import FBO and FBS orders, sync stock and price via the seller Uzum Seller API token (BYOK), on the published Uzum seller-openapi
Want Uzbekistan Uzum Market installed and configured for you? Onboarding Pack: $350 one-off
Support plans from $425 a monthUzbekistan Uzum Market Connector
Direct Uzum Market Seller API connector for Odoo — FBO & FBS orders, stock and price sync in one app
Connect Odoo straight to your Uzum Market Seller cabinet. Pull marketplace orders into Odoo sales for both fulfilment models — Fulfilment by Operator (FBO) and Fulfilment by Seller (FBS) — keep stock and prices in sync by SKU, and drive the FBS order through its confirm / pack / ship / cancel state machine, all from your own Uzum API token.
Key Features
Order Sync (pull)
A scheduled job and an on-demand button pull recent Uzum orders page by page, filtered by FBS status and a creation-date window. Each order becomes an Odoo sale order with customer, delivery address and lines.
FBO & FBS Models
Both Uzum fulfilment models are supported. FBS (seller-fulfilled) orders carry the full action workflow; FBO (operator-fulfilled, shipped from the Uzum Tashkent warehouse) orders are imported read-only for bookkeeping. The model is stored and searchable.
Stock & Price Sync (push)
Push available quantity and sales price to Uzum by SKU — per product, in bulk from the product list, through a guided wizard, or via an hourly cron. Stock goes out by the Uzum SKU barcode, batched at 100 SKUs per call, and prices one call per Uzum product; Link Uzum catalogue reads your shop's SKUs and stores the Uzum product, SKU and barcode identifiers on each matching product.
FBS State Machine
Confirm a new FBS order, mark it packed (the official FBS label is attached to the order), ship it (an Uzum handover invoice at a drop-off point and time slot Uzum offers; its number becomes the tracking number) or cancel it — each as a one-click button on the sale order that calls the matching Uzum endpoint. Optional auto-confirm on import.
STIR / PINFL Validation
Customer taxpayer numbers are validated structurally: the 9-digit STIR/INN of a company and the 14-digit PINFL of an individual (with its embedded birth-date and century marker) are checked before they are stored on the partner form; an Uzum order itself carries no taxpayer number, so an import never writes one. The PINFL birth date is reconciled with its century marker, so 29 February is accepted only in a year that has one.
Buyers stay Uzum buyers
An imported order is matched only against buyers this connector itself created, so it can never attach to one of your own vendor or customer records — and a returning buyer is recognised by the phone number Uzum sends with the order, not by a bare email address. The delivery address that arrives with an order is written onto the buyer, so a picking prints where this parcel is going.
Your SKU mapping wins
The Uzum SKU you map on a product is the first lookup, ahead of internal reference and barcode. An Uzum SKU that happens to equal another product’s internal reference no longer imports the order against the wrong product.
An explicit price unit
Choose whether Uzum expects som or tiyin and see the multiplier that will be applied before anything is sent. Prices in another company currency are converted to UZS first. Upgrading an existing database keeps publishing in som, which is what it already publishes, until you choose.
FBS stock only
Stock is published for FBS products only, because an FBO product’s stock sits in Uzum’s warehouse rather than yours. Prices are published for both. These figures are company-wide and are not warehouse-scoped.
An import that finishes
Each order is imported in isolation, so one malformed order no longer discards every order the run had already imported. The upstream FBS confirmation is sent only after the local order is safely recorded, so Uzum and Odoo cannot disagree about whether an order exists.
Test Connection & API Log
One button validates your token with a real lightweight call. Every API call is recorded in a unified log — successes as well as failures, and the buttons on a form as well as the crons — with operation, HTTP method, status, duration, a truncated request payload and a response excerpt. Log rows are scoped to the company whose credentials made the call, and a reply that is not JSON is recorded as the failure it is rather than as a silent success.
What gets synchronised
| Direction | Data | How |
|---|---|---|
| Uzum → Odoo | FBS orders + lines | Cron + on-demand button, paged, status filtered |
| Uzum → Odoo | FBO orders + lines | Cron + on-demand button (read-only bookkeeping) |
| Uzum → Odoo | Customer & delivery address | Matched / created by the buyer's phone |
| Odoo → Uzum | Available stock by SKU | Per product, bulk, wizard or hourly cron |
| Odoo → Uzum | Sales price by SKU | Per product, bulk, wizard or hourly cron |
| Odoo → Uzum | FBS order state | Confirm / pack / ship / cancel buttons |
Bring Your Own Key (BYOK)
This is a BYOK connector. You paste the API token issued in your own Uzum
Market Seller cabinet; data is sent only to the Uzum Seller endpoint you configure. The base
URL ships as an editable default (https://api-seller.uzum.uz) so you can point at
a reverse proxy or a future host without code changes. We are not an Uzum reseller or
accredited integrator — the connector simply speaks the published Seller API on your behalf.
The request paths and payloads follow the seller-openapi 1.0.0 document Uzum publishes
(api-seller.uzum.uz/api/seller-openapi/swagger/api-docs), and the token is sent the way it
prescribes, without a Bearer prefix.
Requirements
- Odoo 18.0, 19.0 or 20.0 (Community or Enterprise).
- Depends on the standard
sale_management,sale,stockandproductapps only — no Enterprise-only modules. - An active Uzum Market Seller cabinet with an API token.
- The Python
requestslibrary (bundled with Odoo).
Screenshots
Api Log
Settings
Push Stock Price
Upgrading an existing database
Prices keep being published in som, exactly as they are today, until you choose a price unit in Settings — nothing about a live listing changes behind your back. Pick “Tiyin” only if your Uzum account expects it; the multiplier is shown next to the setting so the choice is never a guess. A company kept in a currency other than UZS will publish different numbers on its next price sync, because prices are now converted first.
Products default to FBS, so stock publishing is unchanged for everyone selling from their own warehouse. Mark your FBO products as FBO to stop publishing your own on-hand as their availability. Partners that already carry an Uzum identifier are marked as Uzum buyers on upgrade, so returning buyers are still recognised; new orders will no longer attach to your own contacts. Existing partners with a malformed taxpayer number are left alone, but editing one will now ask you to correct it.
Pushing prices and stock now requires the Uzum Market / User group. Grant it to the people who already do that work; it carries no accounting or inventory rights of its own.
Update date: 2026-10-06
User guides (PDF)
Related modules
CDON Marketplace Connector
Sell on CDON (Sweden, Denmark, Finland, Norway) from Odoo: listings, stock, prices, orders, tracking. Official CDON Merchant API, BYOK.
Duct Takeoff & Weight
Ductwork takeoff into straight runs and fittings with surface area, sheet gauge by size class, weight, insulation area, order lists and quotation lines
Engineering Fee Proposal
Engineering consultancy fee proposals from deliverables x discipline x role hours and rates, multipliers, risk allowance, margin, quotation and hand-over to project budget