Real Estate Units
Off-plan unit inventory, milestone payment plans, and the overdue drawdowns behind them.
The short answer
Real Estate Units is an Odoo application for property developers and off-plan sales teams. It holds development projects, buildings and individual units, shows each building as a stacking-plan grid coloured by availability, and attaches a milestone payment plan to every reservation so the amounts derive from the unit price. Its cockpit leads on overdue drawdowns in money, not as a collection ratio.
Last updated
What it is for
Selling off-plan inverts the usual order. The buyer pays as the building rises, so the money for the next stage has to arrive before the stage is built. Miss an instalment and you have not lost a receivable, you have lost the funding for a floor. A generic CRM will tell you the deal closed. It will not tell you the site is short, and it will not tell you which drawdown is the one holding up the concrete.
- Platform
- Odoo
- Category
- Assets & rentals
- Works with
- Odoo 18 · Odoo 19
- Technical name
construction_realestate_units- Status
- Direct from webbox
- Pricing
- Paid
What is inside it
- 01
The drawdown
Receivables opens filtered to unpaid with the overdue rows picked out, each carrying the buyer, the milestone it belongs to, the due date and a Mark Paid action.
- 02
Payment plans
A reservation carries milestones, each a percentage of the unit price. Amounts are derived rather than typed twice, so repricing a unit cannot leave a plan that no longer adds up.
- 03
The stacking plan
Every building draws its units by floor, coloured available, reserved, sold or blocked from the records themselves. Each status has a legend key, and clicking a unit opens it.
- 04
Inventory boards
Sell-through and presale are reported apart, with sales velocity as units sold over the last thirty days. Every tile drills through to the rows it counted.
What it looks like in practice
-
The finishing drawdown is past due and the floor above it is unfunded
A unit has its Booking, Foundation and Structure milestones paid. The Finishing milestone fell due twenty-one days ago and is still open.
Receivables lists that row in red under the buyer and the milestone it belongs to, and the cockpit adds it into overdue instalments stated in money. Because overdue depends on today, the tile expresses the condition against the stored due date and paid flag rather than an unstored compute, so the drill-through opens the same rows it counted.
- Overdue on the demo book
- $166,000
- This drawdown
- $120,000
- Days past its due date
- twenty-one
Figures from the module's own demo data, on a fresh install. Install with demo data and open Real Estate, then the cockpit and Receivables.
The drawdownPayment plans
-
A plan is derived from the price so no amount is typed twice
A reservation is confirmed on a unit and needs a schedule the contract can be checked against.
Milestones are generated as percentages of the unit price: Booking at 10, Foundation at 20, Structure at 20, Finishing at 20, Handover at 30. The footer totals what is paid, what is overdue and how much of the price is collected, so a plan that stops adding up shows on the record.
- Paid on the demo plan
- $300,000
- Overdue on it
- $120,000
Figures from the module's own demo data, on a fresh install. Install with demo data, open a reservation and read its payment plan footer.
Payment plansThe drawdown
-
A lender asks for presale, not sell-through
The same book of units has to answer two different questions on the same board.
Sell-through counts only what is sold. Presale counts sold plus reserved, which is the figure asked for before the next tranche is released. Inventory analysis then splits the book by status, by unit type and by building.
- Sell-through
- 42.9%
- Presale
- 64.3%
Figures from the module's own demo data, on a fresh install. Install with demo data and open the inventory board.
Inventory boardsThe stacking plan
What it deliberately does not do
- No invoicing or accounting.
- An instalment is marked paid on the plan and the collections figures move. Nothing reaches the ledger: no journal entry, no tax, no payment reconciliation.
- No construction management.
- Milestones are payment stages, not site tasks. There is no schedule, no contractor, no bill of quantities and no progress claim.
- No mortgage or escrow handling.
- Buyer financing, lender approvals and regulated escrow accounts are out of scope, which matters in jurisdictions that require them.
- No contract or statement generation.
- The plan is data. No sale agreement, allocation letter or statement of account is produced as a document.
- The stacking plan is a grid.
- Units sit on a floor in sequence. No CAD import, and irregular floors are not modelled.
Questions
Can I install this on Odoo Online?
Will it invoice the buyer and post the payments to accounting?
Does the stacking plan import our architectural drawings?
Who can see what, and does it hold up across companies?
Have something to build?
Tell us the problem. We'll come back with a plan, a price, and who'd actually build it.
- Free scoping call
- Reply within 1 business day
- No lock-in