Construction Builder

Name: Construction Builder
Brand: ECOSIRE
SKU: construction-builder

Key Features

Hierarchical WBS / cost-code tree on a self-referencing `models.Model` with `parent_id`, and stored `@api.depends` roll-ups of budget, committed, and actual amounts up every branch

Bill-of-quantities model linked to `product.product`, with quantity, unit rate, and markup lines that seed both the client estimate and the internal budget

Budget vs. committed vs. actual cost dashboard per cost code, pulling live from analytic lines, `purchase.order` commitments, and posted `account.move` bills

Subcontract records that generate and track `purchase.order` commitments, retention on subcontract payments, and variation/change-order lines against the original value

Progress (application-for-payment) billing that produces draft `account.move` customer invoices by percent-complete or measured quantity, with retention/retainage withheld automatically

Retention ledger tracking amounts withheld and scheduled for release, with a cron-driven reminder when release conditions or dates are met

Change-order / variation workflow with state machine (draft → submitted → approved) that adjusts contract value and budget once approved

Analytic-accounting integration: every timesheet, material PO, and subcontractor bill posts to the job's `account.analytic.account` and cost code for true job costing

QWeb PDF reports for payment applications, cost-value reconciliation (CVR), subcontract status, and budget-variance statements

Record rules and `ir.model.access.csv` giving site foremen job-scoped access while commercial and finance roles see the full portfolio

Automated actions for budget-breach alerts (committed + actual approaching or exceeding budget) and stage-change notifications to the responsible manager

OWL planning/progress board view for updating percent-complete and reviewing cost status without leaving the job record

Optional per-job WIP and revenue-recognition helper lines (percentage-of-completion) posting to configurable accounts

Full XML-RPC / JSON-RPC exposure of job, cost-code, and billing models so external field apps, BI, or payroll can read and write the live cost picture

Built and tested against your target Odoo 17.0, 18.0, or 19.0, with Community-safe equivalents where an Enterprise-only dependency would otherwise be required

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Construction teams that run Odoo quickly hit the ceiling of the native Project and Sales apps. A project.project is a flat list of project.task records with no notion of a work breakdown structure, a bill of quantities, retention/retainage, or committed cost from purchase orders and subcontracts. Estimators build tenders in spreadsheets, foremen track progress on paper, and finance reconciles it all weeks later — so by the time you see a job is over budget, the concrete is already poured. Odoo core gives you timesheets and analytic accounting, but it does not give you the cost-code hierarchy, the budget-vs-committed-vs-actual view, or the progress-based invoicing that a builder actually manages by.

Construction Builder is a module ECOSIRE designs and writes for exactly that gap. We add a construction job layer on top of project.project — a hierarchical WBS/cost-code tree (models.Model with a parent_id self-relation and stored @api.depends compute fields that roll up budgeted, committed, and actual amounts), a bill-of-quantities model linked to your product catalog, and subcontract records that create and track purchase.order commitments against each cost code. Every labour timesheet, material PO, and subcontractor bill posts to the right analytic account and rolls up the tree, so the over/under-budget number is live, not a month-end surprise. Progress billing is driven by percent-complete or measured quantities and generates draft account.move customer invoices with retention withheld automatically, plus QWeb PDF reports for the payment application, cost-value reconciliation, and subcontract status.

Technically it is a clean, upgrade-safe addon: its own __manifest__.py declaring dependencies on project, account, and purchase; new models and inherited views (XML, with OWL components where an interactive planning board earns it); ir.model.access.csv plus record rules so a site foreman sees only their assigned jobs while a commercial manager sees the whole portfolio; and automated actions/scheduled crons for budget-breach alerts and retention-release reminders. Everything it exposes to project, purchase, and account is reachable over the standard XML-RPC/JSON-RPC API, so your BI tool or field app can read the same live cost picture. We build for your target — Odoo 17.0, 18.0, or 19.0 — and handle the Community vs. Enterprise differences (for example, wiring to Enterprise Accounting and Field Service where you have them, or providing Community-safe equivalents where you do not).

Because this is build-to-order, nothing ships until we agree scope. A short scoping call maps your cost-code structure, billing rules, and approval flows to concrete models and views; we then build on a staging instance, run UAT with your team against your real data, and cut over with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, depending on complexity and integration count. Pricing starts from $349 (indicative, single-company base scope); multi-company consolidation, retention and tax localization depth, extra integrations (field apps, BI, payroll), and the volume of legacy job data to migrate increase the quoted scope. You get the full installable source, a git repo handover, and a support window after go-live.

What you get

