New: Odoo and Dynamics 365 cost calculators.Estimate your costs

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

Odoo Recruitment is a built-in ATS: six Kanban stages, career-site postings, scored screening surveys, OCR, refuse hygiene and Create Employee into HR.

OdooOdoo Apps8 min readUpdated 29 sources

Key takeaways

  • Native ATS: job positions, applicant Kanban, stage emails, surveys, résumés, refuse reasons, hire hand-off.
  • Job position fields: role design, interviewers, company, email alias for inbound CVs.
  • Applicant Acknowledgement (auto-sent in New)

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 recruitment-to-payroll path is what partner and practitioner messaging emphasizes in 2025 to 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.

Odoo's default recruitment Kanban stages and what each is for
StagePurpose in the pipeline
NewAll applicants land here; Applicant Acknowledgement email auto-sent
Initial QualificationFirst screen; Schedule Interview email auto-sent with calendar context
First InterviewFirst interview round (phone, video, or onsite)
Second InterviewDeeper interview or panel round
Contract ProposalOffer extended; salary package and offer-expiration window
Contract SignedHired stage; Hired banner; basis for Create Employee

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 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 one pipeline of record 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

Interview surveys, scored tests and certifications

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.

Odoo Surveys is the module behind these tests, and for most small teams it only matters inside hiring, eLearning and appraisals. Appraisal surveys follow the same mechanics and are covered in the Odoo HR guide. The next section covers how to build a screening test that scores itself.

Building a scored screening test in Odoo Surveys

A screening test in Odoo is a survey with points attached to the answers. Odoo sums the points into a final score and offers two modes in the Scoring section of the Options tab: "Scoring with answers at the end" shows candidates their answers and highlights the correct one for each question they missed, while "Scoring without answers at the end" shows only the final score. For hiring, the second mode is usually the better pick because the same questions can go to every candidate without leaking the answer key.

Odoo documents eight question types: multiple choice with one answer, multiple choice with several answers, multiple-line text box, single-line text box, numerical value, date, datetime and matrix. Questions can be grouped into sections, and the Randomized per Section option picks a set number of questions from each section for every participant (the default is one per section, and you can change it). That keeps a ten-question test from being identical for each candidate. Free-text answers cannot be auto-scored, so plan on a hiring manager reading those.

To turn a scored survey into a pass or fail gate, enable Is a certification. You then choose a certification email template and set Success %, the percentage of correct answers a participant needs. Participants who meet or exceed it receive the email automatically. Give Badge and Attempts Limit appear only when Login Required is on, which asks participants to sign in. For outside candidates that is a trade-off: a retry cap needs a login, and many firms skip the cap and send each candidate one survey link from the applicant card instead.

  1. Write the questions

    Use single-answer multiple choice and numerical questions for anything you want scored automatically, and add one text question for the candidate to explain their approach. Group them in sections if you want a random draw.

  2. Assign points and pick a scoring mode

    Give each correct answer its points, then choose whether candidates see the answers at the end. Use scoring without answers if you will reuse the test.

  3. Set the pass mark

    Enable Is a certification only if you want an automatic pass email. Set Success % to the score a candidate must reach, for example 70 for a ten-question developer screen.

  4. Send it from the applicant card

    Use the Send Interview Survey action on the applicant. The applicant needs an email address on the card. The result stays linked to the candidate record the hiring manager already reads.

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 accurate.

From applicant to workforce system of record
StepWhere it livesOutcome
Offer / contract proposalRecruitment (Contract Proposal stage)Candidate receives package; expiration window optional
Contract Signed / Hired stageRecruitment KanbanHired banner; hire date context
Create EmployeeApplicant form → EmployeesMaster HR record for onboarding and payroll
Ongoing HRTime Off, Appraisals, PayrollSame employee ID, no second HRIS import

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 rather than a silent archive. Configure refuse reasons that match how you 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 same reporting logic applies to screening tests. From the Surveys dashboard, the See results page shows each question with Responded and Skipped counts, plus a Correct count for scored number and date questions. A single-correct multiple-choice question appears as a pie chart and multi-answer questions as a bar chart, and numeric questions show maximum, minimum and average. When a survey has scoring or certification enabled, a pass or fail filter lets you look at passed or failed candidates only. Clicking the filter icon beside an answer re-slices the whole page for people who gave that answer, which helps when one question looks like it screens out good candidates.

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, so 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.45 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.

Dynamics 365 also has a survey tool, Dynamics 365 Customer Voice, which matters if you plan to run applicant tests or candidate feedback on the Microsoft side. Customer Voice offers eight question types: Choice, Text, Rating, Date, Ranking, Likert, File upload and Net Promoter Score. As of October 2026, Microsoft lists these service limits: 400 surveys per user, 200 questions per survey, 500,000 responses per survey, 4,000 characters per question and per single response, and 200,000 characters of responses per survey. A Likert question counts each statement as a question, so a Likert with two statements counts as three. Customer Voice also blocks surveys that appear to collect passwords or other credentials until an administrator unblocks them from the Message center.

