Odoo Recruitment: pipeline, stages and applicant tracking for fast-hiring SMEs

What Odoo Recruitment does for an SME

Odoo Recruitment is the applicant-tracking module inside Odoo's HR suite. Official docs describe a preconfigured applicant flow: stages carry specific actions and templated communications so recruiters are not inventing a process from a blank board.

For a small or mid-size business, the pitch is fewer tools. One native app covers the candidate-facing job posting (via Website), the recruiter's Kanban pipeline, automated acknowledgement and interview-scheduling emails, structured interview questionnaires (Surveys), résumé storage (and optional OCR), refuse/archive hygiene, and the hand-off into Odoo Employees when someone is hired—then Time Off, Appraisals, and Payroll sit on the same employee master.

That end-to-end path is what partner and practitioner messaging emphasizes in 2025–2026: recruitment → employees → attendance/time off → payroll on one stack, rather than bolting Greenhouse or Lever onto a separate HRIS and re-keying hires.

• →Native ATS: job positions, applicant Kanban, stage emails, surveys, résumés, refuse reasons, hire hand-off.
• →Default pipeline runs New → Initial Qualification → First Interview → Second Interview → Contract Proposal → Contract Signed.
• →Plays with Website (careers pages), Referrals, Employees, Payroll, and Surveys—same database, no CSV shuttle.

The default Odoo recruitment pipeline and Kanban stages

When an applicant applies for a job position, Odoo automatically creates an applicant card for that specific job. The recruitment team moves the card stage to stage as the person progresses. The default Kanban for a job shows six stages: New, Initial Qualification, First Interview, Second Interview, Contract Proposal, and Contract Signed.

In New, applicants land whether they applied online, arrived via email alias, or were entered manually. Contract Signed is folded by default—folded columns appear gray and hide cards until expanded—so the board stays focused on open work. Stages apply to all job positions unless marked job-specific; additions and deletions therefore affect every position unless you scope them.

Configuring stages, status bars and automated emails

Each Kanban stage shows a color-coded status bar under the stage name: green means ready for the next stage, red means blocked, gray means in progress. Status is set manually on each card via the status circle. Applicants move by drag-and-drop or by clicking the stage on the status bar at the top of the applicant form; every stage change is logged in the chatter.

Automation lives on the Edit Stage form. Stage Name is required. Optional Email Template fires when a card enters the stage. Other options: Folded in Kanban, Hired Stage (drives hire date and the Hired banner), Job Specific (stage only for certain positions), and Show in Referrals with a Points field. Status tooltips (In Progress, Blocked, Ready for Next Stage) are renameable; Requirements holds internal notes for recruiters.

Customize stages to match real hiring steps—phone screen, technical task, culture fit—but keep one clear Hired stage so reporting and Create Employee stay unambiguous. Probability-style stage thinking (how far along is this candidate?) helps managers scan the board without opening every card.

Job positions, email aliases and publishing to the careers site

Hiring starts with a job position: title, department, company (critical in multi-company databases), expected employees, and the people who will interview. Each position can carry an email alias so résumés mailed to that address create applicant cards on that job's pipeline—useful when candidates still apply by email or when you route board applications to a dedicated inbox.

To publish on the company website, enable Online Posting under Recruitment → Configuration → Settings (requires the Website app). Publish individual jobs so they appear on the careers/jobs pages candidates actually visit. Only published jobs are shareable that way; draft positions stay internal for headcount planning.

Odoo also documents posting to external job boards from Settings (for example choosing a board integration such as the Monster recruitment module path in the post-job guide). Treat boards as acquisition channels; keep the Kanban as the single source of truth so LinkedIn, the careers site, and email aliases all land in the same applicant flow.

Referral campaigns and trackable share links sit alongside Website posting: employees promote open roles, points can be tied to stages marked Show in Referrals, and hired referrals still convert through the same Contract Signed → Create Employee path.

• →Job position fields: role design, interviewers, company, email alias for inbound CVs.
• →Online Posting + Website = public careers listings candidates can apply on.
• →Board integrations and referrals feed the same per-job Kanban—do not run parallel trackers.

