Odoo Recruitment: Pipelines, Offers, and Hiring Analytics

Introduction

Odoo Recruitment centralizes employee data, time off, recruitment, and HR documents so managers and HR work from one file per person instead of parallel folders and tools.

People processes affect every department, yet leave balances, contracts, and hiring status are often unclear until someone escalates a problem.

The Recruitment apps connect HR events to the org chart, approvals, and, where relevant, payroll or expense flows, giving leadership a live view of headcount and availability.

HR business partners, office managers, and executives planning workforce changes will find practical patterns to compare with their current setup.

Recruitment is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Recruitment: Pipelines, Offers, and Hiring Analytics states the storyline for stakeholders approving budgets while.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Recruitment.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Recruitment is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

HR sends a leave approval by email. Payroll finds out late. The manager on site has no idea who is available Tuesday. Everyone trusts HR, but the data is always one step behind reality.

HR processes touch every employee, yet leave, recruitment, and contracts often sit in separate tools. Managers lack a single place to approve requests and see team availability.

Sound familiar? Teams usually hit these walls:

• Leave balances disputed because requests live in email
• Recruitment status unclear across hiring managers
• Contracts signed without a central employee file

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Recruitment, and measure what changes.

Top 10 Recruitment Use Cases

10 use cases for Odoo Recruitment, ranked from Level 1 (easy, do it this afternoon) to Level 10 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Publish your first job opening on a website careers page Level 1 — Easy

Level 1 is the simplest possible Recruitment action: one HR user, one role, one shareable page. No automation, no scoring, just a job ad on your website that drops every applicant into one kanban.

Here's how you'd do it in Odoo:

1. Install the Recruitment app, then go to Recruitment, Configuration, Job Positions, New, and fill in title, department, employment type and number of seats.
2. Open the Description tab and write the role impact, responsibilities and requirements in short H2 sections instead of one long paragraph.
3. Click Publish on Website; Odoo automatically generates the public careers page with the apply form already wired to your kanban.
4. Share the careers URL on LinkedIn, Indeed and your social channels so every candidate lands on the same form.
5. New applications appear in Recruitment, Applications, in the first kanban stage, ready for the team to review the same day.

What you get: Applications stop scattering across three inboxes and a personal Drive; every candidate lives in one searchable kanban from day one.

2. Build a measurable kanban pipeline with stages, probabilities and lost reasons Level 2 — Easy

Level 2 still uses one HR user, but the kanban becomes the hiring pipeline view. Stages, probabilities and lost reasons turn ad hoc hiring into a managed funnel.

Here's how you'd do it in Odoo:

1. Go to Recruitment, Configuration, Stages and create Initial Qualification, Phone Screen, Onsite Interview, Final Round, Offer and Hired.
2. Open each stage and set a Probability % (10, 30, 50, 70, 90, 100) so the pipeline shows where every candidate really stands.
3. From Recruitment, My Pipeline, drag candidate cards from one stage to the next as interviews progress through the week.
4. When a candidate drops out, click Refuse and pick a Refusal Reason (Skills mismatch, Salary, Withdrew) so the kanban stays clean.
5. Open Recruitment, Reporting, Recruitment Analysis and group by Stage to see time-in-stage per role and spot the bottleneck.

What you get: Hiring becomes a visible funnel for the whole team; managers see in seconds which roles are blocked and where candidates drop.

3. Capture inbound CVs automatically with a dedicated email alias per role Level 3 — Easy

Level 3 introduces a Recruitment-specific automation: a unique inbound email alias per job position. Resumes that arrive by email become candidate cards with zero copy-paste.

Here's how you'd do it in Odoo:

1. Open a Job Position form, scroll to the Recruitment tab and set the Email Alias to jobs-engineer or jobs-sales on your catch-all domain.
2. Verify the inbound mail server in Settings, Technical, Email, Incoming Mail Servers so the alias really receives external mail.
3. A candidate emails the alias from any client; Odoo creates a candidate card, attaches the CV and stores the email body in the chatter.
4. Repeat the alias on every job position so each role has its own inbox and the kanban never mixes roles together.
5. From any candidate, click Reply to keep the entire conversation in the chatter; nothing slips into someone's personal inbox.