The comparison for hiring is narrow. Odoo gives you scoring, a pass mark and a certification email inside the same database as the applicant. Customer Voice is built for feedback. Its file upload question can collect a résumé, but only when the survey is limited to people in your organization, so it does not suit outside candidates. Microsoft's documentation also does not describe a native pass or fail scoring workflow, so a scored screening test would need extra build work.

How Flectic can help

Flectic implements Odoo for companies of 20 to 100 people in the US and Canada, with recruitment, HR, sales and finance on one database, so a hired applicant becomes an employee record without re-keying. Recruitment goes into the same phased plan as the rest of your Odoo implementation. Flectic sends a written proposal with a fixed price for each phase before work starts. To scope your hiring pipeline, Book a free discovery call.

Sources

  1. Odoo Recruitment uses a preconfigured applicant flow of stages that each applicant moves through, with stage-specific actions and templated emails.

    odoo.comChecked
  2. Applying for a job position automatically creates an applicant card; the team moves the card from stage to stage as the applicant progresses.

    odoo.comChecked
  3. Default Kanban stages are New, Initial Qualification, First Interview, Second Interview, Contract Proposal, Contract Signed; Contract Signed is folded by default.

    odoo.comChecked
  4. Stage color-coded status bar: green = ready to move to next stage, red = blocked, gray = in progress; status set manually on each applicant card via the lower-left circle.

    odoo.comChecked
  5. Edit Stage form fields: Stage Name (required), Email Template, Folded in Kanban, Hired Stage, Job Specific, Show in Referrals with Points, status Tooltips, Requirements notes. Stages apply to all jobs unless job-specific.

    odoo.comChecked
  6. Preconfigured templates: Applicant Acknowledgement (auto-sent in New), Schedule Interview (auto-sent in Initial Qualification), Interest, Not interested anymore, Refuse.

    odoo.comChecked
  7. Enabling Send Interview Survey installs the Surveys application once settings are saved; an Interview Survey link lists all surveys in the database.

    odoo.comChecked
  8. Résumé Display stores all resumes in the Documents application and surfaces the CV on the applicant card in full-screen mode.

    odoo.comChecked
  9. Résumé Digitization (OCR) is an IAP feature with three modes (Do not digitize, Digitize on demand only, Digitize automatically) that extracts name, phone, and email; disabling OCR uninstalls the module while Do not digitize keeps it installed.

    odoo.comChecked
  10. SMS text messaging to applicants is supported from the Recruitment app and requires IAP credits via the Manage Service & Buy Credits link.

    odoo.comChecked
  11. Salary package configurator lets you set an offer-expiration window in days; after that window an unaccepted offer is no longer available.

    odoo.comChecked
  12. Online Posting must be enabled in Recruitment Settings to publish jobs on the company website; the option requires the Website application.

    odoo.comChecked
  13. Job positions can be shared on the company website or on job boards; Settings can open board integration choices (e.g. Monster recruitment integration path).

    odoo.comChecked
  14. Once hired, Create Employee on the applicant form opens an employee record prefilled from the applicant card and contract data; the employee is saved in the Employees app.

    odoo.comChecked
  15. Applicants can be refused at any point; refuse flow supports refuse reason and optional Send Email with Refuse template before confirming Refuse.

    odoo.comChecked
  16. Source Analysis report is available under Recruitment → Reporting → Source Analysis (e.g. Last 365 Days Applicant view).

    odoo.comChecked
  17. Velocity Analysis report shows how long applicants stay in each stage of the recruitment process.

    odoo.comChecked
  18. Odoo product page positions Recruitment as sourcing through contract signature on one platform, with Create Employee / onboarding launch from the app and Website sync for job postings.

    odoo.comChecked
  19. Dynamics 365 HR Recruitment has two experiences: Recruitment projects (default, per legal entity) and HR Recruitment; an applicant may have multiple applications across companies.

    learn.microsoft.comChecked
  20. HR Recruitment is designed to coexist with a separate recruiting application; candidates can also be managed manually.

    learn.microsoft.comChecked
  21. The Recruiting add-on is a preview feature with prerequisites: Dynamics 365 Human Resources environment version 10.0.45 or later, Dynamics 365 Human Resources license, system admin on HR and Power Apps, Power Platform/Dataverse, Finance and Operations Virtual Entity and Microsoft Flow Approvals solutions.

    learn.microsoft.comChecked
  22. Recruiting add-on enabled via (Preview) Enable recruitment add-on in Feature management and Human resources parameters Recruitment tab; app installed from Power Platform admin center; Power Pages careers site; HCM recruiting flows including Portal create candidate; Approvals + Dataverse connectors.

    learn.microsoft.comChecked
  23. Partner positioning (2026): Odoo HR as one platform for recruitment, attendance, payroll, leave, and employee records, unified stack vs fragmented HR tools.

    x.comChecked
  24. Partner positioning (2026): manage recruitment, attendance, payroll, leave, expenses, performance, and employee records from one Odoo HR platform.

    x.comChecked
  25. Odoo Surveys scoring: two modes (Scoring with answers at the end, Scoring without answers at the end); Is a certification enables a certification email template and Success %; Give Badge and Attempts Limit appear only when Login Required is enabled.

    odoo.comChecked
  26. Odoo Surveys has eight question types (multiple choice one answer, multiple choice multiple answers, multiple lines text box, single line text box, numerical value, date, datetime, matrix); Randomized per Section picks questions at random per participant, defaulting to one per section.

    odoo.comChecked
  27. Survey results show Responded and Skipped counts, pie graphs for a single correct answer and bar graphs otherwise, Maximum, Minimum and Average for numeric questions, a pass or fail filter for scored surveys, and answer-level filters.

    odoo.comChecked
  28. Customer Voice limits: 400 surveys per user, 200 questions per survey, 500,000 responses per survey, 4,000 characters per question and per single response, 200,000 characters per survey response; Likert statements count as questions; phishing prevention blocks surveys until an administrator unblocks them in the Message center.

    learn.microsoft.comChecked
  29. Customer Voice question types: Choice, Text, Rating, Date, Ranking, Likert, File upload and Net Promoter Score.

    learn.microsoft.comChecked