Preconfigured recruitment email templates

Odoo ships preconfigured recruitment email templates so stage communications are mostly done for you. Recruitment: Applicant Acknowledgement auto-sends in New to confirm receipt. Recruitment: Schedule Interview auto-sends in Initial Qualification when someone passes the first screen. Interest, Not interested anymore, and Refuse cover typical decision paths.

Templates can be created, modified, or deleted. The full composer in the chatter supports attachments and saving a message as a new template. Keep refuse language consistent and professional: high-volume pipelines fail candidate experience when rejection is silent or vague.

• →Applicant Acknowledgement (auto-sent in New)
• →Schedule Interview (auto-sent in Initial Qualification)
• →Interest, Not interested anymore, and Refuse for decision paths

Interviewers, surveys and structured assessments

Assign interviewers on the job position so the people who score candidates are named, not assumed. Schedule interviews from the recruitment flow so activities and calendar context sit on the applicant card rather than in a personal inbox.

Odoo can send a survey to gather more information. Surveys work as exams, questionnaires, tests, or certifications per job—for example a programming quiz for a developer role or an availability questionnaire for a restaurant server.

Enabling Send Interview Survey in Recruitment Settings adds an Interview Survey link that lists every survey in the database (not only recruitment surveys). Saving settings installs the Surveys app if it is missing. Sending a survey requires an email address on the applicant card.

SME pattern: reuse Surveys for skills tests and screening questions instead of buying a separate assessment SaaS. Scores and chatter stay on the candidate record the hiring manager already uses.

Résumés, OCR digitization and SMS

Résumé handling has two layers. Free Résumé Display surfaces the CV on the right of the applicant card in full-screen mode; submitted résumés are stored in Documents and remain accessible from the card.

Résumé Digitization (OCR) is an In-App Purchases (IAP) feature that extracts name, phone, and email into the applicant form. Modes: Do not digitize, Digitize on demand only (Digitize document button), Digitize automatically on submission. Disabling OCR entirely uninstalls the module; Do not digitize keeps it installed but inactive. Credits are purchased via Manage Service & Buy Credits; View My Services shows remaining balances.

SMS to applicants also uses IAP credits from the same management links. The Salary package configurator lets recruiters set an offer-expiration window in days; after that window, an unaccepted offer is no longer available—pair it with Contract Proposal so offers do not linger indefinitely on the board.

Hire action: Contract Signed to employee record

When a candidate accepts, move the card into the Hired stage (default: Contract Signed). That stage should be marked Hired Stage so the card shows the Hired banner and hire-date logic applies. Official offer documentation: once hired, click Create Employee on the applicant form. An employee form opens prefilled from the applicant card and related contract/offer data; complete remaining fields and save into the Employees app.

That handoff is the reason SMEs pick a native ATS over a disconnected recruiter tool. The person who was an applicant becomes the same master record used for onboarding checklists, Time Off allocations, Appraisals, and—when you run Odoo Payroll—contracts, work entries, and payslips. Re-keying name, email, and bank details across systems is where errors and delay accumulate.

Operational checklist after Create Employee: confirm company and department, working schedule, manager, private contact data needed for payroll localization, and any equipment or access tickets. Refuse remaining finalists with reasons so the job's Kanban closes cleanly and source/velocity reports stay honest.

Refuse reasons, talent pool and pipeline hygiene

At any point a candidate can be refused. Odoo's refuse flow prompts for a refuse reason and can send the Recruitment: Refuse email when Send Email is ticked—documented so rejection is deliberate, not a silent archive. Configure refuse reasons that match how you actually filter (skills mismatch, salary, withdrew, overqualified, role closed) so Applicant Analysis and source reporting can answer why people drop out.

Partner guides emphasize cleaning the Kanban: refuse with a reason instead of leaving ghost cards in Second Interview for months. Some databases also support adding candidates to a talent pool when they are strong but not right for this role—keep them reachable without pretending they are still active for the open headcount.