What you get: Inbound resumes flow into the right kanban with zero manual entry; HR stops being a forwarding service for hiring managers.

4. Shortlist candidates fast with the Skills matrix and required criteria Level 4 — Medium

Level 4 activates the Skills feature, the Recruitment lever to stop reading every CV in full. Required skills become filters and qualified candidates surface in one click.

Here's how you'd do it in Odoo:

1. Go to Recruitment, Configuration, Skill Types and define your skills (Python, Outbound Sales, German, ISO Audit) with levels Beginner, Intermediate, Expert.
2. On each Job Position, open the Skills tab and tag must-have and nice-to-have skills with the minimum required level.
3. On every new candidate, open the Skills tab and fill in the levels declared in the CV or confirmed in the screening call.
4. From Recruitment, My Pipeline, click Filters, Skills, and only candidates meeting the required skills for the role stay visible.
5. Save a custom kanban filter Match Score per role so screening starts every morning from the strongest profiles first.

What you get: Screening time drops from hours to minutes; hiring managers see a short list of real matches instead of a fat folder of CVs.

5. Standardize screening with a reusable scored interview survey Level 5 — Medium

Level 5 wires Recruitment to the Survey app. The same screening questions, scoring grid and shareable link go to every candidate for a given role.

Here's how you'd do it in Odoo:

1. Open Survey, New, give it a title (Engineer Phone Screen), set the type to Recruitment and add scored questions with weights per answer.
2. Back in Recruitment, open the Job Position and link the survey in the Interview Form field on the Recruitment tab.
3. On any candidate card, click Send Interview, choose the survey, and Odoo emails a personal link with a clear deadline.
4. The candidate fills the survey from any device; answers and auto-computed score appear on the candidate form and chatter.
5. From Recruitment, Reporting, Survey Scores, filter by job and rank candidates by score before the panel meets in person.

What you get: Every candidate is evaluated on the same grid; interview decisions are documented and defensible instead of based on gut feeling.

6. Let candidates self-book interviews from a shared Appointments link Level 6 — Medium

Level 6 connects Recruitment to the Appointments app. Instead of three back-and-forth emails to find a slot, candidates self-book directly in the panel's real calendar.

Here's how you'd do it in Odoo:

1. Open Appointments, New, create a schedule type Phone Screen 45 min with the right resources (HR, hiring manager) and their working hours.
2. Set the buffer time, the visible window (next ten working days) and the form fields (Name, Email, LinkedIn URL).
3. Copy the public Appointments URL and paste it in the email template Phone Screen Invite stored on the Job Position record.
4. On every candidate moved to Phone Screen, click Send Booking Link; the candidate picks a slot and the event lands in Calendar.
5. The booked event is auto-linked to the candidate card; reschedules and reminders fire with zero HR intervention afterwards.

What you get: Time-to-first-interview drops from a week of email tag to under 24 hours; HR reclaims a half-day per open role per week.

7. Refuse with a reason, send a template, then build a re-usable talent pool Level 7 — Hard

Level 7 turns rejection into a long-term asset. Refusal reasons feed reporting, an email template protects the brand, and Talent Pool tags create a re-engagement layer.

Here's how you'd do it in Odoo:

1. Open Recruitment, Configuration, Refusal Reasons and create Skills mismatch, Salary expectations, Withdrew, Filled internally and Strong but no fit now.
2. Go to Configuration, Email Templates, write one polite template per reason and link each template to its reason record.
3. On any candidate to decline, click Refuse, pick the reason; the email sends automatically and the chatter records both the reason and the message.
4. On Strong but no fit now candidates, add the tag Talent Pool and archive them so the kanban stays focused on active roles.
5. When a similar role opens, filter Recruitment, All Applications by tag Talent Pool, unarchive the best fits and re-engage with a personal note.
6. Open Reporting, Recruitment Analysis, group by Refusal Reason to fix the funnel where candidates drop most often per quarter.

What you get: Employer brand stays clean even for declined candidates; past pipeline becomes a half-priced source for the next similar opening.

8. Send the offer letter via Sign and create the Employee on Hire Level 8 — Hard

