ERP implementation in Tashkent and across Uzbekistan: we configure Odoo for multi-branch retail, automotive, and grocery companies.
"Stock in the program never matches stock on the shelf."
"Every branch reports its own numbers — consolidating them takes my finance team a week."
"I learn we're out of a product when the customer is already at the till."
Process audit: we map your sales, inventory, purchasing, and finance flows before configuring anything.
Odoo configured for your operation: POS, inventory, purchasing, accounting, HR — only the modules you need.
Data migration from Excel and your current systems: products, stock balances, counterparties, history.
Hardware and integrations: barcode scanners, RFID readers, POS equipment, payment systems.
Training on your real data — cashiers, storekeepers, accountants, managers.
Post-launch support: fixes, adjustments, and new modules as you grow.
From 6 weeks for a first working contour (for example, POS + inventory), depending on branch count and data volume. Exact dates go into the written scope.
From $7,000 for a first working contour. You see the full figure in the written scope after the process audit — before any work starts.
For Carland, a multi-branch auto retailer, we built Odoo with POS, a loyalty and cashback program, and RFID-based inventory across branches. For Fresh Mart, a grocery retailer, we implemented barcode-driven sales, HR attendance, and an offline mode so the tills keep selling when the internet drops.
Yes — data migration is a standard part of every implementation. We move products, stock balances, counterparties, and transaction history, and we reconcile the numbers with you before go-live.
The tills keep working. We configured exactly this for Fresh Mart: an offline mode that syncs sales back to Odoo when the connection returns.
No. Post-launch support is part of the offer: fixes, adjustments as your processes change, and new modules when you're ready. Terms are set in the written scope.
Odoo implementation in Uzbekistan starts at $7,000 for a first working contour — for example, POS plus inventory. The final figure depends on the number of modules, branches, and integrations, and is fixed in a written scope before work starts. The Odoo Enterprise license — an annual per-user subscription — comes on top; most of the implementation budget goes into configuration, data migration, and training.
Odoo is the stronger choice when you need operations — POS, inventory, CRM, purchasing, and finance — in one system; 1C remains strong for local statutory accounting. Many of our clients run day-to-day operations in Odoo and keep 1C for accounting — we build the integration between the two. On a free consultation we'll map your processes and tell you honestly which combination fits.
Yes — during implementation we localize Odoo for Uzbekistan: VAT calculation, electronic invoices (ESF) through Didox, and the data your accountant needs for soliq.uz reporting. Tax rules and document flows are configured as part of the project, so invoices go out of the same system your sales run in.
A first working contour of Odoo typically goes live in 6–12 weeks. The exact timeline depends on branch count, data volume, and how many modules launch in the first phase — it's fixed in the written scope. Larger rollouts ship in stages, so your team starts working in the system early.
Yes — that's exactly how we recommend rolling out Odoo. We start with the most painful area, for example POS and inventory, get it live, and add accounting, HR, or purchasing once the team is comfortable. Every stage runs on the same database, so nothing is entered twice.