Filters on applications commonly include Unassigned, In Progress, Hired, Ready for Next Stage, Blocked, Archived, and Refused; grouping by Job, Stage, Responsible, Refuse Reason, or Company keeps multi-role weeks manageable. Hygiene is a management habit, not a module toggle.

Applicant data privacy and multi-company hiring

Applicant records hold personal data: CVs, contact details, survey answers, interview notes. Odoo stores them in your database with the same access-control model as other HR apps; it does not replace legal advice. Practical SME controls: limit Recruitment group membership, avoid pasting sensitive notes into unrestricted chatter, put clear consent and privacy language on Website apply forms, and define a retention habit for non-hired candidates (archive after a set period; purge personal fields when your counsel requires it while keeping anonymized funnel stats if needed).

Multi-company databases should set Company on each job position so hiring for entity A does not pollute entity B's pipeline. Careers-site and multi-company job portals have historically been a configuration topic (which companies' jobs appear on which website). Plan record rules and website company mapping during implementation rather than after the first public posting goes live.

If you operate across regions, localize job descriptions and apply-form language, and align refuse/retention practices with the strictest jurisdiction you hire into. The product gives you stages, access rights, and archive tools; the compliance design is still yours.

Recruitment reporting: sources, velocity and team performance

Odoo 19 documents dedicated recruitment reports under Recruitment → Reporting. Source Analysis shows where applicants come from over a period (for example last 365 days), so you can compare careers site, boards, referrals, and email aliases with hire outcomes—not just application volume.

Velocity Analysis measures how long applicants stay in each stage. That is the report that exposes bottlenecks: Initial Qualification sitting for two weeks is a process problem, not a candidate shortage. Applicant Analysis surfaces which jobs attract volume and referrals; Team Performance supports manager coaching when multiple recruiters share the load.

Use reports after stage names stabilize. Renaming stages every quarter breaks trend lines. Pair velocity with refuse-reason grouping: slow stages plus "skills mismatch" refusals point to job-description quality; slow stages plus no refusals point to interviewer capacity.

The Dynamics 365 HR recruitment equivalent

Dynamics 365's recruitment story is split across two experiences, and SMEs evaluating platforms should understand both. Native Dynamics 365 Human Resources recruitment (Recruitment projects) organizes recruiting requests and applicants per legal entity; a single applicant may have multiple applications within the same legal entity or across companies. Strength: hand-off from candidate to employee inside the same HR system, designed to coexist with an external recruiting application—HR enters the request, the external tool sources candidates, referrals return into HR, approval runs there. Candidates can also be managed manually.

The newer HR Recruitment experience is delivered through a Recruiting add-on app (documented as Preview). Per Microsoft's setup documentation, the add-on requires a Dynamics 365 finance and operations environment on version 10.0.40 (10.0.1935.72) or later with the latest quality update, a Dynamics 365 Human Resources license for that environment, system administrator permissions on both Dynamics 365 Human Resources and Power Apps, Microsoft Power Platform integration with Dataverse, and the Finance and Operations Virtual Entity and Microsoft Flow Approvals solutions installed. It is enabled through Feature management ((Preview) Enable recruitment add-on) and the Human resources parameters Recruitment tab; the app is installed from the Power Platform admin center.

The Recruiting add-on includes a Power Pages-based careers site (reactivated from Inactive sites in Power Pages) and cloud flows under HCM recruiting flows and HCM Recruiting solutions—including a Portal create candidate flow that must be active for candidates to create a profile. Connections use Recruiting approvals (Approvals connector) and Recruiting dataverse (Microsoft Dataverse connector).

Compared with Odoo's single-app, Kanban-default, OCR-IAP model, D365 recruitment is more enterprise and modular: more licensing prerequisites, legal-entity and project structure rather than per-position Kanban, heavier add-on install before the candidate portal. Odoo's bundled pipeline is faster for a small team; Dynamics 365 fits organizations already on finance-and-operations that want legal-entity recruitment, formal approvals, and the HR master record.

Frequently asked questions