The website, warehouse, POS and marketplace do not keep separate books: the order lands in one place, the stock level drops in one place, and the refund and payment are tied to the same document. Connections to local payment systems and marketplaces are estimated separately.
Once sales go out through several channels, each channel starts keeping its own records. The customer, however, relies on one and the same promise.
An online store is the link between the website, the warehouse and accounting. Which apps are needed is determined during the diagnostic.
Catalog, cart, checkout, customer portal, return request.
Building pages without a developer, versions in Uzbek and Russian.
A delivery document from a confirmed order, product reservation, stock levels.
Fixed fee, rule-based fee, carrier connection, choice of delivery date.
Online reservation and pickup in the store; stock level by warehouse.
Card and other methods, bank transfer, cash on delivery, payment against an invoice.
Invoice, credit note, matching the payment against the bank entry.
In-store sales and online orders draw on the same warehouse stock.
Promo code, loyalty points, reward indicator in the cart.
An online order goes through three stages: sale, delivery and invoice. Each one creates its own document.
Products, variants and price lists are maintained. Settings are chosen for selling when stock runs out and for showing the quantity.
As soon as a customer adds a product to the cart, a quotation appears in Odoo. A reminder email is set up for an abandoned cart.
Card through a provider, bank transfer, payment in the store, cash on delivery or payment against an invoice.
If the payment succeeds, the quotation becomes a sales order. With a bank transfer, the order is confirmed manually once the money arrives.
A delivery order is created on confirmation. With the “At Confirmation” setting, the reservation is made at the moment of confirmation.
A carrier, a method you define yourself or Click & Collect. The customer follows the status in the portal.
The customer requests a return through the portal, and the refund is issued once the goods arrive. The invoice is sent automatically or manually after the payment is recorded.
The example is illustrative. There are three units of one product in the warehouse. The website, the store POS and the marketplace can all sell them at the same time. To keep the stock level accurate, the reservation rule and the synchronization interval are agreed in advance.
The online store is a ready-made Odoo app. Local payments, the marketplace and electronic documents are separate work. The list is clarified during the diagnostic. The information follows the Odoo 20 documentation; if your version differs, we check it during the diagnostic.
| Goal | In standard Odoo | Extra work (BUline) |
|---|---|---|
| Online store: catalog, cart, order | Available (eCommerce) | Design, pages, catalog upload |
| Stock levels: linking the website and the warehouse | Available: reservation, continued selling, showing the quantity. In Odoo 20, products are automatically unpublished based on the stock level | Setting up stock rules by product group |
| Delivery methods | Available: fixed fee, rule-based fee, Click & Collect, carriers such as FedEx, UPS, DHL | The documentation has no ready-made connector for courier services in Uzbekistan; the connection is estimated |
| Bank transfer, payment against an invoice, cash on delivery | Available | How receipt of the money is checked |
| Card payment through Click and Payme | Not in the official list: they were not found among the 21 providers in the Odoo 20 documentation | A third-party module or separate development; the module does not work on Odoo Online |
| Marketplace: Uzum Market | Not in the official documentation; a third-party module exists | Testing the module, obtaining a token, agreeing the stock rule |
| Marketplace: Amazon | Odoo has its own Amazon connector (a separate section in the documentation) | Usually not needed for a seller in Uzbekistan |
| Cash register receipt after electronic payment | Not mentioned in the documentation | Through the API of the payment platform or the cash register equipment; estimated |
| B2B store: closed catalog, price list, access by invitation | Available; two separate websites are recommended for B2B and B2C | Setting up customer groups and price lists |
| Electronic invoicing | Not mentioned in the localization documentation; the Apps Store has third-party modules | Test the module or connect through the operator's API |
The information below is taken from the page of an existing third-party module for Uzum Market. We confirm its capabilities and limits by testing the module on your own database. Uzum launched the FBS scheme on 10 October 2024: the seller stores the goods in its own warehouse, while the marketplace provides the storefront and logistics.
| Question | What the module page says | What we check |
|---|---|---|
| Orders: from Uzum to Odoo | FBS and FBO orders are imported as sales orders; FBO orders are for accounting only and cannot be changed | The sequence of order and return statuses |
| Stock levels: from Odoo to Uzum | FBS products only, by SKU, up to 100 per request | Update interval; FBO stock sits in the Uzum warehouse and is not sent from Odoo |
| Prices: from Odoo to Uzum | For FBS and FBO products | Compatibility with price list rules |
| Breakdown by warehouse | The stock level is for the whole company, not broken down by warehouse | How to split stock across multiple branches |
| Access key | A Uzum API token is required; how to obtain it is not described in the documentation and is confirmed with Uzum; the official seller API documentation (OpenAPI) is publicly available | Token owner and security |
| Hosting | The page also lists Online, but the Odoo documentation states that Apps Store modules are not compatible with Online | Odoo.sh or your own server; written confirmation from Odoo |
Click, Payme and Uzum are not in Odoo’s official list of providers. This does not mean they cannot work, but connecting them is not a ready-made button.
| Approach | Does it work out of the box | Note |
|---|---|---|
| Bank transfer | Yes | Receipt of the money is matched against the bank entry and the order is confirmed manually; until then the goods are not reserved |
| Payment against an invoice | Yes | The order is confirmed immediately; convenient for legal entities, usually limited to a B2B price list |
| Payment in the store | Yes | Appears when Click & Collect is enabled |
| Cash on delivery | Yes | Since Odoo 19 it works with all delivery methods |
| Card payment through Click | No | A third-party module exists (for Odoo 19); there is no refund or card saving; the server must be reachable from the internet |
| Card payment through Payme | No | According to the Payme documentation, your server receives the requests and responds in the prescribed format |
The Law “On Electronic Commerce” ZRU-792, per the text on lex.uz. The law changes from 12 December 2026. This is not legal advice.
Each connection is assessed and built separately. We do not promise that a “ready-made connector exists.”
The stages follow the general BUline Method. The timeline is agreed in writing after the diagnostic. Implementation process →
We study the channels, the source of stock data, the payment and delivery methods and the marketplace scheme (FBS or FBO). Outcome: a business requirements document (BRD).
We confirm the apps, the warehouse structure, the stock rules, the payment connection and the hosting type (Online, Odoo.sh or your own server).
First, one product group and one payment method go through the whole flow; the rest and the marketplace follow.
Order operators, warehouse staff and accountants are trained by role, with practice on a real order.
Enhanced support, then new channels and reports.
This list speeds up the diagnostic. We can start even if not everything is ready.
| Mistake | Consequence | How we prevent it |
|---|---|---|
| Choosing a payment module without regard to hosting | The module does not work on Odoo Online | Decide the hosting type at the start of the project |
| Testing the module on the live database | Confusion in invoice numbers and in the books | Testing on a copy of the database |
| Overlooking that card payments reach the bank as a lump sum | Manual work piles up at month-end | Agree the matching rule with the accountant in advance |
| Not monitoring bank transfers | A paid order sits waiting | A responsible person who checks the “To Confirm” filter every day |
| Connecting the marketplace without checking stock levels | Excess orders | A trial on a small product group and a reserve rule |
Yes, but not as a ready-made button. They are not in Odoo’s official list of providers. A third-party module exists for Click, while Payme requires your server to receive the requests. The options and risks are assessed during the diagnostic.
A third-party module exists for Uzum Market: FBS stock levels and the prices of all products are sent from Odoo, and orders are imported into Odoo. FBO stock sits in the Uzum warehouse. We test the module on your database.
The website and the warehouse run in one database, so the website uses the Odoo stock level. Sending data to the marketplace depends on the module’s interval. Reservation happens on confirmation; with a bank transfer, the goods are not reserved until the money arrives and the order is confirmed manually.
Yes. The customer requests a return through the portal, and the refund starts once the goods arrive. To refund the money, the payment must have gone through a provider that supports refunds. The time limits and reasons are your own rules.
Odoo Online is not compatible with third-party and custom modules. If you need a local payment or marketplace module, Odoo.sh or your own server is chosen. Hosting types →
As a seller, you are subject to the offer terms, the delivery time, and the rules on defective goods and refunds. The website text and the process in Odoo must match. A new edition takes effect on 12 December. Get a legal opinion from a lawyer.
The Odoo license depends on the number of users and apps (terms at odoo.com). The scope of the BUline service depends on the number of channels, the payment and marketplace connections, the warehouse, the data volume and the training. Exact costs and timelines are given in a written proposal after the free diagnostic.
During the diagnostic, we review your processes and tell you where standard Odoo is enough and where configuration is needed — with an app list, edition and phases.