A site is split into stages, material and subcontractor costs are recorded against that site, and an invoice is issued for completed work. Odoo's documentation does not describe a ready-made cost estimating app based on Uzbekistan's norms, but there are industry packages for construction. We state the scope openly.
There are many sites, and each has its own stages, crew and client. If everything is run in Excel and messages, the mistake surfaces at handover.
Odoo lists two industry packages for construction. They are not separate apps but a set of standard apps, fields and templates. The author is Odoo S.A., the licence is OEEL-1, which means Enterprise is required. The Apps Store listing shows Odoo Online, Odoo.sh and On Premise.
The core set for a contractor. Documents, Planning and Approvals are part of Enterprise (they are not in the open-source repository). Which apps are needed is determined at the diagnostic.
A site is run as a project: stage, task, dependency and milestone. A template speeds up repeat sites.
A quotation split into sections, an advance payment and stage invoicing. Additional work goes on a separate line.
Request for quotation for materials and services, a blanket agreement, matching the bill with the order and the receipt.
Receipt and issue of materials. A site warehouse is kept as a separate warehouse or location.
Crew hours are logged against the task. Hours and photos are entered from the site by phone.
Analytic accounting ties costs to the site. If a budget is entered, costs are compared against it.
Drawings, the contract, permits and site photos in one place.
Crew, equipment and time in one schedule. Equipment such as a crane becomes a resource too.
An approval chain for purchases, additional work and payment.
Each stage leaves its own record, so the manager, the foreman and the accountant look at the same figure.
The client's request is kept in CRM, and the proposal is built as a sales order split into sections. The terms for the advance and the invoice are set.
When the order is confirmed, a project is opened (if that is how the product is set up). Stages, tasks and dependencies are taken from the template.
Cost estimate lines are linked to analytic accounting and the budget by cost type.
A request for quotation for material, or a blanket agreement. The purchase order is linked to the project: Odoo has a standard module for this.
Material is received into the site location and issued from it. The stock level and consumption are visible in the records.
Crew hours, equipment and subcontractor work are logged. The foreman enters the stage status from the site.
The invoice is prepared when a stage is completed or based on the volume of work done. The work acceptance certificate is issued in a form agreed with the client.
The site is handed over and the warranty period is put under control. The manager sees the final margin for the site.
The example is hypothetical. On an interior finishing site, the client asked for additional work on a wall. How it is settled depends on what share of the cost estimate the additional work makes up. Resolution No. 306 of the Plenum of the Supreme Economic Court (23 December 2016) states that the contractor must warn the client that additional work is needed and that the cost estimate will rise. If the additional work is up to 10 percent of the total cost estimate value and does not change the nature of the work, a client who has agreed after the warning may amend the design and cost estimate documentation on its own. If it exceeds 10 percent, the amendment is formalized in writing by agreement.
Odoo's documentation does not describe a cost estimating app based on Uzbekistan's construction norms. In Odoo, the cost estimate is kept as sales order lines, sections and a bill of materials (BoM). The Property Developer package has cost types, work-unit norms and a cost update widget, but this is Odoo's own logic, not a local norms database.
For state program sites, the cost estimate value must be built from the data of the “National Classifier of Construction Resources” electronic platform: Presidential Resolution PQ-165 of 29 April 2024, clause 3, from 1 July 2024. The move to the “volume method” from 1 January 2025 is also set out in that clause. The resolution applies to state programs and programs financed from the budget; its application to private clients' sites has not been verified and is clarified in writing at the diagnostic.
Most of the project, purchasing and invoice chain is available in ready-made apps. A cost estimate under Uzbekistan's norms, the work acceptance certificate form and electronic invoicing are separate work. The information follows the documentation, release notes and package descriptions for Odoo 19 and 20; if your version differs, we check it at the diagnostic.
| Goal | In standard Odoo | Extra work (BUline) |
|---|---|---|
| Site, stage, task | Available: Project. Dependency, milestone, template, roles, subtasks | Adapt the site template and the list of stages to your types of work |
| Multi-level work breakdown structure (WBS) | In the Property Developer package: a WBS view from the sales order and the project (Odoo 20). Standard Project has subtasks | Try the package or build the structure with subtasks |
| Cost estimate (Uzbekistan norms) | No separate cost estimating app is described in the documentation. Available: a quotation with sections, BoM; in the package, work-unit norms | Cost estimate import, line structure, norms database: assessed |
| Cost control | Available: analytic accounting, analytic budget (Accounting), linking the purchase order and the warehouse document to the project | Cost types and budget structure |
| Purchasing and comparison | Available: Purchase. Blanket agreement, alternative quotations, matching the bill with the order and the receipt | Approval chain, purchase list per site |
| Site warehouse | Available: warehouses and locations. In Property Developer, site locations (Odoo 20) | Structure of site warehouses, procedure for issuing materials |
| Invoicing for completed work | Available: advance payment, milestone (the invoice is created separately), time and materials. In Property Developer, by cumulative completion | An invoicing rule based on the volume completed, aligned with the client's contract |
| Retention | No separate function is described in the standard documentation. The General Contractor description mentions retention tied to a stage | Try it in the package or set up a separate calculation rule: assessed |
| Form of the work acceptance certificate (akt) and the statement of completed work | The documentation (Odoo's official Uzbekistan localization, Fiscal Localization → “uz Uzbekistan”) does not mention forms for the work acceptance certificate or the statement of completed work | Preparing a printed form; the form is agreed with the client at the diagnostic |
| Subcontractor | Odoo's Subcontracting app is for manufacturing. Construction subcontracting is run as a purchase of services; the Property Developer description mentions subcontractor management | Subcontract agreement, scope of work and payment control: assessed |
| Electronic invoicing | No: not mentioned in Odoo's official Uzbekistan localization (Fiscal Localization → “uz Uzbekistan”) | Connection to the operator's system is estimated |
The items below have been checked against official sources. Those that apply to your line of business, we list in writing at the diagnostic.
Each connection is assessed and built separately. We do not promise that a “ready-made connector exists.”
Reports are not copied into a separate spreadsheet; they are generated from the documents in the same database.
The stages follow the general BUline Method. The timeline is agreed in writing after the diagnostic. Implementation process →
We study site types, the cost estimate structure, purchasing and warehouse, work with subcontractors and the document flow. Result: a business requirements document (BRD).
We approve the site template, cost types, budget structure, approval rules and document forms. We decide whether an industry package is needed.
First, one site goes through the whole process from start to finish, then the remaining sites, the purchasing chain and integrations.
The estimator, foreman, buyer, storekeeper and accountant are trained by role. An instruction guide and video lessons are provided.
Enhanced support, then adding new site types and reports.
This list speeds up the diagnostic. We can start even if not everything is ready.
| Mistake | Consequence | How we prevent it |
|---|---|---|
| Entering the cost estimate as a single sum | There is no control by cost type | Enter it by lines and cost types |
| Not linking the purchase order to the site | The site's costs are shown incompletely | Make a project or an analytic distribution mandatory on every order |
| Rating profit as high when the material has been received but the bill has not arrived | A purchase order reaches the costs only once the supplier's bill is confirmed | Track received material with no bill separately |
| Agreeing additional work verbally | The right to payment may be lost (Resolution No. 306) | Keep the warning and the confirmation in the project correspondence |
| Assuming the invoice is issued as soon as the milestone is reached | The stage updates only the delivered share | Write down the procedure for creating the invoice separately |
| Installing the Property Developer package without trying it out first | Dependence on Studio and many apps creates unexpected work | Compare the package with your process in a test database |
A separate cost estimating app based on Uzbekistan's norms is not described in Odoo's documentation. The cost estimate is kept as sales order lines, sections and a bill of materials, and the Property Developer package has work-unit norms. Entering a norms database and adapting the cost estimate format are assessed at the diagnostic.
Yes. Odoo lists two industry packages: General Contractor and Property Developer. They are Odoo S.A. packages, require Enterprise and rely on Studio. The documentation does not describe them as a separate app, so their scope is checked in a test database.
Odoo generates invoices and document layouts, but the documentation on Odoo's official Uzbekistan localization (Fiscal Localization → “uz Uzbekistan”) does not mention a form for the work acceptance certificate. A single mandatory form for completed-work documents has not been confirmed in an official source. The form is agreed with the client and prepared as a printed report.
Odoo's Subcontracting app is for manufacturing. Construction subcontracting is run as a purchase of services: the order, volume and payment are linked to the site. The Property Developer description mentions subcontractor management, but the details are checked at the diagnostic.
Material is received into a separate warehouse or location and issued from it, and the purchase order and the warehouse document are linked to the project. Property Developer has site locations (Odoo 20). With the standard setup, we design the structure together.
The industry packages rely on Studio, and custom code does not run on Odoo Online. The Apps Store listing shows Online, Odoo.sh and On Premise for the packages; the exact restriction is checked at the diagnostic. Hosting types →
The Odoo licence depends on the number of users and apps (terms at odoo.com). The scope of BUline's work depends on the number of users, site types, branches, customization, integrations, data volume and training. The exact cost and timeline 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.