Level 8 connects Recruitment to Sign and Employees. The offer-to-hire transition becomes a one-click flow with legal signature and an active employee record at the end.

Here's how you'd do it in Odoo:

1. Install Sign, then go to Sign, Templates, upload the offer letter PDF and place fields for Name, Salary, Start Date, plus candidate and HR signatures.
2. On the candidate moved to Offer, click Send Offer, pick the Sign template; Odoo pre-fills the fields from the candidate record automatically.
3. The candidate signs first on any device, HR counter-signs second; reminders fire after 48 hours of silence without manual nudging.
4. Once fully signed, click Hire on the candidate; Odoo creates an Employee record with the right department, manager and contract type.
5. On the new Employee, the standard Onboarding project is auto-generated with tasks (laptop, accounts, induction) assigned to the right owners.

What you get: Time from yes to legally hired drops from one to two weeks down to a single afternoon, with the signed PDF archived for the entire employment.

9. Track sources, UTM and cost-per-hire in a live Spreadsheet TA dashboard Level 9 — Hard

Level 9 turns Recruitment into a measurable channel mix. Source tags, UTM capture and a Spreadsheet dashboard expose which channels actually produce hires versus which only burn budget.

Here's how you'd do it in Odoo:

1. In Recruitment, Configuration, Sources, create LinkedIn, Indeed, Website, Referral and Headhunter, then tag every new candidate with the right one.
2. On Website apply forms, capture utm_source, utm_medium and utm_campaign into hidden fields so paid campaigns map to real candidates.
3. Use Studio Automation: when a referral candidate is hired, schedule an activity on HR to pay the internal referral bonus on time.
4. Open Spreadsheet, New from Recruitment Pivot, build the TA Dashboard with Applications per Source, Conversion per Stage and Cost-per-Hire.
5. Pull monthly spend per channel from Accounting, divide by hires per channel and pin the best and worst CPH on the first sheet.
6. Schedule a monthly hiring review that reads only from this dashboard; budget then shifts to the channels that actually convert.

What you get: Recruitment marketing stops being a feeling and becomes a budget line with a number; cost-per-hire drops 20 to 40 percent within two quarters.

Wiring UTM capture, source attribution, referral automations and the Spreadsheet TA dashboard across Recruitment, Website and Accounting is exactly the kind of cross-app build Dasolo runs as a partner-led engagement.

10. Run a multi-language, GDPR-compliant talent OS with AI screening and live analytics Level 10 — Expert

Level 10 is the full operating system: AI screens incoming CVs, automations enforce GDPR retention, the careers site speaks every market language, and a real-time dashboard links hiring to business outcomes.

Here's how you'd do it in Odoo:

1. Enable AI screening on Recruitment so every new candidate is parsed, scored against the Job Position skills, with a justification posted in the chatter.
2. Publish Website, Careers in several languages with localized job descriptions, explicit GDPR consent on the apply form and a clear retention notice.
3. Studio Automation: 24 months after the last activity on a non-hired candidate, archive the record and purge personal data while keeping anonymized funnel stats.
4. On qualified candidates, trigger an outbound flow: Appointments link for the screen, Marketing Automation drip in the candidate language, Helpdesk ticket if anything stalls.
5. Build a Spreadsheet Talent OS dashboard combining hiring funnel, time-to-fill, source ROI, diversity targets and a link to Payroll cost forecasting.
6. Run a quarterly governance ritual: review AI accuracy on hires versus rejections, refresh GDPR retention rules and rebalance source spend based on the live numbers.
7. Promote the best repeating procedures (offer templates, screening surveys, onboarding checklist) into the Knowledge workspace so they survive every team change.

What you get: Talent acquisition runs as a measurable, compliant, multi-channel platform; recruiters focus on closing and human judgment while the system handles paperwork and reporting.

Designing AI screening prompts, GDPR retention automations, multi-language careers content and the live Spreadsheet Talent OS end-to-end is the architecture Dasolo assembles as a partner-led engagement, so most teams skip the multi-quarter trial-and-error phase.

When Expert Help Makes Sense

If levels 1 to 6 fit your world, you can often succeed with standard Odoo Recruitment, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 7 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Recruitment includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo