Make every CRM stage earn its data
Configure which lead and opportunity fields are mandatory per stage or on creation, then guide reps to complete them with a live readiness checklist — before a blocked save ever happens.
The problem
Odoo's native CRM lets a rep drag an opportunity to "Qualified" without ever recording a budget, an expected revenue, or a lead source. Native required fields are all-or-nothing and Studio-based rules need paid Studio access, so managers end up with a pipeline that looks healthy but cannot be forecast against or trusted.
The solution
Configure required fields per stage or on creation, scoped by lead type, sales team and user role. The server blocks the transition when a required field is empty — through the form, imports and the API alike — while a live readiness panel on every lead shows reps exactly what is left before they ever hit a wall.
Everything a data-quality layer needs
Every capability below is implemented in the module.
Per-stage required fields
Pick any number of fields that must be filled before a lead can enter a given stage, or before it can be created at all — no code required.
Leads and opportunities, default and custom stages
Rules apply equally to lead capture and opportunity stage transitions, and to every stage — Odoo's built-in ones and any stage the customer adds later.
Enforced everywhere, not just the form
Missing-field checks run on create and on stage-entry through the form, data imports and the API, so no path around the rule is left open.
Live readiness panel on every lead
A checklist on the form shows what the current stage still needs, plus a preview of the next stage's requirements, so reps self-serve instead of hitting a blocked save.
Contextual "why it's required" help
Every required field carries a short explanation of its business purpose, so reps understand the rule instead of just hitting it.
Scoped by team, role and lead type
Rules can target specific sales teams, user roles or lead types, so an enterprise process and an SMB process can run side by side without conflicting.
Ready-made methodology templates
Apply a reusable requirement bundle, such as BANT, across your stages in one click instead of configuring every stage from scratch.
Bulk configuration across stages
Assign the same fields to several stages at once with a guided wizard, so setting up a full pipeline takes minutes, not an entry per stage.
Export, import and audit log
Move a validated configuration from test to production with the transfer wizard, and every change to a requirement is tracked in the chatter for accountability.
How it works
Configure a rule
Pick a trigger — creation or a specific stage — the fields to require, and any team, role or lead-type scope.
Reps see the checklist
The moment a lead opens, the readiness panel shows what is still missing for the current stage and what the next stage will need.
Server blocks the gap
If a required field is still empty, creation or the stage move is blocked with a message listing exactly what is missing.
Pipeline stays clean
Every deal that reaches a stage carries the data that stage promised, so forecasts and reports can be trusted.
Frequently asked
No sales fog. If your question isn't here, email us and we'll answer it the same way.
Yes. Requirement rules can trigger on lead/opportunity creation or on entering any CRM stage, covering the full pipeline from first capture through every stage transition.
Buy it on the Odoo App Store
Purchase, download and install directly from the official Odoo Apps Store — you'll always get the latest supported build.
CRM Mandatory Fields — Guided Stage Requirements
Per-stage required fields enforced everywhere — form, list and kanban drag — with a live readiness panel, contextual "why it's required" help, team and role scoping, methodology templates and an audit log.
Buy on Odoo App Store