Most HR teams outgrow generic recruitment the moment their hiring gets real: multi-stage pipelines that differ per department, offer approvals that route through finance and legal, evaluation scorecards that only certain interviewers may see, and hard requirements to prove where every candidate came from. Odoo's core Recruitment app gives you a solid hr.applicant kanban, a stage model, and job positions — but it runs out of road when you need weighted evaluation scorecards, structured interview scheduling tied to interviewer calendars, offer-letter generation with conditional approval chains, or field-level visibility so a hiring manager cannot see another team's salary discussions. Bolting all of this onto the base app with a pile of Studio automations quickly becomes fragile and breaks across version upgrades.

This is a build-to-order module: ECOSIRE designs and builds it around your process, then installs and supports it. Technically, we extend hr.recruitment with new and inherited models.Model classes — for example an evaluation/scorecard model with computed weighted scores via @api.depends, an offer model driven by an explicit state machine (draft → review → approved → sent → accepted/declined), and inherited hr.applicant fields for source attribution and stage-entry timestamps used in time-to-hire reporting. Access is enforced correctly through ir.model.access.csv for CRUD rights plus record rules that scope applicants, scorecards, and offers by recruiter, department, or hiring team, so confidential evaluation and compensation data stays visible only to the right roles.

The user-facing side is real Odoo, not a bolt-on. We build backend views in XML with kanban, list, form, and pivot/graph analysis views, optional OWL components for interactive scorecard or pipeline widgets, and QWeb PDF reports for offer letters and interview packs. Automated actions and scheduled crons handle SLA nudges (stale applicants, pending approvals), and everything is reachable over the XML-RPC/JSON-RPC API so your careers site, job boards, or assessment tools can push candidates in and read status out. Where Enterprise-only features are involved (such as advanced approvals or sign-based offer acceptance) we scope a Community-compatible path or use your existing Enterprise apps — and every module targets Odoo 17.0, 18.0, or 19.0 cleanly, with the manifest, models, and views tested per version rather than a single build hoped to work everywhere.

Delivery is build-to-order: it starts with a scoping call to map your pipeline, roles, approvals, and integrations, after which we send a fixed quote and a written scope. Typical delivery is 2–4 weeks from confirmed scope, depending on complexity — you review the module on a staging database (UAT) before it ever touches production, and we hand over the git repository plus documentation. Pricing starts from $249 (indicative, single-company base scope); multi-company setups, deeper localization, external integrations (job boards, HRIS, assessment platforms), and large candidate-data migrations increase the quoted scope.