Real-estate teams that run Odoo usually end up stitching property operations across Sales, Contacts, and Accounting, then filling the gaps with spreadsheets. Out of the box, Odoo has no concept of a rentable/sellable unit with its own status lifecycle, no lease contract that generates recurring rent with escalation, and no single view that shows which units are available, reserved, sold, or occupied. Deposit handling, renewal reminders, and per-unit profitability all live in someone's head or a parallel sheet — which breaks the moment two agents touch the same building. This is exactly where native Odoo runs out of road: it can invoice and hold contacts, but it cannot model a property portfolio or the sale-versus-rent workflows that sit on top of it.

ECOSIRE builds a dedicated property module that introduces first-class records for your portfolio. We add models such as property.property (the physical asset), property.unit (the individually sellable/rentable space with a state machine of available → reserved → sold/occupied → returned), and property.lease for rental agreements, alongside a sale flow that reserves a unit and drives it to a confirmed sale. Each model uses proper fields.Many2one/One2many relations to res.partner, product.template, and account.move, with @api.depends computes for figures like occupancy rate, next-due rent, outstanding deposit, and lease days remaining. Rent is generated as recurring account.move invoices via a scheduled ir.cron job that reads each active lease's period, escalation clause, and billing day — so month-end is a review, not a re-key.

The build is genuinely Odoo-native, not a bolt-on. Access is governed by ir.model.access.csv plus record rules that scope a leasing agent to their own assigned units while managers see the whole portfolio; multi-company record rules keep separate legal entities clean. The UI ships as list, kanban (unit status board), form, and calendar/gantt views in XML/OWL, with a portfolio dashboard, and QWeb PDF templates for lease agreements, rent statements, and sales reservation letters. Automated actions handle renewal and payment-due reminders, and everything is reachable over the external XML-RPC/JSON-RPC API so a website or CRM can push enquiries and pull availability. We target your exact Odoo line — 17.0, 18.0, or 19.0 — and respect Community versus Enterprise boundaries (for example, we won't assume the Enterprise rental or accounting-full features are present unless your edition has them, and we build the equivalent where it doesn't).

Because this is build-to-order, nothing is downloaded and switched on blindly. We start with a short scoping call, confirm the data model and workflows against how your team actually leases and sells, then build on a staging database, run UAT with your users, and cut over with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full installable source for your version and a git repo handover, so you are never locked to us. Pricing starts from $999 (indicative, single-company base scope); multi-company portfolios, deeper accounting/localization integration, external-website availability sync, and migrating large volumes of existing units and historical leases increase the quoted scope.