A build-to-order ERPNext application that adds BOQ cost estimation, subcontractor and labor management, site material control, and milestone progress billing on top of ERPNext core. ECOSIRE scopes, builds, installs, and supports it for your firm. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $799.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext application that adds BOQ cost estimation, subcontractor and labor management, site material control, and milestone progress billing on top of ERPNext core. ECOSIRE scopes, builds, installs, and supports it for your firm.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Contractors and developers running ERPNext quickly hit a wall: the standard Project and Task DocTypes track internal time and to-dos, but they were never designed for a construction BOQ, a subcontractor work-order chain, retention held against a running bill, or material issued to a specific site store. Teams end up bolting the estimate onto a spreadsheet, tracking subcontractor advances in Journal Entry notes, and reconciling "% complete" by hand at month-end. ERPNext's native Sales Invoice can do milestone billing in the abstract, but it does not understand progress against a BOQ line, cumulative quantity certified this period, or retention release on practical completion — so the numbers never tie back to what was actually built on site.
BOQ DocType with a child `BOQ Item` table carrying item, unit, quantity, rate, and cost-code, feeding project budget and committed-cost roll-ups
Subcontractor Work Order DocType linked to ERPNext `Supplier` and `Project`, with scope-of-work lines, agreed rates, and advance/recovery tracking
Interim Payment Certificate / Progress Bill that certifies cumulative quantity per BOQ line and posts through `Sales Invoice` and `Purchase Invoice` to the real GL
Automatic retention calculation and release, with retention-held aging exposed via scheduler events and reports
Site Material Requisition that draws stock from a project-scoped `Warehouse`, creating `Stock Entry`/`Material Request` against site inventory
`on_submit` / `validate` doc-event guards in `hooks.py` that block over-certification beyond BOQ quantity and prevent double retention release
ECOSIRE builds a proper Frappe app (its own module, installed via bench get-app and bench install-app) that models construction the way your quantity surveyors and site engineers actually work. We add DocTypes for the project BOQ (parent BOQ plus a child BOQ Item table with rate, quantity, and cost-code breakdown), Subcontractor Work Orders linked to your existing Supplier records, Site Material Requisitions that draw from a project-scoped Warehouse, and Progress Bills / Interim Payment Certificates that certify cumulative quantity per BOQ line and compute retention automatically. Everything reuses ERPNext's real accounting engine — a certified progress bill posts through Sales Invoice/Purchase Invoice and hits your GL, so finance keeps one source of truth rather than a parallel shadow ledger.
The logic lives in server-side controllers and hooks.py doc events (validate, on_submit, on_cancel) rather than fragile UI rules, so a work order can't be over-certified beyond its BOQ quantity and retention can't be released twice. Cross-line roll-ups (committed cost vs. certified vs. billed) are exposed through whitelisted methods and the Frappe REST API for your dashboards and any mobile/site app, with scheduler events for period-end reminders and aging on retention. Client scripts drive the site-friendly UX — quick quantity capture, issue/complaint logging with photo attachments, and asset check-in/out — and we wire dedicated role profiles and permissions (Site Engineer, QS, Project Manager, Subcontractor portal) so field staff see only their project's data.
Because this is build-to-order, nothing is a generic download. We start with a scoping call, agree the exact DocTypes, workflows, and reports for your BOQ format and billing terms, then build against your target ERPNext version (Frappe/ERPNext v15 or v16). Typical delivery is 2 to 4 weeks from confirmed scope. You get the installable app source, a UAT pass on a staging bench with a documented rollback, install and configuration on your instance, documentation, a user-guide and training session, and a post-go-live support window — plus the git repository handed over so the code is yours.
Needs the BOQ to be the single source of truth for estimate, committed cost, and certified value, with retention and progress billing that reconcile to the GL instead of a month-end spreadsheet.
Wants fast on-site capture of certified quantities, material requisitions from the site store, and snagging/issue logging with photos — without wrestling ERPNext's full desk on a phone.
Wants subcontractor work orders, advances, and interim payment certificates flowing into ERPNext accounting so cash position, retention held, and supplier liabilities are always current.
Managing multiple site projects and needs portfolio-level roll-ups of budget vs. committed vs. billed, with role-scoped access so each project team sees only its own data.
Buy the license on ecosire.com and download the Construction & Project Site Management app ZIP from your account dashboard.
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Construction & Project Site Management and apply its schema.
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Fit to construction workflow | Built to your BOQ, retention, and certification rules | Fully bespoke but you define everything from zero | Generic construction app, fixed assumptions | |
| BOQ & progress billing | BOQ DocTypes with certified-quantity progress bills to the GL | Possible but you build and test it all | Varies; often shallow or spreadsheet-linked | |
| Retention handling | Auto-calculated and released via doc events, with aging | Must be designed and validated in-house | Sometimes present, rarely to your terms | |
| Accounting integration | Posts through native Sales/Purchase Invoice — one GL | Your responsibility to wire correctly | Usually integrated, depth varies | |
| Delivery model | Build-to-order, 2-4 weeks from confirmed scope | Weeks to months depending on team | Instant install, then heavy configuration | |
| Code ownership | Full git repo and source handed over | You own it (you built it) | Vendor-controlled, often closed or licensed | |
| Version support | Built and tested for Frappe/ERPNext v15/v16 | Depends on your maintenance discipline | Depends on vendor release cadence | |
| Support after launch | Post-go-live support window plus optional retainer | Internal team or none | Vendor support tiers, extra cost |
This is a build-to-order app, not an instant download. After a scoping call to confirm your DocTypes, workflows, BOQ format, and billing terms, typical delivery is 2 to 4 weeks from confirmed scope. Larger or heavily customized scopes are estimated up front before you commit.
Every build includes a post-go-live support window for bug fixes and configuration adjustments. Because we hand over the git repository, your team or ECOSIRE can maintain and extend the app. We also support porting the app forward across Frappe/ERPNext versions (for example v15 to v16) as a follow-on engagement.
We build and test against Frappe/ERPNext v15 and v16. We confirm your exact bench version during scoping and target that version so the app installs cleanly via `bench get-app` and `bench install-app`.
No — it builds on it. Progress bills, subcontractor certificates, and material issues post through ERPNext's real `Sales Invoice`, `Purchase Invoice`, and `Stock Entry` documents so finance keeps one GL. The app adds the construction layer (BOQ, retention, certification) that ERPNext core does not model.
Yes. The BOQ DocType, cost-code structure, retention percentages, and certification logic are configured to your contract terms during the build. The rules are enforced in server-side doc events, so they hold regardless of who enters data.
We deliver client scripts for fast quantity capture and issue logging with photo attachments, and whitelisted REST API methods so your data is available to dashboards or a mobile/site app. Role profiles keep field staff scoped to their own project.
Yes. On completion we hand over the full git repository and the installable app source. The codebase is yours to run, audit, and extend without lock-in.
A build-to-order ERPNext application that adds BOQ cost estimation, subcontractor and labor management, site material control, and milestone progress billing on top of ERPNext core. ECOSIRE scopes, builds, installs, and supports it for your firm.