Installable source code for the Construction Builder module, pinned to your Odoo version (17.0, 18.0, or 19.0)

Installation and configuration on your instance (or staging first), including cost-code structure, billing rules, and role setup

Technical documentation: data model, field/compute reference, security matrix, and integration/API notes

End-user guide plus a live training session for estimators, site, commercial, and finance roles

Post-go-live support window for defect fixes and questions, with agreed response terms

UAT on a staging instance against your real data, with a documented cutover and rollback plan

Git repository handover with full commit history so you own and can extend the code

Access-control specification (`ir.model.access.csv` + record rules) documented per role for audit

Who this is for

Commercial / QS Manager

Runs cost value reconciliation and needs a live budget-vs-committed-vs-actual view per cost code, subcontract tracking, and variation control — instead of rebuilding it in spreadsheets every month.

Construction Finance Controller

Owns progress billing, retention, and revenue recognition. Needs application-for-payment invoices, retention withheld and released correctly, and job costing that ties back to the general ledger.

Odoo-running Contractor / Ops Director

Already committed to Odoo for accounting and purchasing and wants construction workflows on the same platform, not a second disconnected system, with roles that keep site and head-office data appropriately separated.

Project / Site Manager

Updates percent-complete and progress on live jobs, raises variations, and needs a job-scoped view that shows only their projects and the cost status that affects their decisions on site.

How Construction Builder Compares

Criterion	ECOSIRE	Custom Build	Competitor
Fit to construction workflow	Built around your cost codes, WBS, and billing rules	Whatever you specify, but you drive the design	Generic construction template, may not match your process
Job costing (budget vs committed vs actual)	Live roll-up per cost code from analytics, POs, and bills	Achievable but you build the roll-up logic	Basic budget tracking, often no committed-cost view
Progress billing & retention	Application-for-payment invoices with auto-withheld retention	Must be specified and built from scratch	Varies; retention handling often limited
Subcontract management	Subcontract records with commitments, variations, retention	Possible with dedicated development effort	Sometimes included, depth varies by product
Ownership & source code	Full source plus git repo handover, you own it	You own it, if built in-house or by contractor	Licensed module, upgrades tied to the vendor
Delivery model	Scoped, built, UAT on staging, cutover with rollback	Depends on your internal team or contractor capacity	Instant install, then you configure and adapt
Support & accountability	Post-go-live support window from the team that built it	Whoever built it, if still available	Vendor support per their terms and roadmap
Total cost profile	Fixed quote after scoping, from an indicative base	Often highest, open-ended developer time	Low list price, hidden cost in adapting to your process

Frequently Asked Questions about Construction Builder

Is this an existing app I can download and install today?

No. Construction Builder is build-to-order. ECOSIRE designs, writes, and tests the module against your requirements and your Odoo version — there is no instant download. You request a quotation, we scope it, and we build and install it for you.

How long does delivery take?

Typically 2–4 weeks from confirmed scope. A single-company base configuration is at the shorter end; multi-company consolidation, heavy localization for retention/tax, extra integrations, and large legacy-data migrations push toward the longer end. We give you a firm timeline in the fixed quote after the scoping call.

How does pricing and scoping work?

Pricing starts from $349 as an indicative single-company base figure. It is not a fixed price — after a short scoping call we send a fixed quote based on your cost-code structure, billing rules, integrations, and data-migration volume. The from-price is a starting point, not the final number.

Which Odoo versions and editions do you support?

We build for Odoo 17.0, 18.0, or 19.0 — you tell us your target and we pin to it. We handle Community vs. Enterprise differences: where you run Enterprise we wire into Enterprise Accounting and related apps; where you run Community we provide Community-safe equivalents so the module works either way.

What about support and future Odoo upgrades?

Every build includes a post-go-live support window for defect fixes and questions. Because you receive the full source and git repo, you own the code. Version upgrades (for example moving from 18.0 to 19.0) are handled as a separate scoped engagement, since Odoo core changes between major versions can affect any custom module.

Will it integrate with the rest of our Odoo and outside tools?

Yes. It is a native addon depending on `project`, `account`, and `purchase`, so timesheets, POs, subcontract bills, and progress invoices all flow through standard Odoo documents and analytic accounting. External systems — field apps, BI, payroll — connect over the standard XML-RPC/JSON-RPC API to the same live data.

Do you migrate our existing job and cost data?

We can. Data migration is scoped separately because effort scales with volume and the state of the source data. During scoping we assess your current jobs, budgets, and open commitments and include a migration plan and UAT validation in the quote where you need it.