Frequently asked questions

What are the default Odoo recruitment stages?

Odoo Recruitment's default Kanban shows six stages: New, Initial Qualification, First Interview, Second Interview, Contract Proposal, and Contract Signed. Each stage can carry its own automated email template. Stages can be job-specific or marked as the Hired stage. Contract Signed is folded by default, shows the Hired banner when configured as hired, and is the usual trigger point before Create Employee.

Is Odoo Recruitment a full ATS?

Yes for most SME use cases: job positions, website careers posting, email-alias intake, per-job Kanban pipeline, stage emails, interview activities, Surveys-based assessments, résumé storage with optional IAP OCR, refuse reasons, referrals, source/velocity reporting, and Create Employee into the same HR database. High-volume enterprise teams that need deep agency portals or complex multi-brand career sites may still pair Odoo with specialist tools, but many mid-market firms replace a standalone ATS entirely.

How do I publish jobs on the company website?

Install/enable the Website app, turn on Online Posting in Recruitment → Configuration → Settings, configure the job position, then publish it so it appears on careers/jobs pages. Only published jobs are publicly apply-able that way. You can also set an email alias on the job so CVs sent to that address create applicants on the same pipeline.

How do you turn a hired applicant into an employee?

Move the applicant to the Hired stage (default Contract Signed), then use Create Employee on the applicant form. Odoo opens an employee record prefilled from the applicant (and related offer/contract data). Complete the remaining HR fields and save. The person is now managed in Employees and can receive Time Off, appraisals, and payroll contracts without a second import.

Does Odoo Recruitment include résumé parsing or OCR?

Yes, as an In-App Purchases (IAP) feature called Résumé Digitization. It extracts name, phone, and email from the résumé into the applicant form. Modes: Do not digitize, Digitize on demand only, Digitize automatically. IAP credits are purchased via Manage Service & Buy Credits, which is the same place SMS credits are managed. Free Résumé Display still shows the full CV without OCR.

How should we refuse candidates without wrecking the pipeline?

Use the Refuse action with a clear refuse reason and send the Refuse email template when appropriate. Standardize reasons (skills mismatch, salary, withdrew, role filled) so reporting stays useful. Archive or talent-pool strong-but-not-now candidates instead of leaving cards frozen mid-stage. Silent rejection damages employer brand and pollutes velocity metrics.

What about GDPR and applicant personal data?

Treat applicant records as personal data under your privacy program: limit who has Recruitment access, document purpose on apply forms, set retention for non-hired candidates, and purge or anonymize when required by counsel. Odoo provides access rights, archive, and form tools; compliance design (consent wording, retention periods, multi-country rules) is an implementation and legal matter, not a single checkbox.

How does Odoo Recruitment compare to Dynamics 365 HR recruitment?

Odoo is a single native app with a default per-position Kanban and bundled IAP résumé OCR/SMS, strong for SMEs wanting recruitment tied to HR in one install. Dynamics 365 Human Resources organizes hiring per legal entity via recruitment projects and often coexists with an external ATS; the separate Recruiting add-on (Preview, version 10.0.45+ prerequisites, Power Pages careers site, Dataverse flows) is heavier to stand up. Flectic implements both and can map fit.

Can Odoo score a candidate screening test?

Yes. Odoo Surveys assigns points to answers and sums them into a final score. You choose whether candidates see the correct answers at the end or only their score. Enabling Is a certification adds a Success % pass mark and an automatic email to candidates who reach it.

What question types does Odoo Surveys support?

Odoo lists eight: multiple choice with one answer, multiple choice with several answers, multiple-line text box, single-line text box, numerical value, date, datetime and matrix. Sections can pick questions at random for each participant. Free-text answers need a person to read them, since only choice, numeric and date answers carry a correct value.

More on the blog: Choosing an ERP or CRM