Construction ERP for material procurement: from site requisition to daily consumption

Short answer: NodeDR Construction ERP models the whole material lifecycle on a construction project as one connected workflow: site requisition, approval, purchase order, goods receipt, inventory and daily consumption, tied to milestones and budgets. It is a paid, licensed product from NodeDR Infotech. This article describes the product design and published feature set and does not claim client outcomes or deployment statistics.

What goes wrong with material spend on a construction site?

Spend is usually scattered across spreadsheets and paper, so questions such as how much cement is left on site, or whether an order exceeds its requisition, cannot be answered from the records. Each handover in the chain is a place for the record to be lost.

What is the workflow?

• Requisition: a site engineer requests material.
• Approval and purchase order: the request is approved and becomes an order.
• Goods receipt note: records delivered, accepted and rejected quantities separately.
• Inventory ledger: stock changes only when material is accepted.
• Daily consumption: attributed to work on a project milestone.

That chain lets a project manager investigate a discrepancy from its source. A supplier delivery does not automatically become usable site inventory, and the ledger gets a precise event to record.

Who sees what?

There are eleven project roles, including admin, site engineer, project manager, procurement, store keeper, financial controller and auditor, each seeing only their own modules. Page-level role checks were not enough for this domain, so a data-driven permission matrix sits on top, letting responsibilities change by organisation and site without a code change.

What domain details does it model?

• Materials carry CPWD wastage tolerance bands with a minimum and maximum percentage.
• Vendors record PAN, GSTIN, entity type and a reliability score for compliance tracking.
• A financial dashboard compares spend against budget and tracks retention, with a separate inventory view for stock on hand and restock priority.

How is it secured and built?

TOTP two-factor authentication with backup codes, device session management with remote revocation and an append-only audit log of logins, permission changes and security events. Approval rules live on server-side actions, where a direct request cannot bypass them. The stack is Next.js, PostgreSQL and Prisma, with Redis-backed background jobs for email notifications, packaged for Docker with a one-click install.

What does it cost to operate?

Fine-grained permissions add configuration work, and separate background jobs make notifications more resilient while adding another service to run. The Construction ERP case study lays out those trade-offs, and the NodeDR software page has product details.